Harbor Table
A restaurant owner handed Telvon a disputed chargeback so the kitchen could stay on service.
Someone needed to speak for the restaurant when the processor pulled the funds.
I cannot sit on hold during service. Telvon took the file, assembled the documentation, and spoke with the processor on our behalf.
The challenge
Harbor Table is a neighborhood restaurant. A diner disputed a large party charge after the night was over. The processor pulled the funds. The owner had a receipt, a signed check, and no time to assemble a rebuttal.
The notice, the receipt, and the signed check were sitting in three different inboxes. The owner was running service, not reconstructing a rebuttal for the processor.
How the file was handed over
Telvon took the notice, the receipt, and the signed check. The team documented the reason code and submitted a rebuttal to the processor.
The file included:
- Chargeback notice with reason code, amount, and response deadline.
- Signed check and POS ticket for the original table.
- Any reply already sent to the processor or the bank.
- Written authorization for Telvon to speak for the restaurant.
“Telvon took the chargeback file so the kitchen could stay on service — I did not have to rebuild the rebuttal between tickets.”
What changed
The kitchen stayed on service while the file moved. No recovery amount is claimed here.
The owner kept a dated record of every notice without assembling a separate summary deck.
What this note is not
- Chargeback notice received during a service week.
- Kitchen stayed on service while Telvon assembled the file.
- Processor received a documented rebuttal, not a phone call.
- Owner kept a complete copy of every notice and reply.
- File status lived on the desk instead of a personal inbox.
This is an operator note, not a verified case study. Telvon does not publish recovery amounts or timelines unless the owner supplies them.
