In this post
- The wrong unit: rings and minutes
- $0.90 per successful order (many pilots)
- Aligned incentives—you and your vendor
- What counts as a successful order
- What should not hit your invoice
- Illustrative math (not a guarantee)
- No per-minute stack on top
- How this compares to other models
- Next step: pricing page, then a demo call
- Questions owners ask
The wrong unit: rings and minutes
Most owners do not want more phone minutes—they want more completed pickups on the pass.
Traditional stacks bill extensions, hold time, and inbound volume whether or not anyone ordered. Some AI vendors do the same: longer calls, larger invoices, same busy Friday.
Per-minute surprises show up after rush: callbacks, read-backs, handoffs, guests who never order. You pay for talk; the pass stays quiet.
Success-based pricing changes the unit to the outcome you sell: a ticket your kitchen can fulfill.
$0.90 per successful order (many pilots)
On pricing, ROAL publishes a pilot success rate of $0.90 per successful order—meaning the guest confirmed on the line and the pickup finalized on your kitchen display (KDS).
That is not $0.90 per ring, per minute, or per "AI conversation." A ten-minute call that ends in a hang-up should not behave like revenue on your invoice.
High-volume or multi-location groups may receive different rates in writing before live traffic—your pilot terms are confirmed up front, not discovered from a minute-by-minute stack.
Aligned incentives—you and your vendor
When both sides care about finalized tickets, the product favors accurate live menus, clean confirmations, and fewer wrong items—not longer chatter.
Per-minute pricing rewards talk time. Flat SaaS rewards logins. Success pricing rewards orders that made it to the pass with a real guest attached.
During rush you want the agent efficient and correct, not chatty. That is the same moment per-minute bills hurt most.
What counts as a successful order
A successful order means: real name and phone on the call, pickup ticket finalized on your KDS, food your team can make tonight.
Same bar you would use internally—not "we discussed pad thai," but "pad thai is on the rail with a callback number."
Your pilot agreement spells this before go-live so accounting and ops agree on what the invoice reflects.
What should not hit your invoice
Wrong numbers, hang-ups before confirmation, prank calls, and "what time do you close?" should not bill as successes.
Menu tests while you wire voice, training calls, and abandoned carts that never finalize should not surprise you on a success invoice.
Clear exclusions build trust—you should not feel punished for testing before you forward Friday traffic.
Illustrative math (not a guarantee)
Compare tickets on the pass to success fees—not rings.
Example only: six extra completed pickup orders on a weekend at a $40 average ticket is roughly $240 in food revenue on the pass (not profit after food and labor). At $0.90 per successful order, illustrative platform fees for those six are about $5.40—not your full labor or onboarding.
Whether that trade works is your worksheet: see cost of unanswered calls with your own missed-call data. We are not promising six orders or any ROI.
Track phone tickets on the KDS for two weekends with and without coverage, then compare to fees—not to a telephony minute report.
No per-minute stack on top
Owners hate finding a base platform fee plus metered minutes after go-live. ROAL's public pilot story is success-based: pay when pickup hits the pass under the definition you agreed.
Production pricing after pilot depends on completed order volume, locations, and menu complexity—confirmed in writing before live guest traffic. No surprise per-minute layer sold as "usage."
If you are evaluating vendors, ask: "What bills if rush hour is loud but only three calls become tickets?" Minutes-heavy models charge more; success models charge for the three.
How this compares to other models
Per-minute AI: cost rises with interruptions, read-backs, and handoffs—even when no ticket completes.
Flat unlimited SaaS: simple subscription, but slow weeks still pay full freight when value was Friday coverage.
Marketplace delivery: perpetual slice per ticket; phone pickup keeps margin when you answer.
ROAL success pricing: cost tracks completed phone pickups on your screen—aligned with recovering orders you lost when nobody answered during rush.
Next step: pricing page, then a demo call
Read the full breakdown on pricing—what counts, what does not, and pilot notes.
Listen to a demo call with your menu, run test tickets on the pass, then forward peak nights when tickets look boringly correct.
Questions on volume or locations? Use contact—terms stay in writing before live guests hit the line.