An agent that works
while you don’t

01 · Watch a call

Ninety-four seconds,start to booked.

A real call pattern, played out. Watch what it reads, what it says, and the exact moment it stops and waits for a person.

02 · Anatomy

Four parts.All of them yours to inspect.

Nothing here is a black box. Each layer can be swapped, hosted on your own infrastructure, or handed over entirely.

1. The brain

   Judgement that does not freeze

   Scripts break the moment a caller says something unexpected.

   The reasoning layer reads the situation, works out what is missing, and chooses the next step — not a rigid menu tree. It can rephrase, ask a clarifying question, or escalate when the request is outside the map.

   Runs on our infrastructure, or entirely on yours.

2. What it knows

   Your business, loaded in

   Generic chatbots invent prices and policies.

   Prices, hours, service areas, warranties, who qualifies for what — answers come from your records. Every reply can be traced back to the document or field it came from, so you can audit what it said.

   Yours: nothing leaves your systems unless you say so.

3. What it can reach

   Calendar, CRM, messaging — with limits

   An agent that cannot book or follow up is just a talking FAQ.

   Each connection is a separate tool with its own permission: read the diary without emptying it, draft a text without blasting your list, log a lead without editing closed jobs.

   Added one at a time. Each with its own limits.

4. What stops it

   The part that makes it safe to sell

   Autopilot without brakes is a liability, not a product.

   Reads run freely. Anything that changes the schedule, moves money, or leaves the building stops and waits for a person. What a caller says is treated as information — never as instruction to rewrite the rules.

   Non-negotiable: every write is gated.

03 · What it does

Work that used towait for you

Not a chatbot demo. An agent wired into how a real business runs — phone, calendar, follow-up, records — with brakes on anything that can hurt you.

• Answer when you cannot

  After hours, lunch rush, or mid-job — the line still gets a human-sounding answer, not voicemail that never gets returned.

• Book and reschedule

  Pull open slots from your calendar, confirm the visit, send the reminder. Edge cases (double-book, VIP override) wait for you.

• Qualify before you talk

  Service area, budget band, urgency, job type — the warm leads get to you; the tire-kickers get a polite path off the phone.

• Follow up without nagging

  Estimate sent but no reply? Quote aging? The agent runs the sequence you approve — SMS, email, or voice — and stops when a human takes over.

• Answer from your docs

  Policies, menus, warranties, FAQs — grounded in what you actually publish, with a trail back to the source.

• Write to the CRM, carefully

  Notes, tags, and new contacts land where your team already works. Destructive actions stay behind a human gate.

04 · A day in the life

While you stayon the tools

Roofing, clinics, shops, services — same pattern. Volume handled. Exceptions escalate. You keep the relationship.

1. 7:12 AM

   Missed call

   You are already on a roof. The agent picks up, confirms the address is in-zone, and offers two windows this week.

2. 7:14 AM

   Booked

   Slot locked on your calendar. Confirmation text goes out. You get a one-line brief: who, what, when, how they found you.

3. 11:40 AM

   Exception

   Caller wants a price you do not list. Agent explains the process and flags you — no invented number, no dead air.

4. End of day

   You kept the work

   Three jobs booked you would have missed. Zero policy freelancing. You close the loop on the one exception in two minutes.

05 · Trust

Safe enough toput on the line

The sell is not “AI magic.” It is controlled autonomy — speed where it is safe, a human where it is not.

• Human in the loop

  Writes that matter wait. You approve exceptions from your phone.

• Voice is information

  A caller cannot talk the agent into changing its rules or emptying the calendar.

• Audit trail

  What was said, what tool ran, what source answered — available when you need it.

24/7

the line is covered — nights, weekends, mid-jobno voicemail, no missed lead

94s

from missed call to booked job in the demo aboveowner never picked up the phone

0

writes executed without a human gateby design, not by policy

06 · Before you ask

The four questionseverybody has

What if it says something wrong?

It answers from your records — your prices, your hours, your policies — and when the answer is not in them it says so and flags you instead of guessing. The clinic call in the demo above is exactly this: asked about a payment plan it has no document for, it refuses to invent one.

Does it work with the calendar I already use?

Each connection is its own tool with its own permission, added one at a time. Reading your diary and writing to it are separate powers — it can be given the first without the second. If you tell us what you run on, we will tell you plainly whether it connects before you pay anything.

Where does my data go?

It can run entirely on your own infrastructure — that is the point of the four layers being separable. Nothing leaves your systems unless you say so, and every answer it gives can be traced back to the record it came from.

What stops a caller talking it into something?

What a caller says is treated as information, never as instruction. Anything that changes the schedule, moves money, or leaves the building stops and waits for a person — so the worst a bad-faith caller gets is a polite answer and a flag on your phone.