Do-not-call policy

1. Lists Dials enforces

Dials checks the following lists before originating each covered communication:

• Federal Do Not Call Registry — refreshed daily.
• State do-not-call registries — for states that maintain them, refreshed weekly.
• Customer-maintained internal lists — operated through the dashboard or API and updated by the Customer.
• Industry exclusion lists — when the Customer's brand or sector requires them (e.g., reassigned-numbers checks, wireless-port-out lists).

A covered communication is, in general, a telemarketing call or text to a residential or wireless line in the United States. Different rules apply to non-telemarketing calls, charitable and political calls, and to communications outside the US.

2. Suppression logic

When a Customer instructs Dials to originate a covered communication, Dials evaluates the recipient against each applicable list. If any list returns a positive match and no recognized exemption applies (existing business relationship within the rule's window; a separate prior express written consent; charitable or political content where the rule permits), Dials refuses to dispatch and writes a denial event to the ledger. The denial event includes the recipient, the matched list, and the Customer's brand.

3. Existing business relationship and consent

A Customer may override a federal DNC suppression only by attaching, at the time of the send, a verifiable record of either (a) an existing business relationship that meets the FTC's TSR window, or (b) prior express written consent that meets the TCPA's marketing-consent standard. Override records are subject to review on complaint.

4. Internal list

Dials records every opt-out it sees, across every channel a Customer operates, on the Customer's internal do-not-call list. The internal list is honored at the boundary for the configured retention period (default ten years).

5. Inbound rules

The Customer's internal list does not suppress inbound calls or messages from the recipient. If a recipient calls or texts the Customer's number after opting out, Customer may respond using the channel of inquiry, in the scope of the inquiry.

6. Wireless number portability

Wireless number portability rules require Customers to check the reassigned-numbers database before contacting numbers that may have changed subscriber. Dials integrates with the database and refuses to dispatch covered communications to numbers that show a reassignment after the consent date on record, absent a fresh consent.

7. Carrier blocking

Some downstream carriers block traffic in addition to the rules described above. Dials surfaces carrier blocks as terminal events. Customers cannot override carrier blocks through the Dials API.

8. Recordkeeping

Suppression decisions, list-membership snapshots, and override records are retained for a minimum of four (4) years and exported to the Customer on request, in JSON or PDF.