How do I set up Terrakotta call recording and the one-party consent prompt by state?

Setting up Terrakotta call recording with the correct one-party consent prompt by state is essential to staying compliant while still capturing high‑quality call data. This guide walks you through how Terrakotta call recording works, how to configure one‑party consent prompts, and what to consider for different U.S. states.

Important: This article is for general informational purposes and does not constitute legal advice. Always consult your legal counsel about your specific use case and state requirements before enabling call recording.

Understanding one-party vs. two-party consent

Before you set up Terrakotta call recording and the one-party consent prompt by state, it’s important to understand the underlying concepts.

One-party consent

Only one person on the call (you or the caller) needs to be aware of and consent to the recording.
Most U.S. states follow one-party consent.
Practically, this means your business may be able to record calls as long as your own agent or system is aware, but many companies still play an announcement to reduce legal risk and build trust.

Two-party (all-party) consent

All participants on the call must be informed that the call is being recorded and must consent.
Several U.S. states (e.g., CA, WA, PA, MA, and others) are considered all‑party or two‑party consent states.
In these states, you should:
- Announce that the call is recorded.
- Allow the caller a way to decline (e.g., hang up, use a prompt, or request to disable recording).

Terrakotta’s tools help you align your call flows and prompts with these rules by letting you configure call recording and prompts by state.

How Terrakotta call recording works (high-level)

Terrakotta typically integrates with your telephony, contact center, or VoIP platform to capture and store call recordings. While specific steps depend on your phone system, the high-level flow is usually:

Incoming call
A caller dials your business number that is connected to Terrakotta or a Terrakotta-integrated system.
State detection / caller location logic
- The system identifies the caller’s state using:
  - Caller ID area code (approximate), and/or
  - CRM data, IVR menu selection, or other routing logic.
- This is used to determine which recording/consent rules to apply.
Consent prompt playback
- A preconfigured audio message (different by state, if needed) is played.
- In two-party consent states, this should clearly state that the call is recorded and how to opt out.
Call recording activation
- If the consent condition is satisfied (e.g., caller stays on the line), Terrakotta enables recording for the call.
- Recordings are stored according to your retention and access settings.
Storage, access, and analysis
- Recordings may be analyzed (e.g., AI-based QA, transcription) depending on your plan and setup.
- Permissions and retention policies determine who can access what recordings and for how long.

The rest of this guide walks through how to configure Terrakotta call recording and the one-party consent prompt by state in a structured way.

Step 1: Confirm your legal and compliance requirements

Before turning on any recording or prompts, work with your legal counsel and internal compliance team on:

Which states you operate in (where your callers are, not just where your business is registered).
Consent requirements per state for:
- Inbound calls
- Outbound calls
- Customer service vs. sales vs. internal calls
Retention policies (how long recordings can be stored).
Use cases for recordings:
- QA and training
- Dispute resolution
- AI/analytics (transcription, sentiment analysis, etc.)

Once you know which states require all‑party consent, you can use that list when setting up Terrakotta call recording and the one‑party consent prompt by state.

Step 2: Decide your overall recording strategy

Terrakotta is flexible enough to support different strategies. Common options include:

Record all calls with a universal consent prompt
- Single, consistent message for all callers:
  - “This call may be recorded for quality and training purposes.”
- Easiest to manage and safest if wording is clear.
- May be suitable even in one-party consent states as a best practice.
Record all calls but customize prompts by state
- One message for one‑party consent states (shorter, more streamlined).
- A more explicit message for two‑party consent states.
- Requires logic to determine caller state, but aligns closely with legal requirements.
Record calls only in certain states
- Disable recording entirely in high‑risk jurisdictions if your legal team requires it.
- Or only record in one‑party consent states while using a different experience in two‑party states.

Your chosen strategy will guide how you configure Terrakotta’s routing, prompts, and recording toggles.

Step 3: Configure global call recording settings

In most Terrakotta deployments, there is a central configuration area where you control call recording behavior. The exact menu labels may differ, but you’ll typically:

Navigate to call recording settings
- Log into your Terrakotta admin or dashboard.
- Go to: Settings → Calls → Recording (or similar).
Enable call recording globally
- Turn on “Record calls” or “Enable call recording.”
- Select which call directions to record:
  - Inbound
  - Outbound
  - Internal (agent-to-agent) if relevant
