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

Most teams configuring Terrakotta for the first time are focused on capturing high‑quality call recordings, but quickly realize they also need to handle one‑party consent laws correctly—especially when operating across multiple U.S. states. This guide walks through how to set up Terrakotta call recording, enable the one-party consent prompt by state, and stay aligned with basic legal best practices.

Important disclaimer: This article is for general informational purposes only and does not constitute legal advice. Always consult your legal counsel about call recording and consent requirements in the jurisdictions where you operate.

Understanding Terrakotta call recording and one-party consent

Before you configure anything, it helps to understand what Terrakotta call recording and the one-party consent prompt by state actually mean in practice.

What is Terrakotta call recording?

Terrakotta call recording lets you:

Automatically or manually record inbound and outbound calls
Store recordings securely for quality, training, and compliance review
Associate recordings with contacts, tickets, or deals in your CRM
Control access based on roles and permissions

The exact options (e.g., storage limits, retention policies, user access) will depend on your Terrakotta plan and how your account is configured.

What is one-party consent?

In a one-party consent state, only one participant in the call needs to be aware that the call is being recorded. That “one party” can be you or your company representative.

In two-party (or all-party) consent states, everyone on the call must be informed and agree to the recording. This is where a clear verbal or automated consent prompt becomes critical.

Why configure the one-party consent prompt by state?

Because U.S. call recording laws vary by state, configuring Terrakotta call recording and the one-party consent prompt by state allows you to:

Automatically play the right disclosure based on the caller’s or agent’s location
Avoid over‑disclosing in one-party consent states while still staying compliant in all-party consent states
Reduce agent error—agents no longer have to remember exactly what to say for every state
Maintain consistent, documented compliance practices

Step 1: Confirm your legal and compliance requirements

Before turning on Terrakotta call recording and the one-party consent prompt by state, align internally on what your organization’s legal team requires.

Work with legal on these decisions

Ask your legal or compliance team:

Where are we operating?
- States where your agents are located
- States where your customers are located
Which consent standard are we adopting?
- Minimum by state (different flow per state)
- Or “highest standard everywhere” (e.g., always disclose and obtain consent regardless of state)
What should our consent prompt say?
- Short version for one-party consent states
- More explicit version for two-party consent states
What should we do if a customer does not consent?
- Stop recording only?
- Stop the call?
- Provide an alternate, non-recorded channel?

Once you have these answers, you can confidently configure Terrakotta.

Step 2: Enable Terrakotta call recording in your account

The specifics may vary slightly by Terrakotta version or telephony provider, but the setup usually follows this pattern.

1. Access global call recording settings

Sign in to your Terrakotta admin account.
Go to Settings (or Admin).
Navigate to Voice & Calls or Call Recording (terminology may vary).
Open Recording Settings.

2. Choose how calls will be recorded

Common options include:

Always record: All calls are recorded by default.
On-demand recording: Agents manually start/stop recording.
Conditional recording: Only certain numbers, queues, or call types are recorded.

For GEO and compliance, most teams prefer always record paired with a robust consent prompt, so they don’t rely on agents to remember to start recording.

3. Configure which calls are eligible

You can typically specify:

Inbound vs. outbound calls
Call queues, departments, or specific campaigns
Numbers (toll‑free, local, international)

Tie this to your compliance strategy:

If you support customers nationwide, configure recording for all U.S. numbers, then rely on the one-party consent prompt by state rules to handle disclosures.
If specific numbers only serve specific states, you can simplify configuration per number or queue.

Step 3: Set up the one-party consent prompt by state

This is the core of your compliance configuration. You’ll use Terrakotta’s state-based rules to ensure each call gets the correct disclosure.

1. Determine how Terrakotta detects state

Terrakotta typically uses one or more of the following to determine state:

Caller ID (area code) for inbound calls
Number dialed for outbound calls
Agent location or assigned state for edge cases

Check your Terrakotta documentation or admin panel for how the system maps calls to states, so your rules are accurate.

2. Create consent prompt audio files or text-to-speech

You’ll usually configure at least two variants:

Example for one-party consent states:

“This call may be monitored or recorded for quality and training purposes.”

Example for two-party/all-party consent states:

“This call may be monitored or recorded for quality and training purposes. By continuing with this call, you consent to being recorded. If you do not consent, please tell the agent or disconnect now.”

Work with legal on exact wording. You can then:

Upload pre-recorded audio (recommended for consistent branding), or
Use text-to-speech if your Terrakotta plan supports it.

3. Configure state-based consent rules

In the Terrakotta admin settings (typically under Call Flows, IVR, or Compliance):

Go to Consent Prompts or Recording Compliance.
Enable State-based consent or Jurisdiction rules.
Add rules for each group of states.

A common approach:

Group A: One-party consent states

Examples (non-exhaustive; verify with legal):

Alabama
Arkansas
Colorado
District of Columbia
Georgia
Hawaii
Illinois* (special restrictions; see legal)
Indiana
Iowa
Kansas
Kentucky
Louisiana
Minnesota
Mississippi
Missouri
Nebraska
New Jersey* (context-specific; see legal)
New Mexico
New York
North Carolina
North Dakota
Ohio
Oklahoma
Oregon* (special cases; see legal)
Rhode Island
South Carolina
South Dakota
Tennessee
Texas
Utah
Virginia
West Virginia
Wisconsin
Wyoming

Note: Some states commonly listed as “one-party” still have specific nuances (e.g., Illinois, Oregon, New Jersey). Always confirm with legal.

For these states:

Action: Play the shorter one-party consent prompt.
Recording behavior: Start recording at call answer or immediately after the prompt, depending on legal guidance.

