AI voice fallback is the path you save for the moment no routing rule matches and the profile cannot help. The choices are a polite decline, which is the default, a transfer to a queue, voicemail, or hang up immediately. Decline can use a custom message. Transfer needs a destination queue. Pick one before the first live call and write it on the campaign card. Do not leave the default in place by accident if you meant a transfer, and do not pick hang up because a test call annoyed you. A confused caller is still a person who reached your agency. The fallback is how you exit without guessing a product, a price, or an enrollment.
Fallback choices on the profile
Choose an AI voice fallback before the number is public
Open the call-behavior settings and read the fallback line out loud. Polite decline is the default, and it is the right default for a campaign that should not bridge an unknown request. Write the decline sentence in plain language: say you cannot help with that request, and stop. Do not add a product name as a consolation. Transfer to a queue is the right fallback when a human should sort the residue, and only if that queue is staffed and licensed for the states you accept. Voicemail fits a message you want on the record when nobody should take the bridge live. Hang up immediately is the sharp tool. Use it for abuse or for a line that must not continue, not for an older caller who paused.
The product describes this control as what happens when no routing rule matches and the agent cannot help. That is a different moment from a clean not-qualified result. Not qualified means your rules fired and the caller is outside the campaign. Fallback means you do not know what they wanted. Treat the transcripts differently. A rise in not-qualified is a rule question. A rise in fallback is a greeting, a question, or an audio-path question. Do not 'fix' fallback volume by widening the qualified rule until everyone transfers. You will fill the licensed queue with people you cannot place. Set the incomplete and timeout outcome to the same exit so silence and confusion do not take two different ad-lib paths.
Say what the decline must not do. It must not quote, bind, recommend, or start an application. It must not ask for a Social Security number, a Medicare number, or a medication list in order to 'figure it out.' If the call may contain health details, keep the fallback short and follow the privacy process you already use. A long fallback interview is how a front door becomes an unlicensed needs analysis. One sentence, then the action. If you need a fact such as office hours, that belongs in a tool result you trust, not in a guess spoken on the way out. The caller should be able to repeat what happened: you could not help, and you either ended, transferred, or took a message.
Transfer, voicemail, and hang up are different exits
Transfer as fallback is a burden on the floor. Tell those agents the AI did not understand, so their first question is the sort, not a sales opener. Give them the transcript, including the failed turns, so they do not pretend the screen is a clean qualification. If fallback transfers crowd out true qualified bridges, the AI is no longer saving time. Switch the fallback to decline or voicemail and fix the question card. A transfer destination that is a phone number or SIP URI, rather than your licensed queue, is a different decision and should not be the silent default for 'I did not understand.' Send unclear calls to your own floor or to a message, not to an outside closer.
Voicemail as fallback stores a message instead of forcing a live rescue. Use it when the campaign can return the call inside your calling rules, not when you are hoping a recording replaces a sale. The message the AI speaks before voicemail should say what you need recorded: name, number, and the reason for the call. It should not ask for medical detail. Hang up immediately ends the audio with no cushion. Callers experience that as a drop. Reserve it for cases you have written down, such as repeated silence after the retry count on a line that already played the decline, or abusive audio. Do not make hang up the fallback for Medicare inbound. A dropped beneficiary call is an operating incident, not a clean disqualification.
Test the four exits on a number that is not advertised yet. Force a no-match by asking for something you do not sell. You should hear the decline, the transfer, or the voicemail greeting you saved, and you should not hear a premium. Force silence and confirm the retry count hands off to this same fallback. Then look at where the transcript and any message landed on the contact. A message is a finished outcome. The human queue still has to be ready if you chose transfer. A fallback you have not heard yourself is a rumor.
Tell a bad rule from a bad audio path
Two weeks of fallbacks can mean two different faults. If the transcripts show clear requests you simply did not write a rule for, add a question or a route. If the transcripts show the caller answering and the profile marking the turn empty, look at silence, retries, and interruption mode before you rewrite the script. A five-second silence and an ignore-interruptions setting will throw people into fallback who were only talking over the prompt. That is a settings bug wearing a comprehension mask. Change one control, run the test calls again, and compare. Do not ship a warmer prompt to cover a clock that cuts callers off.
Report fallback as its own count next to transfer, book, message, and disqualification. You want the reason mix, not a single 'containment' number borrowed from another industry. If you do not have a baseline yet, your baseline is this campaign's first clean week. A sudden jump after a greeting edit means the edit broke recognition or the rules. Roll the greeting back. A slow climb during a holiday week may be more wrong numbers. Listen before you theorize. The point of a named fallback is that unclear calls have a boring, repeatable end. Boring is what you want. Improvised help is how the model starts recommending products it is not allowed to recommend.
Write the fallback on the campaign card
The card needs four lines. The behavior you chose. The exact sentence. The destination, if any. The person who reviews fallback transcripts daily in week one. Add the condition that sends a call here: no rule matched, or retries exhausted. If marketing wants a friendlier sentence, they may edit the sentence. They may not add a plan name. If operations wants fewer fallbacks, they may edit questions and rules. They may not turn hang up on to make the chart look cleaner. Hang up reduces the count by discarding the caller. That is not containment. That is a drop you chose.
Revisit the choice when the campaign changes product, language, or hours. A Spanish profile needs a Spanish decline, not the English sentence on a translated voice. An after-hours AI queue should not fall back to a transfer into a closed human queue. Book or voicemail instead, and say the next open window in words you have verified. None of these choices is automatically lawful or automatically kind. They are configurations. FCC guide to robocalls and robotexts rules on artificial voice still apply if this profile ever dials out. Inbound confusion is not outbound consent. Keep the fallback as the exit from a call the person placed, and keep outbound on its own review.
How AgentTech exits when it cannot help
AI voice agents stores fallback as polite decline, transfer to a queue, voicemail, or hang up, with a destination or a custom decline message. AI receptionist and AI lead qualification should point incomplete and timeout at that same exit. queue routing matters only if you transfer: skills, states, and hours still apply, so do not dump unclear calls onto a queue that cannot take them. The $50 seat unlocks the profile. Minutes bill from the wallet whether the call ends well or not, which is another reason to exit instead of chatting.
compliance scoring lets you review the fallback recordings beside every other call. Look for a decline that still mentions a product, and for a transfer that arrives with no transcript. AI lead qualification should have done the sorting before this path. If most calls fallback, the qualifier is not qualified as a design. Fix the questions. Do not add a second model. The honest exit is a sentence you wrote and an action you configured. That is the whole feature. Review those recordings in week one, not at month end.
Frequently Asked Questions
What is the default AI voice fallback?
Polite decline. You can replace the message, or choose transfer to a queue, voicemail, or hang up immediately. Choose before the campaign number is public, and test it by asking for something you do not sell.
Should unclear Medicare callers be hung up on?
Not as the standard path. Hang up is for cases you have written down, such as abuse or dead air after the decline already played. A confused beneficiary should get the decline, a message, or a staffed transfer.
Does fallback mean the call was TCPA compliant?
No. Fallback is an exit when no rule matches. It does not create consent, and it does not bless an outbound dial. Inbound and outbound stay separate reviews.
Key Takeaways for Agency Operators
- Pick the exit in advance. Decline, transfer, voicemail, or hang up.
- Decline is the default. Hang up is not the everyday Medicare path.
- Unclear is not unqualified. Count them separately.
- Do not guess a product on the way out. One sentence, then the action.
- Test a no-match and a silence. Hear the fallback before you publish.
Decide whether unclear calls become a message instead of a sale and whether a transfer still fits the human queue you designed.
