Hello VAPI
team,
We are seeking guidance on integrating VAPI's outbound call feature with third-party dialer companies that are already making outbound calls via their APIs. Specifically, we need to understand how to incorporate VAPI's bot functionality, ensuring the context (like customer names and other details) is passed appropriately.
Context:
Many of our customers use third-party dialers, which make outbound calls to numbers uploaded in their CRM. These dialers typically handle the call initiation and routing but lack the ability to provide detailed context to VAPI's bot.
Challenge:
When using the VAPI Create Call API, we pass specific context details (e.g., customer name) to personalize the bot's interaction. However, if the call is initiated by an external dialer, this context may not be directly available to VAPI.
Questions:
Webhook: How can we ensure that when a third-party dialer initiates an outbound call, the necessary context (customer name, etc.) is passed to VAPI's bot?
API: Is there a recommended workflow for third-party dialers to interact with VAPI to maintain context? For example, should they first hit an endpoint in our system to store the context before initiating the call through VAPI?
Call Transfer Mechanism: What is the best practice for transferring a call initiated by a third-party dialer to VAPI, ensuring the bot has all the required information to handle the interaction effectively?
Proposed Solution:
Our initial thought is to have the third-party dialers send a webhook to our system with the call details, including any contextual information. We would then store this information temporarily and initiate the call via VAPI, ensuring the bot has the necessary context. However, we are looking for your expert advice on whether this is the optimal approach or if there are better practices we should consider.
We appreciate your assistance and look forward to your guidance on this integration.