Autonix AI SolutionsChat on WhatsApp
Lead-response system

What the System Actually Does, Measured.

Autonix has no client case studies yet, because it is new. What it has is a test programme — run against deliberately difficult enquiries, with the failures published alongside the wins.

Everything on this page measures the lead-response system. Website projects are scoped and discussed separately, on the Websites page.

Read this first Everything on this page comes from simulated enquiries — test businesses we built, messaged by real people who were briefed to be awkward on purpose. This is not live customer data and no number here describes a real client’s results. When a pilot client produces real numbers, those will be published separately and clearly labelled as such.
Method

How the Benchmark Is Run

A single friendly test proves nothing. The programme is designed so that the numbers mean something even when they are unflattering.

Three test businesses
The same scenario set runs against a home-services firm, a clinic, and a coaching practice — so the results show whether it generalises, not just whether it works once.
100+ enquiries per run
Enough volume that a single lucky or unlucky conversation doesn’t move the percentage. Testers are briefed to be difficult, not cooperative.
Failures induced on purpose
The calendar and CRM are deliberately broken mid-run, to test whether the lead is preserved and the team alerted — not just whether the happy path works.
What gets measured

Every Number We Publish

Including the two that most vendors would quietly leave out.

Metric Why it matters Run 01
Median first-response time The core promise, at the typical case. Pending
90th-percentile first-response time The honest number — what your slowest tenth of customers actually experience. Pending
Booked with no human involvement The headline outcome. Pending
Escalated to a human, split by reason Escalation is a feature. Correct escalation is a win, and the split proves the rules fire as designed. Pending
Escalated when it shouldn’t have been A real failure mode — wasted team time. Pending
Handled when it should have escalated The dangerous failure mode. Published prominently, because it is the one that costs you a customer. Pending
Correctly said “I don’t know” Proves it declines rather than inventing an answer. Pending
Booking accuracy Right slot, right calendar, no double-booking. Where automation usually breaks. Pending
CRM record completeness Backs the “every lead tracked” claim with a number. Pending
Recovery success on an induced failure When we break the calendar on purpose: was the lead preserved and the team alerted? Pending
Run 01 is being prepared
Results will be published here in full, including every failure, and dated.
RUN 01 · [DATE TBC]
Scenario mix

What the Testers Are Told to Try

The easy cases are included so the numbers stay representative. The highlighted ones are where systems like this usually fall over.

Straightforward booking Reschedule an existing appointment Cancel an appointment Ask about services and process Out-of-hours enquiry Price negotiation — must escalate Question outside approved info — must decline Angry or unhappy prospect — must escalate Explicitly asks for a human One-word and ambiguous messages Three messages sent in a row Deliberately broken calendar mid-conversation
Publishing rules

How We Report It

  • 01Methodology is stated before any number, every time — including sample size, who the testers were, and what they were told.
  • 02Failure rates get the same prominence as success rates. If a number is bad, it appears at full size, not in a footnote.
  • 03Every run is dated and versioned. Old runs stay published, so improvement is visible and nothing is quietly deleted.
  • 04Simulated data is labelled simulated, on the page and in the page’s structured data. It is never presented as a client result.
  • 05No review or rating markup until real, attributable client reviews exist.
Coming later

Client Case Studies

Nothing here yet — on purpose.
Real case studies need a real client with a real business outcome. The 30-day pilot is how the first one gets written. Until then, the benchmark above is the honest version of proof, and this space stays empty.

Want to Be the First Real Number on This Page?

The 30-day pilot runs on your real enquiries, heavily discounted, in exchange for an honest testimonial — good or bad — once it has been live long enough to mean something.