1. Approve the audience and list source

Document where each record came from, why the person is eligible for the campaign, which jurisdictions are involved, and which fields are reliable. A purchased or imported record is not automatic permission to call.

Apply existing suppression lists, customer preferences, duplicate checks, exclusions, and any campaign-specific eligibility rules before records reach the dialer.

  • List owner and source documentation.
  • Audience relationship and campaign purpose.
  • Required consent or other legal basis.
  • Suppression, exclusion, and duplicate rules.
  • Process for correcting inaccurate contact data.

2. Define the reason for the call and the qualified outcome

The setter needs a truthful reason for calling and a clear explanation of the next step. Define what is being offered, who it is suitable for, what the setter may promise, and which questions determine whether an appointment is qualified.

Write the completion states before the script. A record may become a qualified booking, callback, referral, decline, request to stop contact, wrong number, ineligible prospect, or escalation. Each state needs a corresponding system action.

3. Build a script that supports conversation

The script should cover the opening, caller identity, required disclosures, reason for the call, qualification questions, approved answers, common objections, booking language, confirmation, and close. It should guide the setter without forcing every prospect through an unnatural monologue.

Setters also need a clear boundary. Questions about pricing, technical details, policy, contracts, or sensitive account information may require transfer, callback, or written follow-up from an authorized person.

Test the script aloud

A script can look clear on a page and still sound confusing during a real conversation. Practice the normal path, interruptions, objections, and polite exit.

4. Protect the calendar and confirmation process

Define the appointment types, durations, available calendars, territories, buffers, lead times, owner assignment, required fields, and rules for rescheduling or cancellation. The setter should never guess where a meeting belongs.

Confirm the date, time, time zone, contact method, expected participants, and purpose with the prospect. Send the approved confirmation and make ownership of reminders or later changes explicit.

5. Configure the dialer, caller identity, dispositions, and CRM

The dialer setup can include pacing, callbacks, calling hours, agent queues, caller ID, list priority, recordings where permitted, and stop conditions. GOautodial or another platform should be configured around the approved campaign rather than left with generic defaults.

Every disposition should answer a management question or trigger a real next action. Define required notes, CRM fields, calendar actions, notifications, suppression updates, and who resolves failed records or integrations.

6. Train, review quality, and measure verified outcomes

Training should include the business context, campaign purpose, audience, script, qualification, systems, required disclosures, contact preferences, escalation, and role practice. Quality review should score the behaviors that matter to the campaign.

Useful reporting can include records attempted, contacts reached, qualified conversations, appointments booked, callbacks, declines, suppressed records, data issues, and quality findings. Attendance or sales measures require reliable downstream data and shared definitions.

  • Calibrate call reviews with approved examples.
  • Separate setter performance from list and system problems.
  • Track appointment quality, not only booking count.
  • Review objections before changing the script or audience.
  • Expand only after the complete record and calendar flow works.