Free recipes / Guardrails and Compliance

Outbound AI Calls and Texts: The Consent Checklist

A builder prompt that turns your client's outbound plan into a consent checklist, an opening line and opt-out handling, with the gaps flagged for their lawyer.

Your client wants the AI to call or text people, such as reminders, win-backs or callbacks to old leads, and you need to check consent before a single call goes out. Saves about 40 minutes

The prompt

Role: You write careful compliance checklists for an AI agency. You are not a lawyer and do not give legal advice; you list what must be checked, and by whom, before an outbound campaign starts. Context: My client [BUSINESS_NAME] wants to contact people with an AI voice agent or automated texts. Locations: [LOCATIONS]. Purpose: [CAMPAIGN_PURPOSE]. Contact list source: [CONTACT_SOURCE]. Consent evidence: [CONSENT_EVIDENCE]. Channels: [CHANNELS]. Facts: In the US, the FCC's February 2024 ruling treats AI-generated voices as artificial voices under the TCPA, so these calls need the right prior consent unless an exemption applies, and telemarketing calls of this kind to mobile or residential lines need prior express written consent. Artificial voice messages must identify the business at the start and give a phone number, and telemarketing ones must offer an automated way to opt out. Texts, do-not-call lists, calling hours, recording, AI disclosure and state or national rules can add more. Task: 1) Classify the campaign as a callback the person asked for, a service message to existing customers, or marketing, say why in one line, and flag it if it is mixed or unclear. 2) Write the consent checklist as yes or no questions, each with an owner: agency, client or lawyer. 3) Draft the call's first two sentences: the business name and AI assistant in the first, then the reason and how to opt out. 4) Describe how the agent handles "stop calling me" and where that opt-out is recorded so it is honored on every channel. 5) List the gaps in my inputs, especially consent that does not clearly cover this purpose or channel. 6) End with questions for the client's lawyer. Constraints: Never say the campaign is legal or compliant. Mark every item that depends on local law with (CHECK LOCAL RULES). Keep the checklist under 25 items. If the consent evidence is missing or vague, say plainly that the campaign should wait until it is fixed.

Fill in these brackets

`[BUSINESS_NAME]`	e.g. Maple Street Dental
`[LOCATIONS]`	e.g. business in Florida, USA, contacting patients mostly in Florida and Georgia
`[CAMPAIGN_PURPOSE]`	e.g. call patients who have not booked a cleaning in 12 months and offer an appointment
`[CONTACT_SOURCE]`	e.g. existing patient list exported from the practice software
`[CONSENT_EVIDENCE]`	paste the exact consent wording and say where, when and how people agreed, e.g. a checkbox on the new patient form
`[CHANNELS]`	e.g. AI voice calls, then one follow-up text

Pro tip

Consent to appointment reminders is not the same as consent to marketing, so running a win-back campaign on a reminder list is a common mistake; get the exact consent wording from the client and keep a copy in your project file. Treat the output as a starting point for the client and their lawyer, not as legal advice.

Variation

For clients in the EU, replace the US facts with a request to check the local marketing and data protection rules and the AI Act duty to tell people they are talking to an AI.

Test this prompt with a few practice calls before real callers hear it. Tool names such as check_availability are generic: rename them to your platform's own.