Controls help enforce a policy.
They do not create permission.

How DialBreeze helps.

These defaults are on in every account. They are aids to your compliance program, not a guarantee that any call is lawful:

• Internal do-not-call list. Numbers on it are excluded from dialing.
• Opt-out capture. A stop request is recorded with the Do Not Call outcome, which removes the number from dialing.
• Quiet hours. Calls only go out between 8am and 8pm in the called number's local time by default, worked out from its area code; you set your own hours in settings. Outside that window the lead is skipped and the reason is recorded.
• Attempt caps. No more than 3 calls to one number in any rolling 24 hours (a ceiling you can lower, never raise). Up to 15 call attempts per lead, ever; you can set a lower limit.

These controls do not scrub the National Do Not Call Registry, do not establish consent, and do not replace your review of each list.

What the product controls.

DialBreeze includes internal do-not-call handling, per-lead quiet hours and attempt caps. The operator can record the call outcome, add a note and set a follow-up task. These controls support a configured campaign policy; a visible button or a callable queue is not a legal conclusion about the underlying number.

Use internal DNC for a stop request, not an ordinary callback status. Configure calling windows according to the approved policy for the affected contacts. Treat an attempt cap as a maximum within that policy, not a target to exhaust. A saved task does not override a new stop request or another change in eligibility.

The DNC policy covers stop requests and suppression during list work. The list workflow explains the operational review before a list enters a session.

What the customer supplies.

Your business owns the source and eligibility review, applicable consent records, federal-registry scrubbing and any additional state or industry requirements. It decides which people may call, what may be said, whether recording is permitted and what happens when the contact's request or status changes. DialBreeze does not establish those facts by importing a CSV.

Give operators an approved policy they can apply, including a clear hold-and-escalate path when information is missing. A manager should be able to identify the source of the list, the last relevant review and the person accountable for releasing the campaign. Keep that evidence outside the operator's memory alone.

Human-operated is not an exemption.

A human handles DialBreeze conversations. That product distinction does not remove duties associated with prerecorded messages, abandoned calls, calling times, identity, recording or do-not-call handling.

Voicemail drop plays a prerecorded message, even when a human selected it. Multi-line dialing can create a second live answer while the operator is already occupied. Do not infer compliance from the words “power dialer,” a three-line limit or a promise that an operator is present. Evaluate the actual calling behavior and the rules applicable to the campaign.

The federal Telemarketing Sales Rule treats abandonment and prerecorded messages separately in 16 CFR 310.4. The abandonment safe harbor is in 16 CFR 310.4(b)(4), not paragraph (b)(3). See the safe-harbor guide for the evidence to discuss with counsel. This page does not certify that a DialBreeze deployment satisfies it.

Use the called person's location for time review.

A team's office clock is not a reliable substitute for the contact's local time. Check the location information and the approved calling window before releasing a mixed-region list. A mobile area code alone may not establish where the person is. When the time zone is uncertain, hold the record for review rather than guessing that it is inside the window.

As a straightforward time-conversion example, 7:45 p.m. Eastern is ordinarily 4:45 p.m. Pacific, not 10:45 p.m. Pacific. The conversion alone does not decide whether a particular call is allowed; applicable rules and the contact's circumstances still need review. The calling-hours guide owns the working checklist.

Recording needs its own decision.

Do not assume that permission to place a call is permission to record it. Determine the relevant jurisdictions and recording requirements with the person responsible for the campaign. Operators need an approved disclosure or other required process, and a clear response when someone objects or the policy is uncertain.

Collect only information the workflow needs, control access and review important statements against the audio. The Breeze and Jetstream call notes is an operational preparation aid, not a state-by-state legal opinion.

Test controls without contacting an opted-out person.

Use permitted test records to inspect the configured DNC, quiet-hours and attempt-cap behavior. Record the expected outcome before the test, then preserve the observed result and the relevant configuration. Test an ordinary eligible case as well as a blocked case so the result does not hide a general failure to dial.

If an ineligible record reaches the calling workflow, stop the affected session and report the issue. Preserve the record reference and the circumstances; do not repeatedly contact a real person to prove the failure. Resume only after the responsible team has reviewed the correction and the permitted test passes.

Use the right specialist for the campaign.

Real estate prospecting, final-expense insurance and Medicare-related marketing do not have identical requirements. An enrollment calendar is not permission to cold-call. The Medigap page is limited to correcting the enrollment distinction and identifying the need for specialist review; it is not an approved Medicare campaign playbook.

Keep a dated policy, an accountable reviewer and a procedure for changes. The official sources and the actual configuration should be checked when decisions are made. A disclaimer on a marketing page does not repair an ineligible list or an operator instruction that contradicts the policy.