How we keep compliance.
The exact mechanisms DialerSeat uses to enforce TCPA and FTC TSR rules in software. The receipts page for the "we take compliance seriously" claim.
Compliance is the floor, not a feature.
Most dialers treat compliance settings the way airlines treat seat selection — technically available, but inconveniently buried, and you can opt out for any reason. We took the opposite approach. Every rule on this page is enforced at the architecturelevel, which means it's not a checkbox in a settings panel that someone can disable at 11 PM on a quarter-end deadline. It just happens.
That principle is the whole point. If you'd like the broader context — why these rules exist, who wrote them, and why so many incumbents treat the fines as a cost of doing business — read why is compliance important? first.
Every rule, every enforcement point.
1. Calling-time window enforcement
The TCPA prohibits outbound calls before 8 AM or after 9 PM in the called party's local time zone. Every lead in a DialerSeat campaign has a phone number; before every dial, we resolve that number to its time zone (via NPA/NXX lookup) and check the current local time at that lead's location.
If the lead is currently outside its calling window, the dial doesn't fire. The lead gets a TCPA_BLOCKEDdisposition with the timestamp, and the campaign engine advances to the next eligible lead automatically. The agent doesn't have to think about it — and there's no setting to disable this.
2. Predictive abandon-rate monitoring
For predictive campaigns, the abandon rate is the number that matters. The FTC TSR caps abandoned calls at 3% of answered calls, measured on a rolling 30-day window. Cross that line and the safe harbor evaporates.
Our pacing controller computes the rolling 30-day abandon rate continuously — recomputed every 5 seconds while a campaign is active. The live rate is displayed on the agent terminal so nobody has to log into an admin panel to see where they stand.
3. Auto-degrade at 2.5%
The legal cap is 3%, but waiting until you're at 3% to intervene is too late. When the rolling rate hits 2.5%, the controller automatically degrades the campaign to 1× lines per agent (effectively progressive mode). It stays degraded until the rate drops back below 2.0%, then resumes the configured multiplier.
That 0.5% buffer is deliberate. It means a sudden answer- rate spike — caused by a bad list, a great script, or a statistical fluke — gets caught at 2.5% rather than at 3.1%. You should never see your campaign cross the legal threshold even under abnormal conditions.
4. The 8-agent multi-line gate
Predictive's mathematical advantage over progressive depends on having enough concurrent agents that statistical smoothing dampens variance. With 2 agents on a 2× campaign, you have 4 lines in flight; one unexpected pickup can spike your abandon rate dramatically. With 10 agents on a 2× campaign, you have 20 lines in flight; the same surprise event barely moves the needle.
DialerSeat's predictive controller currently engages multi-line dialing only when 8+ concurrent agents are active on the campaign. Below that threshold, the campaign runs effectively as progressive even if predictive is configured. We surface this in the dialer with a banner so nobody is surprised.
5. AMD pre-screen on progressive and predictive
Answering Machine Detection runs on every progressive and predictive call by default, via Telnyx's native call detection. Machine-detected calls drop server-side and never reach an agent — which means the abandon-rate math isn't polluted by phantom "answered" calls that are just voicemail greetings.
The AMD result is stored on every call record. How AMD works has the full breakdown.
6. Ring duration ≥ 15 seconds
Per § 310.4(b)(4)(i) of the TSR safe harbor, an unanswered call must ring for at least 15 seconds (or 4 rings) before being treated as no-answer. Our outbound calls are configured to honor this duration. Calls that ring through are not eligible for early disconnect.
7. Recorded notice on abandoned calls
When an abandoned call doesoccur — meaning a human answered and no agent was available within 2 seconds — the TSR safe harbor requires a brief recorded notice identifying the seller and the call's purpose, per § 310.4(b)(4)(iii). Every DialerSeat campaign has this configured by default with a sensible generic notice; campaign owners can customize the recording per campaign.
8. STIR/SHAKEN attestation
Outbound calls placed through DialerSeat go through Telnyx, which attests calls at the A level where the call path supports it. This is the carrier-level proof-of-identity that downstream carriers use to decide whether to label your call as spam, "Likely Scam," etc. A-level attestation doesn't eliminate spam-labeling risk, and attestation level can vary by number, route, or downstream carrier — it's the strongest level available, not a guarantee for every call.
9. Records: 24 months minimum, exportable
Every dial attempt, AMD result, agent assignment, disposition, abandon event, and calling-window skip is stored and retained for at least 24 months — the TSR's record-keeping floor. Records are exportable from your dashboard for compliance audits, internal QA, or any other reason you need them.
Call recordings are the one exception:they're retained for 30 days, then automatically deleted (see our Privacy Policy). Download recordings before the 30-day window closes if you need to keep them longer — the surrounding call record (disposition, duration, AMD result, timestamps) stays in your dashboard for the full 24 months regardless.
What we don't do for you.
Compliance is a layered problem. The list above covers the dialer-side layers — the parts that have to happen during the call itself, on the platform that places the call. There are other compliance layers that fall on you, the campaign owner, and which no dialer software can fully automate:
CONSENT RECORDS
The seller is responsible for prior express written consent. We store consent metadata per-lead so you can show it on demand, but you supply the consent itself.
NATIONAL DNC SCRUBBING
You are responsible for scrubbing your list against the National DNC Registry before upload. We're evaluating commercial DNC integrations; not in yet.
LITIGATOR SCRUBBING
Commercial databases of known TCPA plaintiffs exist. Scrubbing against them is industry best practice for high-volume dialers. Not integrated yet.
STATE-SPECIFIC RULES
The 8 AM–9 PM window is federal. Several states impose stricter rules (call frequency caps, holiday restrictions, registration requirements). Those are on you.
We list these openly because that's how we'd want a platform to talk to us. A dialer that claims to handle every layer of compliance for you is either lying or charging you a lot more than $35/week.
Three scenarios.
Scenario A: You upload a list at 11 AM ET
Your list contains 5,000 leads across all four U.S. time zones. When dialing starts, the system filters in real-time: leads currently in their local 8 AM–9 PM window are eligible, leads outside it are skipped with TCPA_BLOCKEDand re- queued for when they enter their window. By 2 PM Pacific you'll have called a different mix than you did at 11 AM Eastern. The agent never thinks about it.
Scenario B: Predictive abandon rate spikes
You're running predictive at 2.0× with 6 agents. A campaign on a Tuesday afternoon hits an unusually high answer rate — maybe a fresh batch of warm leads dropped in — and your in-flight calls outpace agents being free. The 30-day rolling abandon rate ticks up to 2.51%. Within 5 seconds, the controller cuts you back to 1.0× lines. You keep dialing, but as progressive, not predictive. When the 30-day average works its way back below 2.0%, you resume 2.0× automatically.
Scenario C: You get an audit request
An attorney asks for records of every call placed to a specific phone number over the last 18 months. You filter the calls log to that number, see every dial timestamp, AMD result, agent who took the call, disposition, recording link, and any TCPA-window skips. Export the result to CSV; hand it over. You did the right things, you have the proof.
The platform should make doing the right thing the default.
That's the design philosophy. Compliance shouldn't require expert knowledge of 16 CFR 310. It shouldn't require remembering to flip a switch. It shouldn't require trusting that your agents will check the lead's time zone before every dial. It should just be how the platform behaves.
We obviously can't guarantee your compliance — that depends on what you actually do with the platform, what consent you have, what state you're calling into. But we can guarantee that the dialer itself won't be the reason you end up in trouble. That's the line we drew, and we held it.
Other explainers
Compliance you don't have to babysit.
The 3% cap, the 8 AM–9 PM window, AMD, STIR/SHAKEN, 24-month records — enforced in software, not in policy docs. $35/week per seat, every mode included.