Prebuilt Templates & Example Use Cases

Overview

Rather than building an assistant or squad from a blank canvas, you can start from a prebuilt template designed around a common use case. Templates give you a working system prompt, tool set, and (for squads) member structure out of the box, which you can then customize.

These templates are built as a single assistant and are the best starting point for most use cases:

• Customer Support — automates inbound support calls with knowledge base access and escalation to a human when needed.
• Sales & Lead Qualification — makes outbound sales calls, qualifies leads, and schedules appointments using branching logic based on the caller's answers.
• Appointment Scheduling — handles booking requests, checks availability, and confirms appointments with conditional routing.

For multi-agent scenarios, these templates are built as squads — multiple specialized assistants that hand a call off between each other:

• Medical Triage & Scheduling — a clinic squad with a Triage assistant that assesses symptoms, an Emergency assistant for urgent cases, and a Scheduler for booking appointments.
• E-commerce Order Management — separate assistants for order tracking/status, returns processing and label generation, and a VIP concierge service, with intelligent transfers between them.

Squads solve problems that show up in large, all-in-one assistants: models lose focus and hallucinate more when a single prompt tries to cover too many scenarios, longer prompts cost more per call, and larger contexts add latency. Splitting responsibilities across focused assistants avoids all three.

Beyond assistant and squad templates, there are ready-to-use structured-output schema templates for extracting clean, validated data from a call transcript in common business scenarios:

• Healthcare Appointment Booking — captures patient details and appointment preferences (type, department, urgency, preferred time slots).
• E-commerce Order Processing — captures customer, item, shipping, and payment details from a sales call.
• Real Estate Lead Qualification — captures contact details, property search criteria, timeline, and a lead score.

Each of these ships as a complete JSON schema you can attach to an assistant, so call data comes back in a consistent, structured format rather than free text you'd have to parse yourself.

Starting from a template in the dashboard automatically applies the Model Preset that best fits that use case — for example, a support template lands on a Balanced preset by default, while a high-stakes triage template may start on High Intelligence. You can always swap the preset afterward; doing so moves the assistant to a Customized state, as described in Model Presets.

Use a single Assistant when you're handling support, lead qualification, appointment booking, or FAQs — most use cases fit comfortably in one focused assistant. Reach for a Squad when the workflow genuinely needs multiple specialists handing off to each other: multi-step triage, routing across departments, or complex handoffs where a single assistant's prompt would otherwise have to cover too much ground. See Squads & Handoffs for how transfers, context handling, and squad setup work in detail.