What disclosure and compliance rules does Chloe follow on calls?
Chloe has to tell every lead she's an AI, and that the call is being recorded, before the conversation goes any further. That's not optional, and it shouldn't be, regardless of how it might affect a conversion rate.
An AI agent calling real people on your behalf isn't just a sales question — it's a compliance one, and treating it purely as the former is how businesses end up with problems they didn't see coming. Close builds in some baseline requirements automatically, but plenty of the responsibility still sits with you, and it's worth knowing exactly where that line falls before you scale a calling program to any real volume.
This matters more the further your business is from a straightforward, simple B2B pipeline. If you're calling consumers, regulated industries, or leads outside your home state or province, the compliance surface area gets bigger fast, and it's worth taking seriously from the very outset rather than treating it as an afterthought.
What does Chloe disclose automatically?
At the start of every single call, she identifies herself clearly as an AI agent and notes that the call may be recorded for quality and training purposes. This isn't a setting you can turn off or soften — it's baked directly into how she operates by default, which is exactly how it should work given what's at stake.
What's still your responsibility, not Chloe's?
Consent for the leads you're calling in the first place, before Chloe ever dials. Time-of-day calling restrictions that vary by state or region. Do-not-call list compliance, which is entirely on your list hygiene, not the AI's judgment. Chloe handles the disclosure on the call itself. She doesn't audit whether you should be calling that number at all before she picks up the phone.
Where do call recordings actually go, and who can see them?
Every call is transcribed and logged directly on the lead record inside Close, without ever leaving the platform your team already uses daily. Nothing routes through a third-party AI vendor separately — your data stays inside the platform, reviewable by your team at any time, with no separate login or export process required.
What about leads outside the US who might have different rules?
Voice calling is currently limited to US and Canadian numbers, but compliance requirements still vary meaningfully by state and province even within that footprint. Don't assume one blanket policy covers every lead uniformly — check the specific rules that apply to where your leads actually live before you scale a segment up.
What should you actually check before scaling Chloe up?
Whether your lead sources have the consent language you need baked into how they were collected, whether your state has specific AI-disclosure or recording laws beyond what Chloe already handles automatically, and whether your do-not-call suppression list is actually current and being enforced. Get a real, specific answer here, not a guess — this is the one area where 'probably fine' genuinely isn't good enough.
It's worth a short conversation with counsel if you're calling into a regulated industry or a state with stricter telemarketing rules than most. That conversation is cheap insurance compared to the alternative of finding out the hard way after the fact.
How does this compare to the compliance bar for human reps?
In most respects, it's the same bar, just enforced more consistently. A human rep can forget to mention a recording disclosure on a rushed call. Chloe can't skip it — it's built into every single call by default, which actually makes compliance easier to demonstrate later if it's ever questioned, since there's a full transcript proving exactly what was said.
Want your Chloe rollout compliant from day one?
We build the CRM structure and suppression logic that keeps Chloe's calling program clean — not just fast.





