Product
Outgoing Voice is the control plane for outbound AI phone calls: you set the rules, the agent works inside them, and your team steps in only when needed.
Journey story: How it works · Responsibility split: Compliance · This page is what you get in the product.
01
Purpose, destinations, consent tags, open, allowed topics, tools.
02
Allow or block before anything rings. Every attempt is logged.
03
Identity + AI disclosure, dialogue inside policy, tools for stop / human / end.
04
Transcript, disposition, suppressions, callback tickets for your staff.
The control plane you operate day to day. Multi-tenant organizations: each workspace has its own campaigns, lists, and tickets.
Each call type has its own settings: purpose, mobile or landline, whether a consent artifact is required, opening script, allowed and blocked topics, and which tools the agent may use. Those fields are the knobs—not a free-form chatbot prompt box.
Before anything rings: campaign on? number suppressed? destination allowed? consent tag present when required? under frequency caps? Fail → no dial, reason recorded. Pass → eligible for live placement when telephony is connected.
Listens, decides within policy, speaks with a brand AI voice. Forced open: who you are, that it’s AI, why it’s calling. Human path in MVP is a callback ticket—not a live warm transfer.
Org-wide (and campaign-scoped) block lists. Opt-out on a call writes here so the next attempt never clears the gate.
When the person asks for a human—or the agent escalates—we open a ticket. Your staff returns the call on your SLA. We don’t drop the request on the floor.
Test a number against the gate with no live dial. For completed calls: timing (answer, first AI response), disposition, searchable transcript, optional recording under retention limits.
These are our most popular starting points—not an exhaustive catalog. Each is Pilot ready and Template ready (full config, seeded for new orgs). Design partners often begin with appointment confirm; turn others on when your lists and content are ready.
People who already booked. Confirm, reschedule path, opt-out, or ask for a person. Primary design-partner queue.
Consented informational / GOTV-style calls—not a politics free pass. Same gate and callbacks.
Main or after-hours number: company info, hours, take a message, callback ticket. Same voice stack.
Day-before or morning-of remind on the same consented relationship as confirm.
Arrival window updates for field and home services—consented customers only.
Memberships, classes, and events for people who signed up—containment-friendly.
Inbound vs outbound: Outbound uses the pre-dial safety gate. Inbound uses the same agent stack and call review; the “list” is your DID and knowledge base. Starter configs: /templates · Need a type that isn’t listed? We’ll customize it.
Built for consented queues you already run. Starters help you evaluate; we customize agents to your exact program when you pilot.
See Compliance for the responsibility split.
See it or talk pilot
Walk the control plane with demo data, or start with appointment confirms for a real queue.