Designed for the rush. Honest about the ceiling.
Fire It handles concurrent calls per location by design, with soft and hard caps you control. We won't promise a blanket concurrent-call SLA — capacity is tuned per setup.
Stretch the ETA before the kitchen breaks.
When active orders cross your soft cap, quoted pickup windows automatically expand. Callers hear a realistic time; the kitchen keeps its rhythm.
Turn down cleanly rather than over-promise.
At the hard cap, new orders are declined with a clear reason. Callers are offered voicemail or a callback — never an order the line can't make.
End-to-end workflow
- 01Configure caps
Set soft and hard caps per location during onboarding, and adjust them at any time.
- 02Detect load
Fire It watches active call and order state to determine current concurrency and queue depth.
- 03Stretch ETAs
Above the soft cap, quoted pickup windows expand automatically.
- 04Protect the kitchen
Above the hard cap, new orders are politely declined with a clear reason.
Where Fire It actually helps
- You have a real peak-hour ceiling on kitchen throughput.
- You want callers to hear honest ETAs at every load level.
- You want caps that adapt to your actual staffing and prep.
What we don't claim
- We do not publish a blanket concurrent-call SLA.
- Practical capacity depends on your voice-provider configuration.
- Very high concurrency scenarios may require additional voice QA during onboarding.
Related on Fire It
Concurrent-call FAQs
- Fire It is designed for concurrent calls per location. The actual capacity depends on how your line is configured with your voice provider — we tune it during onboarding. It is designed and configured behavior, not an absolute SLA.