Skip to main content

Run a calling campaign

Launch outbound voice when you need AI agents to reach a list—renewals, appointment reminders, lead qualification. The flow parallels email: pick audience, choose Call Template or custom script, assign agent/voice, schedule, and monitor results in Call Logs.

Video

Video coming soon for this topic

Who can do this​

Calling create/edit permission.

Before you begin​

  • Phone Number purchased and linked
  • AI Employee with voice credentials (Retell AI connected in Credentials tab)
  • Smart List or segment with phones
  • Credits for estimated minutes

What you'll accomplish​

  • Calling Campaign created and executed
  • Outcomes logged with recordings where enabled

Step-by-step procedure​

Create campaign​

  1. Calling Campaigns → Create Campaign (/ai-voice-calling/create).
  2. Name campaign and optional description.
  3. Select audience (Smart List / filters per UI).
  4. Choose Call Template from library or build inline.
  5. Assign AI Employee / voice profile.
  6. Set schedule—immediate or windowed calling hours.
  7. Review summary → Start or Schedule.

Monitor execution​

  1. Return to Calling Campaigns list; watch status chips.
  2. Open Call Logs for per-contact outcomes (answered, voicemail, failed).
  3. Re-run failed subset after fixing numbers or credentials.

Post-call automation​

  1. Configure Smart Flow on call disposition if available.
  2. Create tasks for human follow-up on warm leads.
  3. Export metrics via Reports — Calls.

Extended guidance​

Segment pilots by disposition outcomes before scaling—voicemail-heavy lists need different scripts. If success rate flatlines, inspect Call Logs for short-duration failures (bad numbers vs hang-ups). Coordinate with sales so human callbacks trigger within SLA after AI qualifies a lead.

Practice scenarios​

Pilot 10 contacts, review Call Logs dispositions, tune script, then scale—never dial full lists on first script draft.

Sandbox validation​

Repeat the procedure in a test workspace or with two internal colleagues before customer-facing launches. Document who approved each step (marketing, legal, ops). Screenshot Verify your work outcomes for audit trails. When something fails, capture the URL, role, timestamp, and exact UI label clicked—Support resolves tickets faster with that context. Re-read See also links after your first successful run; adjacent topics often cover edge cases you have not hit yet.

Team rollout checklist​

Assign a single owner for this workflow per workspace. Schedule a 30-minute handoff training with screen share. Add the See also links to your internal Notion or wiki. Re-verify after each major product release (labels move occasionally). Pair junior staff with a senior reviewer for the first live execution. Log lessons learned in your team retro—especially permission surprises and integration timeouts.

Keep learning​

Bookmark this page and the Product module map. After major releases, re-walk Step-by-step procedure—UI labels move occasionally. Share feedback with your workspace Admin so Help stays aligned with how your team actually works.

Verify your work​

  • Campaign status shows active/completed
  • Sample contact receives call at scheduled time
  • Call Logs entry includes duration and outcome

Tips​

tip

Start with a 10-contact Smart List pilot before full-list dial—tune voice speed and script first.

tip

Open Call Templates from the hub to standardize intro, compliance disclaimer, and voicemail drop.

Troubleshooting​

| Calls fail instantly | Retell Not Connected—fix Credentials | | Wrong voice | Update template voice ID | | Campaign paused | Insufficient credits | | Duplicate dials | Exclude recently called via Smart List filter |

See also​