A restaurant taking sixty calls a day generates roughly twenty-two thousand conversations a year. If you record all of them and keep them, that is twenty-two thousand pieces of stored customer conversation sitting somewhere, growing by the same amount every year, and the reason most of them exist is that someone turned recording on during setup and nobody has thought about it since.
One-party consent frameworks are why that is possible without anyone breaking a rule. They are also why operators stop thinking about the subject too early, because "we're in a one-party state" feels like the end of the analysis when it is closer to the beginning of it.
What follows is general education, not legal advice. Anything you actually deploy should be reviewed by an attorney licensed where you operate.
What the rule says, in plain terms
A one-party consent framework treats the consent of a single participant in the conversation as sufficient to record it. Because your business is a participant in calls placed to your business, that consent is typically yours to give, which is what makes recording your own customer calls permissible without asking anyone.
The contrasting framework requires every participant to consent, and it is described in all-party consent states and what restaurants get wrong.
Two things this does not settle. It does not settle what you may then do with the recording, which is governed by an entirely different set of considerations. And it does not settle which framework applies to any particular call.
The map is not the answer
Operators picture their state, look up its rule, and stop. The reason that fails is that a phone call has more than one location.
Your restaurant sits in one place. The caller sits somewhere else, and on a mobile phone that somewhere can be anywhere, since area codes stopped indicating physical location a long time ago. A regular who moved across the country and kept their number will call you from two thousand miles away with a local-looking number. The recording itself is created and stored in a third location, usually a data center you have never thought about.
Jurisdictions have reached different conclusions about how their rules apply to calls involving their residents. That disagreement is precisely why the state-by-state list feels more authoritative than it is, and it is the reason careful multi-state businesses tend to apply the strictest standard that could plausibly reach any of their calls rather than sorting call by call.
You cannot sort call by call anyway. The information you would need arrives after the conversation is over.
Three reasons to announce it regardless
The first is the one above. Announcing removes the jurisdictional guessing game from your operation entirely. One sentence, every call, no decisions.
The second is that the recording eventually has an audience. Recordings are useful because they get used, in refund arguments, in chargeback disputes, occasionally in something more formal. The moment a recording is played back to someone who did not know it existed, the conversation stops being about what was ordered and becomes about why you were recording them. That is a losing exchange even where the recording was entirely permissible. A disclosure at the top of the call makes the recording boring, and boring is what you want your evidence to be.
The third is simple respect for the customer. People generally do not mind being recorded by a business. They mind finding out later. The disclosure costs you a couple of seconds and buys you the ability to say, truthfully, that every caller was told.
What a good announcement sounds like
Short, plain, and first. Something on the order of "this call may be recorded for order accuracy" said before your greeting rather than after it, because a notice that arrives once the caller has already recited half an order has not given them a chance to do anything with it.
Resist the urge to write a paragraph. Long notices get spoken over, produce hang-ups, and encourage staff to abbreviate them. Resist the opposite urge too, which is a mumbled half-sentence that a caller cannot parse. Have counsel look at the exact wording, because this is one of the few places where a specific phrasing carries weight and where you should not copy the script off another restaurant's line.
Then give callers a route. If someone objects, there should be a way to continue without being recorded, which usually means a person picking up on a line that is not recorded. If your answer to an objection is "then hang up," you have a policy rather than a practice.
The line everybody forgets
Restaurants accumulate phone numbers. The main line, a catering line, a number a marketing agency issued years ago, an overflow path that rings a manager's cell, a forwarding rule set up during a snowstorm and never removed.
Whatever your recording practice is, it applies to all of them or it applies to none of them, and the one that is usually configured differently is the catering line. That is also the line carrying your highest-value conversations and the most detailed customer information. Inventory every path a call can take into your business, then check what each one does with recording. Most operators find at least one surprise.
Not every use case needs audio
Before settling the consent question, settle whether you need the recordings.
The most common reason operators give is order disputes, and audio is a heavy tool for that job. A timestamped order record showing exactly what was entered, with modifiers, usually resolves the disagreement faster than finding and playing a four-minute conversation. The accuracy work described in improving phone order accuracy depends far more on the order data than on the audio.
Training is a genuine reason to keep audio, and it needs a rotating sample rather than an archive. Complaint handling, discussed in handling refund and complaint calls, benefits from the record but rarely from a permanent one.
If you record everything by default, you did not decide to. Someone left a switch on.
Consent ends; retention does not
The permission to capture a call says nothing about how long you may keep what you captured, who inside your business or your vendor's business can listen, or what happens to it in a breach. Those questions live in a different body of law and in your own data practices, and they are where an accumulating archive turns into exposure.
Write down what you keep, in what form, for how long, and then verify that something actually deletes on that schedule. Call recording retention policy covers how to set one, and call recording and consent for restaurants frames the broader set.
The practical takeaway is one paragraph long. Announce recording on every line whether your framework requires it or not, keep the announcement short and reviewed by a lawyer, give objecting callers somewhere to go, and set a deletion schedule before you set anything else. Then spend the hour with counsel on the questions this article deliberately did not answer, because those answers depend on where you operate and this does not.