Use cases
AI voice employee for inbound calls
Tobiloba Odejinmi · 30 Jan 2026 · 6 min · 1,209 words
Direct answer
An inbound voice employee picks up, asks the questions you already ask, and books a slot or routes the call. Good looks like a calendar event and a note the next person can use. Escalate money, medical, legal, and any caller who asks for a human. Do not start with clinical advice or collections on the phone. Measure booked appointments, transfer rate, and whether the caller had to repeat themselves.
- The job is greet, qualify, book, or route. It is not a phone therapist.
- Handoffs must carry the answers already given. Repeating is a miss.
- Money, medical, and legal stay behind a hard gate.
- Measure bookings that stick and transfer quality, not talk time.
What should an inbound voice employee actually do?
Pick up. Ask the questions your front desk already asks. Book the slot or route the call. Write the note. That is the whole job. If you cannot list the questions, you are not ready for a voice employee. You are ready for a script workshop.
The employee has to live in the calendar and the CRM or EHR you already use. A phone that talks but cannot write an appointment is a toy. I will not ship a toy into a clinic queue. At 10mg the providers need systems that open on Monday. A ghost booking is downtime with extra steps.
Voice makes people expect a person. That is fine. Be honest in the first sentence. “This is the booking line. I can take details or put you through.” Callers handle that. They do not handle a fake receptionist who cannot say when a human will call back.
What does a good inbound call look like?
The caller says why they rang. The employee collects name, reason, and the fields you need to book. It offers real slots. It confirms the time. It writes the same time into the system. The next person can open the record and not ask the first three questions again.
Good also sounds like a short call. No jokes. No “happy to help you today” loop. If the intent is “I need Tuesday after 3”, the path is Tuesday after 3. If there is no slot, say so and offer the next one or a transfer.
Record the reason for every transfer. “Caller asked for a person” is valid. “Could not match a slot” is valid. “Did not understand” is valid and should make you fix the script. Hide those reasons and you will argue about the model instead of the path.
- Slots offered are slots that exist
- Booking written before the call ends
- Transfer includes the answers already given
- First sentence says what this line can do
When do you hand the call to a person?
When the caller asks. When the intent is clinical, legal, or money. When the caller is angry or scared. When the employee has missed the same question twice. Those are gates, not suggestions. Voice is a bad place to bluff.
The handoff is a state, not a recording dump. The person who picks up should hear or see the name, the reason, and what was already tried. If the caller has to start over, you made the wait worse. I treat that as a product bug, not a “voice limitation”.
Aim for a transfer rate you can explain by intent. Booking a flu shot follow-up should rarely transfer. A side-effect scare should transfer immediately. A 10–15% escalate target is a useful overall number once the simple intents work. Watch the tails.
What should you not put on a voice agent first?
Do not start with diagnosis, medication changes, or “is this covered” when coverage is a judgment. Do not start with collections. Do not start with a line that can cancel a procedure. Those need a person and a record you can defend.
Skip the open-ended “how can I make your day better” prompt. You want a short menu of intents you already handle. Open-ended voice is how you get a ten-minute story and no booking.
Do not replace the on-call clinician with a night voice. Take a message, book the morning slot, or wake a person if the protocol says wake a person. Pretending you have coverage you do not have is how you get a headline.
How do you measure inbound voice without lying?
Bookings that still exist the next morning. Wrong-day bookings. Transfers that arrive with a complete note. A weekly sample where you listen for the caller repeating a name or a date. Those are the numbers. Containment alone will hide the misses.
Do not chase a lower handle time. You can win that number by hanging up politely. Do not chase a higher containment if the callback queue explodes. The point is booked work and fewer repeats, not a prettier voice dashboard.
When a booking is wrong, write why. Wrong slot inventory. Wrong timezone. Caller said Thursday and the system heard Tuesday. That list is the work. If you cannot explain a miss, turn the intent off until you can.
How do you keep the caller from repeating themselves?
That is the whole design problem. Capture the answers as fields, not as a story. Pass those fields into the booking and into the transfer. If your helpdesk and your phone system do not share a record, fix that before you buy a voice model. The model will not glue two systems you refused to glue.
I use the same test I used for bank integrations. If the next person cannot see the state before lunch, you still have work to do. Callers are less patient than banks.
After hours, write the note as if the morning desk will read it at 8:01 with a line at the door. Time, reason, callback number, what the caller was told. If that note is sloppy, you did not save a night shift. You made a morning mess.
Questions people ask
What should the voice employee do on a live call?
Identify the reason, collect the fields you already collect, and either book a slot or transfer. It should confirm the time out loud and write the same time in the system. If it cannot write the booking, it should not take the call.
When do you transfer?
When the caller asks for a person, when the intent is money, medical, or legal, when the caller is distressed, or when the employee has failed twice to understand. Transfer with the answers already given. A cold transfer is a failure.
Can it take payments on the phone?
Not as a first job. Payments are a hard gate. If you later take a card, use a proper pay path and a person who can see a failure. Do not let a model invent a paid-in-full.
What about after hours?
Booking and message-taking work at night. Clinical advice and money do not. If the next open slot is Tuesday, say Tuesday. Do not pretend a clinician is in the building if they are not.
How do we measure it?
Appointments booked that still exist the next day. Share of calls that transfer with a complete note. Caller repeat-yourself rate on a sample. Average handle time is a trap. A short call that booked the wrong day is a miss.
Written by
Tobiloba Odejinmi
Head of Engineering at 10mg Health. I have run engineering at Zeeh Africa and sold Insurpass and Shopl. I still write the code. If you have one process that still runs on people copying things, we can look at it in thirty minutes.
