Policy
TCPA-aware AI disclosure + automated consent logging.
On every inbound call, Hatchdesk reads a short disclosure before any other utterance, asks the caller to confirm, and writes the result to your audit log. The script is the same on every line — the audit trail is the operator’s defense under tightening state voice-AI rules, not a feature we’ll quietly drop.
Disclosure
What the AI says on every call.
The receptionist opens every inbound call with the same disclosure, verbatim. The wording is pinned to a versioned string tied to the call record, so a later regulator or carrier ask is satisfied by replaying the call against the disclosure revision that was live at the time.
“Hi, you’ve reached [business name] — calls on this line may be answered by an automated AI receptionist. We’ll record this call for quality and consent. If you’d like to speak with a human or stop the call at any time, just say so and we’ll transfer you. Do I have your consent to continue?”
Audit log
What’s recorded in your audit log.
The consent record is stamped at the moment the caller responds, not at the moment the call ends. Each row below is searchable, exportable, and tied to a single call SID so a dispute resolves down to one transcript, not a pile of summaries.
- Caller number — ANI for the inbound call, masked to last 4 after export.
- Timestamp — Server time at the moment the caller responded (UTC + operator TZ).
- Disclosure version — The exact script revision the AI read, so later policy edits never overwrite history.
- Caller-attested consent — Yes / No, set by the caller’s spoken answer. ‘No’ routes the call to a human and is still logged.
- Transcript excerpt — The full text from the disclosure prompt through the caller’s response, preserved verbatim.
Why
Why we log it.
State voice-AI rules are tightening. Carriers and state attorneys general are asking the same question on every complaint: did the caller know, and can you prove they consented? The audit log is the affirmative answer. Hatchdesk writes the consent record on every inbound call — the disclosure text, the caller’s attestation, and the transcript — so the operator is defending a real record rather than a vendor promise.
We don’t require the operator to do anything new to get this protection. The disclosure runs on every call, the record lands in the same CRM a dispatcher reads the next morning, and exporting the row for a regulator is a one-click report — not a forensic exercise.
Revisions
What changes between policy revisions.
Both the disclosure text read on every call and this policy note are versioned. A new revision is published when state rules or carrier guidance meaningfully shift, the older revision stays in force for any in-flight dispute, and the audit log records which revision was live at the timestamp a caller consented. Operators are notified by email before a disclosure-text revision ships.
Last updated: 2026-07-25