Workflow to Assistant(Last Node) unable to End cal...
# support
h
Here is my workflow link: https://dashboard.vapi.ai/workflows/7d4ca7af-796e-453a-9177-979a6dac6d32 As you can see in the last I have another Assistant in this. Now the problem is when it reaches the end and transfers to the second Assistant, it doesn't end the call automatically even after the communication seems completed. What could be the reason? https://cdn.discordapp.com/attachments/1368453306179125288/1368453306321600582/Screenshot_2025-05-04_at_10.31.39_AM.png?ex=681846f4&is=6816f574&hm=90d649dfb15bfa1635bf9f01be4e7a208065f3a256b1662da9570c252cd0cb43&
v
Based on the information available, there are several possible reasons why your call isn't ending automatically after transferring to the second Assistant. Is the
endCall
tool configured in your second Assistant's settings? According to Vapi documentation, the Assistant needs to have the
endCall
tool specifically enabled and properly configured to terminate calls automatically. To help diagnose your issue further, could you share how your second Assistant (the "Hospital at Home AI Agent") is configured, particularly regarding its tools and end call settings? Source: - [Vapi Documentation Default Tools](https://docs.vapi.ai/tools/default-tools)
v
I notice you've enabled the End Call Function, but there might be other factors affecting it. According to the information I found, the "Enable End Call Function" method is actually deprecated, and the newer recommended approach is to add the
endCall
tool type to your call configuration. Which language model are you using for your second Assistant? The documentation notes that the
endCall
function works best with GPT-4 and larger models, so this could be affecting its performance. Source: - [Vapi Documentation Default Tools](https://docs.vapi.ai/tools/default-tools)
h
GPT4.1 Nano @Vapi Support Bot
v
The issue is likely that GPT4.1 Nano isn't fully compatible with the
endCall
tool. According to documentation, the
endCall
function works best with GPT-4 and larger models. Instead of using the deprecated "Enable End Call Function", try adding the
endCall
tool type to your configuration:
Copy code
json
"tools": [ { "type": "endCall" } ]
Also, set your model temperature to 0.3 for better performance. According to [Vapi Documentation](https://docs.vapi.ai/tools/default-tools), consider switching to a larger model like GPT-4 if the issue persists. Sources: - [Vapi Documentation Default Tools](https://docs.vapi.ai/tools/default-tools) - [Discord Channel](https://discord.com/channels/1211482211119796234/1341663336621674558)
h
@Vapi Support Bot Ok thanks, can you also tell me the pricing of my AI assistant?
v
I couldn't find all the details about your AI assistant's pricing. You might want to check our [pricing page](https://vapi.ai/pricing). I'm escalating your query to a human agent for further assistance! 👍
k
total pricing is 5 cents per minute which is Vapi charge + Underlying provider cost.
h
Ok for buying number do we have to pay any additional charges?
We are not going to us the Twilio number
@Kings_big💫
Our usecase is slightly different its the combination of multiple Agent. We have created workflow which triggers on call and its not the LLM based but yes that workflow we have is using the prompts in it, which I have attached in the screenshot. Now on the last node we are going to send the user to next Agent which is pure AI LLM based. So I want to understand following things 1. Do workflows have any pricing? 2. for calling a phone to user we are going to use the Vapi number so do we have to pay any extra amount in this or its included in 0.05?
k
Vapi provides up to 10 free US phone numbers per account with no extra charges if you’re not using Twilio.
2 Views