Skip to main content

Calling overview

Calling Campaigns (/ai-voice-calling) runs outbound AI voice programs at scale. Supporting surfaces include Call Templates (script/voice presets), Phone Numbers (/ai-employees/phone-numbers and /phone-number-marketplace), and Call Logs (/call-logs). Voice agents typically come from AI Employees with Retell credentials.

Video

Video coming soon for this topic

Who can do this​

Users with Calling Campaigns permission.

Before you begin​

  • Credits for minutes
  • At least one purchased Phone Number
  • AI Employee configured for voice with credentials
  • Contact list with valid phone numbers

What you'll accomplish​

  • Map of calling stack from number → campaign → logs
  • Test call connects with expected voice
  • Path to Run a calling campaign

Step-by-step procedure​

Calling Campaigns hub​

  1. Sidebar → Marketing → Calling Campaigns.
  2. Toolbar: Refresh, Call Templates, Create Campaign.
  3. Filter by search, status, and date (same pattern as email campaigns).
  4. Table shows campaign progress, success rate, recipients.

Phone Numbers​

  1. Marketing → Phone Numbers or open /phone-number-marketplace to purchase.
  2. Assign number to AI Employee or campaign per UI.
  3. Verify caller ID on a test handset.

Call Logs​

  1. Open Call Logs (/call-logs) from Marketing or Inbox links.
  2. Review inbound/outbound history, recordings, transcripts when available.
  3. Managers use Reports — Calls for rep metrics.

Integration points​

  • Smart Lists define audiences.
  • Smart Flows can trigger follow-up tasks after call outcomes.
  • Command Centre monitors AI workforce load during heavy campaigns.

Extended guidance​

Voice programs fail quietly when credits dip mid-campaign—monitor Credits Dashboard hourly on launch days. Align calling hours with recipient time zones even when AI can dial 24/7—local regulations still apply. Use Call Templates to enforce mandatory compliance intros; do not rely on ad-hoc agent prompts alone.

Practice scenarios​

Place a test inbound call to a purchased number and an outbound Calling Campaigns call—confirm both rows in Call Logs.

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​

  • Test call appears in Call Logs
  • Campaign moves from draft to active/completed
  • Success rate visible on hub stats

Tips​

important

Confirm local telemarketing and recording consent laws before launching outbound AI voice.

Troubleshooting​

| No dial tone | Phone number not assigned | | Agent silent | Retell credentials missing on AI Employee | | Zero connects | DNC numbers; scrub list | | Missing menu | calling_campaigns module disabled |

See also​