For a missing item, the restaurant usually investigates the order and packing record first. For a late delivery, start with whoever controls the driver or dispatch. For a payment issue, start with the business that took the payment. The restaurant should still name one person to follow the complaint through, even when another company must make the correction.
That distinction matters. The person who owns the guest conversation may not have the tools to issue a refund, locate a driver, or change a charge. Your handoff should identify both the follow-up owner and the party with authority to fix the problem.
Map the channel and fulfillment partner
Before deciding who handles a complaint, establish how the order reached the kitchen and how it was fulfilled. An order placed on your own website can still be delivered by an outside courier. A marketplace order can be picked up by the guest, delivered by marketplace dispatch, or handled under another arrangement.
Record these details for each channel you use:
- Order source: Your direct website, a marketplace, or another ordering channel. The order confirmation and order dashboard should help identify it.
- Fulfillment: Guest pickup, restaurant delivery, or an outside delivery partner. Your shift lead should know which arrangement applied to the order.
- Payment collection: Who charged the guest and which system shows the transaction. Ask your payment and channel providers how to identify the collector.
- Correction authority: Who can adjust a charge, authorize a refund, arrange a replacement, or investigate delivery. Confirm this in your agreements and provider workflows.
- Contact path: The dashboard, support contact, or internal manager responsible for the next action, including after hours.
Do not assume that the logo on an ordering page tells you who controls every part of the order. Your restaurant website may be the guest's starting point, while payment and delivery involve separate providers. Likewise, a marketplace order can require the restaurant and marketplace to coordinate.
Give each channel a short reference card at the counter or in the manager's workspace. Include the shift role that receives complaints, the systems they can access, and the escalation contact. Avoid putting passwords or full payment details on the card.
Assign the fix and the follow-up
Use the table as a starting responsibility matrix, not as a promise about a particular provider. The follow-up owner keeps track of the case and tells the guest what happens next. The correction owner is the party to check first for the action described; confirm the actual authority for each channel before service.
| Issue and order path | Follow-up owner | Correction owner to check first | First action |
|---|---|---|---|
| Missing item, direct or marketplace order | Restaurant shift lead | Restaurant for preparation; channel or delivery partner if their action is needed | Compare the order with the packing record and agree on replacement or remedy. |
| Late delivery, restaurant driver | Restaurant shift lead | Restaurant dispatch or driver supervisor | Check dispatch status and give the guest a realistic update. |
| Late delivery, outside dispatch | Restaurant shift lead | Delivery or marketplace dispatch, depending on the arrangement | Check when the order was ready, then request a driver status. |
| Payment issue, direct order | Restaurant manager | Payment collector or processor, depending on the action | Locate the transaction and check who can correct it. |
| Payment issue, marketplace order | Restaurant manager | Marketplace or other payment collector | Match the order and payment reference; ask the collector for the correction path. |
For a missing item, first check whether it was ordered, prepared, and packed. If the restaurant missed it, the shift lead can decide what the restaurant is able to offer. A replacement may solve the problem, but it also requires a practical way to get it to the guest. If an outside party must arrange another delivery or approve a payment adjustment, contact that party rather than promising an action you cannot perform.
For a late delivery, separate kitchen delay from dispatch delay. Record when the order was accepted and ready, then check pickup and delivery status with the party that has it. If the food is still at the restaurant, the shift lead can decide whether quality has suffered and what to offer. If a driver has it, dispatch may be the only party able to locate the driver. Avoid giving an arrival time until the responsible party can support it.
For a payment issue, a manager should identify the charge and ask the collector about the available correction. A payment showing as pending may need a different response from a completed charge. Do not promise that a charge has been reversed merely because a request was submitted. Tell the guest who is handling it and when your team will check the status again.
If the guest contacts the wrong business, avoid a dead-end handoff. Give the appropriate contact route and, where your arrangement permits, pass along the order reference and issue summary. Keep the restaurant's follow-up owner assigned until the guest knows the next step.
Prepare a shared evidence checklist
A useful handoff contains enough information for the next party to act without making the guest repeat the entire story. Keep the record factual and brief:
- Order reference, channel, date, and the guest's preferred contact method.
- Pickup or delivery method, plus the dispatch partner when relevant.
- Items ordered and the specific item or charge in dispute.
- Available timestamps: acceptance, preparation or ready time, pickup, and delivery.
- Payment reference and status visible to staff, without copying full card details.
- Actions already taken, who can make the next correction, and the next follow-up time.
Use the least sensitive information needed to resolve the complaint. Follow your own access rules for order and payment records; a shared shift note should not become a repository for card numbers or unnecessary guest details.
Walk through one hypothetical complaint
Assume a guest places a direct order for two meals and a side. An outside delivery partner collects it. The guest reports that the side is missing. The shift lead finds the order reference, checks the kitchen and packing notes, and sees that the notes do not establish whether the side went into the bag.
The lead remains the follow-up owner. They check what remedy the restaurant can offer and whether another delivery can be arranged. If a payment adjustment is appropriate, they check who can authorize it and what the guest needs to do. The case note records the uncertainty about packing rather than assigning blame without evidence. The guest receives a clear next update time.
This example shows the handoff, not a guaranteed outcome. Your records may not prove what happened after the bag left the kitchen, and your delivery agreement may limit who can arrange a replacement. The useful result is a named owner and a documented next action, even when the cause remains uncertain.
Review handoff failures and practice the process
Once a week, a manager can review a small sample of closed and open complaints by channel. Look for cases where the guest was sent between parties, a support request lacked an order reference, or a promised update never happened. Count repeat handoffs separately from the underlying problem: a late delivery and three transfers are different failures.
Turn patterns into a specific change. If staff repeatedly contact the payment processor before checking which business collected the payment, add that check to the reference card. If outside dispatch needs a ready time that staff rarely record, decide who records it during the shift. If no one has authority after hours, name the manager who will acknowledge the complaint and set the next update.
Practice with a simulated order and fictional guest details before changing the live workflow. Ask one employee to report a missing item, another to act as shift lead, and a third to play the outside partner. Check whether the lead identifies the channel, names the correction owner, records the uncertainty, and sets a follow-up. Keep the exercise out of live systems or use a designated test environment: it must not trigger a real payment, guest message, or courier dispatch.
A live service pilot is different. If you introduce the process on one shift, use it for actual complaints as they arise, with the normal guest and provider communications. Review the notes afterward and adjust the handoff. Do not create a real charge, send a test message to a guest, or dispatch a courier just to see whether the process works.
When evaluating tools, ask vendors which order, payment, and delivery details staff can see; who can make each correction; and how a case is handed to another provider. The online ordering buying guide can help frame those questions. For a broader look at channel economics, use the guide to direct and marketplace order contribution.
Next, fill in the matrix for your busiest channel and review it with the next shift lead. For a direct-ordering setup, ask Fleksa about its restaurant online ordering, the relevant handoff workflow, and current US availability.
Frequently asked questions
Who owns a complaint when an outside courier is involved?
Assign a restaurant employee to follow up with the guest. The dispatch provider may need to investigate the driver or arrange a delivery action, depending on the agreement.
Should the restaurant refund every missing item?
Not automatically. Confirm the order, consider the remedy available, and identify who has authority to adjust the payment. A replacement may also be an option if it can reach the guest.
What should staff do if they cannot identify the payment collector?
Keep the manager assigned to the case, match the order and transaction references, and ask the channel or payment provider to identify the correction route. Give the guest a time for the next update.
