> For the complete documentation index, see [llms.txt](https://docs.limephone.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limephone.io/ai-receptionist/ai-disclosure-and-compliance.md).

# AI disclosure and compliance

Set up your receptionist so callers know they're talking to an AI and your recordings stay on the right side of the law.

> **This is general guidance, not legal advice.** Rules differ by country, state, and industry, and they change. Confirm your obligations with a qualified lawyer in the jurisdictions where you and your callers are located.

## Tell callers they're talking to AI

Being upfront that your receptionist is an AI is increasingly required — several jurisdictions regulate automated and AI-generated calls — and it's good practice everywhere. Callers who know they're talking to an assistant adjust their expectations, get to the point faster, and don't feel tricked when they later realize.

The simplest approach: put the disclosure in the **greeting**. Edit the agent on the **AI Receptionist** page and make the first sentence do the work:

* "Thanks for calling Acme Plumbing. I'm Acme's AI assistant — how can I help?"
* "You've reached Riverside Dental. Our team is unavailable, so you're speaking with our AI receptionist. I can answer questions or take a message."

Also add a line to the agent's **instructions** such as: "If asked whether you are a human or an AI, say clearly that you are an AI assistant." An agent that dodges the question reads as deceptive.

## Recording consent varies by jurisdiction

Your agent can record and transcribe calls — both are toggles in the agent's settings (**Edit** on the AI Receptionist page). Before leaving recording on, know your consent regime:

* **One-party consent** (US federal law and many US states): one participant consenting is enough.
* **Two-party / all-party consent** (e.g., California and several other states; many countries): every participant must consent. Since callers can be anywhere, the safe default is to behave as if all-party consent applies.
* **GDPR and similar regimes** add requirements around informing callers, having a lawful basis, and retention.

The practical fix is announcing recording in the greeting: "This call may be recorded and transcribed so we can follow up accurately." A caller who stays on the line after a clear notice is generally treated as consenting in most regimes — but again, verify for yours. If you can't announce it, turn recording off.

## Tips for a compliant greeting

A greeting can cover everything in two short sentences:

> "Thanks for calling Acme. You're speaking with Acme's AI assistant, and this call may be recorded — how can I help?"

Keep it natural; don't bury the caller in boilerplate. And review your recordings' handling like any customer data: limit who on your team can access **Call Logs**, and delete what you don't need.

For US SMS rules (10DLC registration), see [Trust center: 10DLC & compliance](https://docs.limephone.io/workspace/trust-center-10dlc-and-compliance). For what the AI does on calls generally, see [Meet your AI Receptionist](https://docs.limephone.io/ai-receptionist/meet-your-ai-receptionist).