Compliance in the code path, not in a policy document.

How does Assurna enforce TCPA and calling-hours rules?

In the calling path, before a number is dialed. Consent state and internal do-not-call state ride on the lead record, and calling hours are evaluated against the prospect's own time zone rather than the agent's. Because every outbound call goes through one path, including calls placed by the AI Appointment Setter, the check applies to every dial rather than to the ones an agent remembered to think about. Assurna is software and not a law firm, and this describes how the product behaves rather than guaranteeing your agency is compliant.

Why does it matter whether compliance is in the code or in a policy?

A policy describes what should happen and depends on every person following it, including your newest agent in the last hour of a hard day. A check in the calling path happens whether anyone remembers it or not. Both are worth having. Only one of them is a control you can rely on when you are not watching.

Are calls recorded, and where do the recordings go?

Yes. Recordings and transcripts attach to the lead record automatically, along with the disposition and the agent who made the call, and retention is handled by the system rather than by someone maintaining an archive. When a complaint arrives months later, the conversation is on the record that produced it.

Does Assurna scrub against the federal do-not-call registry?

Internal do-not-call state is enforced at the record: a request made on one call is honored on the next one, by a different agent, on a different campaign. We do not present federal registry scrubbing or state-level rule enforcement as active controls on this page, because we only describe what is actually running. Bring your list sourcing and your scrubbing arrangement to the demo call and you will get a straight answer about where the boundary sits today.

How are calling hours handled for a floor that sells nationally?

Against the prospect's own time zone, which is the case that breaks agencies selling across the country. An agent working late on the east coast is not the same thing as a prospect being called late on the west coast, and the system evaluates the one that matters.

Does the AI Appointment Setter follow the same rules?

Yes. It dials through the same path with the same checks in front of it. Automating outreach does not route around the rules, and if it did, it would be the single most dangerous thing you could put on a telesales floor.

What happens after the call?

Completed calls are scored against compliance dimensions and the ones that need a human look surface in an administrator review queue with the transcript attached. Random sampling finds problems eventually. Scoring every call and reviewing the flagged ones finds them while you can still do something about them.

Does Assurna hold a security certification?

No, and we will not imply one. Assurna holds no security certification today. If your governance requirements need one, say so on the demo call so nobody wastes a quarter finding out. A dedicated instance is available if your data cannot sit alongside other agencies.

Does using Assurna make my agency compliant?

No. Nothing does. Software can enforce rules in the calling path, keep the record of what was said, and put the risky calls in front of a human. Your consent sourcing, your scripts, your lead vendors, and your training are yours, and your counsel is the right person to tell you where you stand. We would rather say that plainly than sell you a feeling of safety.

Assurna is software, not a law firm, and nothing here is legal advice. These controls are how the product behaves. Whether your agency is compliant depends on your own program, your consent sourcing, and counsel who knows your situation. Read our legal disclosures.