A stop request is a stop.

Updated September 26, 2026 · Operational guidance, not legal advice.

DialBreeze includes internal do-not-call controls. Your team supplies the eligible list, the applicable permission records and the external registry review.

Record the request during the call.

When someone asks not to be contacted, acknowledge the request without making them listen to another pitch. Use the Do Not Call outcome and record the essential context while the correct lead is open. Do not substitute an ordinary callback or an uninterested outcome for an explicit stop request.

The operator interface places Do Not Call alongside the other call outcomes. Internal DNC is a product control, not a reminder to try again with a different opener. The customer is responsible for making sure the request is reflected across the systems and campaigns used by its business, not only the screen the operator happened to have open.

Keep internal suppression separate from registry scrubbing.

The product excludes records flagged for internal do-not-call handling from its calling workflow. This is different from checking the National Do Not Call Registry or resolving the legal basis for a particular campaign. DialBreeze does not perform the customer's federal-registry scrub or establish consent merely because a number appears on an imported list.

Before a campaign, the responsible manager should confirm the source, applicable eligibility review, prior stop requests and any suppression information that must travel with the data. Obtain campaign-specific advice about federal, state and industry requirements. Neither a purchased list nor a phone number published online is a blanket instruction to call.

Preserve the decision when lists change.

Reimporting a number, copying a list or moving work between operators must not become a way to disregard a known stop request. Review how the source system represents suppression and confirm how it is handled in the destination before releasing the list for calling. Test with permitted test records rather than a real person who has opted out.

If a duplicate record appears with a different status, hold the affected contact out of calling and resolve the conflict. Do not choose the version that happens to be callable. The important outcome is that the business's suppression decision is respected wherever the contact is worked.

Do not confuse quiet hours with permission.

Per-lead quiet hours and attempt caps are additional controls. Being inside a configured time window or below an attempt cap does not make an otherwise ineligible call permissible. A callback task also does not override a later stop request. Review current eligibility before making the next attempt, especially when information has changed since the task was created.

Keep the person's request distinct from a software or carrier failure. A failed call, a wrong number, an unanswered attempt and a do-not-call instruction are different outcomes. Accurate dispositions help the next operator avoid acting on the wrong assumption.

Report an unexpected call or suppression failure.

Contact brayden@themilnerteamfl.com with the relevant account or call reference, date and the issue. A person reporting an unwanted call can include the number called and approximate time so the event can be investigated. Do not include unrelated personal information or credentials.

For an internal test failure, stop the affected workflow and preserve the record references and observed behavior. Report what was expected and what actually happened; do not repeatedly call the same person to reproduce it. Have the responsible manager confirm the correction before the contact returns to any eligible workflow.

For the wider division between product controls and campaign responsibilities, read calling controls and compliance. The federal rule itself is available at 16 CFR 310.4; applicable requirements depend on the campaign and jurisdiction.