Use Case To Product Path
Start with the path that matches the operational goal.| Use case | Recommended product path | Main evidence to review |
|---|---|---|
| Lead qualification | Single Prompt Agent or Conversational Flow Agent, outbound number, post-call fields, CRM or owner notification. | Qualification result, transcript, sentiment, duration, extracted fields |
| Appointment booking | Agent function for booking, inbound or outbound number, confirmation message. | Booked slot, function result, call summary |
| Payment or renewal reminder | Batch Call with CSV variables, retry settings, call outcome export, follow-up message. | Completed calls, did not pick rows, failed rows, retry history |
| Support intake | Inbound number, triage prompt, post-call fields, support handoff. | Issue summary, escalation flag, recording |
| Multi-step follow-up | Workflow with call nodes, condition nodes, time nodes, and application nodes. | Lead history, node transitions, application success or failure |
Common Integrations By Use Case
| Use case | Helpful connections | Why |
|---|---|---|
| Lead qualification | HubSpot, Salesforce, Slack. | Send qualified context to the owner while the call is still fresh. |
| Appointment booking | Google Calendar, Gmail, Resend. | Confirm the booked time in writing. |
| Payment or renewal reminder | Stripe, Google Sheets, WhatsApp with Wati. | Check payment context, review exceptions, and send follow-ups. |
| Support intake | Zendesk, Intercom, Google Sheets. | Move issue context to the team that will handle it. |
| Ecommerce order follow-up | Shopify, Gmail, Slack. | Combine order context, written updates, and internal alerts. |
Reusable Building Blocks
Most use cases are combinations of these product pieces.Prompt and welcome message
Tell the agent what to do, how to speak, and who starts the conversation.
Dynamic variables
Personalize calls with values such as name, due date, location, plan, or assigned representative.
Post-call analysis
Turn a conversation into structured fields that appear in call details and exports.
Retries
Retry failed or unanswered calls in batch campaigns, then inspect retry chains in Call History.
Pick The Shape Of The Conversation
- One clear objective
- Branching script
- Automation after the call
Use a Single Prompt Agent for a call that can be handled by one instruction set: qualify, remind, collect feedback, or answer a narrow FAQ.
Use Case Design Checks
Can the agent succeed without external data?
Can the agent succeed without external data?
If not, add dynamic variables, functions, integrations, or a knowledge source before testing.
What is the success field?
What is the success field?
Create a post-call field that tells operations whether the call achieved its purpose.
What happens if the person does not answer?
What happens if the person does not answer?
Use batch retry rules or workflow routing instead of hoping the first call works.
What should users audit later?
What should users audit later?
Make sure the expected proof appears in Call History: transcript, recording, summary, extracted fields, transfer data, or export columns.
Related Reading
Single Prompt Agents
Use one instruction set for one goal.
Conversational Flow Agents
Use explicit branches and call paths.
Batch Calls
Run list-based outbound campaigns.
Workflows
Automate multi-step follow-up.