AI dispatcher: answer, sort, send.

The numbered dispatch workflow, start to finish

1. The phone rings and Ansio answers, day or night, in a natural voice. No "please hold," no hours sign on the door at 11pm.

2. It figures out who is calling and what they need. It pulls up the caller if they have phoned before, then asks the plain questions a good front desk would: what is happening, what is the address, is there water or power or heat involved, and how to get in.

3. It triages: urgent or routine. Using the rules you set, it decides whether this is a same-night emergency or a job that can sit on the schedule. (More on how that judgment works below.)

4a. If it is routine, it books it. Ansio reads your live availability on your own Google, Outlook, or Square calendar before it confirms anything, so it never double-books your morning. The customer gets a real slot, not a callback promise.

4b. If it is an emergency, it dispatches. Ansio texts your on-call tech the whole picture: the address, the issue in plain words, how to get in, and a live ETA so the tech knows what they are walking into. Then it does the part a voicemail never could: it keeps trying. It calls and texts again until someone actually acknowledges the job, instead of leaving an urgent call sitting in an inbox.

5. It closes the loop with the customer. Once a tech has the job, Ansio texts the customer the ETA so they are not pacing by the window wondering if anyone is coming.

6. It logs everything. The call is recorded and transcribed, and the whole dispatch (who called, what was decided, who got the job, when they acknowledged) is written down so you can check the morning after, settle any "nobody told me" argument, and tune the rules.

What counts as an emergency, and how the AI tells

This is the question every trades owner asks, and fairly so. A dispatcher that treats a dripping faucet like a flooded basement will burn out your on-call rotation in a week.

You set the line, in plain language, for your trade. For a plumber that might be: active water you cannot shut off, a sewage backup, or no water to the whole house counts as tonight; a slow drain or a running toilet can wait for the schedule. For HVAC in February, no heat with a baby or an elderly person in the house is urgent; a noisy fan is not. For an electrician, a burning smell or sparking panel goes straight to the on-call tech; a dead outlet in the garage does not.

Ansio does not guess from a single word. It asks the follow-ups that sort a true emergency from an anxious caller: can you shut the water off, is the breaker tripping, is anyone unsafe, is the heat fully out or just weak. Then it matches the answers against your rules and routes accordingly. When it is genuinely on the fence, it leans toward getting a person involved rather than letting a real emergency cool off in a message queue. You stay in control of where that line sits, and you can move it any time the rules are not matching how your shop actually runs.

Why "keep retrying" is the part that earns its keep

The difference between an answering service and an AI dispatcher is what happens after the message is taken. An answering service hands you a note. A dispatcher makes sure the right person actually received the job.

When Ansio sends an emergency to your on-call tech, it does not assume the text landed. Phones get left in trucks. People are asleep. So it retries by both call and text until someone acknowledges, the way a sharp dispatcher keeps the late-night job in front of a real person until it sticks. That single behavior is the reason an after-hours emergency turns into a booked, paid job instead of a missed call the customer rings your competitor about ten minutes later.

And it works alongside your team, not around them. Your techs are still the ones who fix the pipe and earn the trust. Ansio just makes sure the call gets answered, the right facts get to the right person, and nothing urgent slips through while everyone is busy on the tools.