Feature / phone-order accuracy

Accuracy is a system, not a slogan.

Fire It does not claim perfect accuracy on any single call. It claims structural safeguards: authoritative pricing, enforced modifier caps, sold-out awareness, and full transcripts.

Safeguards

Six things that make a phone order honest.

  1. 01Server-side pricing

    The server prices every order against your live menu. The model never authoritatively prices anything.

  2. 02Modifier caps enforced

    Required groups, single/multi selects, and max quantities are enforced during capture.

  3. 03Sold-out awareness

    86'd items and modifiers disappear from what the agent will offer, instantly.

  4. 04Deterministic confirmation

    Order state is a finite state machine. 'Confirmed' means the authoritative state was recorded.

  5. 05Full transcripts + summaries

    Every call carries a transcript, structured events, and a plain-English summary you can audit.

  6. 06Human transfer any time

    Callers can request a human at any point in the call, no matter what state they're in.

How the call goes

End-to-end workflow

  1. 01Capture as fields

    Items and modifiers land as structured fields, not paraphrased notes.

  2. 02Repeat back

    The agent repeats the running order and asks for confirmation on ambiguous parts.

  3. 03Price authoritatively

    The server prices against your live menu, then reads the total back.

  4. 04Confirm honestly

    The caller only hears 'you're all set' after the authoritative order state is recorded.

Good fit if

Where Fire It actually helps

  • You want structural accuracy safeguards — not marketing promises.
  • You want transcripts and summaries for every call.
  • You want a state machine, not a wishful 'confirmed' status.
Honest limits

What we don't claim

  • We do not promise perfect transcription on any single call.
  • We do not publish a headline accuracy percentage until QA proves it per setup.
  • Correction handling depends on the caller cooperating with the read-back.
Frequently asked

Accuracy FAQs

No — nobody honestly can. We promise structural safeguards: authoritative server-side pricing, enforced modifier caps, sold-out awareness, deterministic confirmation semantics, and full transcripts you can QA.