Build-your-own sandwiches on the phone, with exclusions as fields.

This schema is not a Fire It invention — it's how your POS already thinks about sandwiches. The voice agent just binds to it.

For complex custom builds, the agent reads back the ticket and asks the caller to confirm. This surfaces mishearings before the ticket fires, and produces a transcript where you can see the caller's exact confirmation.

'No mayo' is not a note — it's an exclusion on the sauces modifier group. Fire It's schema represents exclusions as explicit negations bound to the caller's confirmation, so the make-line sees a red 'NO MAYO' flag rather than parsing a paragraph. The distinction matters because handwriting 'no mayo' at the end of a ticket is exactly the kind of instruction the make-line misses in a rush. Structured exclusions render at the top of the ticket where they can't be missed.

A custom sandwich order is a decision tree the caller walks. Bread first, then protein, then cheese, then toppings, then sauces, then prep. Fire It walks the caller through the tree in the order your POS already models it, prompting only when a group is required and skipping past optional groups the caller doesn't invoke. That means a caller who says 'turkey club, no changes' gets a fifteen-second interaction, not a five-question interrogation.

For a sandwich with more than four modifiers the agent always reads back the full build before confirming. That doubles the caller-time by a few seconds and cuts mishearings meaningfully. The transcript records both the initial capture and the read-back confirmation, giving you an audit trail where the caller's yes is timestamped against a specific rendering of the ticket. That trail is the reason a manager can trust a phone-built custom sandwich as much as one built at the counter.

The build-your-own sandwich flow only feels natural on a phone call if the menu schema was set up for it before the agent ever answers a ring. That is a one-time hour of admin work, and it is the hour that determines whether custom orders feel like a phone-friendly experience or a fifteen-question interrogation. Do this once and revisit only when the menu changes.

Fire It does not handle catering trays priced by the platter, sandwich-of-the-day specials that change weekly without a menu update, or callers who want a bespoke item that isn't on the schema at all. Those cases route to a callback with the full transcript so a manager can price and confirm. That deliberate scope is what keeps custom-sandwich phone tickets safe — the schema constrains the agent to items the kitchen already knows how to build. The deli hub at /solutions/delis-sandwich-shops explains the operational split, and /use-cases/restaurant-menu-voice-ordering covers the general menu-binding architecture that underlies exclusions as fields.