Field Notes
How Does a Chiropractic Group Run 12 AI Voice Agents?
Back to Mind runs twelve AI voice agents by giving each one a single job. The South Florida chiropractic group, which treats personal injury patients across several offices, has a bilingual agent that answers and routes callers, and separate agents for appointment confirmations, billing calls, and medical-records follow-up. Calls, texts, WhatsApp, and faxes all feed one intake flow, and staff run it from one dashboard.
This is a field note on how that system is built, drawn from the Back to Mind case study.
Why does one practice need twelve AI voice agents?
Because personal injury chiropractic is several businesses sharing one phone number. Every case brings calls from the patient, from the patient's attorney, and about insurance and personal injury protection (PIP) benefits, in English and in Spanish. Each of those calls needs different information and ends in a different place.
One agent trying to handle all of it would need a script long enough to fail in surprising ways. Twelve agents with one job each is the same idea as hiring a digital employee for each role: a narrow job description, clear rules, and a defined handoff.
What do the agents do?
The case study names the main roles:
| Agent | Job |
|---|---|
| Bilingual intake and routing | Answers calls in English or Spanish, captures intake, and routes each caller to the right office or team |
| Appointment confirmations | Calls patients to confirm upcoming visits |
| Billing calls | Makes outbound billing calls |
| Medical-records follow-up | Follows up on medical records requests |
Splitting the jobs keeps each script short enough to test on its own.
How do calls, texts, WhatsApp, and faxes become one intake?
By converting everything into the same intake record. People reach the practice in different ways, so the system takes intake from WhatsApp, text messages, and faxes, which are read with OCR, alongside phone calls and an AI messenger agent in GoHighLevel. Whatever the channel, the result lands in the same flow, so staff do not keep four inboxes. Connecting agents to a practice's own records system is a separate question, covered in whether an AI receptionist can book into your EHR.
What does the operations team still own?
The work that needs judgment. A production dashboard runs RAPID verification through aCom Health, the PIP reductions workflow, and medical-records packets, and it monitors all twelve voice agents. Attorney records requests and PIP reductions are tracked workflows that staff work from that dashboard, not tasks the agents finish on their own.
The newest piece follows the same rule. An email triage assistant, now launching, sorts incoming email and drafts replies, and a person approves every message before it is sent. That is the human-in-the-loop handoff built into the design from the start.
How much work do the agents handle?
A lot of phone time. Across seven invoiced months, from September 2024 to June 2025, the agents logged more than 34,000 AI voice minutes, which is more than 560 hours of calls. In each invoiced month, usage ran between 2,994 and 7,110 minutes. The system has been in production since 2024 and is still being extended in 2026.
What makes a dozen agents manageable?
Three choices visible in the build:
- One job per agent. Narrow scripts are easier to test, and a change to billing calls cannot break intake.
- One intake record for every channel. Staff see a single flow, whatever the patient used to reach out.
- One dashboard for monitoring. Every agent is visible in the same place as the work staff do.
That combination is what front desk operations at Cream Digital is built around.
Key facts
- Back to Mind runs 12 AI voice agents in production, monitored from one dashboard.Source: creamdigital.ai/case-studies/back-to-mind
- The group's AI voice agents logged over 34,000 minutes across seven invoiced months, September 2024 to June 2025, and between 2,994 and 7,110 minutes in each invoiced month.Source: creamdigital.ai/case-studies/back-to-mind
- Calls, texts, WhatsApp messages, and faxes read with OCR feed a single intake flow.Source: creamdigital.ai/case-studies/back-to-mind
Frequently asked questions
Why use twelve agents instead of one?
Because each job has different rules, scripts, and handoffs. A confirmation call, a billing call, and an attorney asking for records need different information and different endings. Separate agents keep each script short and testable, and a problem in one does not affect the others.
Do the agents speak Spanish?
Yes. Back to Mind's intake and routing agent answers in English or Spanish, captures intake, and sends each caller to the right office or team.
What happens to a call the agents cannot handle?
It goes to a person. The intake agent routes callers to the right office or team, and the operations team works the cases that need judgment, such as PIP reductions and records requests, from one dashboard.