From ring to receipt, four honest steps.
A guided tour of what happens on every Fire It call. No fake screenshots. No claims we can't defend. Every guardrail below is enforced in code.
- RingAnswered in under 2 seconds
Fire It picks up on your existing number via forwarding, or on a provisioned line. Every simultaneous ring gets a voice — no rollover, no voicemail.
- UnderstandReal conversation, structured intent
The agent listens, clarifies, and captures against your live menu — sizes, halves, required modifier groups, sold-out items. Accents and corrections are handled.
- PriceRead the complete order back, confirm verbally
Totals are computed authoritatively on Fire It's servers — the browser and the voice model never compute money. The agent then reads the complete order back (quantities, sizes, modifiers, pickup or delivery details, the total, and the ready time when available) and the caller confirms verbally on the call. A correction triggers a fresh read-back. No text message is sent and none is required.
- RoutePOS handoff — or internal queue
Only after an unambiguous verbal yes does Fire It submit the order — exactly once. It appears immediately in your dashboard order queue, and lands in your POS via a certified adapter. If POS is offline, Fire It queues to the internal dashboard. Nothing is lost. Nothing is silently retried.
The caller only hears "you're all set" when the authoritative order state reaches acknowledged. No optimism, no rollback drama.
Every provider webhook is deduplicated by (provider, event_id). Every order write is tenant-scoped and idempotent.
Order state transitions and privileged actions land in an append-only audit log accessible to owners and platform admins.