Compliance you can't switch off.
FiveFacts AI puts the compliance inside every touch instead of a policy PDF. Five gates sit between an upload and a phone: per-state calling windows enforced in code, one-way STOP opt-outs, DNC suppression checked on every dial, a carrier gate on every text, and a pullable audit log. Consent basis and list origin stay the client's; everything after intake is enforced in code. Machinery, not legal advice.
Everyone selling into this market says "TCPA compliant" and hands you a policy PDF. This page is the other thing: the machinery that governs every dial and every text, gate by gate. None of it is optional. There is no tier where it turns off, and nobody on our side can turn it off for you.
Five gates between an upload and a phone.
These controls sit inside the calling and texting path itself. Load-bearing machinery, in the order a record meets it.
Per-state calling windows, enforced in code.
Every dial is checked against the merchant's state window before it is placed. The check runs inside the dialing path itself, on every attempt. Outside the window, the dial never leaves the machine. It cannot be talked into a call outside the window, because there is nothing to talk to. All 50 state calling windows, zero judgment calls.
One-way opt-outs. STOP is terminal.
A merchant who says STOP is out: instantly, permanently, across voice and text. The record latches, and the latch is one-way by design. No re-upload flips it back and no cleanup script un-latches it. There is no re-activate button anywhere in the machine. Opt-out is a terminal state.
DNC suppression, checked on every dial.
The do-not-contact gate fires at the moment of dialing, not just at list load. A record that was clean yesterday and latched last night does not get called today. Per dial, every dial, retries included. The gap between "checked at upload" and "checked at dial" is where depositions come from.
A carrier gate on every outbound text.
Every text passes a carrier-compliance gate before it leaves. Language and formatting that carriers filter gets stopped at the gate instead of sent out to burn the number. Behind it, the posture is registered traffic under your brand from one stable sender identity: no gray routes, no rotating pools. A burned number delivers nothing, which is why the gate sits in front of every message instead of in a best-practices doc.
An audit log you can actually pull.
Every contact attempt, call and text, is logged with timestamps and outcomes as a per-record contact history. When your lawyer asks what happened on a record, you hand them the log: an export, not a reconstruction from memory. If a carrier or a regulator asks, same answer. One log, pullable on demand.
What the log says when you pull it.
Every gate writes down what it did. Pull a record and this is the shape that comes back.
Who owns what. In writing.
The first question a competent lawyer asks is where the responsibility line sits. Most vendors mumble. Our answer takes two sentences.
Yours: consent and origin
Consent basis and list origin belong to you. Where the records came from, and the legal basis for contacting them, is your side of the line. It's your paper. You know it; we don't pretend to.
Ours: everything after intake
From the moment data hits the machine, the calling windows, the opt-outs, the gates, and the audit trail are enforced in code by us. Every record, every dial, every text. The line is written down, not implied.
Compliance machinery, not legal advice. We build and enforce the controls; your counsel owns your compliance strategy.
In MCA, the lawsuit is never hypothetical.
Generic tools will dial anything you upload.
Feed a CSV to any horizontal dialer and it starts dialing. Windows, opt-outs, suppression: your problem, covered somewhere in a help-center article. That posture survives in industries where nobody sues. MCA is not that industry. The plaintiff's bar has this vertical bookmarked, the demand letters are templated, and aged paper, the exact paper worth working, is where consent trails run thinnest. A tool that dials anything is a liability with a login.
The gates are why the machine gets to run at all.
The only reason software can work an entire aged book 24/7 with nobody hovering is that the rules ride inside every touch. A rep under quota pressure freelances. The machine cannot, because there is nothing to freelance with. Strip the gates out and you don't have an opener, you have exposure at scale.
The hard part is the point.
Anyone can rent a voice API and start blasting; the demo takes a weekend. Window enforcement, one-way latches, per-dial suppression, per-message carrier gates, and a log that holds up when somebody hostile reads it do not take a weekend. Generic vendors treat all of that as overhead and skip it. In this industry, skipping it is how vendors end up as case captions.
Bring your counsel; we like operators who have one. If they want to inspect the machinery, we pull the logs and walk them through the gates.
Try to make her break one.
Apply for the demo and play the hostile merchant: stall her, brush her off, lowball your revenue. Then load the book, a slice of it, and let your counsel watch the log fill in.