wirevo
07/26/2024, 8:16 PMhuseyinozcan.
07/26/2024, 6:42 PMEddie
07/26/2024, 6:01 PMalifarahat
07/26/2024, 5:45 PMPSAI_Marketing
07/26/2024, 5:33 PMSigurd
07/26/2024, 5:17 PMPatriotSoul
07/26/2024, 4:21 PMbuytslacalls_
07/26/2024, 3:43 PMjames_apex
07/26/2024, 3:23 PMSair
07/26/2024, 1:53 PMEthan
07/26/2024, 1:29 PMEthan
07/26/2024, 1:23 PMYoshi
07/26/2024, 12:38 PMChris
07/26/2024, 10:46 AMRick S.
07/26/2024, 10:45 AMLajiao
07/26/2024, 9:51 AMLorenzo Ceschia
07/26/2024, 9:39 AMPrashant
07/26/2024, 9:34 AMbeta kostík
07/26/2024, 8:52 AMming
07/26/2024, 8:48 AMLuka
07/26/2024, 7:25 AMPeppelerd
07/26/2024, 7:16 AMrob
07/26/2024, 4:33 AMVapi Support Bot
07/26/2024, 3:49 AMlookupState
function is being called correctly and that the assistant is properly handling the response.
First, we need to confirm that the lookupState
function is being triggered with the correct Zip Code parameter and that it is returning the expected result. If the function is part of an external system like make.com, you should check the logs there to ensure that the function is being called and that it's returning the correct state for the given Zip Code.
If the function is working as expected, then the issue might be with how the assistant is processing the result. The script within your prompt should dynamically insert the state into the placeholder {lookupState result}
. Make sure that the assistant's script is set up to receive the Result
parameter from the lookupState
function and replace the placeholder with the actual state.
If you're still encountering issues after checking these points, it might be necessary to look into the specific error messages you're receiving or any logs that could provide more insight into where the process is breaking down. If you need further assistance with this, please provide more detailed information or consider reaching out to support for a deeper investigation.Joonho
07/26/2024, 1:55 AMforwardingCallNumber
parameter(you can see that in the screenshot), even though I set a number is the dashboard.
Can you please have a look?
call id: d4ebd3d0-eb2d-426a-b1d2-3309788ed2aa
.
https://cdn.discordapp.com/attachments/1266212139253891133/1266212139501228032/2024-07-26_10.14.23.png?ex=66a45373&is=66a301f3&hm=71cc14fadeb603e8dcffc6f1d938d3721def4835a9150474daf4ae323c83bfc8&
https://cdn.discordapp.com/attachments/1266212139253891133/1266212139778048020/2024-07-26_10.14.35.png?ex=66a45373&is=66a301f3&hm=cd6e0e00dbcc96eee4589f4bc7d2512287ca0a7e098abd0c8cf47324ec0f9630&vanguy
07/25/2024, 11:46 PMlarrypowers
07/25/2024, 11:15 PMMamata Kondapally
07/25/2024, 10:54 PMVapi Support Bot
07/25/2024, 10:46 PMassistantOverrides.firstMessageMode
is set to 'assistant-speaks-first'. This setting should prompt the assistant to deliver its message without waiting for the user's input.
If you've already set this and it's not working as expected, there might be a problem with how the setting is being applied or there could be another issue at play. To assist you further, I would need to know more details about how you've configured the prompt or any specific settings you've applied.
If you believe the settings are correct and the issue persists, it might be necessary to reach out to the support team for a more in-depth look into the problem. Please let me know if you would like to proceed with that or if there's anything else I can do to help!Vapi Support Bot
07/25/2024, 10:03 PMassistantOverrides.firstMessageMode
should be set to assistant-speaks-first
. If this is already set and the assistant is still not behaving correctly, there might be a different issue at play.
Could you please confirm if the assistantOverrides.firstMessageMode
is set to assistant-speaks-first
? If it's not, we should change it to this setting. If it is already set correctly, then we may need to look into other aspects of the configuration or the implementation of the assistant's behavior.