Compliance tools
built into every dial.
Calling-hour checks, state attempt caps, your internal DNC list, abandon-rate pacing and recording-disclosure prompts run before and during each call, with an append-only audit log. Connect your agency’s DNC.com account to add its screening to imports and to the checks before each campaign dial. EmberDial supplies the tools and the records; your agency stays the caller responsible for consent, registrations and how your team calls.
Every dial clears the gates first
State attempt caps
Florida, Maryland and Oklahoma: 3 calls per 24 hours. Maine: 1 call per 8 hours. The cap is checked before each dial, and a call over the cap is not placed. Blocked dials are written to your audit log with the reason.
Calling hours
Each campaign’s calling window in the lead’s local time (8am to 9pm by default; your agency can change it), plus built-in Texas, Alabama and Louisiana windows: Texas Sundays noon to 9pm, and no Sunday calls to Alabama or Louisiana. Dialpad calls use a fixed 8am to 9pm window. Federal holidays are blocked by default; your agency can turn that off.
Internal DNC
When an agent dispositions a lead as Do Not Call, the number goes to your internal DNC list. Checked on every future dial across every campaign. Audit-logged.
Choose how your agency handles screening
- Connected screeningUse your agency's DNC.com account for integrated screening. Vendor charges depend on your subscription and enabled services.
- Self-managed screeningIf your agency handles DNC screening outside EmberDial, record that arrangement through the self-managed attestation. EmberDial does not perform federal DNC screening in this mode.
- Registry accessWhere registry access is required, use the appropriate agency subscription. Qualifying exempt organizations can receive free access; a SAN does not automatically mean a paid nationwide subscription.
- Lead consent recordsKeep the consent evidence supplied with your leads. EmberDial can capture Jornaya and TrustedForm receipt URLs from CSV imports and from leads your vendors post directly.
- DNC.com screening during CSV import and lead posting, and before campaign dials, when configured
- State attempt caps (FL, OK, MD, ME) checked on every dial
- Calling windows checked on every dial: each campaign’s own window (dialpad calls: 8am to 9pm), plus TX, AL and LA windows
- Abandon-rate pacing in power and predictive campaigns: slows above 2.5%, one line at a time above 3%, pauses above 4.5% after at least 50 answered calls and 10 abandons
- Consent capture from CSV imports and direct lead posts (auto-detects Jornaya LeadiD and TrustedForm fields)
- Append-only audit log of compliance events
- Written internal DNC policy editor + on-demand PDF download
- Exportable CSV reports for any date range
Match the setup to your calling activity
Required registrations, registry access, and consent depend on your calling activity and applicable exemptions. An FTC exemption does not automatically remove FCC or state obligations. EmberDial supplies workflow controls and records; the platform does not determine your agency's legal exemption status.
What EmberDial checks, and what stays with you
| Control | What EmberDial does | What stays with your agency |
|---|---|---|
| Calling hours | Each campaign’s calling window in the lead’s local time (8am to 9pm by default), plus built-in windows for Texas, Alabama and Louisiana. Dialpad calls use a fixed 8am to 9pm window. Federal holidays blocked by default. | Setting each campaign’s window to the strictest rule in the states you call, and any exemptions you rely on. |
| State attempt caps | Florida, Oklahoma and Maryland: 3 calls per 24 hours. Maine: 1 call per 8 hours. Checked before each dial. | Caps in other states and your own contact policy. |
| Do Not Call | Internal DNC on every dial. DNC.com screening on import and before each campaign dial when your agency connects its account. | Registry access, your DNC.com subscription, or screening you manage outside EmberDial. |
| Abandoned calls | Power and predictive pacing slows above a 2.5% abandon rate and drops to one line above 3%. The campaign pauses above 4.5% once it has at least 50 answered calls and 10 abandoned calls. Measured per campaign over a rolling 30 days. | Choosing the dial mode for each campaign and list. |
| Recording disclosure | A prompt for the agent when the lead is in an all-party-consent state. | Giving the disclosure on the call. |
| Consent records | Jornaya LeadiD and TrustedForm columns picked up from CSV imports. | Collecting valid consent for every lead you call. |
| Audit log | Append-only. Compliance events kept for 5 years; recordings and transcripts for 24 months by default. | Exporting the records you need to keep. |
| Fees | No separate compliance fee. Calling is $99 per concurrent calling license per month plus $0.02 per connected minute. | Any DNC.com or registry charges under your subscription. |
Common questions
Do I need a separate compliance vendor?
Why does the customer bring the credentials?
What does the audit log capture?
How long are call recordings kept?
Which state rules does EmberDial enforce?
Is EmberDial TCPA compliant?
Our ATDS posture
EmberDial campaigns run in power or predictive mode, agents can also dial by hand from the dialpad, and every dial is tied to a signed-in agent. Our position is that EmberDial is not an Automatic Telephone Dialing System under the Facebook v. Duguid (2021) reading of the TCPA. Every manual dial from the dialpad writes an audit record.