60% of Field Service Software Vendors Name an AI Company

60% of the five field service software products name an AI company in their own robots.txt. That 60% is 3 of 5 named products — Jobber, Housecall Pro, and Simpro — not a rate for field service software as a market. 0 of 5 block any AI company. All 5 returned a readable file on September 1, 2026, so vendors unreadable is 0.

The other two products on the shelf, ServiceTitan and Workiz, leave all 11 crawler names unmentioned. Unmentioned is not allowed. A dispatcher asking an assistant how to wire Jobber to the rest of the shop is in a different published-request world from a dispatcher whose vendor never named GPTBot at all.

A robots.txt file is a plain-text request about crawling, not a licence and not an API policy. The 30-product census that contains this shelf is the series page.

60% of the five field service products name an AI company.

Thirty named vertical business-software products, five in each of six industries (Insurance agency software; Accounting and tax software; Healthcare practice software; Legal practice software; Property and construction software; Field service software), asked one question each: what does the robots.txt you publish say about 11 named AI crawlers from 6 AI companies.

The cohort is US Tech Automations’ own named list, written out in the builder, and is not a ranking, a sample, or anything derived from another publisher’s data.

Thirty named companies are not an industry. Nothing here is representative of insurance software, accounting software, or the web, and no figure may be presented as a rate for anything wider than these thirty. A vendor that never names an AI company has NOT allowed it — unmentioned is its own answer and must never be reported as allowed.

A vendor whose address returned an HTML page instead of a plain-text file has not answered at all; it is unknown, never open. robots.txt is a request about crawling, not a licence and not permission to use content, and a vendor blocking a crawler is not evidence about its API, its integrations, or its product. This edition is one reading on one day; a change between editions is a change in what the vendor published, not proof of intent.

0 of 5 field service products block any AI company.

Key Takeaways

• 5 of 5 field service products published a readable robots.txt.

• 3 of 5 name an AI company — 60% of the five.

• 0 of 5 block any of the 11 crawler names.

• 2 of 5 name none: ServiceTitan and Workiz, unmentioned 11.

• Jobber, Housecall Pro, and Simpro each allowed 8 names.

• Jobber redirected to https://www.getjobber.com/robots.txt and still answered.

Frequently Asked Questions

Q: How would a field-service operator act on a vendor that never names a crawler?
A: Treat ServiceTitan and Workiz as unpublished on the 11 tokens. Do not tell a dispatcher that those files “allow ChatGPT.” Unmentioned 11 is silence. Re-read those two addresses whenever the vendor ships a help-center or marketing-site change.

Q: Is 60% of field service software an industry rate?
A: No. 60% is 3 of 5 named products: Jobber, Housecall Pro, and Simpro. Five products are not an industry. Keep “of the five” in the sentence with 60%. The figure is for these names on September 1, 2026.

Q: Do any of these five block GPTBot, ClaudeBot, or Google-Extended?
A: Vendors blocking any AI is 0 of 5. Jobber, Housecall Pro, and Simpro each blocked 0, allowed 8, and left 3 unmentioned. ServiceTitan and Workiz each blocked 0, allowed 0, and left 11 unmentioned. A zero block count is not a permission grant for the unmentioned tokens.

Q: Why does Jobber’s row mention a redirect?
A: The published address at getjobber.com redirected to https://www.getjobber.com/robots.txt. The destination still published a readable robots.txt, so Jobber is in the 5 that answered, not in an unknown bucket. A redirect to a real file is not unreadable.

Q: What should a dispatcher do with allowed 8 on Jobber, Housecall Pro, and Simpro?
A: Those three files named AI companies without a site-wide shutoff on 8 tokens and left 3 unmentioned. That is a crawl request, not an integration, not a marketplace listing, and not a price. Watch for the first Disallow: / on a shelf that currently has 0 blockers.

Q: How does this shelf sit next to the 30-company cohort?
A: Across the 30-company cohort, 26 vendors answered and 21 of those 26 named no AI company — 80.8% of the 26, cohort of 30. This shelf does not match that silence: 3 of its 5 name crawlers. That contrast is still five products, not a market.

The Five Field Service Products

