Phones and Call Handling

Restaurant Call Recording Laws by State

Which states need every caller's consent before a restaurant records a call, how to word the greeting, and how long to keep the recordings.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. Why recording is a legal question, not just a settings toggle
  2. One-party and all-party states
  3. Calls that cross state lines
  4. How to word the disclosure
  5. Setting up compliant recording, step by step
  6. How long to keep call recordings
  7. Example: a two-state restaurant group
  8. Common mistakes to avoid
  9. Frequently asked questions
  10. References
Phones and Call Handling: Restaurant Call Recording Laws by StateArticle coverPHONES AND CALL HANDLINGRestaurant CallRecording Laws by StateAva for RestaurantsInsightsPhones and Call Handling: Restaurant Call Recording Laws by StateArticle coverPHONES AND CALL HANDLINGRestaurant CallRecording Laws byStateAva for Restaurants

Key takeaways

  • Federal law lets one party consent to a recording, but California, Florida, Washington and several other states require consent from everyone on the call.
  • You rarely know where a caller is standing, so the safe default for any recorded line is a short disclosure at the very start of the call.
  • In Washington the announcement only counts as consent if the announcement itself is captured in the recording.
  • Write a retention schedule before you switch recording on: keep routine calls briefly, keep dispute calls until the matter is closed, and limit who can listen.

Most restaurants that record calls do it for ordinary reasons: coaching new hosts, settling a disputed takeout order, or checking what was promised on a catering inquiry. The phone line carries a lot of that work. Hosts are the people who greet guests, seat them and manage reservations and waiting lists, and a large share of that happens on calls[1]. Recording those calls is useful, but it is also regulated, and the rules change at the state line.

Federal wiretap law follows a one-party consent rule. It is not unlawful for a person who is a party to a call, or who has one party's prior consent, to record it[2]. If your host is on the call and your system records it, federal law is usually satisfied. The problem is that some states set a stricter rule, and California is the best-known example: it requires the consent of every party[2].

This guide explains how the rules work in practice for restaurant phone lines. It is not legal advice. Statutes and court decisions change, so confirm your setup with a lawyer licensed in the states where you operate.

One-party and all-party states

The Digital Media Law Project, a former Berkman Klein Center project whose legal guide is no longer updated, names ten states with all-party consent laws: California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Pennsylvania and Washington[3]. The same page says eleven states require everyone's consent but lists only ten, which is a good reminder to check the current statute rather than rely on any single list[3].

States and DC by consent rule, as listed in the DMLP guideTen states named as all-party; the guide is no longer updated, so check current statutes
States and DC by consent rule, as listed in the DMLP guideStacked bar chart. All-party consent (named): 10; Other states and DC: 41.All-party consent (named): 10 (20%)Other states and DC: 41 (80%)States and DC by consent rule, as listed in the DMLP guideStacked bar chart. All-party consent (named): 10; Other states and DC: 41.All-party consent (named): 10 (20%)Other states and DC: 41 (80%)
  • All-party consent (named) 10 20%
  • Other states and DC 41 80%

Source: Digital Media Law Project, Berkman Klein Center for Internet & Society, 2014[3]

Show the data
ItemValue
All-party consent (named)10
Other states and DC41

Two statutes show how much the details matter. Florida makes interception lawful when all parties to the communication have given prior consent, and a violation of the main prohibition is a third-degree felony[4]. Washington requires the consent of all participants in a private telephone call, but it treats consent as obtained when one party announces to everyone that the call is about to be recorded, provided the announcement is itself recorded[5].

How common consent rules translate into restaurant phone practice (summary, not legal advice)
JurisdictionConsent ruleWhat it means for your phone line
Federal lawOne party may consentYour own staff member on the call can consent, unless a state rule is stricter
CaliforniaAll partiesDisclose at the start of every recorded call, inbound and outbound
FloridaAll parties, prior consentDisclosure must come before the recording captures the conversation
WashingtonAll participants; a recorded announcement countsPut the announcement inside the recording, not before it starts
Connecticut, Illinois, Maryland, Massachusetts, Montana, New Hampshire, PennsylvaniaNamed as all-party in the DMLP guideTreat as all-party and confirm the current statute with counsel
Other statesGenerally one-partyDisclose anyway, because callers may be in an all-party state

Calls that cross state lines

A restaurant does not choose where its callers are. A guest planning an anniversary dinner may call from another state, a tourist may call from a hotel across the border, and a mobile area code says nothing about where the phone is today. If even one party is in an all-party state, the cautious reading is that the stricter rule applies to that call.

For that reason most restaurant groups set one rule for every recorded line: disclose first, everywhere. It costs a few seconds per call and removes the need for hosts to work out which state a caller is in. Groups with locations in more than one state should apply the same greeting at every store so a transferred call never lands on an undisclosed recording.

How to word the disclosure

Keep the disclosure short, plain and at the top of the call, before any order or reservation detail is taken. Guests should hear it before they say anything you would want to keep. These scripts work for most lines; adjust the restaurant name and purpose.

  • Main line: “Thanks for calling Harbor Grill. This call may be recorded for training and order accuracy. How can I help?”
  • Catering line: “You've reached the Harbor Grill events team. We record calls so we have your event details right. What date are you planning for?”
  • After-hours message: “This message and any call you leave may be recorded. Leave your name, number and party size and we will call you back tomorrow.”
  • Outbound callback from a recorded system: “Hi, this is Sam from Harbor Grill returning your call. Just so you know, this call is recorded. Is now a good time?”

