NEW

What it Takes to Hit 100 Million Drive-Thru Orders Per Year, and Why it Matters for QSRs

Back to Glossary

Full Menu Coverage

What is Full menu coverage?

Full menu coverage means a Voice AI system can recognize, process, and correctly order every item, modification, size variation, and valid combination available on the menu. This includes core items, limited-time offers (LTOs), regional variations, all standard modifications, and combo configurations. Without full coverage, the AI must fall back to humans for items it can’t handle—undermining automation benefits and creating inconsistent experiences.

If customers can order it, the AI should be able to take it.

Why Full Menu Coverage Matters

completion rate Impact

Gaps in coverage mean:

  • Automatic fallback for unknown items
  • Lower overall completion rate
  • Unpredictable performance by order content
  • Inconsistent automation benefits

Operational Complexity

Partial coverage creates:

  • Staff must know what AI can/can’t handle
  • Unpredictable intervention needs
  • Training complications
  • Scheduling challenges

Customer Experience

Coverage gaps cause:

  • “I can’t help with that” responses
  • Mid-order handoffs to humans
  • Confusion about AI capability
  • Frustration for certain orders

Business Value

Incomplete coverage reduces:

  • ROI from Voice AI investment
  • Labor efficiency gains
  • Upselling on affected orders
  • Consistency across menu

Components of Full Menu Coverage

Core Menu Items

All permanent items:

  • Entrees
  • Sides
  • Beverages
  • Desserts
  • Kids meals

Modifications

Standard customizations:

  • Ingredient removals (“no pickles”)
  • Additions (“extra cheese”)
  • Substitutions (“fries instead of salad”)
  • Preparation requests (“well done”)

Size and Variation

All options:

  • Size selection (small, medium, large)
  • Flavor variations
  • Protein choices
  • Sauce selections

Combos and Meals

Combination logic:

  • Meal configurations
  • Side selection
  • Drink choices
  • Upgrade options

Limited-Time Offers

Promotional items:

  • Seasonal products
  • Promotional bundles
  • Limited availability items
  • Test market products

Regional Variations

Location-specific:

  • Regional menu items
  • Franchise additions
  • Local favorites
  • Market-specific products

Measuring Menu Coverage

Coverage Percentage

“`
Menu Coverage = (Items AI can handle / Total menu items) × 100
“`

What to Count

Include:

  • All base items
  • All valid modifications
  • All size/variant combinations
  • All combo configurations
  • Current LTOs
  • Regional items

Coverage Levels

| Coverage | Percentage | Implication |
|———-|————|————-|
| Full | 100% | Complete automation possible |
| Near-complete | 95-99% | Rare gaps, high completion |
| Substantial | 90-95% | Some orders need intervention |
| Partial | 80-90% | Significant gaps |
| Limited | <80% | Major coverage issues |

Coverage Gaps: Common Problem Areas

Limited-Time Offers

LTOs challenge coverage because:

  • Short promotion windows
  • Frequent turnover
  • Unique naming conventions
  • Complex configurations

Solution: Rapid LTO addition process, advance integration with promotional calendar

Complex Modifications

Modification challenges:

  • Endless combinations possible
  • Natural language variation
  • Brand-specific terminology
  • Unusual requests

Solution: Comprehensive modification vocabulary, flexible handling logic

Regional Items

Regional coverage issues:

  • Not in central menu database
  • Franchise-specific additions
  • Local naming conventions
  • Limited training data

Solution: Regional menu management, franchise flexibility tools

Combo Complexity

Meal configurations:

  • Multiple components to track
  • Substitution logic
  • Upgrade handling
  • Pricing implications

Solution: Complete combo logic, flexible substitution handling

Achieving Full Menu Coverage

Initial Setup

Menu ingestion:

  • Complete menu database
  • All modifications mapped
  • Combo logic configured
  • Size/variation mapping

Training:

  • AI trained on all items
  • Natural language variations
  • Pronunciation variations
  • Common shortcuts

Ongoing Maintenance

LTO process:

  • Advance integration (before launch)
  • Rapid turnaround capability
  • Testing before deployment
  • Removal when ended

Menu changes:

  • Regular sync with menu database
  • Change detection
  • Impact assessment
  • Quick updates

Quality Assurance

Testing:

  • New item verification
  • Modification testing
  • Combo validation
  • Regional coverage checks

Full Menu Coverage and Franchise Flexibility

Brand vs. Franchise Control

Brand-controlled:

  • Core menu items
  • Brand-wide LTOs
  • Standard modifications
  • Quality standards

Franchise flexibility:

  • Regional additions
  • Local pricing
  • Promotional timing
  • Test items

Supporting Both

Full coverage requires:

  • Central menu management
  • Franchise addition capability
  • Version control
  • Consistent quality

Hi Auto’s Approach

Hi Auto enables full menu coverage through:

  • Complete menu configuration for all items and modifications
  • Franchise flexibility for regional and local additions
  • Rapid LTO integration process
  • Continuous updates across ~1,000 stores

Menu Coverage vs. Menu Time

Relationship

Full coverage affects menu time:

  • Complete coverage = no fallback delays
  • Gaps = conversation disruption
  • Natural handling = faster orders

Balance

Both matter:

  • Coverage: can we handle it?
  • Speed: how efficiently?
  • Quality: how accurately?

Testing Menu Coverage

Coverage Audit

Systematic review:

  • Compare AI capability to full menu
  • Identify gaps
  • Prioritize additions
  • Track resolution

Real-World Testing

Order analysis:

  • Monitor fallback reasons
  • Identify unknown items
  • Track modification failures
  • Assess regional gaps

Ongoing Monitoring

Continuous assessment:

  • New item tracking
  • Coverage metrics
  • Gap alerts
  • Performance by item

Common Misconceptions About Menu Coverage

Misconception: “We can start with partial coverage and add items over time.”

Reality: Launching with gaps creates unpredictable performance and staff confusion. The AI either works for an order or doesn’t, with no way to predict which. Full coverage from launch creates predictable, reliable automation.

Misconception: “90% coverage means 90% of orders will succeed.”

Reality: If missing items appear in 30% of orders, 90% item coverage could mean 30%+ of orders need intervention. The impact depends on how frequently gap items are ordered, not just the count of items missing.

Misconception: “Modifications are optional—we can add them later.”

Reality: Modifications are extremely common. “No onions,” “extra sauce,” or “make it a meal” aren’t edge cases—they’re standard ordering behavior. Without modification coverage, most orders would require intervention.

Book your consultation