Launch a campaign

You need an active workspace with voice enabled, funds, a caller-ID number and an active hosted agent. There is no campaign switch to request.

Before you launch: test it

• Talk to the agent in your browser, capped at 180 seconds, for voice, recognition, latency and interruptions. See Test an agent.
• Run a simulation suite in the Simulations Lab: scripted callers, your own pass and fail rules, text or voice.
• A conversation workflow adds Chat for wording and branches, and Phone, which arms one number so your next call to it, from the caller ID you declared, answers with the pinned draft.
• None of these prove the carrier route. Place one real call to your own number, or a one-contact campaign with yourself.

Build the list

• Upload a CSV or an Excel workbook (.xlsx), one row per person, or paste rows. Only the phone column, in international format, is required.
• A workbook is read in your browser: the first sheet, the first row as column names, then the same mapping, preview and per-row report a CSV gets. Date and number cells arrive as the text the sheet shows — no 46280 in place of a date. Keep account references and phone numbers in text-formatted columns; a spreadsheet stores a number as a float and rounds anything past 15 digits before you export it.
• Up to 10,000 rows per import. Duplicates are skipped, invalid numbers reported per row.
• Every other column becomes a variable: 28 per contact, 512 characters each, 4 KB in total. No secrets.
• Time zone defaults from the number's country. Calling hours run in each contact's zone, or one fixed zone.
• Numbers on your do-not-call register are marked and never dialed.

Per-customer data in the call

• The wizard's Message preview fills a pasted line with the first contact's values. It previews in your browser, not on the call.
• Each attempt carries that contact's variables as the call's context, plus campaign id, run id, attempt number and name.
• A free-form agent does not read them aloud on its own, and nothing fills a {{field}} placeholder in a browser test.
• A conversation workflow states them: a read tool's projection is served from that context, and a step flagged discloses debt fills its {{field}} placeholders — only after the caller passed your verification step. See Serving a read tool.
• The Payment reminder from contact variables starter template is exactly that: its one read tool projects the contact's obligations list, and its disclosing step reads every loan out through a section ({{#obligations}} … {{/obligations}}) in the words the template authored — no customer endpoint. Several rows per phone number in your sheet become one contact with that list when you turn on Several rows per phone number in the contacts step. See Several obligations on one account.
• Otherwise give it a read tool that fetches the fact mid-call: an Integration, whose URL and secret the model never sees, or a webhook tool.

Create and launch

• Contacts — the list, the purpose, and the consent basis: existing customers or explicit consent.
• Agent and numbers — the hosted agent and the numbers to rotate caller ID across.
• Schedule and retries — calling hours per weekday, at most four windows a day, and a retry preset: sales, collections, single attempt or custom.
• Review and launch — contact count, spend estimate, and a preview of every launch check.

Launch runs one check against your workspace capabilities: no sanctioned destination, workspace active, voice enabled, every country on your allowlist, a permitted purpose, a declared consent basis. Caps apply per call.

Watch the results

• The campaign page shows audience, remaining, pick-up rate, outcomes and spend.
• Each attempt opens its call: recording, transcript and any post-call extraction. See Read call evidence.
• Export CSV gives the disposition per contact, and webhooks push campaign.launched, campaign.contact.completed and campaign.completed. See Post-call results.

Common questions

• Why did my launch go to review? Your workspace is not active, voice is not enabled, or a destination is not on your allowlist.
• Why did a country need review? It is not on your workspace's destination list yet.
• Why is a contact skipped? It is on your do-not-call register, its calling hours never reopen, or the campaign was cancelled. A contact whose window is merely closed waits for the next one.
• Can I change settings after launch? Pause, then change hours, caller IDs, retries, concurrency and end date. List, agent, purpose and consent are locked — duplicate to change those.
• How many calls a day? Whichever workspace cap binds first. The Capabilities page lists them.
• How do I stop it? Pause keeps the remaining contacts. Cancel ends the run and skips them.
• Which lists may I call? Your own customers, or people who explicitly agreed. See Policy and outbound.