How it works
A small team of agents, a foreman checking the work, and you in charge.
Each agent has one job. A foreman checks the work and asks a person before anything risky, and bigger setups have more than one foreman. Tap a role to see its job and its guardrail.
Customers
calls, texts, web
every request
asks you, gets your rules
You or your office
approve what matters
the foreman hands work to
every agent works from
Your shop playbook and your existing tools
price book, service area, on-call rules, tone · field-service app, phones, texts, accounting
Role
Foreman
Reads every request first, hands it to the right specialist, checks the result against your playbook.
Guardrail
Asks a person before refunds, discounts, emergencies, or anything the playbook doesn't cover.
Replays
Four real-world nights and mornings, step by step
Simulated replays based on real call patterns. Pause, step through, or hide the reasoning.
2:14 a.m., AC out
HVAC · Tampa · simulated replay based on real call patterns
- Press play to watch the crew work this call.
The build
Live in about four weeks
Week 1
Listen and map
We shadow your calls, map your systems, and collect your price book, service area and on-call rules. Text-number registration starts now, because carriers take 2–4 weeks.
Week 2
Write the playbook, build
Your rules go into a written playbook you approve. We build the agents in test mode, connected read-only to your field-service app and other systems.
Week 3
Test
You and your office place scripted test calls. We fix what you find, then switch on bookings and other changes with your OK. The crew goes live for after-hours calls only.
Week 4
Live and tune
The crew takes overflow during the day too. You approve decisions from your portal. Months 2–3 are weekly tuning.
The Lab follows the same shape over 6–8 weeks, going live one workflow at a time. Custom builds go live in phases, on a timeline we agree with you.
Your software stays
The crew plugs into the systems you already run, through their APIs: field-service software such as ServiceTitan, Housecall Pro, Jobber or FieldEdge, QuickBooks for accounting, your phones and texting, and your calendars and CRM. We map them in week 1, the crew starts read-only, and bookings, updates and invoices are switched on only with your OK. We connect where a vendor offers an API; we aren't an official partner of any of them. More on how we connect.
What always needs a person
The crew does the routine. People decide what costs money.
- Emergency dispatch and after-hours fees go to your on-call tech.
- Discounts, refunds and prices outside your price book go to the owner.
- Anything the playbook doesn't cover goes to one of our engineers, then to you.
You approve from your portal, a text or an email. Every decision is written down. Clients who need a signed audit trail can add one, built with AFA Protocol.
Every month
How we manage your crew
- An evaluation agent reviews every conversation daily against your playbook and flags misses.
- An engineer aims to fix each flag within one business day, and logs it.
- You get a plain monthly report: calls answered, jobs booked, hours saved, mistakes found, fixes made, usage against your cap.
Plain words
Glossary
- AI agent
- Software that reads a request, decides what to do, and uses your tools to do it, like a new hire who follows your playbook.
- Crew
- A small team of AI agents built for one shop, each with one job.
- Foreman
- The agent that hands out work, checks it, and asks a person before anything risky.
- Playbook
- Your shop's rules in writing: price book, service area, on-call rules, tone of voice.
- Guardrail
- A rule the crew can't break, such as no discounts without the owner.
- Approval
- A decision the crew sends to a person: you, your on-call tech, or us.
- Usage cap
- The voice minutes and texts included in your monthly price.
- Reasoning trace
- The written record of what an agent thought, which tools it used, and what it decided.
- Field-service app
- The software you already run jobs in, such as ServiceTitan, Housecall Pro or Jobber.
- Escalation
- When a call or task needs a person and the crew hands it over.
- Hours saved
- Office time the crew takes on: calls, follow-ups and reschedules, counted each month.
- Audit trail
- A signed record of every gated action, showing who allowed it and when.