Blocked means a named group with Disallow: /. Allowed means a named group without that shutoff. Unmentioned means the file never used that token. The 11 names asked are GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, Claude-SearchBot, Google-Extended, PerplexityBot, Perplexity-User, CCBot, and Applebot-Extended, from 6 AI companies.

Closed-to-everyone on every row is no. None of these five shuts the whole site with a wildcard Disallow: /.

3 of 5 field service products — Jobber, Housecall Pro, Simpro — each allowed 8 crawler names.

ServiceTitan and Workiz each left 11 crawler names unmentioned; that is not permission.

The matching allowed-8 rows are not proof the three vendors copied a policy, and not proof they agree. They are three published files that happened to score the same way on September 1, 2026. A later edition would be a new reading.

A 60% Naming Share Among Six Shelves

Among the 6 industries in the 30-company cohort, this is the naming shelf. 60% of the five is the only naming share on the comparison that is not 0% or 40%. Accounting and tax software is the other shelf that names crawlers, at 40% of its five, and it is also the shelf whose five include a blocker. This field service software shelf’s blocker count is 0 of 5.

The accounting and tax software cut is the natural comparison: it names crawlers and it also blocks. The property and construction software cut is the thin-file contrast: 3 of 5 answered, 2 unreadable, 0 naming. A contractor who runs both a field-service product and a construction product should not assume the two files match.

3 of 5 field service products name an AI company; 2 of 5 name none.

How the Field Service Files Were Read

Read from each vendor’s own published robots.txt on September 1, 2026 as USTA-DataResearch. Jobber’s fetch followed the published redirect and still received a readable file. Method notes live on the research index. Figures on this page are copied from the sealed snapshot; nothing is estimated, modeled, or extrapolated.

Thirty named vertical business-software products, five in each of six industries (Insurance agency software; Accounting and tax software; Healthcare practice software; Legal practice software; Property and construction software; Field service software), asked one question each: what does the robots.txt you publish say about 11 named AI crawlers from 6 AI companies. The cohort is US Tech Automations’ own named list, written out in the builder, and is not a ranking, a sample, or anything derived from another publisher’s data.

Thirty named companies are not an industry. Nothing here is representative of insurance software, accounting software, or the web, and no figure may be presented as a rate for anything wider than these thirty. A vendor that never names an AI company has NOT allowed it — unmentioned is its own answer and must never be reported as allowed.

A vendor whose address returned an HTML page instead of a plain-text file has not answered at all; it is unknown, never open. robots.txt is a request about crawling, not a licence and not permission to use content, and a vendor blocking a crawler is not evidence about its API, its integrations, or its product. This edition is one reading on one day; a change between editions is a change in what the vendor published, not proof of intent.

A related construction-adjacent crawler audit on a different cohort is the Construction sites crawler audit. Do not blend that denominator with these five products.

1. List the five. ServiceTitan, Jobber, Housecall Pro, Workiz, Simpro — the field service software row in the builder.

2. Read each file. Follow a published redirect when the file is still plain text, as with Jobber. Score blocked, allowed, or unmentioned for 11 tokens from 6 AI companies.

3. Keep of-the-five on the share. Publish 3 of 5, 0 of 5, 2 of 5, and 60% of the five. Do not promote 60% into a market rate.

Put AI-Access Data to Work

A field-service operations manager or dispatcher whose shop runs ServiceTitan, Jobber, Housecall Pro, Workiz, or Simpro should put those five hosts on a weekly robots.txt watch. The trigger is the first Disallow: / on a shelf that currently has 0 of 5 blocking, or a move in Jobber, Housecall Pro, or Simpro off allowed 8 / unmentioned 3.

A home-services marketing lead trying to get “how do I connect Jobber to our CRM” answers out of an assistant should treat Jobber, Housecall Pro, and Simpro as the three files that already name crawlers, and should treat ServiceTitan and Workiz as currently silent on all 11 tokens — then re-check those two the day a vendor ships new help articles.

A retrieval-pipeline engineer wiring work-order and dispatch data should record this shelf’s blocker count of 0 of 5 as the baseline and alert the moment that baseline moves, rather than assuming field-service SaaS will stay unnamed or unblocked.

US Tech Automations automates those re-reads and routes a file change into an agentic workflow. The company homepage is the public door.

Source: US Tech Automations Research — computed from the sealed vendor AI-access snapshot, September 1, 2026.