CallTurbo Build an agent

Field guide · 2026-09-11

Outbound AI Calls: Consent, Opt-Out and Quiet-Hours Checklist

Checklist for outbound AI call consent, STOP/opt-out handling, quiet hours and records for CallTurbo campaigns, SMS and CRM.

Call center agent with headset reviewing notes at an operations desk before outbound calls

Operational guidance only, not legal advice. Confirm current rules for your jurisdiction and carriers with counsel before launching.

If you run outbound AI campaigns, consent, opt-outs and calling times decide whether your program lasts. Use this checklist before you import a list into CallTurbo.

1. Consent basis — prove why each number can be called

  • Separate existing customers / inbound inquiries from cold lists.
  • Store source, date/time, and exact wording agreed to.
  • Match type to consent: informational vs marketing; voice vs SMS need separate confirmation.
  • If you cannot prove basis, exclude the record.
  • Re-confirm aged lists before first AI call.

2. Opt-out / STOP handling — voice + SMS

  • Open each call with who is calling, why, and how to opt out by voice — e.g. say stop anytime.
  • Train agent to recognize stop, do-not-call, remove, unsubscribe, no more calls/texts — then end politely.
  • SMS: support STOP/HELP, send HELP info, confirm STOP once, then silence except as carriers allow.
  • Sync opt-outs immediately to Campaigns + CRM so redial, retry and SMS flows respect them.
  • Maintain company do-not-call list and honor requests without delay.

3. Quiet hours — respect local time

  • Store recipient timezone, not just area code.
  • Set quiet-hour windows per recipient local time in Campaign scheduling.
  • Block auto-dial/SMS outside windows, including retries and follow-ups.
  • Pause for holidays / local restrictions where applicable.
  • Log every attempt with local timestamp.

Calling-hour windows vary by jurisdiction and carrier — verify current FCC and carrier rules before you set schedules.

4. Record-keeping — what to keep

  • Consent record, recordings/transcripts, opt-out events, attempt logs, timezone used.
  • Defined retention period, accessible for complaints/disputes.
  • CRM shows: consent status, last opt-out, last attempt in local time.

5. Map it in CallTurbo

  • Outbound campaigns: separate campaigns by consent basis; set schedule windows, retry limits, auto-suppress opted-out.
  • SMS: connect STOP/HELP flows; confirm opt-out, stop further marketing texts.
  • CRM: make consent status + opt-out date required fields; use as sequence exit conditions.
  • SIP trunking / routing: keep caller ID consistent, monitor answer/complaint signals, throttle new lists.

For qualification, see Lead Qualification and AI Call Center Guide.

Pre-launch pass/fail

Source documented, opt-out tested by voice and SMS, quiet-hours tested with multi-timezone sample, CRM suppression verified, logs exportable. If any fails, do not launch.

Build your outbound agent with guardrails on.

Build your first outbound agent in CallTurbo with consent checks, suppression, and schedule windows in place from day one. Build agent · See current credit plans

Photo by Yan Krukau on Pexels (Pexels License).

Build and test the route

Turn the framework into a working CallTurbo flow.

Build an agent
Help & support