First Campaign Checklist

Configure a campaign correctly before opening the dialer.

What this covers

Set up a campaign from /campaigns with all required values, add campaign users, and upload the CSV call list.

When to use this

Use this before opening the dialer for your first campaign.

Before you start

  • You have at least one active Application you can access.
  • You have at least one campaign user assignment with role `Agent` (solo users can assign themselves as Agent).
  • Your CSV call list file is ready.

Steps

  1. Open /campaigns , click New Campaign , and select an active Application you can access.
  2. Choose a provider phone number from the dropdown. If the list is empty, verify the selected Application has provider numbers/caller IDs available and credentials are valid.
  3. Complete required fields (Name, Start Date, Campaign Type, Ringing Timeout) and assign at least one campaign user with role Agent .
  4. Click Save and, after success, upload your call-list CSV from the campaign call-list action.

Important fields and options

Campaign basics

Name, Start Date, Campaign Type, and Ringing Timeout are required.

Application selection

Only accessible active Applications are eligible for new campaigns.

Campaign users

At least one assigned user must have role `Agent`; `Supervisor` can be added but does not replace this requirement.

Validation and common errors

  • A successful create flow confirms: "Campaign saved successfully. Now upload your call list."
  • If no Agent is assigned, campaign creation fails with validation that at least one Agent is required.
  • CSV upload accepts only supported CSV/text types up to 5 MB.

Notes

  • Start Date uses your profile timezone in the form and is stored consistently for scheduling; verify the displayed local date/time before saving.
  • Campaign Type options are loaded from active available types (for example Calls/SMS/Email depending on environment); choose the option that matches your outbound workflow.
  • If Ringing Timeout causes provider-side issues, retry with a conservative value (for example 20–30 seconds) and re-test with one sample call.

Related guides