Almost nobody orders a menu item exactly as it's written. They want the burger medium-well with no onions, the combo with a Diet Coke, the dressing on the side and the fries swapped for sweet potato fries. In your POS, every one of those is a modifier. On the phone, every one of them is a chance for the order to go wrong.
Modifiers are where AI voice ordering succeeds or fails. An agent that handles the easy order but stumbles on "swap the slaw for mac and cheese, the large one" sends wrong tickets to the kitchen and unhappy guests back to the phone. This guide explains what modifiers are in voice ordering, the substitution patterns guests actually use, where phone orders break, how to get your menu ready and how to keep it accurate after launch.
Quick Answer: How Should an AI Voice Ordering Agent Handle Modifiers?
- Build every order from the modifiers in your POS, not from free-text notes.
- Ask for every required choice, like size, temperature or side, before moving on.
- Map substitutions to options that exist, and quote any upcharge.
- Say no politely and offer the closest option when a request isn't something you offer.
- Read the order back and send it to the POS only after the guest confirms.
What Are Menu Modifiers in Voice Ordering?
A modifier is any choice or change attached to a menu item. In Toast, Square, Clover, NCR Aloha and most other POS systems, modifiers live in modifier groups, such as "Bread," "Temperature" or "Add Toppings." Each group has rules: whether a choice is required, how many options a guest can pick and what each option costs. For voice ordering, the main types are:
- Required choices: size, meat temperature, bread, side or dressing. The kitchen can't make the item without them.
- Optional add-ons: extra cheese, add bacon, add avocado, usually with a price.
- Removals: no onions, no mayo, hold the pickles.
- Substitutions: swap fries for a side salad, oat milk instead of whole, a gluten-free bun instead of the regular one.
- Amount and placement: extra sauce, light ice, dressing on the side, well done.
- Nested modifiers: a combo where the drink has its own size and the side has its own options.
- Split items: half pepperoni, half mushroom.
- Special instructions: free-text notes like "cut it in half," if your kitchen accepts them.
A voice agent has to turn the way a guest says each of these into the exact option your POS expects, so the ticket that prints in the kitchen matches what the guest asked for. For the basics of how voice ordering works, see AI voice ordering, explained.
Why Modifiers Are Where Phone Orders Go Wrong
- Guests don't use your menu's words. They say "the spicy one," "a large fry" or "the chicken thing with the ranch."
- Changes come in any order. Mid-sentence, after the fact or both: "Actually, make that two, and one with no cheese."
- Required choices get skipped. During a rush, nobody asks how the steak should be cooked, and the ticket goes out incomplete.
- Notes become a junk drawer. Substitutions typed as free-text notes get missed on the line, and they can't carry a price.
- Upcharges get lost. A swap that should cost $1.50 rings in for free.
- The menu changes under you. An item that sold out at 6 PM is still being promised at 7.
When someone writes a phone order on a notepad and rings it in later, these mistakes add up. An AI agent can do better, but only if the menu underneath it is set up well and the agent is built to handle modifiers rather than guess at them.
Substitution Patterns: How Guests Actually Ask
Guests use a small set of patterns over and over. A good agent recognizes each one and turns it into the right modifier:
- "Swap," "sub" or "instead of": "Can I get fries instead of the slaw?" The agent replaces the default side with the chosen option and quotes any price difference.
- "No X, add Y": "No onions, add jalapeños." One removal and one add-on, each mapped to its own modifier.
- "Make it a…": "Make it a combo," "make it a large," "make it spicy." An upgrade that often changes the item or the price.
- "Same, but…": "Two of those, but one without cheese." The agent should split them into two lines instead of applying the change to both.
- "On the side," "light" or "extra": amount and placement modifiers, if your menu has them.
- "Half and half": split toppings or a split plate, if your POS supports it.
- "Do you have…?": "Do you have oat milk?" A question that becomes a substitution once the guest hears yes.
- Requests that aren't on the menu: "Can you make it with brown rice?" when you don't offer brown rice. The agent should say so and offer what you do have.
The last one matters most. The bad outcome isn't a guest hearing "We don't have brown rice, but we have white rice or a side salad." It's an agent saying "Sure!" and the kitchen finding out when the ticket prints.
When the Agent Gets It Wrong: Intent Failures and How to Catch Them
An intent failure is when the agent misunderstands what the guest wants. With modifiers, the usual ones are:
- Wrong item: hearing "chicken sandwich" as "chicken tenders" when you sell both.
- Wrong modifier: mapping "spicy" to the wrong sauce, or "large" to the wrong group.
- Missing required choice: a steak sent with no temperature.
- Change on the wrong item: "no cheese" applied to both burgers when the guest meant one.
- Missed correction: the guest says "actually, no bacon" and the bacon stays on.
- Unsupported request accepted: a substitution promised that the kitchen can't make.
Each one costs more than the order itself: a remade meal, a refund, a callback and sometimes a bad review. The safeguards are simple, and any agent you use should have them:
- Ask for required choices before moving on to the next item.
- Confirm upcharges out loud when a substitution changes the price.
- Read the full order back, including every modifier, and let the guest correct it.
- Hand the call to a person when an order gets unusual or the guest gets frustrated.
- Keep call transcripts, so you can compare what the guest said with what the ticket says.
Large orders with many custom changes are often better handled by a person anyway. Our guide to catering calls covers how to route those.
Voice Ordering Readiness: Is Your Menu Set Up for Phone Orders?
Most phone ordering problems are really menu problems. Before you launch any voice agent, check your POS menu against this list:
- Item names guests say out loud. If guests call your "Big Kahuna" the pineapple burger, make sure your vendor knows both names.
- Clearly named modifier groups. "Choose Your Side" beats "MOD GRP 14." These names are what the agent works from.
- Required and optional set correctly. If an item needs a temperature, mark that group as required.
- Limits on choices. Set the maximum number of toppings or sides, so an order can't come out impossible.
- Prices on modifiers. Every paid add-on and upcharge substitution should carry its price, so phone orders total correctly.
- Allowed substitutions listed as options. If fries can become onion rings for $1, that should be an option in the side group, not something your staff just know.
- Dine-in-only and test items hidden. Anything that can't be ordered for pickup shouldn't be orderable by phone.
- Sold-out items kept current. Mark items sold out in the POS as you run out.
- Combos built properly. Each part of a combo should have its own choices, so it rings in as one item with the right options.
- A notes policy. Decide whether the kitchen accepts free-text special instructions, and which kinds.
Each POS handles this a little differently. Our guides for Toast, Clover, Square, NCR Aloha and Olo go into the details.
Menu Governance: Keeping Phone Orders Accurate After Launch
A menu that's set up perfectly in March is out of date by June. Governance just means deciding who owns the menu and how changes happen, so the phone keeps up:
- One owner per brand for the POS menu, with a backup.
- Change the menu in the POS and nowhere else. If the agent reads your menu from the POS, one change updates the phone too. If changes have to be made in two places, one will get missed.
- Test after every menu change. Place a phone order for the new or changed item and check the ticket.
- Review a few orders every week. Compare transcripts with the tickets they created, especially orders with several modifiers.
- Track wrong-order complaints by item. If one item keeps coming out wrong, the problem is usually how that item or its modifiers are set up.
- Set up seasonal menus the same way. Holiday and limited-time items need the same modifiers and prices as the core menu.
For groups with many locations, this fits into the same weekly routine as the rest of the phone. See our guide to multi-location restaurant phone calls.
How to Test Modifier Handling in a Demo
- Order your most complicated item, with several modifiers.
- Make a substitution that costs extra, and listen for the upcharge.
- Skip a required choice, and see whether the agent asks for it.
- Order two of the same item with a change to only one.
- Change your mind mid-order: "Actually, no bacon."
- Ask for something you don't offer, and see whether the agent says no and suggests an alternative.
- Mark an item sold out in your POS, then try to order it.
- Open the ticket in your POS and check every item, modifier, price, note and the pickup time.
The restaurant AI phone agent buyer's guide has the full checklist, and our post on what a restaurant phone bot can and can't do covers where a person should take over.
How HeyTARA Handles Modifiers and Substitutions
On the Main Course plan ($199/month per location), TARA takes takeout orders by phone in natural conversation, including combos, substitutions, add-ons and pickup times, and sends them into your POS as tickets. Every plan includes unlimited calls and no commissions.
- Built from your POS menu: TARA uses the items, modifier groups and prices you already have in Toast, Clover, Square, SpotOn, NCR Aloha, SkyTab or any POS that uses Olo, so every option on the ticket is one your POS can ring in.
- Real-time menu sync: price changes and items you mark as sold out carry over without anyone updating the AI by hand.
- Required choices: TARA asks for things like size or how a steak should be cooked when the item needs it.
- Intelligent upselling: TARA suggests add-ons based on the order and the conversation, or promotes the items you choose.
- SMS order confirmations and payments by text: guests get a text confirming their order details and can pay through a secure link.
- Warm handoff: when a call needs a person, TARA briefs your team member on why the guest is calling before connecting them.
- Call transcripts for checking orders, training and resolving disputes.
- Spanish: TARA understands and responds to callers in Spanish.
Clean, clearly named modifier groups make phone orders faster, and we help with that during setup. Paying for the year up front saves 25%. Want to know what it costs across your stores? See what AI phone answering costs or try the ROI calculator.
The Bottom Line
Phone orders are rarely wrong because of the main item. They're wrong because of the side that didn't get swapped, the cheese that should have been left off or the upcharge that never rang in. Set up your modifiers properly in the POS, use an agent that builds orders from them, asks for required choices and reads the order back, and keep one person in charge of the menu. Then the ticket that prints in the kitchen matches what the guest asked for.
Frequently Asked Questions
What are menu modifiers in voice ordering?
A modifier is any choice or change attached to a menu item: a size, a meat temperature, an add-on, a removal like no onions or a substitution like fries instead of slaw. In voice ordering, the AI agent has to turn the way a guest says each change into the exact modifier your POS expects, so the kitchen ticket matches what the guest asked for.
What are the main types of menu modifiers?
Required choices (size, temperature, bread, side), optional add-ons (extra cheese, add bacon), removals (no onions), substitutions (swap fries for a salad), amount and placement (extra sauce, dressing on the side), nested modifiers inside combos, split items like half-and-half pizza, and free-text special instructions if your kitchen accepts them.
Can an AI phone agent handle substitutions?
A good one can, as long as the substitution exists as an option in your POS menu. The agent should map the request to that option, quote any upcharge, and say no politely, with the closest alternative, when a request isn't something you offer. HeyTARA takes phone orders with combos, substitutions, add-ons and pickup times, built from the items, modifiers and prices in your POS.
What happens if the AI misunderstands an order?
The safeguards are asking for every required choice, confirming upcharges, reading the order back so the guest can correct it, handing unusual orders to a person and keeping call transcripts so you can compare what the guest said with what the ticket says. Test all of these in a demo before you buy.
How do I get my menu ready for AI voice ordering?
Use item names guests say out loud, give modifier groups clear names, mark required choices as required, set limits on how many options can be picked, put prices on paid add-ons and substitutions, list allowed substitutions as options, hide dine-in-only and test items, keep sold-out items current and build combos with their own choices.
Does the AI know when an item is sold out?
It should, if it reads your menu from your POS. With HeyTARA's real-time menu sync, price changes and items you mark as sold out in your POS carry over to the phone without anyone updating the AI by hand.