Winning direct orders back from delivery apps

Direct orders matter because they usually cost less than app orders. Third-party delivery apps commonly charge restaurants roughly 15-30% commission per order, and that can add up fast on a $25 or $40 ticket. With direct orders, you keep more of the sale and you also get the caller’s name and number for future repeat business.

Here is a simple way to look at it:

Plug in your own average order. If you take a lot of pickup orders, even a few extra direct calls a day can matter more than a small jump in app volume. The point is not to quit apps overnight. The point is to keep the orders you can control.

A good owner rule is simple: every caller should get an easy path to order direct. If they have to wait on hold, repeat themselves, or hear “call back later,” they will go elsewhere. That is where a phone host like ROAL can help by answering the phone, quoting the order back, and sending the ticket straight to the kitchen.

Most restaurants lose direct orders on the phone before the customer ever reaches the menu. The problem is usually not the food. It is the wait, the confusion, or the missed call.

Start with this short checklist:

• Answer quickly, especially during rushes.
• Know your hours, address, parking, and best-selling items.
• Make pickup and delivery ordering easy to hear and repeat.
• Tell the caller the ready time before the call ends.
• Give a clean path for allergies, catering, and manager requests.

A simple phone script can help your team stay consistent: "Thanks for calling. We can take your order now for pickup or delivery. I’ll repeat it back, give you the ready time, and send it to the kitchen."

That script does three useful things. It tells the caller they can order now, it sets a clear process, and it gives confidence. If you use ROAL, it can handle this flow from your live menu and even speak the caller’s language. It also will not offer items marked sold out, which avoids the awkward back-and-forth that often kills a direct order.

To win direct orders back, your phone experience has to feel easier than opening an app and waiting on a driver estimate. That does not mean fancy tech. It means fewer steps and clearer answers.

Use this comparison as a practical target:

Here is a concrete example. Say a customer wants two slices, a salad, and a soda. On the phone, the order should sound like this: "Two slices, one salad, and one soda. Any dressing on the side? Great. Your total is $28, and it will be ready in about 20 minutes."

That feels fast. It also feels personal. If your team is too busy to do that during rush hour, an AI phone host can help. ROAL reads the live menu, takes items, sizes, modifiers, and notes, then confirms the order back before sending it to the kitchen screen. That is the kind of smooth experience that can bring direct callers back.

You do not need a huge discount to pull some customers back. Often, a cleaner promise works better than a coupon. People call direct when they expect faster help, fewer mistakes, and less hassle.

Try one of these messages on your menu, receipts, website, or social posts:

• "Order direct by phone for quick pickup help and menu questions."
• "Call us to place your order and get a ready time before you hang up."
• "Need substitutions or allergy questions? Call us directly."

If you want to make the switch more measurable, use a simple example:

• Say your average direct order is $30.
• Say one app order would cost you 20% in commission, or $6.
• If a caller switches to direct, you may keep that $6 inside the business instead of sending it away.

You can also use direct ordering for customers who want a human answer, not another checkout screen. That matters for older regulars, large family orders, and people with special requests. A phone host can help there because it can answer hours, address, parking, and menu questions while the caller is still interested. For common menu and ordering questions, see menu, hours and allergen questions.

A lot of direct orders are lost because the phone rings unanswered at the worst possible moment. Lunch rush, dinner rush, one person in the back, and suddenly the caller hangs up. That is why forwarding matters.

Most owners should know the basic setup options, but always confirm with your carrier or phone system and test it with a real call. On many landlines and some carriers, dial 72 then the forwarding number to forward all calls, and 73 to turn it off. On some GSM mobile carriers, *21number# forwards all calls and ##21# turns it off; *61number# forwards unanswered calls and *67number# forwards busy calls. Verizon Wireless uses 72 / 73, and *71 for busy/no-answer forwarding. Business VoIP systems usually set forwarding in the web portal.

Use this checklist before you go live:

1. Test forwarding during a quiet hour.
2. Call from a mobile phone and make sure it rings where you expect.
3. Check that the caller can still place an order normally.
4. Make sure staff know when forwarding is on and off.

ROAL gives each location its own phone line automatically once the owner claims the host, and the restaurant can forward its existing number to it. That means you can send all calls, or only busy and unanswered calls, depending on your setup. The restaurant keeps its own number, and forwarding can be turned off any time.

Winning direct orders back is not only about the first call. It is about making the second call easier. If a customer had a good phone experience, they are more likely to use the same number again.

The best repeat-order habits are simple:

• Save the customer’s name and number when the order is taken.
• Give a clear ready time every time.
• Keep the kitchen ticket clean so the order comes out right.
• Answer questions once, then keep that answer for next time.

Here is a practical repeat-order routine you can use:

• Customer calls for a pickup order.
• The host confirms items, sizes, modifiers, and notes.
• The host repeats the order back.
• The kitchen gets a clean ticket.
• Next time, the caller already knows the process is easy.

ROAL includes call history with transcripts and recordings, plus a menu editor, hours, FAQs, upsell suggestions, and multi-location menus in the dashboard. If the host cannot answer a question, it goes to an inbox. You answer it once, and the host knows it from then on. That helps the phone get better over time without making the customer wait.

You do not need a complicated marketing plan to start. You need a few numbers you can check by hand. Pick one week and track what happens on the phone.

Use this simple scorecard:

Then ask one question: where are callers getting stuck? If the problem is hours and address questions, fix your public info. If the problem is slow ordering, tighten your script. If the problem is missed calls, set up forwarding or use an AI phone host.

If you want a simple place to start, build a free test host from your website. You can paste your restaurant website, Google Maps link, or name and city, then test-call it in the browser before deciding whether to go live.