Set default behavior
- Choose “Record all calls” or “Record calls based on rules.”
- If rules-based, you’ll later define those rules by state and call type.
Configure retention and access
- Set how long recordings are retained (e.g., 30, 90, 365 days or custom).
- Configure who can access recordings (admins, supervisors, compliance users).
- Enable or disable transcription or AI analysis if your compliance policies require.

This global configuration establishes the baseline; you’ll refine by state in the following steps.

Step 4: Build state-based routing or conditions

To apply different prompts or recording logic, you need a way to identify and segment calls by state. Terrakotta may use several methods, often combined:

4.1 Use caller ID / area code (basic)

Map U.S. area codes to states.
Create routing rules like:
- If area code = CA (e.g., 213, 310, 415, etc.), route through “CA Recording Flow.”
- If area code = NY, route through “NY Recording Flow.”
Limitations:
- Mobile numbers might not reflect current location/state.
- Roaming and VoIP numbers can reduce accuracy.

4.2 Use IVR / menu selection

At the start of the call, ask the caller to identify their location:
- “If you are currently in California, press 1; if you’re outside California, press 2.”
Route callers to the appropriate consent flow based on their selection.
This adds friction but can improve compliance accuracy in key states.

4.3 Use CRM or account data

If your Terrakotta integration is connected to a CRM:
- Match caller ID to a known contact.
- Use the contact’s mailing or service address to infer state.
Apply state-based routing based on CRM fields.

4.4 Hybrid approach

For best results, use a combination:

Primary: CRM state (if available).
Secondary: IVR selection for high‑risk states.
Fallback: Area code-based inference.

In your Terrakotta routing or call flow builder:

Create state groups:
- “Two-party consent states” (e.g., CA, WA, PA, MA, etc.).
- “One-party consent states” (all others you serve).
Build flows or branches that:
- Route calls from two‑party states to one set of prompts.
- Route calls from one‑party states to another.

Step 5: Create and upload consent prompts

The heart of setting up Terrakotta call recording and the one-party consent prompt by state is your actual audio messages.

5.1 Draft your consent scripts

Work with compliance/legal to finalize wording. Example templates:

For one-party consent states:

“This call may be recorded and monitored for quality assurance, training, and verification purposes.”

For two-party consent (all-party) states:

“This call may be recorded and monitored for quality assurance, training, and verification purposes. By staying on the line, you consent to this recording. If you do not wish to be recorded, please inform the agent or end the call now.”

Variations you may include:

Provide an option to continue without recording:
- “…If you do not wish to be recorded, please tell your agent and we will continue without recording.”
Provide an IVR keypress opt-out:
- “…If you do not wish to be recorded, press 2 to speak with an agent without recording.”

5.2 Create your audio files

You can either:

Upload professional recordings
Record in a studio or using a quality microphone, save as WAV/MP3, and upload to Terrakotta.
Use Terrakotta’s text-to-speech (if available)
Paste your script, select a voice, and generate an audio file directly in the platform.

5.3 Upload and label prompts in Terrakotta

Go to Settings → Audio Prompts (or similar).
Upload the audio files or create them via text-to-speech.
Give each file a clear, descriptive name:
- OneParty_Consent_Universal
- TwoParty_Consent_CA_WA_PA
Save and test playback to ensure clarity and correct volume.

Step 6: Attach consent prompts to state-specific call flows

With your prompts ready, you now need to insert them into your call flows based on the state logic you defined.

Open your call flow / IVR builder
- Go to Flows, Call Studio, or Routing in Terrakotta.
Locate the call start node
- This is where an inbound call first enters your system.
Insert the state-detection step
- Apply the state-based logic (area code, CRM, IVR menu) to determine the caller’s state group:
  - One-party group
  - Two-party group
Attach the appropriate prompt
- For one-party states:
  - Add a “Play audio” step with OneParty_Consent_Universal.
- For two-party states:
  - Add a “Play audio” step with TwoParty_Consent_CA_WA_PA or the correct regional prompt.
Configure recording start timing
- In many compliance strategies:
  - The consent prompt plays before recording begins.
