Consent Management
Before your AI agent calls or texts someone, you need the right consent. Taalk doesn't store consent records for you; it gives you the controls to honor consent and opt-outs. This article covers the background and the settings that matter.
This is not legal advice. Consent rules depend on your industry, your call purpose and the states you call. Confirm your approach with counsel.
Consent background
| Type | Typical use | What it usually means |
|---|---|---|
| Prior express consent | Informational calls (appointment reminders, account updates) | The person gave you their number for that purpose and hasn't revoked it. |
| Prior express written consent | Telemarketing and sales calls or texts using automated technology or an artificial voice | A clear written (or electronic) agreement that names your business and authorizes these calls to that number. Consent can't be a condition of purchase. |
AI voice calls generally count as artificial-voice calls under the TCPA, so the stricter rules usually apply. See the TCPA Guide.
Keep your consent records
Taalk has no built-in consent type, source or proof fields. Keep the proof (form, timestamp, IP, wording shown) in your own system or CRM. If you want the consent date in Taalk, include it as a column when you upload contacts (custom columns use the Taalk_ prefix) and use it with RND Consent Date Field below.
RND Consent Date Field
Go to campaign Settings › Outbound setup › RND Consent Date Field.
This tells Taalk which contact field holds the date the person gave consent. It's used by the reassigned-numbers check, which looks for numbers that changed owners after consent was given.
- Enter the field name (up to 30 characters). If you leave it empty, Taalk uses the date the contact was created (
createdAt). - The reassigned-numbers check runs only when Taalk turns it on for your workspace. Ask Taalk support.
Confirm consent at launch
Every launch opens Before you launch. You must tick each item before Confirm & Launch is enabled:
- Consent: "Every contact in this campaign gave express written consent to be called and texted. You are responsible for that consent (TCPA)."
- Calling hours: your daily window, with an Edit link.
- Do-Not-Call: the campaign's DNC Detection level, with Change and Manage DNC list links.
Your name and the time are recorded with the confirmation. Campaigns started through the API must send complianceAttested: true the first time, or the start is rejected. See Campaigns API Guide.
Honor opt-outs
| Where someone opts out | What happens in Taalk |
|---|---|
| On a call with your AI agent | With any DNC Detection level, contacts who ask to stop are treated as opt-outs (AI Auto DNC). |
| By text, in a playbook | Turn on Opt-Out on an end step, or add a Conditional Jump to OPT-OUT. See Playbook Steps Reference. |
| On a call with a Taalk Phone operator | The operator picks a post-call choice marked DNC. |
| Any other way (email, letter, your CRM) | Add the number to Platform › Compliance › Company DNC, or use Add to campaign DNC on the contact. |
[Confirm] The AI agent flags a contact as an opt-out when they ask to stop, without extra setup.
To stop every campaign from calling an opted-out number, add it to Company DNC and use a DNC Detection level that includes it. See DNC Detection Levels.
Re-consent
Only remove a number from DNC when the person has given new, documented consent. When you remove an opted-out contact with Remove from campaign DNC, Taalk asks you to confirm ("This contact opted out").
Checklist
- Collect the consent type your call purpose needs, and keep the proof.
- Upload only contacts with valid consent.
- Pick a DNC Detection level that matches your consent coverage.
- Keep TCPA Calling Hours on.
- Register for texting before you text. See A2P 10DLC Registration.