Campaigns

Build a campaign from a CRM list, a CSV file or inbound leads, and set pacing, retries and calling hours.

A campaign is a queue of leads your team works through, with its own pacing, retry rules, calling hours and script. Managers and admins create campaigns; agents join active ones.

Lead sources

CRM list

Pick a list from your connected CRM: a HubSpot contact list, a Salesforce list view, a Zoho custom view or a Pipedrive filter. NitroDialer keeps the campaign in step with it:

new records in the list are added to the queue,
records already in the campaign get their name and phone numbers refreshed (their place in the queue is kept),
records that leave the list — converted, disqualified, reassigned — are removed from the queue if they haven't been finished yet.

Campaigns re-sync every hour and when you select Sync now. Records without a valid phone number are skipped and counted in the sync result.

CSV file

Upload a CSV with a header row. These column names are recognised (case doesn't matter):

Lead field	Recognised headers
First name	First Name, FirstName
Last name	Last Name, LastName
Company	Company, Account Name
Email	Email
Phone	Phone, Phone Number
Mobile	Mobile, Cell, Mobile Phone
Other phone	Other Phone
City	City, Mailing City
State or province	State, Province, Mailing State
Postal code	Postal Code, Zip Code, Zip, Mailing Zip
CRM record id	Record Id, Id — links the row to the CRM record so notes are written back
Consent	Consent — `yes`, `true` or `1` marks express consent

Numbers are normalised to international format (North America by default), and duplicates within a row (the same number as phone and mobile) are dialed once.

Leave the campaign empty and let leads arrive as they're created — from a CRM workflow, a form tool, Zapier or Make — through the speed-to-lead webhook or the API. Inbound leads get top priority, so the next free agent calls them first.

Lead time zones

Calling hours come from your workspace's calling region (Settings → Compliance) and are checked in the lead's time zone. NitroDialer works it out from the lead's state or province first, then from the phone number's area code (North American numbers and Australian landlines), and falls back to your workspace time zone.

Pacing and retries

Setting	Default	What it does
Wrap-up before next dial	15 s	Countdown after saving an outcome in power mode
Hang up after ringing	25 s	Unanswered calls are ended so the agent moves on
Max attempts per lead	6	Across all of the lead's numbers
Max attempts per day	2	Stops the same person being called repeatedly in one day
Default gap between attempts	180 min	Used when an outcome has no specific retry time
Retry after no answer	120 min
Retry after busy	15 min
Retry after voicemail	1,440 min (next day)
Call first	Mobile, then phone	Which number to try first

See Dispositions and retry rules for exactly how these combine.

Calling hours

Each campaign has team hours — the days and times your team dials, in the workspace time zone (Monday to Friday, 09:00 to 21:00 by default). Legal calling hours in the lead's time zone are always enforced on top. See Compliance.

Lead routing

Shared queue — the next free agent gets the best lead. Two agents can never receive the same lead.
Owner only — agents only get leads they own in the CRM. Match agents to CRM users first (Settings → Team).

Leads are ordered by priority (highest first), then by when they became due, then by when they were added. An agent's own due callbacks always come first.

Consumer or business

Mark a campaign Consumers (B2C) or Businesses (B2B). Consumer campaigns check every number against your national do-not-call list upload unless the lead gave express consent. Business campaigns skip the national list (except in the UK, where companies register on the Corporate TPS) but still follow calling hours and your internal do-not-call list.

Statuses

Draft (not dialable yet) → Active (agents can join) ↔ Paused (agents stop getting new leads; calls in progress finish) → Archived.