Single location
One restaurant with steady phone orders.

OrderFlow answers your pickup calls, takes the order from your menu, and gives your staff a ticket to check before it reaches the kitchen.
Sample audio uses synthesized voices.
2 margheritas · 1 house salad
Sample order · View it ↗Every call, a warm welcome. Your menu and opening hours shape the conversation. The guest can ask a question without pulling someone away from the pass.
Of course. Two 12-inch margheritas with extra basil. Would you like anything else?
Interactive sample. Select a stage to follow the order.
SAMPLE CALL
Hear a sample pickup order and the ticket your staff would check.
Scripted audio example · synthesized voices. This illustrates the experience; it is not a recording of the live agent.
Pizza Palace, this is Alex.
Hey, yeah. Hi. Can I get—hold on. Sorry. Yeah. Two large pepperoni, one with no onions, and a chicken wing combo, and a two-liter Coke.
No problem. Two large pepperoni, one with no onions, one chicken wing combo, and a two-liter Coke. Did I get that right?
Illustrative continuation · not spoken in the audio. Move the no-onion request to the other pizza.
“Actually, make that no onions on the second pizza, not the first.” The no-onion request moves to pizza two, and pizza one returns to standard toppings.
Illustration only. Your staff check every order before the kitchen.
Rehearse an order, test sold-out items or busy pickup rules, and see exactly what reaches the kitchen before you forward a single call.
Sample data. No call is placed and nothing is connected.
Answer every pickup call, keep orders accurate to your menu, and keep your staff focused on cooking.
No hold music, no missed pickup orders while the line is three deep.
Your items, sizes, modifiers and hours. “No onions on the second one” stays with the right item.
Your staff see each ticket before the kitchen does. Callers can ask for a person, and one switch turns the AI off.
Start small: one shift or overflow calls. Nothing goes live until you say so.
Checked tickets can be sent to Toast once that restaurant is connected. Until then, your team runs each order through the usual kitchen process.
A photo, PDF or spreadsheet. We check items, prices, options and hours with you.
Start with one shift or overflow calls only. Your main number stays the same.
Each order lands as a ticket. Your team checks it and runs it through your usual kitchen process.
We’re starting with a small number of local restaurants. Your staff review every ticket, and we watch every call together for the first shifts. No restaurant is live on OrderFlow yet, so you’d be one of the first, and you’d help shape it.
Pilot terms are agreed with you before any live call. Plans start after the pilot, if it’s working for you.
One restaurant with steady phone orders.
Busy restaurants and weekend rushes.
Every plan includes
Several locations, or want help? Tell us about your restaurants and we’ll help you plan setup. An enquiry doesn’t start a subscription.
Talk to us about a group ↗Yes. It says so when it answers.
They can ask at any time. It can transfer to a number you choose, or take their name and number for a callback.
No. You forward calls from your existing number when you want help, for example during one shift. Your phone provider needs to support call forwarding.
When Toast is connected, your staff send the checked ticket into Toast. Until then, they enter it the way they do today.
Guests pay at pickup for now. A texted payment link is included once texting is turned on.
Restaurant name and email is all we need. We’ll set up a short call about your menu and busy hours. Nothing goes live until you say so.