Key takeaways
- Disputes are decided on records: the policy shown, the guest's agreement, the reminders and the no-show log.
- A cardholder's written billing-error notice must reach the card issuer within 60 days of the statement[1]; card networks add their own timelines.
- If you record booking calls, check consent rules: some states, such as California, require every party's consent[2].
- Fighting a small dispute takes manager time, at a median wage of $33.36 an hour[3], so set a threshold for letting go.
How a dispute reaches you
A chargeback starts when a guest tells their card issuer they do not accept a charge. The issuer passes the dispute through the card network to your processor, which notifies you, usually with a reason and a deadline to respond, and often reverses the money while the case is open. You answer through your processor's dispute portal with evidence, and the issuer decides. You do not argue with the guest's bank directly, and you cannot win by phoning the guest after the dispute is filed, although a refund at that point can end it.
Timelines are set by the networks and your processor, so learn yours. Separately, the Fair Credit Billing Act requires a cardholder's written notice of a billing error to reach the creditor within sixty days after the statement was transmitted[1]. In practice, a guest can raise a dispute weeks after the night itself, which is why the evidence has to be captured at the time, not reconstructed later.
Why guests dispute no-show fees
- They did not recognize the charge because the descriptor did not name the restaurant or the fee.
- They believe they cancelled, for example by calling during service when nobody answered.
- They did not know about the policy, because it was buried or never read out on the phone.
- Something happened, such as illness or an accident, and nobody gave them a chance to explain.
- Someone else in the party made the booking with their card.
- The amount felt out of proportion to a missed dinner.
The second cause is the most avoidable. In Cornell's survey of frequent diners, respondents often found it difficult to contact a restaurant when they needed to change a reservation[4]. A guest who tried to cancel and could not get through will feel entitled to dispute, and the issuer may agree. Fix the cancel path and you remove a large share of disputes before they start.
Build the evidence at booking, not after
Everything that wins a dispute is created before the night. Set up your booking flow so each item below is captured automatically or with one click, and keep it attached to the booking record.
- The booking record with the date and time it was made, the channel, party size and the guest's contact details.
- The exact policy text the guest saw, with a version number or date, not just today's policy.
- Proof of agreement: the ticked box and its timestamp online, or the staff member's note of a verbal yes on the phone.
- How the card was captured: the secure form or link used, never a number written on paper.
- The confirmation message and every reminder, with delivery status and any replies.
- The host's record for the night: the booking marked no-show, the time, and any attempt to call the guest.
- The fee receipt sent to the guest, with the policy line that applied.
Storing consent properly
Online consent is easy to prove if the box is unticked by default and the policy appears beside it. Phone consent is harder. Give hosts a script that reads the policy word for word and asks for a clear yes, then send the same wording by text or email straight away, so there is a written record the guest received. If you record booking calls, remember that federal law generally allows recording with one party's consent, but some states, such as California, require the consent of all parties[2]. Announce recording at the start of the call.
Keep records for longer than the longest dispute window you face, and store them securely. Card numbers belong only in your processor's systems. The rest of the record should live in the reservation system, not in a host's personal phone or a shared inbox.
The response packet, step by step
Read the reason and deadline
Note the reason the guest gave and the date your response is due. Put the deadline in the manager's calendar the same day.
Pull the booking record
Export the booking with its creation time, channel, party size and contact details.
Attach the policy
Include a screenshot of the policy as the guest saw it, with the version date.
Attach the agreement
Add the ticked-box record or the phone note and the confirmation message that repeated the policy.
Attach the messages
Add every reminder with delivery status, and any replies, or the absence of replies.
Write a short summary
Explain in a few plain sentences what was booked, what was agreed, what happened and which rule applied.
Submit and log
Submit before the deadline, then record the outcome so you learn which evidence works.
Sample summary
Example summary: “The cardholder booked a table for 8 on Saturday 14 June at 7:30 p.m. through our website on 2 June. Before entering card details they ticked a box agreeing to our cancellation policy (attached, version dated 1 May), which charges a per-guest fee for cancellations after noon on the day or no-shows. A confirmation repeating the policy was sent on 2 June and a reminder on 13 June; both were delivered and neither received a reply. No one from the party arrived, and our host called the number on file at 7:50 p.m. without answer. The fee was charged on 15 June and a receipt sent the same day.”
When to let it go
| Situation | Respond or let go | Reason |
|---|---|---|
| Complete records and a clear no-show | Respond | This is what the evidence is for |
| Guest has proof they cancelled in time | Refund | The policy was followed by the guest |
| Guest says they called and nobody answered | Usually refund | Hard to disprove and a sign the cancel path failed |
| Phone booking with no written confirmation | Usually let go | Weak proof of agreement |
| Small amount, high manager time | Let go and fix the process | The time costs more than the fee |
| Repeat no-show with a documented history | Respond | Consistency protects the policy |
Count the time honestly. Assembling a packet takes a manager away from the floor, and the median wage for food service managers was $33.36 an hour in May 2025[3]. Set a threshold below which you refund and fix the cause instead of fighting.
Example: two disputes, two outcomes
Example: a fictional steakhouse receives two disputes in the same month. The first is a party of six booked online, with a ticked policy box, a delivered confirmation and a delivered reminder, and a host note of a call at 8:05 p.m. that went to voicemail. The manager submits the packet with a four-sentence summary, and the issuer rules for the restaurant.
The second is a party of four booked by phone during a busy service. The host took the card but did not read the policy aloud, and no confirmation was sent because the guest gave no mobile number or email. The guest says they were never told about a fee. The manager refunds the charge, then changes the phone script and makes a confirmation channel a required field for any booking with a card hold. The lesson from both cases is the same: the result was decided at booking, weeks before the dispute arrived.
Prevent the next dispute
Most disputes are prevented by small habits. Use a descriptor that names the restaurant and the fee. Before charging, send a short note: “We missed you tonight. Under the policy you agreed to, a no-show fee applies. If something happened, reply and a manager will review it.” Send the receipt the same day. Text works for most guests, but smartphone ownership is lower among older adults[5], so send confirmations by email as well when you have an address.
Source: Pew Research Center, 2026[5]
Show the data
| Item | Value |
|---|---|
| 18-29 | 97% |
| 30-49 | 97% |
| 50-64 | 91% |
| 65+ | 79% |
Finally, be consistent. Diners accept card guarantees as fair[6], and that acceptance depends on the rules being applied the same way to everyone. Waivers are fine when they follow written exceptions. Random leniency, followed by a hard charge for the next guest, is what makes a fee feel unfair and pushes guests to their bank.
Frequently asked questions
How long does a guest have to dispute a no-show fee?
It depends on the card network and the issuer. Federal law separately requires a cardholder's written billing-error notice to reach the creditor within 60 days of the statement. Keep your records for longer than the longest window you face.
Should we refund as soon as a dispute arrives?
Only if your records are weak or the amount is small. With a complete evidence packet and a clear no-show, responding is reasonable. Either way, fix whatever caused the dispute.
Does a recorded phone call help?
It can, if the recording was lawful. Announce recording at the start of every call, because some states require all parties to consent.
References
Legal Information Institute (Cornell Law School), US Code (2026). 15 U.S. Code § 1666 - Correction of billing errors (opens in a new tab) ↑
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) ↑
US Bureau of Labor Statistics (2025). Occupational Employment and Wage Statistics, May 2025 national estimate: Food service managers median hourly wage (series OEUN000000000000011905108) (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, 2008) (opens in a new tab) ↑
Pew Research Center (2026). Americans’ Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑
Cornell University (Sheryl E. Kimes) (2011). Customer Attitudes towards Restaurant Reservations Policies (Kimes, Journal of Revenue and Pricing Management, 2011) (opens in a new tab) ↑