The assistants in the squad are not being transferred—this issue has been occurring since this morning. Only the first assistant is activated, but it doesn’t hand over to the next assistant as expected.

@User Same issue happening with me for last 3 days

Hi there! I see you're having trouble with assistants not transferring properly in your squad. 👋 I don't have access to your specific squad configuration or logs, but I can definitely help troubleshoot this issue based on common causes and solutions. Here are some key areas to check: ## 1. Squad Configuration Make sure your squad is properly configured with destinations: - Check if your squad members have destinations defined. According to [Vapi documentation](https://docs.vapi.ai/squads), if squad members don't have destinations, your root assistants won't be connected to other assistants, resulting in no transfers. - Verify that the

name

property in your payload matches the associated assistant's name accurately. ## 2. Assistant Configuration - Double-check the assistant IDs to ensure they're correct and that all assistants are active. - Confirm that the assistants have the necessary permissions. - If you're using the

transferCall

function, ensure you're setting the

assistantOverrides

correctly to prevent the system from speaking the transfer message. ## 3. Check for Recent Changes Since this issue started this morning, review any recent changes to: - Squad configuration - Assistant settings - Prompts (especially if they contain transfer instructions) - API calls or code that manages transfers ## 4. Common Issues to Look For - **Phone-call-control server event**: Try removing the phone-call-control server event from your assistant. When this server event is utilized, call forwarding control is managed by you rather than VAPI. - **Model temperature**: For calls where the assistant didn't trigger the transfer function, try setting your model temperature to 0.3 and rework your prompt using the Vapi prompting guide. - **Prompt issues**: Check if your prompt has an immediate transfer instruction that might cause the squad configuration to bypass the conversation flow. - **Insufficient credits**: Ensure you have enough credits on your account.

@Vapi Support Bot How to configure assistants to be used in squad and to transfer call

Hi there! I'd be happy to explain how to configure assistants to be used in a squad and set up call transfers. 🙂 I can help with configuring assistants for squads and setting up transfers between them, which should address your current issue. ## Setting Up Assistants in a Squad According to the [Vapi documentation](https://docs.vapi.ai/squads), squads are designed to break down complex workflows into smaller, specialized assistants. Here's how to configure them: 1. **Create a Squad**: Use a POST request to

https://api.vapi.ai/squad

with your authorization token. 2. **Define Squad Members**: In your request body, include

members

as a list of assistants. The first assistant in this list will start the call.

json
   {
     "members": [
       {"name": "LeadQualifier", "destinations": [{"name": "Scheduler"}]},
       {"name": "Scheduler"}
     ]
   }

3. **Set Up Destinations**: Each assistant should have relevant transfer destinations. If squad members don't have destinations, your root assistant won't be connected to other assistants, resulting in no transfers. 4. **Ensure Correct Names**: Make sure the

name

property in your payload matches the associated assistant's name exactly. ## Configuring Call Transfers To enable transfers between assistants: 1. **Transfer Modes**: Vapi offers different transfer modes: - `blind-transfer`: Forwards without message or summary - `warm-transfer-say-message`: Dials destination, delivers a message, connects the customer - `warm-transfer-say-summary`: Dials destination, provides a call summary, connects the customer 2. **Using the

transferCall

Tool**: If you're using this function, ensure you're setting the

assistantOverrides

correctly to prevent the system from speaking transfer messages. 3. **Conversation History**: Use

transferCall

with

transferMode: 'rolling-history'

to preserve conversation history during transfers. ## Common Issues to Check If transfers aren't working:

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!