Listen
Speech is turned into text so the agent can understand the person — and so you can review a transcript later.
Outbound only works if policy comes first: campaign rules, a list you’re allowed to call, a hard safety check before ring, a controlled AI conversation, then your team on callbacks. Scroll the five steps, then the Tuesday appointment example—that’s the whole product story in one page.
How it works
We never just “hit dial.” Every attempt goes through your campaign settings and a safety check. If something fails, nothing rings — and we log why.
Create a campaign. Choose the purpose, mobile or landline, whether permission is required, the opening lines, and what the AI must not say.
You bring the relationship—someone who booked, joined, or opted in. Numbers that opted out go on your block list. We do not build a cold-list product for you.
Is the campaign on? Is the number blocked? Do you need permission, and do you have it? Have you called too often? If anything fails, we stop and record the reason.
If the check passes, the AI voice call runs. It introduces itself (who you are + that it’s AI + why it’s calling), does the job (for example, confirm an appointment), respects “stop,” and can request a human callback.
Staff work the callback list, review logs and transcripts, and improve scripts—without losing the safety rails.
Example
One realistic path from list to disposition — what “good” looks like without drowning in product jargon.
List + tags
Jane is on your outbound list with consent tagged for appointment reminders (you own that relationship and the lawful basis).
Pre-dial gate
Campaign is enabled, number is not suppressed, destination class is allowed, consent artifact is present, frequency caps are fine → allow. If any check failed, no carrier dial — attempt is logged as blocked.
Forced open
She answers. The agent speaks identity, that the voice is AI, and the purpose — before free-form chat.
Three ways it can end well
“Yes, that works” → outcome confirmed. “I need a person” → callback ticket for your staff (MVP is callback, not a live warm transfer). “Stop calling me” → opt-out and suppression so the next attempt never passes the gate.
Review
Your team sees the call on Call review: times, disposition, and (when live) transcript and optional recording under retention policy.
The “AI agent” is not a free chatbot with a phone. It is a short loop bounded by your campaign and platform rules.
Speech is turned into text so the agent can understand the person — and so you can review a transcript later.
Policy and campaign intent guide the reply: allowed topics, blocked topics, and required tools (opt-out, escalate, end).
A brand AI voice answers — never a clone of a real person, celebrity, or candidate. Opening disclosure is forced.
Confirm-style outcomes, do-not-call, human callback ticket, hang up cleanly. Later: domain tools you allow (e.g. lookup appointment).
Scripts and prompts are not one marketing paragraph. Your campaign sets the opening and what may be discussed; the platform keeps hard rules (AI disclosure, opt-out, no impersonation). How those layers change agent behavior is documented for operators inside the product under Agent guide.
Take the guided product tour
Five stops: this story → dashboard → sample call review → agent guide (prompts & guardrails) → test dial (gate only — no call placed).