Phone order accuracy: read-backs, modifiers and kitchen tickets

A phone order goes wrong at one of five points: the guest is misheard, a required choice is skipped, a change does not reach the ticket, an allergy stays in the order taker's head, or the ticket prints in a way the cook misreads. Make choices required in the POS, read back from the screen, print allergies on the ticket, and count errors per 100 phone orders.

This guide covers the order and the ticket. Our restaurant phone scripts have the words for the read-back, and our drive-thru order guide covers mistakes at the speaker and the window.

Where do phone order mistakes start?

Point	Example	Fix in the POS or the routine	How to check it
Hearing	"Two chicken" heard as "one chicken"	Read back quantities as numbers: "two chicken sandwiches"	Guest confirms each quantity out loud
Required choice	A burger goes through with no temperature	Make the group required so the item cannot be sent without it	Try to send the item with the choice blank
Change	"No onions" typed as a free-text note that the kitchen printer drops	Build common changes as modifiers, with NO, ADD, EXTRA and ON SIDE	Print a test ticket with three changes
Allergy	The order taker hears "nut allergy" and remembers it, but nothing prints	An allergy modifier or item note that prints on the ticket, plus a manager check	Print a ticket with an allergy and show it to the cook
Ticket	Modifiers print in a long line and the cook misses one	Printer settings: group names, one modifier per line, larger font	Ask the line to read three test tickets aloud

How should modifiers be set up for phone orders?

Set up the POS so the screen asks every question the kitchen needs answered. The order taker then only has to answer the prompts. Toast, Square and Clover each document the settings.

POS	Required choices	Changes such as "no" and "extra"	Free-text requests
Toast	A required modifier group blocks sending the item to the kitchen without a selection; a minimum count is set only on required groups	Pre-modifiers such as NO, SUB, ADD, EXTRA and ON SIDE print on kitchen tickets	Print a test ticket to see how a special request shows
Square	Selection rules set whether a choice is required and the minimum and maximum; Square Restaurants steps staff through required sets in order	Conversational modifiers show Add, No and Extra buttons	A text modifier holds up to 150 characters and can be made required
Clover	Each modifier group has a minimum and maximum	Build them as modifiers in the group	Order notes print when the setting is turned on

One Toast detail matters for phone orders taken on more than one channel. Toast says that if a modifier group is not visible on a channel, it will be missing from orders on that channel even if it is marked required. Check visibility on the POS screen your phone staff use.

Before any change, list your ten most-ordered phone items and the questions the kitchen asks about each. Our menu preparation worksheet gives a format for that list, and it works whether a person or software takes the call.

How should the read-back work?

Read the order back from the POS screen once the guest has finished. The screen is what the kitchen will get, so it is the thing to check. Keep the same order every time:

1. Each item with its quantity, as a number.
2. Every choice and change under that item, in the order the ticket will print them.
3. Any allergy, in the guest's words, and who will check it.
4. The name and phone number, digit by digit.
5. Pickup or delivery, and the clock time.
6. The total, if you are taking payment now.

If the guest changes something during the read-back, change it on screen and read that item again. Do not add a change to a paper note to key in later.

Where should an allergy go on the ticket?

Put it where the cook will see it on every ticket, and bring in the person who can answer for the kitchen. The FDA's 2026 Food Code is a model that state and local governments choose whether to adopt. It makes the person in charge responsible for employees being trained in food allergy awareness as it relates to their duties. Paragraph 3-602.12(C) also says the permit holder shall notify consumers in writing when a major food allergen is an ingredient in unpackaged food. Check which edition your health department enforces.

Some states go further. Massachusetts' allergen awareness rules require menus and menu boards to carry this notice: "Before placing your order, please inform your server if a person in your party has a food allergy." A caller cannot see your menu, so ask the question out loud: "Does anyone in your order have a food allergy?"

Then make the allergy print:

• Square: item notes appear on order tickets even when you hide them on customer receipts.
• Clover: turn on order notes in the order receipt settings so they print for the kitchen.
• Any POS: add an "ALLERGY" modifier to the items that need it, so it prints on its own line.

This is not legal advice. Your health department sets the rules where you operate.

What should you check on the printed ticket?

Print a test ticket for your five most-changed items and hand it to the line cook without saying what is on it. Ask them to read it aloud. Anything they skip or misread is a printer setting to fix.

• Clover lets you print modifier group names, condense modifiers onto one line, print customer information, and split one order into separate station tickets by label.
• Square order tickets list customizations and special instructions, can print kitchen-facing names, and can send categories to different printers.
• Toast prints pre-modifiers on kitchen tickets. Check how your special requests print with a test order.

Put the guest's name and pickup time on the ticket so the counter can match the bag at handoff. If the kitchen works from a screen, run the same test on it. Our kitchen display guide covers the screen side.

How do you measure phone order errors?

Keep a log at the counter for two weeks. Write down every phone order that came back wrong, from complaints, remakes and refunds. For each one, record the date, the ticket number, what was wrong, and the point where it started from the table at the top of this page.

Then divide errors by phone orders and multiply by 100. Here is a made-up week:

Point where the error started	Errors
Hearing (wrong item or quantity)	2
Required choice skipped	1
Change missing from the ticket	3
Allergy note missing	0
Ticket misread in the kitchen	1
All points: 7 errors in 180 phone orders	3.9 per 100 orders

In this example, changes cause the most errors, so build the common changes as modifiers first. With 180 orders, each error moves the rate by about 0.56 per 100, so one bad shift can swing a week. Compare the same weeks after the fix and before it.

The log misses errors guests do not report. Once a week, pull ten phone tickets at random and ask the order taker to compare each with what they remember of the call, or with a recording if your phone system keeps one and your local law allows it.

Does AI order-taking change where mistakes start?

An AI order-taker hears the guest and keys the order. The ticket, the kitchen and the handoff stay with your team, so the same checks apply. Maple Pro takes phone orders into supported POS systems, listed on the integrations page. The product page test uses the same checks as this guide: a required choice, a modifier and a change, compared with the final ticket. Log AI-taken and staff-taken phone orders as separate groups in the error log.

Published by Maple. This AI-assisted guide combines Toast, Square and Clover help pages, the FDA's 2026 Food Code and Massachusetts allergen guidance with an original error map, read-back order and error log. The example week is made up. It is not legal advice, and it does not report a Maple test or promise fewer mistakes from any product.