Campaigns

Campaigns drive outbound activity at scale. Upload a contact list, pick a phone widget, schedule a start time, and Insighto dials each contact and runs the assistant against them. Use it for proactive outreach where a phone call still works best — appointment reminders that need confirmation, lead requalification, payment-due nudges, NPS surveys.

Only outbound voice campaigns are supported today. SMS campaigns and chat campaigns are not implemented. Drip / text follow-up has to be built via workflows or external tooling.

What you can do with it

• Lead requalification (B2B sales) — A SaaS company re-engages leads cold for six months. The assistant calls each, asks two qualification questions, books a meeting with sales if the answers fit. 10,000 contacts processed in a week, no SDR time.
• Appointment reminders (healthcare) — A multi-location clinic dials tomorrow's appointment list overnight. The assistant confirms, reschedules, or marks no-show — saving the front desk an hour of phone tag every morning.
• Payment-due nudges (fintech / lending) — A consumer-lending company calls borrowers two days before their due date. The assistant handles "can I pay later" by offering a one-time deferment, then logs the outcome.

What's allowed

A campaign uses one phone widget. Eligible widget types:

• phone (Twilio)
• plivo_call
• telnyx_call
• sip

You cannot run an outbound campaign on a chat / WhatsApp / SMS / Messenger widget.

How it works

Create a campaign

1. Open Outreach → Campaigns → Create campaign.
2. Give it a name.
3. Pick the phone widget that'll do the dialing.
4. Pick the contact list to call (or upload one).
5. Pick a start time — must be at least 30 minutes from now. Insighto rejects schedules with less lead time so you have a chance to cancel typos.
6. Set the concurrent calls pace — how many calls run in parallel. Capped by your plan's concurrent_calls credit.
7. Save the campaign in not_started state.
8. Flip the Enabled toggle when ready — that's what actually launches.

Statuses

Status	What it means
not_started	Created but not yet enabled.
to_be_run	Enabled and queued; will start at the scheduled time.
in_progress	Dialer is currently running through the list.
paused	You hit pause. No new calls are placed; in-flight calls complete.
completed	All contacts have been dialed.
cancelled	You stopped it before completion.

Pacing

The concurrent_calls setting controls throughput. With 5 concurrent calls and 2-minute average call length, you process ~150 contacts/hour. Bumping concurrency requires available concurrent_calls credit on your plan.

Where to next

• Phone widget — the widget that does the dialing.
• Contacts — build the call list.
• Conversations — every call lands here with transcript + recording.