fair-rose
fair-rose•5mo ago

Agent is not speaking first messages according the workflow.

I 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
16 Replies
foreign-sapphire
foreign-sapphire•5mo ago
Looking into it
fair-rose
fair-roseOP•5mo ago
hey any leads on this @Kings_big💫 ? I 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 Also i noticed that when I set the first message in conversation nodes other than the first one, it does not say that
foreign-sapphire
foreign-sapphire•5mo ago
Glad it fixed
fair-rose
fair-roseOP•5mo ago
@Kings_big💫 is there a solution of agent not speaking first? I have to start speaking and then agent speaks the first message
foreign-sapphire
foreign-sapphire•5mo ago
Set "firstMessage" with your greeting and "firstMessageMode": "assistant-speaks-first" in the assistant configuration.
fair-rose
fair-roseOP•5mo ago
xenophobic-harlequin
xenophobic-harlequin•5mo ago
🟡 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?
fair-rose
fair-roseOP•5mo ago
@Shubham Bajaj I am using vapi voice I have shared my updated config. Tha agent still does not speak first Call ID1: b5b7e36d-7068-45b8-b9cd-96f292752e5e Call ID2: daa36f8b-73c7-4ed0-b162-17af7c71f542 Call ID3: dbe19dc6-7a03-46cd-964c-7d867166991c @Shubham Bajaj I have also tried the templates. Their behaviour is also same Any updates on this @Vapi Team
foreign-sapphire
foreign-sapphire•5mo ago
No update yet, I’ll ping you
xenophobic-harlequin
xenophobic-harlequin•5mo ago
@Hasan can you some other voice provider, until this issue is resolved?
fair-rose
fair-roseOP•5mo ago
okay let me check @Shubham Bajaj Call ID: c9d50440-778a-4976-a941-0a193b5d07b0 I 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 @Shubham Bajaj which voice provider should I use?
Kyle Brunker
Kyle Brunker•5mo ago
Please 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. ---
fair-rose
fair-roseOP•5mo ago
okay got it, Let me check again @Shubham Bajaj CallID: 6bae23d2-b451-44ff-ba9f-01a16d3ecbe8 It didnt work It was working with same dynamic variables yesterday. It looks like this issue started happening today
Kyle Brunker
Kyle Brunker•5mo ago
looking into it. Hey 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.
fair-rose
fair-roseOP•4mo ago
@Shubham Bajaj Thanks a lot man. The issue is resolved now.
Kyle Brunker
Kyle Brunker•4mo ago
Marking this ticket as Solved ✅

Did you find this page helpful?