firstMessageInterruptionsEnable: true aint working
# support
h
this aint working when tried to interrupt using add-message | vapi.send triggerResponseEnabled- this also set to true
v
According to the Vapi documentation, the first message cannot be interrupted and is guaranteed to be spoken, which explains why
firstMessageInterruptionsEnable: true
isn't working as expected. Try using the
mute-assistant
control message instead:
Copy code
javascript
vapi.send({
  type: 'control',
  control: 'mute-assistant'
})
This will stop the current LLM generation regardless of whether it's the first message or not. Sources: - [Vapi Documentation](https://docs.vapi.ai/quickstart/dashboard) - [Discord Discussion](https://discord.com/channels/1211482211119796234/1338730919904673853)
According to the Vapi documentation, the first message cannot be interrupted and is guaranteed to be spoken, which explains why
firstMessageInterruptionsEnable: true
isn't working as expected. Try using the
mute-assistant
control message instead:
Copy code
javascript
vapi.send({
  type: 'control',
  control: 'mute-assistant'
})
This will stop the current LLM generation regardless of whether it's the first message or not. Sources: - [Vapi Documentation](https://docs.vapi.ai/quickstart/dashboard) - [Discord Discussion](https://discord.com/channels/1211482211119796234/1338730919904673853)
k
Hey! 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!
h
I 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.
y
Hi, 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.
k
This 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. 
h
assistant-speaks-first-with-model-generated-message enable it
v
To have the assistant speak first with a model-generated, interruptible message, set the
firstMessage
to an empty string and place your initial greeting or instruction in the system prompt. For example:
Copy code
js
const assistantConfig = {
  firstMessage: "",
  model: {
    provider: "openai",
    model: "gpt-4",
    messages: [
      {
        role: "system",
        content: "Hi there! How can I help you today?"
      }
    ]
  },
  // ...other config
};
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: - [Vapi Web SDK Documentation](https://docs.vapi.ai/sdk/web)