A MENU BUILT ON COMBOS AND SPECIALS
St. Louis's menu runs on deals — combos, single-choice specials, spice-required items. We worked with Surender to teach the cart builder to recognize when loose items should become a deal, and to price them right.
THE DEAL IS THE ORDER
At St. Louis, customers do not order items — they order deals. A combo here, a special there, an item that only exists with a spice level attached. If the system treats those as separate line items, the order and the price are both wrong.
The cart builder learned the deals
We built combo-special handling into the cart builder: it models combo components and plans, and collapses regular items into a combo when the order qualifies, so the customer gets the deal they expect.
Remapping loose items
When a caller orders the pieces of a special without naming it, the cart builder auto-remaps them onto the right single-choice special, including items that require a spice selection.
Pricing that holds up
Paid variants keep their base price, duplicate variants are de-duplicated on multi-quantity orders, and special items are modeled in the menu schema itself, so the ticket that reaches the kitchen matches the deal that was ordered.
Combos and specials recognized during the call
Loose items automatically remapped into the correct deal
Spice-required specials handled without extra prompting
Pricing accurate on paid variants and multi-quantity orders
WANT THIS FOR YOUR MENU?
Book a meeting and we will walk through how AI Voice HQ would handle your menu, phone flow, and handoff rules.