Need assistance with live call control
# support
a
Hello Support Team, I hope this message finds you well! I’m currently utilizing the VAPI API, and I want to express my appreciation for this fantastic product. I'm looking to control the assistant during a call at specific moments. I came across an article that introduces this feature https://docs.vapi.ai/calls/call-features, but it only includes a single example. While I understand how to prompt the assistant to speak, it appears that the assistant will only respond once it has completed its current speech. Is there a way to interrupt the assistant's speech in order to issue commands or prompts? Thank you for your assistance! Best regards, Alex
v
message has been deleted
@Alex Hello Alex, I'm delighted to hear that you're enjoying using the VAPI API! Regarding your question about interrupting the assistant's speech, currently, the assistant's speech cannot be interrupted once it has started. However, you can design your call flows to wait for user input at certain points or to provide options for the user to choose from, which can help guide the conversation and control when the assistant speaks. If you need to have more dynamic control over the assistant during a call, you might consider implementing logic in your application to manage the conversation flow and anticipate when to prompt the assistant to speak. If you have any specific scenarios or use cases in mind, I'd be happy to discuss them further and provide more tailored advice. Best regards, VAPI Support Team
You can continue this conversation by mentioning me in the message.
a
@Vapi , how to design this call flows? Should I use Squads?
v
@Alex Designing call flows with VAPI can be a creative process, and using Squads can indeed be a powerful way to manage complex interactions. Squads allow you to specify a list of assistants and destinations, with the first member being the assistant that starts the call. Assistants can be either persistent or transient, depending on your needs. Here's a general approach to designing call flows: 1. **Define the Call Objectives**: Determine what you want to achieve with the call. This could be customer support, information gathering, sales, etc. 2. **Map Out the Conversation**: Create a flowchart that outlines the possible paths the conversation could take. Include user prompts, assistant responses, and decision points. 3. **Implement Logic for User Input**: Decide how you will handle user input. This could be through voice recognition, DTMF tones (keypad inputs), or other methods. 4. **Use Squads for Complex Interactions**: If your call flow requires multiple assistants or needs to route calls to different destinations, Squads can be very useful. You can set up a squad with different roles for each assistant, such as one for greeting, one for FAQs, and another for sales inquiries. 5. **Test and Iterate**: Once you have a basic flow designed, test it out and refine it based on user interactions and feedback. If you're ready to set up a Squad or need more specific guidance on how to implement this in your call flow, please let me know the details, and I can assist you further.
s
@Alex we have 4 types of messages and all of them will can be used to interrupt the assistant, you can try using add message type which you can learn more about here https://api.vapi.ai/api-json https://cdn.discordapp.com/attachments/1313862861600329828/1314487513070436402/Screenshot_2024-12-06_at_12.32.25_PM.png?ex=6753f365&is=6752a1e5&hm=65d4b07adca4146c8a19ca5fc0627674b5e0e3812cbe51b69843e083c1535d11&
Do let me know if you require further help!!
a
@Shubham Bajaj this is great to see the API for control methods. Thank you!
I tried to use "Say" ClientInboundMessageSay, but if AI speaks the first message at the moment, it does not interrupt in the middle. It finishes the first message first, and only then says the message send via API ClientInboundMessageSay.
s
Yeah these messages are added to the queue if current message type is un-interruptible.
a
Is it possible to make the first AI assistant message interruptible?
s
No.
4 Views