https://vapi.ai/ logo
Join Discord
Powered by
Issue with Assistant Agent not automatically sayin...
# support
t
This only starts to happen from today. This was the main reason I switch our whole agent from workflow to Assistant and now it is happeneing in Assistant too. https://cdn.discordapp.com/attachments/1413063047572099157/1413063048322613425/image.png?ex=68ba9104&is=68b93f84&hm=f9ee5d00a8789fc6407b9602e6fe8de592bb9d0e281cd8c5f734356a98a1d65e&
Please hold on... and the Here are your... are both Tool messages.
v
Suggestion: Double-check that your Assistant's configuration includes a valid 
firstMessage
and that both the Assistant ID and Phone Number ID are correctly set. If the 
firstMessage
is missing, the assistant will wait for user input instead of speaking automatically. Here’s an example of setting the 
firstMessage
in your assistant configuration:
Copy code
json
{
  "firstMessage": "Here are your property details."
}
Update your assistant via the API or dashboard and test if the agent now speaks the API result automatically. [Reference: Vapi documentation](https://docs.vapi.ai/api-reference/assistants/update) Source: - [Vapi documentation Update Assistant](https://docs.vapi.ai/api-reference/assistants/update)
t
I didn't do any changes to the Assistant, It was working fine yesterday and this issue where it needs some user input after a tool call was only happening too workflow agent not Assistant. But now it even is happening to Assistant agent too.
a
@Toph Hi fellow VAPI user, trying to help...I guess we had the same issue - literally the caller needed to say something to trigger the output flow continuing. Kyle told me the workaround for now is to configure an "empty" Tool Start Message, so the flow continues. Have you tried that?
r
same problem here.
@Toph
a
However, I just notice the problem is back for us, too!!!
r
it will call the tool and then not say anything
a
If the user speaks, it will continue
r
thats not a fix tho lol
a
I know, been having this problem since weeks man
r
weeks?!?!?
a
Yes
I had a separate thread open, can´t find it anymore
r
I was gonna have a call with a client today aswell luckuily its changed for tommorow but i may have to move over to something else in the meantime
a
Kyle told me to configure an empty "say" message in the tool as start message, as a workaround for now.
However I did not need to do it as apparently it seems to be fixed
But now it is popping up again, same problem.
Just trying the fix... let´s see
r
does the say thing fix it?
add me bro
ima email vapi
@AiforYou add me back asap
a
added
@User -> Kyle Brunker please can you look into this? This is the exact same problem we were discussing on another thread like 2 weeks ago, when you mentioned the workaround with an "empty" start message in the tool call. However, yesterday it worked perfectly fine even without any messages, but since today the problem is back. https://cdn.discordapp.com/attachments/1413063047572099157/1413096651467259904/image.png?ex=68bab04f&is=68b95ecf&hm=2d828a0c4854899c483c733b4b996e64845cce005bb2fd68aa50e8187521d046&
@Vapi Call ID yesterday, where Tool calls worked fine without having any start or else message in the tool call: 24369a89-c0fb-4980-b211-bcdc77a26396
Call ID from TODAY where it does not work, even with a message configured, as long as the user stays silent, the call will just end
5bf0f177-1072-457c-a0cf-4ead43662b73
t
Hi guys, read your discussion. Have you guys found any solution for this yet. @Ronan @AiforYou
This was the main reason I switch from workflow to assistant type of agent.
It starts to happen like today, as It was working fine yesterday.
I emailed the support team but haven't got response yet.
r
I’ll go check it out again soon. Only fix now: After it says booking now or whatever just say okay after it does the tool call then it will talk back and continue on like normal
As long as u speak it will keep going
k
Alot of tickets about this. Having the same problem myself
r
Was talking to my partner were most likely going to move to vapi cli or just get enterprise plan with 24/7 dev support
If u have enterprise plan u just tell em and they will fix bug up for you
t
r
Did it continue talking after u said what’s the detail
Add me back
t
Yes, it talks and say the API result to you but you have to say something to it.
r
@kitten make a post more people who post and email them the better
t
Otherwise, it will be quiet.
r
That’s currently only fix
I have quite a few connections in the space I’ll try get in contact with a senior dev in vapi to find out more
t
This was the main reason I left my whole 1 month of work on the workflow type of agent, this is the main issue that's happening there. But now it is happening in Assistant too.
That'll be great. Keep me updated anything you get on this issue.
s
@kitten @Chris @Kartik Can you switch your orgs from daily to weekly?
c
Ok will try now
@Shubham Bajaj Updated to weekly now
Working better now thanks! 👍
a
Agreed, from the few calls I made since this change it seems to be fixed.
Thanks
k
I tried doing this but none of my orgs are switching. I move into weekly and it never actually updates and remains daily
c
Could you please provide your org id? We can switch it on the backend
k
4e9c8a4f-aac2-4c0b-a030-55bf14b85113
@Shubham Bajaj
01fc90d6-f3d4-425b-bd2e-5d35728fde87
please do it to both of these orgs
@User
c
We have switched your org to the 
weekly
update channel. Please let us know if the changes are not reflecting accurately
k
74a6adfa-72c2-494a-b2be-2370794f6fb7 f95c1b46-0157-4c76-88a3-46d57e7d7caa 2429db6d-6f40-43be-a7f9-f19267b0ccc9 @User Please switch these ones as well to Weekly instead of daily.
c
The provided orgs are also now on weekly
3 Views
PreviousNext
Powered by