If a caller says they do not want to be recorded, have a clear answer ready: switch to an unrecorded line if your system allows it, or offer to take the details by text or email instead. Never keep recording after a caller objects in an all-party state.

Setting up compliant recording, step by step

  1. Write down why you record

    Training, order disputes and catering accuracy are common purposes. A clear purpose tells you which lines need recording and how long to keep each file.

  2. List every line and device

    Main line, catering line, delivery tablet, manager mobiles and any call forwarding to staff phones. Recording rules apply to each one, including calls forwarded off-site.

  3. Put the greeting first

    Place the disclosure before the hold message, menu options or transfer, so every caller hears it no matter which path they take.

  4. Capture the announcement in the file

    Configure the system so the recording starts before the disclosure plays. That satisfies the Washington approach and gives you proof for any other state.

  5. Handle outbound calls

    Calls your staff place from a recorded system need their own disclosure. Add the outbound line to the host script and the callback checklist.

  6. Restrict access

    Limit playback to managers who need it, turn off downloads by default and keep an access log if your provider offers one.

  7. Set and enforce retention

    Choose how long each type of recording is kept, set automatic deletion, and review the setting every quarter.

If an answering service or an AI phone agent picks up for you, the same rules apply to them. Ask three questions before go-live: does the disclosure play before anything is captured, where are the recordings and transcripts stored, and who at the vendor can listen to them. Get the answers in writing, and make sure deleting a recording on your side also deletes the vendor's copy. Our buyer questions for AI phone systems cover the contract side in more detail.

How long to keep call recordings

There is no single federal retention period written for restaurant call recordings, so the decision usually rests on your purpose, your insurer, your lawyer and any privacy law that covers your business. Shorter is generally safer: recordings contain names, phone numbers, sometimes card details read aloud and sometimes health information such as allergies. Every extra month of storage is more data to protect.

  • Example schedule for routine reservation and hours calls: keep 30 days, then delete automatically.
  • Example schedule for complaint or order-dispute calls: tag the call and keep it until the dispute is closed, then delete.
  • Example schedule for catering and private event calls: keep with the event file until the event is paid and reviewed.
  • Never ask guests to read full card numbers on a recorded line; move payments to a secure link or pause recording.

Example: a two-state restaurant group

Example: a fictional group runs one restaurant in Florida and one in Georgia, with a shared reservation line answered at the Florida store. The owner wanted recordings to coach new hosts. Before switching on recording, the manager added a five-second disclosure at the top of the shared line, set the system to record from the first ring so the disclosure is in the file, and added an outbound script for callbacks.

Example: the group kept routine calls for 30 days and tagged disputes for longer review. When a guest asked not to be recorded, hosts offered to finish the booking by text. After a month, the manager used ten flagged calls to rewrite the readback step of the host script, which was the original goal.

Common mistakes to avoid

  • Recording forwarded calls on a manager's mobile with no disclosure because the forwarding app records by default.
  • Placing the disclosure after the hold music, where callers who hang up and redial never hear it.
  • Assuming a one-party rule because your restaurant is in a one-party state, when callers may be elsewhere.
  • Keeping every recording forever because nobody set a deletion rule.
  • Letting staff share clips of rude callers in group chats, which turns a training tool into a privacy problem.

Get these right and recording becomes a quiet, useful habit. For related setup work, see how two-way texting with guests needs its own consent rules, and how call tracking numbers interact with recorded lines.

Frequently asked questions

Do I need consent to record calls at my restaurant?

Under federal law one party to the call can consent, which usually covers your own staff. Several states, including California, Florida and Washington, require consent from everyone on the call, so the safe practice is to disclose at the start of every recorded call.

Is a recorded greeting enough to count as consent?

In many cases a clear announcement at the start of the call, followed by the caller continuing, is how businesses obtain consent. Washington's statute treats an announcement as consent only if the announcement is itself recorded. Confirm the approach for your states with a lawyer.

Can managers record calls on their personal phones?

Avoid it. Personal phone apps often record without any disclosure and store files outside your control. Route business calls through a system that plays the disclosure and applies your retention rules.

Do call transcripts count as recordings?

Treat them the same way. If a system captures or transcribes the conversation, disclose it at the start of the call, restrict access and apply the same deletion schedule as for audio.

References

  1. US Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Food and Beverage Serving and Related Workers (opens in a new tab) ↑

  2. Legal Information Institute (Cornell Law School), US Code (2026). 18 U.S. Code § 2511 - Interception and disclosure of wire, oral, or electronic communications prohibited (opens in a new tab) ↑

  3. Digital Media Law Project, Berkman Klein Center for Internet & Society (2014). Recording Phone Calls and Conversations (legal guide, no longer updated) (opens in a new tab) ↑

  4. The Florida Legislature (2026). Florida Statutes 934.03: Interception and disclosure of wire, oral, or electronic communications prohibited (opens in a new tab) ↑

  5. Washington State Legislature (2026). RCW 9.73.030: Intercepting, recording, or divulging private communication (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo