firstMessageInterruptionsEnable: true aint working
this aint working when tried to interrupt using add-message | vapi.send
triggerResponseEnabled- this also set to true
triggerResponseEnabled- this also set to true
VAccording to the Vapi documentation, the first message cannot be interrupted and is guaranteed to be spoken, which explains why
This will stop the current LLM generation regardless of whether it's the first message or not.
Sources:
firstMessageInterruptionsEnable: true isn't working as expected. Try using the mute-assistant control message instead:This will stop the current LLM generation regardless of whether it's the first message or not.
Sources:
⤵️ Mention @Vapi Support Bot for follow-ups 🐥
VAccording to the Vapi documentation, the first message cannot be interrupted and is guaranteed to be spoken, which explains why
This will stop the current LLM generation regardless of whether it's the first message or not.
Sources:
firstMessageInterruptionsEnable: true isn't working as expected. Try using the mute-assistant control message instead:This will stop the current LLM generation regardless of whether it's the first message or not.
Sources:
⤵️ Mention @Vapi Support Bot for follow-ups 🐥
KHey! To help track down this issue, could you share:
- The call ID
- When exactly this happened (the timestamp)
- What response you expected to get
- What response you actually got instead
This would really help us figure out what went wrong!
OI fixed it by keeping the firstMessage as empty, and putting the first message in the system prompt. since any voice output coming due to system prompt is interruptable, it works.
SHi, My understanding is that by default, VAPI agents are passive at session start — they wait for the user to speak first before responding, unless explicitly configured to begin with a spoken message. So how did you handle this if you leave the first message empty.
KThis ticket has been marked as solved, and as a result, you will no longer receive any further responses. Kindly create a new support ticket to escalate your inquiry.
Oassistant-speaks-first-with-model-generated-message enable it
VTo have the assistant speak first with a model-generated, interruptible message, set the
This ensures the assistant starts the conversation and its first message can be interrupted if needed.
Note: There is no documented
Source:
firstMessage to an empty string and place your initial greeting or instruction in the system prompt. For example:This ensures the assistant starts the conversation and its first message can be interrupted if needed.
Note: There is no documented
assistant-speaks-first-with-model-generated-message flag—use the system prompt as shown above.Source:
