When an AI receptionist transfers a call to a person
An AI receptionist handles many calls on its own. It books visits, answers common questions and sends confirmations. Some calls still need a person. The question is how to decide which calls go to your team.
This guide explains the calls that need a human, how to set transfer rules and what to check after launch.
Calls that need a person
Some calls carry risk. A caller can describe a symptom that needs a nurse or provider. A caller can report a bad reaction after a treatment. A caller can describe a situation that feels urgent.
Other calls need judgment. A caller can ask for a custom price. A caller can ask for an exception to your policy. A caller can be upset and ask to speak with someone.
Write this list for your clinic. Keep it short. Put it where your team can read it.
Calls the agent can handle alone
Many calls need no person. A new patient asks about a service. A current patient moves a visit. A caller asks for the clinic hours. An agent can answer these calls, check the schedule and book the visit.
Clear answers on these calls save staff time. They also keep callers moving toward a visit.
Set the transfer rule
A transfer rule tells the agent when to pass a call. Write the rule in plain words. For example, the rule can say that any symptom question goes to a person.
Decide what happens when no person is free. Some clinics take a message with a callback promise. Others send the call to a backup number. Write the choice in the rule so the agent follows it.
Set the message rule
A message rule tells the agent what details to collect. Name, phone number, the service of interest and the best time to call back are the usual details. Add any field your team needs to act on the message.
A message with full details saves a callback. It also reduces the chance that the caller must repeat the story.
Tell the caller what happens next
A caller who is transferred or left a message wants to know what happens next. The agent must state the next step in plain words. It must say who will call back and when.
Keep the promise. A callback promise that does not happen erodes trust in the clinic. Track each message until the callback is done.
Avoid the wrong handoff
A wrong handoff sends a caller to the wrong person. A billing question sent to a clinical nurse wastes time. A clinical question sent to a billing clerk frustrates the caller.
Test each type of handoff. Make a test call for each rule. Confirm that the call reaches the right person or the right message list.
Review handoffs each week
Look at the calls that went to a person. Count how many were urgent and how many were routine. Look for calls that must have stayed with the agent.
Look at the calls that the agent kept. Check whether any caller needed a person and did not get one. Adjust the rules based on what you find.
Test the handoff at different hours
Test each transfer rule during busy hours and quiet hours. A rule that works at noon can fail at closing time, when fewer staff are on the desk. Record each test and fix any rule that fails.
Name the person who receives the transfer during each shift. Post the list where the team can see it.
A worked example
This example is hypothetical. A clinic gives the agent one rule. Every call that mentions a symptom goes to a nurse, with a message if no nurse is free. Every other new visit request is booked by the agent.
After two weeks, the clinic reviews the transfers. Most symptom calls reached a nurse or a message. The new visit calls were booked in the schedule. The team adds one more rule for billing questions, which go to the front desk the next business morning.
Kepler Voice sets up the handoff rules for your clinic and runs the agent around them. Ivy books visits, answers common questions and passes calls that need a person. To hear how Ivy handles a live call, talk to Ivy at (669) 337-5915.