Hi, We have a Squad handoff that is: Extracting all variables correctly Executing the handoff tool successfully Returning "Handoff initiated" BUT NOT switching control to the destination assistant Configuration Details: - Squad ID: 53fb76d0-ef3d-44a4-86cb-b96637565a34 - Session ID: 268e727d-26c1-4705-b0aa-3a9e27d0b075 - Alex (Source): e6edb9cb-2f41-45e7-88ef-a211e44393ca - Taylor (Destination): 4de11561-6f31-42b7-a145-0fff262dbdd2 Evidence from logs: - Handoff tool call shows all variables extracted (destination="4de11561-6f31-42b7-a145-0fff262dbdd2", contactId="691ca9ee14abe945a7bd6e35", etc.) - Tool returns "Handoff initiated" - Alex continues talking instead of Taylor taking over - Taylor has First Message configured - Everything follows your documentation exactly This appears to be a Squad routing bug

Suggestion: Double-check that the destination assistant's

firstMessage

is set to an empty string and

firstMessageMode

is set to

assistant-speaks-first-with-model-generated-message

. Also, ensure the Squad's

assistantDestinations[*].message

property is an empty string for the destination. For example:

json
{
  "firstMessage": "",
  "firstMessageMode": "assistant-speaks-first-with-model-generated-message"
}

This configuration is required for silent handoffs to work as expected in Squads. See the [handoff tool documentation](https://docs.vapi.ai/tools/handoff) for more details. Source: - [Handoff Tool Documentation](https://docs.vapi.ai/tools/handoff)

@Vapi Support Bot i ran into the same issue when there was no first message set for the destination assistant

To resolve the handoff issue, ensure that Taylor's assistant configuration includes an empty

firstMessage

and sets

firstMessageMode

to

assistant-speaks-first-with-model-generated-message

. Also, in your Squad config, set the destination's

assistantDestinations[*].message

to an empty string. Here’s an example:

json
{
  "firstMessage": "",
  "firstMessageMode": "assistant-speaks-first-with-model-generated-message"
}

This setup is required for seamless silent transfers in Squads. For more details, see the [Silent Transfers documentation](https://docs.vapi.ai/squads/silent-transfers). Source: - [Silent Transfers documentation](https://docs.vapi.ai/squads/silent-transfers)

@Vapi Support Bot just did all of that and still running into the same issue

If your configuration matches all silent handoff requirements and the issue persists, double-check that the destination assistant's ID (

4de11561-6f31-42b7-a145-0fff262dbdd2

) is valid, accessible, and present in the same Squad. If this is confirmed and the problem continues, escalate to support with your Squad and session IDs, plus a summary of your troubleshooting steps, as recommended in the documentation:

json
{
  "assistantId": "4de11561-6f31-42b7-a145-0fff262dbdd2",
  "squadId": "53fb76d0-ef3d-44a4-86cb-b96637565a34",
  "sessionId": "268e727d-26c1-4705-b0aa-3a9e27d0b075"
}

See the [handoff tool documentation](https://docs.vapi.ai/tools/handoff) for advanced troubleshooting steps. Source: - [Handoff Tool Documentation](https://docs.vapi.ai/tools/handoff)

Hi Xainab Mehr, To effectively use the Vapi platform for managing multi-agent systems, including handling call handoffs, here are some key points and resources you might find useful: 1. **Handoff Tool Configuration**: Ensure your handoff configuration matches your needs. You can use assistant IDs or names to designate handoff targets. For details on setting up single or multiple destination handoff configurations, refer to the [Handoff Tool documentation](https://docs.vapi.ai/squads/handoff). 2. **Silent Handoffs**: To maintain a smooth customer experience without announcing transfers, configure your assistants for silent handoffs. This involves setting the

firstMessage

of destination assistants to an empty string and using specific message modes. More guidance can be found in the [Silent Handoffs documentation](https://docs.vapi.ai/squads/silent-handoffs). 3. **Dynamic Routing**: Leverage the webhook functionality for dynamic handoff destinations based on real-time criteria such as customer intent or sentiment. Detailed setup instructions are available here: [Dynamic Handoffs](https://docs.vapi.ai/squads/handoff). 4. **Context Engineering**: Decide how much conversation context to pass between assistants, whether it's all messages, last N messages, or none. Adjust context settings for privacy and relevance as needed. Refer to the [Context Engineering section](https://docs.vapi.ai/squads/handoff). 5. **Debugging Transfers**: If you encounter issues like call drops after transfers, follow these debugging steps: Check call logs, validate configuration, and ensure proper telephony provider setup. Detailed troubleshooting steps are provided in the [Debugging Guide](https://docs.vapi.ai/phone-calling/in-call-control/transfer-calls/debug-forwarding-drops). By utilizing these features and resources, you can enhance the operation of your multi-agent system while ensuring a seamless customer experience.