AI Receptionist agent always offers voicemail / chat / email / "another department" when the extension is unavailable. Can it be removed?

LTImoveis_Jacarei

Customer
Joined
Oct 10, 2026
Messages
1
Reaction score
0
V20 Update 10 (Build 1694), AI Agent type Receptionist, OpenAI Realtime.

When the caller asks for a person and the transfer fails because the extension is unavailable, the agent always says something like: "I couldn't reach X. Would you like voicemail, a chat message, an email, or should I connect you to another department?"

Our company does not use voicemail. Voicemail is disabled on the extension (VMEnabled = false) and on the agent itself, and the system prompt explicitly forbids offering it, but the agent still says it. We even rewrote the "Unreachable Destinations" and "Fallback" sections of the template. The first sentence after a failed transfer seems to be imposed by the platform's transfer tool.

Questions:
1. Is there a setting to remove the "Transfer to Voicemail" tool for an AI Agent?
2. Can we force "Take Message" (chat) only, or customize what the tool tells the agent after a failed transfer?
3. Is the fixed text after a failed transfer configurable?

Thanks!
 
Hello,

Can you advise on the changes you have tried making to the prompt, the exact OpenAI models you have configured, and if the user the transfer failed to does indeed have voicemail disabled on the user config tab?
 
We have a client that only wants the vmail option not chat or email. This works for release 9 but does not work for release 10. I get all 3 options. In release 10 I still get options for chat and and email. Also lines 135 and 136 are ignored. I absolutely love the way this works on release 9 and am hoping it doesn't get goofed up once a10 is officially released. You guys are doing an amazing job on this. Thanks in advance for any assistance
 

Attachments

Hello,

Can you advise on the changes you have tried making to the prompt, the exact OpenAI models you have configured, and if the user the transfer failed to does indeed have voicemail disabled on the user config tab?
 
Has anyone found a way to remove options from AI agents? I know release 10 is around the corner and our one larger client wants on the voice mail option. Our script runs fine on R9 but no matter what we do on RC10 I can not remove options. We are running open AI gpt realtime 1.5 and gpt mini 5.4 on R9 and realtime 2.1 and gpt-sol 5.6 on R10
 
Hello,

Can you advise on the changes you have tried making to the prompt, the exact OpenAI models you have configured, and if the user the transfer failed to does indeed have voicemail disabled on the user config tab?
Has anyone found a way to remove options from AI agents? I know release 10 is around the corner and our one larger client wants on the voice mail option. Our script runs fine on R9 but no matter what we do on RC10 I can not remove options. We are running open AI gpt realtime 1.5 and gpt mini 5.4 on R9 and realtime 2.1 and gpt-sol 5.6 on R10. I have been trying all week and have had no success in limiting options given by AI receptionist agent. I even tried open ai call script. Some clients want voice and chat not email. Others want email only and 1 client wants voicemail only. All my research says this is built into the 3CX code. But you guys are way more intelligent than I am, so I have no way of knowing if that is a true statement
 
if you delete these lines out of the agent prompt, it should do what you want. It does on RC2.

1793823719966.png
 
I did that and it does not work for me. It works on release 9 for me but not R10 rc2. I have pretty much tried everything I could think of before posting (hate sounding like an idiot lol) I appreciate the the suggestion I must be doing some else wrongScreenshot From 2026-11-04 15-30-53.png
 
interesting.
 
interesting.
So you have done this and it works for you? It eliminates the options? I am more than happy to try again using strictly a default template but with those options removed. I did that once but ...
 
I would try these tweaks to the sections Available Actions, Action Rules, Unreachable Destinations :

Markdown (GitHub flavored):
## Available Actions
Use only allowed actions.

{{#allow_transfer}}
- transfer
{{/allow_transfer}}
{{#allow_voicemail}}
- voicemail
{{/allow_voicemail}}
- endcall

## Action Rules
- Verify allowed. If not: unavailable, list allowed, choose if several. After choice: minimum extra info; never substitute.
- Before any action or response, first check known context (screening + caller turns) for a clear reason and use it as content.
- Ask for content only if none is already clear; if clear, do not ask again unless the caller wants to change or add.
- If the caller explicitly selects one allowed option (voicemail/transfer/endcall) or says goodbye/bye/farewell, do not ask any follow-up question; proceed immediately.
- In that same turn, after one brief spoken confirmation, you MUST invoke the correspondent tool.

## Unreachable Destinations
- Unavailable/busy: no auto-pick; offer allowed options only.
{{#allow_voicemail}}- Voicemail.{{/allow_voicemail}}
- Retry later; if calling back, brief OK and end.
 
I tried that on a default template but I did not have any luck support sent me this email.
Hello Curtis,




Currently, V20 Update 10 does not provide a configuration option to enable or disable fallback choices for the built-in AI Receptionist when a destination is unavailable.



Although the AI prompt can be customised, certain fallback responses are generated by the internal call-handling process and cannot be reliably controlled through prompt modifications alone.

For more specific workflows, Update 10 also introduces AI Call Scripts, which allow custom call-handling logic to be developed.



We acknowledge your requirement for greater flexibility in configuring these options. However, we do not have any information on whether this is something that will come in a future release.