Online ordering support should be decided before the first rush
A restaurant does not need a big support department to take direct online orders.
It does need a simple support plan.
That plan answers the questions that show up once real guests start using the link: Who checks a delayed order? Who can approve a refund? Who talks to a customer who entered the wrong pickup time? Who fixes a menu item that keeps causing confusion? Who knows where to look when a guest asks about a card charge?
Those questions are easy to ignore during setup because the exciting part is getting the menu live. But the first busy shift will expose unclear ownership quickly. A customer calls about a missing side. A staff member sees a confusing note. A manager wants to refund an item but is not sure who should handle it. Suddenly the ordering system feels harder than it is.
OmNom gives restaurants direct online ordering with zero OmNom commission and zero monthly platform fees. Standard Stripe processing still applies. The support plan is what makes that direct model feel calm in the restaurant, not just clean on paper.
Name the owner for each type of question
Start by separating support questions into buckets.
Most restaurants do not need a complicated policy. They need a clear first answer for the common situations:
- pickup timing
- missing or incorrect items
- customer cancellation requests
- full or partial refunds
- payment or receipt questions
- menu errors
- delivery availability, if delivery is enabled
- staff questions about where an order appears
Then assign a role to each bucket. The cashier may answer basic pickup timing questions. A shift lead may approve minor fixes. The owner or manager may handle refunds and payment questions. The person who manages the menu should own item changes after repeated confusion.
The point is not to make the process rigid. The point is to prevent every issue from becoming a fresh debate during service.
Write the first version in plain language. For example: "Shift leads can approve replacing a missing item. Managers approve refunds. Menu changes go to the person who owns the online menu." That is enough to start.
Give staff one place to look first
Support gets messy when staff have to search across too many places.
Before the ordering link is promoted, decide where the team should look first when an online order question comes in. That might be the OmNom restaurant dashboard, the tablet at the counter, the order ticket, or the manager's account. What matters is that the normal shift team knows the first screen to check.
For each order, staff should be able to find:
- customer name or order identifier
- ordered items and modifiers
- pickup or delivery status
- order time
- payment status, when relevant to the role
- notes or special instructions
- refund or cancellation ownership
If staff cannot find that information quickly, the restaurant may start solving support issues from memory. Memory is not a support system. It is fine for a familiar regular, but it breaks down as soon as orders stack up.
Pair this support plan with a real launch rehearsal. Restaurant Online Ordering Test Order: What to Check Before You Share the Link gives a practical way to prove the order path before guests use it.
Decide what staff can promise about pickup timing
Pickup questions are usually the first support issue a restaurant sees.
Customers want to know whether the time on the order is real, whether they can arrive early, and what happens if the kitchen is behind. Staff need a consistent answer.
The support plan should define:
- who can update a customer when an order is delayed
- what staff say when the guest arrives early
- where completed orders wait
- how staff identify the order at handoff
- who adjusts prep-time settings if delays become a pattern
This matters because pickup support is not just customer service. It is kitchen flow, counter flow, and expectation management at the same time.
If the restaurant's pickup process is still loose, fix that before pushing the ordering link hard. A direct order should not make the customer feel abandoned between checkout and handoff. For a deeper pickup workflow pass, read Restaurant Pickup Order Handoff: How to Keep Direct Orders Moving.
Write a small refund and cancellation rule
Refunds do not need to be dramatic, but they do need ownership.
A good first policy answers three questions:
- Who can approve a refund?
- When is a replacement or remake better than a refund?
- Where does the reason get recorded?
Do not leave those decisions to whoever happens to answer the phone. During a rush, one employee may promise a refund while another employee remakes the item. The customer gets mixed messages, and the owner has to untangle the money trail later.
Keep the rule practical. A missing drink may be handled by a shift lead. A full order cancellation may require a manager. A card charge concern may go to the person who understands the payment trail. If a refund reveals a repeated menu problem, the menu owner should hear about it.
Direct ordering helps because the restaurant is closer to the order record and customer conversation. That does not remove the need for judgment. It simply makes the issue easier to trace when the team uses the system consistently.
For more detail on the money side, read Restaurant Refunds: Why Direct Ordering Is Easier to Control Than Marketplace Adjustments.
Treat menu confusion as a support signal
Not every support question is a one-time customer problem.
Sometimes the customer is showing the restaurant where the online menu is unclear.
Watch for repeated questions like:
- "Does this come with fries?"
- "Can I choose two sauces?"
- "Why did this add-on cost extra?"
- "I thought this item was available tonight."
- "Where do I write my allergy note?"
Those are menu setup signals. The support response should not stop at answering the customer. Someone should update the item description, modifier, availability rule, or category placement so the next guest does not hit the same confusion.
This is where direct ordering can improve operations over time. The restaurant sees the friction directly, learns from it, and fixes the owned ordering path instead of waiting for a third-party listing to reflect the change.
Keep the feedback loop simple: staff flag confusing orders, the menu owner reviews them, and only the real blockers get fixed right away. A restaurant does not need to rewrite the whole menu because two guests asked a question. It does need to notice patterns.
Know what changes when delivery is involved
Delivery support should not reuse pickup language.
A pickup customer is asking about the kitchen and counter handoff. A delivery customer may be asking about driver assignment, driver arrival, restaurant prep, and drop-off timing. Those are different states, and the restaurant should not casually promise what the delivery system cannot guarantee.
If delivery is enabled, the support plan should explain:
- when delivery is available
- who can answer restaurant-side preparation questions
- who handles driver or dispatch questions
- what staff should say when delivery is unavailable
- when a support issue should be treated as a refund, remake, or delivery-status problem
OmNom's delivery model is designed to be strict about availability. Delivery should only be offered when the restaurant is enabled, the customer is in range, and there is dispatchable driver capacity in the restaurant's zone. That means staff should avoid saying "delivery is always available" unless the live ordering page confirms it.
The clean support answer is honest: pickup is one workflow, delivery is another, and the ordering page should reflect what the restaurant can actually support right now.
Review support questions after the first week
The first version of the support plan will not be perfect.
That is fine. The goal is to make the first week calm enough that the restaurant can learn from real orders.
After the first few shifts, review the questions that came up:
- Did staff know where to find orders?
- Were pickup timing questions easy to answer?
- Did any refund or cancellation feel unclear?
- Did menu confusion repeat?
- Did payment questions go to the right person?
- Did any delivery language over-promise availability?
Then change the plan, not just the people. If three staff members misunderstood the same workflow, the workflow probably needs clearer ownership. If guests keep asking the same menu question, the menu probably needs an edit. If pickup delays keep creating calls, prep-time settings or handoff routines may need attention.
This review pairs well with Restaurant Online Ordering First Week: What to Watch After Launch. The support plan is one part of that broader first-week operating rhythm.
Where OmNom fits
OmNom is built for restaurants that want direct online ordering without giving up restaurant-side commission or paying a monthly platform fee. Restaurants can launch quickly, get free menu setup help, receive orders directly, and keep the economics straightforward. Standard Stripe processing still applies.
But direct ordering works best when the restaurant also owns the support routine.
That routine does not need to be complicated. Assign each question type. Give staff one place to look first. Decide pickup, refund, cancellation, menu, payment, and delivery ownership before service gets busy. Then use the first week of real orders to improve the plan.
A working checkout gets the order in. A clear support plan helps the restaurant keep the promise after the guest taps pay.
If your restaurant is ready for direct online ordering with zero OmNom commission and zero monthly platform fees, start with OmNom or open the restaurant app.