Bypassing Vapi and Routed to GoTo
# support
s
As per your earlier instructions, we have added a dedicated number intended for Vapi to handle customer interactions. However, we're currently facing a routing issue. When a customer directly calls this number, instead of the call being handled by the Vapi agent as expected, it is being immediately routed to GoTo, completely bypassing Vapi. Our intended flow is as follows: Customer calls the configured number. The call should be processed first by the Vapi agent (for IVR, knowledge base interaction, etc.). Only after agent processing, the call should be transferred to the respective department via GoTo. This current behavior is blocking our production flow, as the Vapi agent is not getting triggered at all. Please assist us in ensuring that Vapi is the primary entry point for all inbound calls, and GoTo is only used for post-agent call transfers. Looking forward to your urgent support to resolve this.
s
Please help me with your SIP destination. Share the screenshot here. I may be able to help. This is SIP issue.
s
my SIP provider is GoTo
@User any update?
c
Your vapi number must be set to route all inbound calls directly to your vapi assistant not GoTo, with the assistant handling the initial interaction and using a silent transfer via transfer_call to GoTo..
s
To ensure everything is correctly set up and aligned with your expectations , especially around the assistant handling initial interactions and performing a silent transfer to GoTo , would you be available to connect today for a quick discussion? Looking forward to your response. @Kings Big
c
Hey Suraj, Thanks for reaching out! We're currently swamped with a bunch of tickets and it's taking us longer than usual to get back to everyone. I know waiting isn't fun, but we want to make sure we give your issue the attention it deserves rather than rushing through it. We'll circle back with you soon to get this sorted out.
Hi, First off, we want to sincerely apologize for the delay in getting back to you. We understand how frustrating it is to wait - especially when you're counting on us - and we owe you a clear explanation of what’s been happening and how we’re addressing it. Over the past few weeks, we've seen a significant increase in support requests. While this reflects exciting growth, it has also stretched our small team and exposed some real challenges in scaling our support operations. To improve your experience, we’ve taken a step back to reassess our approach. Here’s what we’re implementing: - Smarter Support Through Automation: We’re investing in our AI support systems to help you resolve issues more efficiently. Soon, our support bot will offer expanded capabilities, making it easier to access accurate, instant help—particularly for common or repetitive queries. - Expanding the Support Team: To meet growing demand, we’re adding 2–3 new team members focused on managing support volume and improving response times. - Prioritized SLAs for High-Usage Accounts: We’re introducing service level improvements for users who are growing with us: - Accounts with usage over 1,000 minutes/month will receive prioritized support. - For all general inquiries, we’re establishing a standardized 48-hour response time. We’re confident these steps will lead to faster, more reliable support and help us better serve you as you grow with us. Also, in case you still need help with this ongoing ticket, do let us know, and we will help you get this resolved as soon as possible. Thank you for your continued patience and for being part of our journey. Warm regards, Vapi Team
s
any update on the above issue , i am still waiting for your response
c
In case we aren't able to schedule a call, would you please provide some more information about how the assistant is currently configured? a call id or PCAP file would also be helpful. I would also like to echo what kings_big said, which is my first thought being you should route your call through VAPI first so the user could be processed by the assistant first, then hand off the call through the transferCall tool to the GoTo destination.