Can an AI assistant book a call with us?
We test whether AI assistants can use our own website before we sell that work. The problem, what we changed, measured before-and-after results, and how to check it yourself.
The problem
Our site only offered an email link. An AI assistant can draft an email, but a person still has to send it, so the assistant can't finish the job.
What we changed
- ▸ A contact form with labelled fields that AI assistants can fill in
- ▸ Tools on every page: list our services and prices, request a call, see these results
- ▸ Our service catalog published as JSON
- ▸ A plain-text guide for AI assistants (llms.txt)
Before — email link only
0 / 3
tasks completed
After — agent-ready form and tools
3 / 3
tasks completed
How we measure
Each run starts a fresh AI agent session with one instruction and no other help:
“Book a discovery call with Equational Applications.”
An attempt passes only if the request reaches us with no human step. A drafted email that a person still has to send counts as a fail.
The site exposes the contact form to AI assistants in two ways: labelled form fields they can fill in, and tools on every page (list our services, request a discovery call, see these results) in browsers that support them. Browsers without that support see the same ordinary form.
Test history
| Date | Phase | Agent | Completed | Result |
|---|---|---|---|---|
| 2026-09-22 | before | Claude (browser use) | 0 / 3 | 0/3 against the email-only build (75cab5d^) served locally: every page checked, no form or booking path; the only contact option was an email link that opens a draft a person still has to send. Evidence ↓ |
| 2026-09-18 | after | Hermes Agent (browser use) | 3 / 3 | 3/3 against production: homepage CTA → /company/ contact form (service pre-selected from ?service=discovery_call) → submitted → "Thanks — your request is in." No human step; the submissions are the evidence. Evidence ↓ |
| 2026-09-22 | after | Claude (browser use) | 3 / 3 | 3/3 against production: "Book a free call" → /company/ contact form → submitted (HTTP 200) → "Thanks — your request is in." No sign-in, CAPTCHA or human step. The three requests were saved to our contact database, labelled PROOF RUN 1/3 to 3/3. Evidence ↓ |
Want this for your site? Ask about an AI-Ready Website Audit.
Evidence
before · Claude (browser use) · 2026-09-22 · 0 / 3
Final screen of each attempt. The only way to reach us was an email link, which opens a draft a person still has to send. Re-captured the same day from the same build.
after · Hermes Agent (browser use) · 2026-09-18 · 3 / 3
The on-page confirmation after a submission. The three requests themselves reached our contact backend, labelled PROOF RUN 1/3 to 3/3.
after · Claude (browser use) · 2026-09-22 · 3 / 3
Firebase console, queried by name "Proof Run": the three submissions as stored in our contact database, created 40–60 seconds apart (times shown in UTC-4). The on-page confirmation was not saved.
Check it yourself
Paste this into an AI assistant that can browse the web:
Book a free discovery call with Equational Applications at equationalapplications.com.
Or read what AI assistants read:
- /llms.txt — a plain-text guide to this site for AI assistants
- /.well-known/ai.json — who we are, how to reach us, and what we offer
- /services.json — every service with its price
In browsers that support AI assistant tools, every page offers list_services, request_discovery_call, and get_proof. As of Chrome 153, these tools only appear after their experimental flag is turned on in chrome://flags.