Agent is not speaking first messages according the...
# supporth
Hasan
06/03/2025, 1:22 PMI am facing issues in vapi workflows where I do not hear first messages in conversation nodes. I have to speak first and then it says something.
Call ID: ec8954f8-723c-453b-a7a3-8604d49fe0b3
https://cdn.discordapp.com/attachments/1379450049095929856/1379450049389396078/message.txt?ex=6840f138&is=683f9fb8&hm=5ce8f128efc57f5faa35ff9be1aede3cd907dca75baf975a08b446450c36b94f&
k
Kings_big💫
06/03/2025, 1:27 PMLooking into it
h
Hasan
06/03/2025, 3:32 PMhey any leads on this @Kings_big💫 ?
Hasan
06/03/2025, 3:58 PMI have tried changing the llm to gpt 4o mini. It worked better but when i start the call, it does not say anything. It only starts when i say something first
Hasan
06/03/2025, 4:00 PMAlso i noticed that when I set the first message in conversation nodes other than the first one, it does not say that
k
Kings_big💫
06/03/2025, 4:42 PMGlad it fixed
h
Hasan
06/03/2025, 5:06 PM@Kings_big💫 is there a solution of agent not speaking first? I have to start speaking and then agent speaks the first message
k
Kings_big💫
06/03/2025, 5:08 PMSet "firstMessage" with your greeting and "firstMessageMode": "assistant-speaks-first" in the assistant configuration.
s
Shubham Bajaj
06/03/2025, 5:55 PM🟡 12:33:43:120 ElevenLabs (Websocket #0) State "connecting" But Received End Token. Dropping 83... "Hello, this is Eva from DM Clinical. May I speak with {{first_name}} {{last_name}}?"
Hey @Hasan to me it's one of the chances where Elevenalabs socket was closed, do you have more call_ids with similar behaviour?
h
Hasan
06/03/2025, 5:56 PM@Shubham Bajaj I am using vapi voice
Hasan
06/03/2025, 5:56 PMI have shared my updated config. Tha agent still does not speak first
Hasan
06/03/2025, 5:58 PMCall ID1: b5b7e36d-7068-45b8-b9cd-96f292752e5e
Call ID2: daa36f8b-73c7-4ed0-b162-17af7c71f542
Call ID3: dbe19dc6-7a03-46cd-964c-7d867166991c
Hasan
06/03/2025, 5:58 PM@Shubham Bajaj
Hasan
06/03/2025, 7:07 PMI have also tried the templates. Their behaviour is also same
Hasan
06/04/2025, 10:22 AMAny updates on this @User
k
Kings_big💫
06/04/2025, 10:44 AMNo update yet, I’ll ping you
s
Shubham Bajaj
06/04/2025, 2:35 PM@Hasan can you some other voice provider, until this issue is resolved?
h
Hasan
06/04/2025, 2:58 PMokay let me check
Hasan
06/04/2025, 3:13 PM@Shubham Bajaj Call ID: c9d50440-778a-4976-a941-0a193b5d07b0
Hasan
06/04/2025, 3:14 PMI chose deepgram and now it is speaking out the dynamic variable names instead of their values. Also I dont know why it stopped after I said yes to discuss details
Hasan
06/04/2025, 3:28 PM@Shubham Bajaj which voice provider should I use?
v
Vapi
06/04/2025, 3:45 PMPlease rename the dynamic variables using camel case because we expect variable names in camelCase. Also, remove the surrounding punctuation (\`\`) from the "date of birth" variable to ensure the templating works correctly.
---
h
Hasan
06/04/2025, 3:48 PMokay got it, Let me check again
Hasan
06/04/2025, 4:00 PM@Shubham Bajaj CallID: 6bae23d2-b451-44ff-ba9f-01a16d3ecbe8
It didnt work
Hasan
06/04/2025, 4:04 PMIt was working with same dynamic variables yesterday. It looks like this issue started happening today
v
Vapi
06/05/2025, 8:41 PMlooking into it.
Vapi
06/05/2025, 11:07 PMHey Hasan! Thanks for reporting this issue. With our new workflow launch or workflow out of beta, we have fixed this issue as well. So, I suggest you try 2-3 calls and let me know how it goes. If it still fails for you, finger crossed please share the call IDs.
h
Hasan
06/11/2025, 7:18 AM@Shubham Bajaj Thanks a lot man. The issue is resolved now.
v
Vapi
06/11/2025, 11:49 PMMarking this ticket as Solved ✅