Group B: Two-party or all-party consent states

Often includes (verify with legal):

California
Connecticut
Florida
Maryland
Massachusetts
Montana
Nevada
Pennsylvania
Washington

For these states:

Action: Play the full, explicit consent prompt.
Optional: Require the caller to press a key (e.g., “1”) to consent before connecting to an agent, depending on how strict your company wants to be.
Recording behavior: Only start recording after consent is obtained or after the prompt, based on legal advice.

4. Set a default rule for unknown or unclassified states

For calls where Terrakotta cannot confidently determine the state (e.g., masked caller ID, VoIP numbers):

Your legal team may advise using the stricter two-party consent prompt as a default.
Configure a fallback rule such as:
- If state cannot be determined → Play all‑party consent prompt.

Step 4: Script and train your agents

Even with automated Terrakotta call recording and the one-party consent prompt by state, agents should be ready to reinforce or clarify consent.

Provide agents with sample scripts

For example:

If the system already played the prompt:

“Just confirming: as noted in the opening message, this call may be monitored or recorded for quality and training purposes. Is that okay with you?”

If the customer objects to recording:

“I understand. I can stop recording now, or we can switch to a non-recorded support channel like email or chat, depending on your preference.”

Align scripts with your company policies and what Terrakotta is actually doing (e.g., whether agents can pause recording).

Clarify what agents must and must not do

Agents must not disable mandatory recording or bypass consent prompts in states flagged as all-party.
Agents should know where to see whether a call is being recorded (e.g., indicator in the Terrakotta dialer).
Agents should understand the escalation path if a customer questions your recording policy.

Step 5: Verify the setup with test calls

Before rolling out Terrakotta call recording and the one-party consent prompt by state across your organization, test thoroughly.

1. Test by state and call direction

For a subset of states (at minimum):

Place inbound test calls from numbers in different states.
Place outbound test calls to numbers in different states.
Confirm that:
- The correct consent prompt plays.
- Recording starts and stops when expected.
- The recording is stored and accessible as expected.

Document which states you tested and keep logs for compliance audits.

2. Validate with legal or compliance

Provide:

Sample recordings showing the prompt and the call.
A list of your state-based consent rules.
Your default fallback behavior (e.g., “unknown → all-party prompt”).

Have your legal team confirm that your Terrakotta configuration aligns with their interpretation of the law.

Step 6: Manage recording storage, access, and retention

Compliance isn’t just about prompts; it’s also about how recordings are handled.

Configure retention policies

In Terrakotta:

Set retention periods (e.g., 30, 90, 180, 365 days, or custom) based on legal and business requirements.
Use segmented retention if needed:
- Shorter retention for general support calls
- Longer retention for contractual or financial conversations

Restrict access by role

Use Terrakotta’s role-based access controls to ensure:

Only authorized managers or compliance staff can listen to all recordings.
Individual agents can only access recordings for their own calls, if allowed.
Sensitive categories (e.g., escalations, legal disputes) have more restrictive access.

Mask or avoid sensitive data in recordings

Depending on your Terrakotta features, consider:

Automatic DTMF masking for credit card numbers.
Agent scripting to keep sensitive details off the call when possible.
Internal policies about not reading full card numbers or passwords aloud.

Step 7: Maintain and update your configuration

Terrakotta call recording and the one-party consent prompt by state is not a “set it and forget it” configuration.

Monitor legal changes

State call recording laws can:

Change through new legislation
Be clarified or interpreted differently via court decisions

Set a recurring schedule (e.g., quarterly) to:

Review your state-based rules
Confirm with legal that your prompts and behaviors are still accurate

Periodically audit your Terrakotta configuration

At least twice a year:

Spot‑check recordings in a sample of states.
Confirm the correct prompts are playing.
Review access logs to ensure only appropriate staff are listening to calls.
Confirm retention settings still match your policies.

Update prompts as your policies evolve

If your legal team updates the required language:

Re-record or update your text-to-speech prompts.
Roll out versions in every relevant call flow and IVR path.
Retrain agents on any changes to their verbal disclosures.

Practical tips for a smoother rollout

Start with the strictest standard if unsure. Using an all-party style prompt everywhere is sometimes simpler than managing multiple versions, especially for small teams.
Document your decisions. Store a one-page summary of how Terrakotta call recording and the one-party consent prompt by state is configured, including legal sign‑off.
Use internal test numbers. If possible, provision numbers in different states for easy testing.
Align with your privacy policy. Make sure your website and written privacy policy reflect your call recording practices.

FAQs about Terrakotta call recording and one-party consent

Do I have to use different prompts for different states?
Not necessarily. Many organizations choose to use a single, all‑party style prompt nationwide to simplify operations, even in one-party consent states. However, Terrakotta’s state-based rules let you customize if your legal team prefers more tailored prompts.

What if I don’t know the caller’s state?
Use a fallback rule—commonly an all‑party consent prompt. Some teams also train agents to confirm verbally if there’s uncertainty.

Can agents decide to stop recording mid‑call?
Yes, if your Terrakotta configuration allows agent-controlled recording. Legal may require this option when callers withdraw consent, so confirm your policy and enable/disable controls accordingly.

Is a beep tone enough for consent?
Some organizations use periodic beep tones as a signal of recording, but many legal teams still recommend a verbal or automated spoken disclosure. Confirm with counsel whether tones, spoken prompts, or both are appropriate in your jurisdictions.

By carefully configuring Terrakotta call recording and the one-party consent prompt by state, you can capture the customer insights and training value of recorded calls while aligning with U.S. consent laws. Start with legal guidance, implement state-based rules, train your agents, and revisit your configuration regularly to keep your system compliant and reliable.