Q4
04/07/2026, 3:48 PMAI Evy
04/07/2026, 3:48 PMAI Evy
04/07/2026, 3:48 PMbegin_message_delay_ms parameter [(2) ]() [(3) ]() [(4) ]() . This delays the first message by the specified amount of milliseconds, with a valid range of [0, 5000] . Note that this only applies when the agent speaks first .
One workaround mentioned in the community is to set the AI to speak first but use just a dash "-" as the initial message [(5) ]() . This makes the agent think it has spoken, but it remains silent, and then the conversation proceeds normally after the user speaks .AI Evy
04/07/2026, 3:48 PMAI Evy
04/07/2026, 3:48 PMQ4
04/07/2026, 3:50 PMAI Evy
04/07/2026, 3:50 PMAI Evy
04/07/2026, 3:51 PMstart_speaker parameter to control who initiates the conversation [(1) ]() [(2) ]() [(3) ]() .
To make your outbound Conversation Flow agent wait for the customer to speak first, set start_speaker to "user" . This parameter determines who starts the conversation and accepts either "user" or "agent" as values .
Here's how to configure it:
javascript
const conversationFlowResponse = await client.conversationFlow.create({
start_speaker: 'user',
// ... other configuration
}) ;
[(3) ]()
If you want the agent to wait for a specific duration before starting (when configured as agent-first) , you can use the begin_after_user_silence_ms parameter [(1) ]() [(2) ]() [(3) ]() . This makes the AI begin the conversation after waiting for the user for the specified duration in milliseconds . However, this only applies if the agent is configured to wait for the user to speak first .
**AI Evy
04/07/2026, 3:51 PMAI Evy
04/07/2026, 3:51 PMQ4
04/07/2026, 3:53 PMAI Evy
04/07/2026, 3:53 PMAI Evy
04/07/2026, 3:53 PMstart_speaker: 'user' when you create or update your Conversation Flow in Retell [(1) ]() [(2) ]() .
This is configured at the Conversation Flow level, not when you make the outbound call. Here's where to set it:
When creating a new Conversation Flow:
javascript
const conversationFlowResponse = await client.conversationFlow.create({
model_choice: { model: 'gpt-4.1', type: 'cascading' },
start_speaker: 'user',
nodes: [
{
id: 'start',
instruction: { text: 'Greet the customer and ask how you can help them.', type: 'prompt' },
type: 'conversation',
},
],
}) ;
[(1) ]()
When updating an existing Conversation Flow:
javascript
const conversationFlowResponse = await client.conversationFlow.update(
'conversation_flow_id',
{
start_speaker: 'user',
// other configuration
}
) ;
[(2) ]()
Once you've configured start_speaker: 'user' in your Conversation Flow, any agent using that flow will wait for the user to speak first—including outbound calls [(1) ]() [(3) ]() [(2) ]() .AI Evy
04/07/2026, 3:53 PMAI Evy
04/07/2026, 3:53 PMQ4
04/07/2026, 4:14 PMAI Evy
04/07/2026, 4:15 PMAI Evy
04/07/2026, 4:15 PMstart_speaker: 'user' isn't working as expected. Let me help troubleshoot this.
First, verify your configuration:
You can configure start_speaker in the Dashboard or via API [(1) ]() .
In the Dashboard:
Click on the begin icon in your Conversation Flow, and you can select who speaks first in the call .
Via API:
When creating or updating your Conversation Flow, ensure start_speaker is set to "user" [(2) ]() [(3) ]() [(4) ]() :
javascript
const conversationFlowResponse = await client.conversationFlow.create({
model_choice: { model: 'gpt-4.1', type: 'cascading' },
start_speaker: 'user',
nodes: [
{
id: 'start',
instruction: { text: 'Greet the customer and ask how you can help them.', type: 'prompt' },
type: 'conversation',
},
],
}) ;AI Evy
04/07/2026, 4:15 PMstart_speaker: 'user' still doesn't work, one community member mentioned setting the begin_message to an empty string "" to make the agent wait for the user to speak first [(5) ]() . This approach was documented for Retell LLM agents [(6) ]() [(5) ]() .
Can you confirm:
1. Where you set start_speaker: 'user' (Dashboard or API) ?
2. Whether you've verified the Conversation Flow was successfully updated with this setting?
3. If you're seeing any specific error messages or unexpected behavior?AI Evy
04/07/2026, 4:15 PMAI Evy
04/07/2026, 4:15 PM