Hi everyone,
We are currently using a single VAPI Assistant for outbound call scheduling, and we’re planning to migrate to a VAPI Squad–based approach. We would like to understand the key differences, required changes, and best practices before proceeding.
### 🔹 Current Setup
* Using a single Assistant for outbound scheduling calls
* Handles greeting, interaction, and scheduling within one flow
### 🔹 Planned Change
* Move to a VAPI Squad (multiple assistants working together)
* Split responsibilities (e.g., greeting, scheduling, follow-ups)
---
## ❓ Questions
### 1. What are the main changes when moving from Assistant → Squad?
* How does conversation routing work between assistants?
* Do we need to redesign prompts and logic completely?
---
### 2. Backend Changes
* Are there any required changes in backend processing?
* API handling
* Webhooks
* Tool/function integrations
* Does Squad introduce new event structures or call handling differences?
---
### 3. Campaign Payload Changes
* Do we need to modify the outbound campaign payload?
* If yes:
* How do we define multiple assistants in the payload?
* How is the entry point assistant configured?
---
### 4. Challenges / What to Expect
* What are the main issues teams face when switching to Squad?
* Latency?
* Cost increase?
* Conversation handoff issues?
* Any limitations compared to single assistant?
---
### 5. Implementation Guidance
We would really appreciate a simple, high-level explanation of how to implement a VAPI Squad.
How should we design the Squad and decide the responsibilities of each assistant?
How do we configure multiple assistants and control how the conversation moves between them?
What is the best way to test the handoff between assistants during a call?
And finally, how can we safely deploy this setup to production without affecting existing outbound calls?
Any guidance, examples, or documentation links would be very helpful.
Thanks in advance!