> ## Documentation Index
> Fetch the complete documentation index at: https://docs.recepta.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Recording & consent

> Call recording, disclosure requirements, and what you're responsible for.

Recepta.ai can record and transcribe calls. Recordings are what make [call review](/receptionist/call-logs) and [QA](/receptionist/qa-and-learning) possible — and they carry legal obligations you own as the business operating the line.

<Warning>
  This page describes how the product behaves. It is not legal advice. Recording law varies by state and by country, and the consequences of getting it wrong are civil and sometimes criminal. If you operate across state lines, take advice.
</Warning>

## One-party and two-party consent

US states split into two camps:

<Columns cols={2}>
  <Card title="One-party consent" icon="user">
    Only one participant needs to know the call is recorded — which can be you. The majority of states.
  </Card>

  <Card title="Two-party (all-party) consent" icon="users">
    Every participant must be informed and must consent. California, Florida, Pennsylvania, Illinois, Washington, and others.
  </Card>
</Columns>

The stricter rule generally governs a call that crosses state lines. If you serve customers in any all-party state, or you can't reliably tell where a caller is, **announce recording on every call**. It costs you three seconds and removes the entire question.

## Disclosure

When recording is enabled, configure the agent to state it at the start of the call, before anything substantive is discussed. Standard wording is enough: *"This call may be recorded for quality and training purposes."*

<Note>
  Treat disclosure as mandatory whenever recording is on. The few seconds you'd save are not worth the exposure, and callers are entirely used to hearing it.
</Note>

If a caller objects, honor it — either stop recording or transfer to a line that isn't recorded.

## Outbound calls

Outbound carries additional obligations beyond recording:

* **Calling hours.** Federal rules restrict marketing calls to 8am–9pm in the *called party's* local time, and some states are tighter.
* **Do-not-call.** Honor the national registry and your own internal list. A request to stop calling must be actioned and must persist.
* **Identification.** Say who's calling and on whose behalf, early.
* **Consent.** Prior express consent is required for certain automated outbound contact. Know which basis you're relying on for each campaign.

See [Outbound](/outbound/overview) before running your first campaign.

## SMS consent

Texting is governed separately and more strictly — see [SMS](/channels/sms) and [A2P 10DLC](/phone/a2p-10dlc). Consent to be called is not consent to be texted.

## Recordings and transcripts in Recepta.ai

|            | Where it lives              | Access                                                                                       |
| ---------- | --------------------------- | -------------------------------------------------------------------------------------------- |
| Recording  | Attached to the call record | Dashboard, or `GET /api/v1/api/calls/{callId}/recording` with `calls:recording` permission   |
| Transcript | Attached to the call record | Dashboard, or `GET /api/v1/api/calls/{callId}/transcript` with `calls:transcript` permission |

Access is scoped to your workspace and further restricted by [role](/account/team-and-roles) and by [API key permission](/api-reference/authentication) — so you can grant transcript access without granting audio.

<Card title="Security & privacy" icon="lock" href="/account/security-and-privacy">
  Data handling, retention, deletion requests, and subprocessors.
</Card>