Outbound Voice Agents

An Outbound Voice Agent is a long-running AI agent dedicated to a single outbound calling job — say, "the appointment-reminder agent" or "the warranty-renewal agent". Unlike a one-off broadcast, it keeps running indefinitely, picking up new contacts as they enter the queue and dialing them on a schedule you control.

Use a Voice Broadcast (Outbound SDR) when you have a fixed list to dial today. Use an Outbound Voice Agent when calls trigger continuously from your CRM, your scheduling system, or a webhook.

What It Does

• Calls on triggers — A new contact lands in the queue (via webhook, CRM event, or scheduled cron) and the agent dials them automatically.
• Owns one job, well — Each agent has one purpose, one script, one voice. Easier to tune, easier to debug, easier to scale.
• Retries gracefully — Voicemail-only on attempt 1? It retries on attempt 2 in the same recipient's local mid-morning window. Configurable per-agent.
• Hands off cleanly — When a call hits a human-needed outcome (booked, refund, escalation), the agent fires a webhook or pushes to your CRM and stops calling.
• Reports per-agent — Every agent has its own analytics, transcript log, and outcome breakdown.

Setup Guide

Step 1: Launch a New Agent

Go to the Launch screen in the agency dashboard and pick Outbound Voice Agent. Name the agent for the job it owns ("Appointment Reminders", "Maintenance Renewals", "Win-Back Q3").

Step 2: Configure the Script

Write the opening line and the system prompt — same shape as inbound SDR or Outbound SDR. The agent will use these on every call. Add FAQ entries if recipients are likely to ask predictable questions.

Step 3: Define the Trigger

Decide how contacts enter the queue:

• Webhook — POST a contact to the agent's webhook URL from any external system. Best for event-driven jobs (form submission, ticket open, calendar booking).
• CRM event — Stage transition, tag added, custom field flipped. Configured in the CRM automation builder.
• Scheduled CSV pull — A daily/weekly cron runs a saved list query and feeds new contacts to the queue.

Step 4: Set the Calling Window

Pick the days and hours the agent is allowed to dial. Defaults to Mon-Fri 9am-6pm in the recipient's local time. Configure retry rules — how many attempts, how long between, and what happens after the final attempt (mark as missed, hand off to human, etc.).

Step 5: Connect Outcomes

For each outcome the agent can reach (booked, interested, wrong number, DNC), pick what happens next — fire a webhook, write a CRM activity, send an email digest, or stop processing.

Step 6: Test, Then Enable

Send a test contact through the queue. Listen to the recording. Tune the prompt. When you're happy, flip the agent to Enabled and it starts processing the live queue.

Outbound Voice Agent vs. Outbound SDR — Which Should You Use?

If you have…	Use…
A fixed list to dial today (one-off campaign)	Outbound SDR — voice broadcast
An always-on stream of contacts (webhook / CRM trigger)	Outbound Voice Agent
A weekly recurring campaign over the same list	Either works — agents are easier if the list grows; broadcasts are easier if you want a discrete report each week
Multiple distinct jobs (reminders + win-back + onboarding)	One Outbound Voice Agent per job — keeps scripts and analytics clean

Billing

Outbound Voice Agents use your shared fuel credits:

• 25 credits/min ($0.25/min) per outbound call, 30-second minimum.
• 200 credits/mo ($2.00/mo) per active outbound agent (covers the dedicated phone number it dials from).
• No charge for unanswered calls under 6 seconds.

Best Practices

• One agent per job — Don't mix appointment reminders and reactivation calls into the same agent. Separate agents = separate scripts, separate analytics, separate tunability.
• Start with a tight calling window — Run the first week 10am-1pm in recipient time. Expand once you've confirmed the script holds up.
• Always test against 5 friendly numbers first — Same rule as broadcasts. Listen to recordings. Tune.
• Wire outcomes to your CRM, not just an email — Email digests rot. CRM activities don't. Configure outcomes to write a structured activity row so the data stays useful.
• Set a sensible retry policy — 3 attempts max for most jobs, with at least 24 hours between. More than that erodes trust in your caller ID.