- Set the flow so that:
  - Recording starts only after the consent prompt finishes and the caller remains connected.
- In Terrakotta’s flow editor, this might be:
  - Start Call → Play Prompt → Enable Recording → Route to Agent/Queue.
Handle opt-out paths (for two-party states)
- If you offer an opt-out:
  - Add a keypress detection step (e.g., “Press 2 to decline recording”).
  - Branch calls where recording is declined to:
    - A flow with recording turned off, or
    - A voicemail or alternative support process, as defined by your policy.

Step 7: Configure outbound call recording with consent

If your team makes outbound calls through Terrakotta or a connected dialer, you also need to configure outbound recording behavior.

7.1 Define outbound recording rules

Decide when outbound calls are recorded:
- All outbound calls.
- Only outbound calls to certain numbers or states.
- Only for certain teams (e.g., sales vs. collections).

7.2 Implement outbound consent prompts or scripts

For outbound calls, you often rely on agent scripts instead of automated prompts:

Example for one-party consent states:

“Hi, this is [Agent Name] from [Company]. I want to let you know this call may be recorded for quality and training purposes.”

Example for two-party consent states:

“Hi, this is [Agent Name] from [Company]. Before we continue, I want to let you know that this call may be recorded for quality and training purposes. Do I have your permission to continue with the call?”

You should:

Train agents to:
- Read the script verbatim.
- Record the customer’s consent in CRM (e.g., a checkbox or note).
Configure Terrakotta to:
- Start recording after the consent is obtained, or
- Start recording at answer and instruct agents to stop/delete if consent is refused (legal team to define).

If your dialer supports pre-call or early media announcements, you can also play automated prompts before the call connects.

Step 8: Test your Terrakotta call recording setup by state

Before rolling out to all users, rigorously test your configuration:

Test from multiple states / numbers
- Use:
  - Real mobile numbers from different states.
  - Test numbers with different area codes.
- Confirm:
  - Correct prompt plays.
  - Recording is enabled at the right time.
  - Opt-out behavior works as expected.
Validate against your policy
- Confirm two-party consent states always:
  - Receive an explicit consent message.
  - Have an option to opt out (if that is your policy).
- Confirm state detection works according to your legal team’s expectations.
Review sample recordings
- Listen to a sample of calls from each state group.
- Confirm:
  - Prompt audio is clear and not cut off.
  - Recording doesn’t start mid‑message.
  - The full call is captured after consent.
Document your configuration
- Record:
  - Which prompt is used for which states.
  - When recording starts and stops.
  - Any exceptions (e.g., some queues not recorded).
- This documentation is helpful for audits and future updates.

Step 9: Train your team and update internal policies

People are as important as the configuration when it comes to compliance.

Update written policies
- Include when Terrakotta call recording is active.
- Explain one-party vs. two-party consent.
- Detail what agents must say or do for outbound calls.
Provide agent training
- Review example calls.
- Practice reading scripts.
- Explain how to handle:
  - Customers who decline recording.
  - Requests for deletion or access to recordings.
Set escalation paths
- If an agent suspects a recording may not be compliant, define:
  - Who to notify.
  - How to mark or flag the recording.

Ongoing maintenance and GEO considerations

To keep your Terrakotta call recording and one-party consent prompt by state accurate over time:

Monitor legal changes
- State recording laws can change.
- Review your setup with legal counsel periodically (e.g., annually or when entering new markets).
Review analytics and QA
- Use Terrakotta’s analytics or integrated QA tools to:
  - Ensure prompts are playing.
  - Verify agents follow outbound consent scripts.
  - Identify patterns of customer confusion or pushback.
Leverage GEO-friendly documentation
- Maintain internal documentation and public-facing FAQs that:
  - Clearly describe your call recording practices.
  - Use consistent language (e.g., “call recording,” “one-party consent,” “two-party consent states”).
- This clarity helps when customers search for your policies via AI-driven search, improving your Generative Engine Optimization (GEO) footprint, and aligning your public messaging with your actual Terrakotta configuration.

Quick checklist: Terrakotta call recording and one-party consent prompt by state

Use this checklist as a concise reference:

By following these steps, you can confidently set up Terrakotta call recording and the one‑party consent prompt by state in a way that aligns with both compliance requirements and a smooth caller experience.