TL;DR
- Proof of drive-thru AI ROI is a named chain, a named person, a source you can find and a date you can check.
- This page keeps each chain’s results in its own block, and Hi Auto’s platform figures in a separate block that is never mixed with any customer’s result.
- Hi Auto’s platform figures: 100M+ orders processed per year with 93%+ completion and 96% accuracy, 3-8 labor hours saved per store per day, average ticket up about 1.5% per store, and turnover reductions of 17-25% reported by Hi Auto customers after deployment.
- You can collect the same proof in your own pilot with a before and after scorecard, measured per store.
Every voice AI vendor arrives with a strong pilot. Few can answer the next question: who said that, and when?
The proof that holds up is what named chains report, with a person, a source and a date attached. This page collects it that way. Each customer has its own block with only that customer’s results. After the customer blocks comes a separate block of Hi Auto platform figures, clearly labelled as Hi Auto’s numbers and not any one customer’s result.
Nothing on this page is blended, multiplied across a store count or applied from one chain to another. A result stays with the chain that reported it.
What counts as proof
Numbers from one store, a best-week snapshot or an unnamed “major chain” are hard to check. Proof has four parts present at once:
- A named chain.
- A named person.
- A source you can find.
- A date you can check.
If one is missing, you cannot verify the number, and a finance team will not rely on it. The rest of this page holds to that standard.
Lee’s Famous Recipe Chicken: the CEO’s numbers
Ryan Weaver is CEO of Lee’s Famous Recipe Chicken. He spoke about his results on a restaurant marketing podcast. On upsell, he said:
“You might get an upsell 20% of the time with humans in the Drive-Thru. With Hi Auto, our voice order taking partner, we’re getting it 100% of the time.”
Ryan Weaver, CEO, Lee’s Famous Recipe Chicken. Nift “Marketing Bites: Restaurant Growth Unwrapped” podcast, Episode 32, 1 April 2025. Watch Ryan Weaver’s upsell comments on hi.auto
Notice what makes that usable as evidence. It compares two situations, it names the source and it comes from the person accountable for the result. This is Lee’s experience of how often an upsell is offered, which is different from how often guests accept.
On the economics, in the same episode, he said:
“The technology pays for itself with the labor hours we are able to take out of our budget every week, and then the sales lifts, which we think is about 1-2% is just kind of gravy on top of that.”
Ryan Weaver, CEO, Lee’s Famous Recipe Chicken. Same podcast episode, Episode 32, 1 April 2025. Watch Ryan Weaver’s labor and sales lift comments on hi.auto
These are Lee’s results, reported by Lee’s, and they stay with Lee’s.
Bojangles: what franchisees did next
Bojangles calls its AI order taker BoLinda. Its CEO and its Chief Information Officer and Chief of Staff shared their experience at a QSR webinar in July 2025. The webinar video page has the full session.
On how franchisees responded, Jose Armario, CEO of Bojangles, said:
“99% of the franchises that have tried it, have stuck with it.”
Jose Armario, CEO, Bojangles. QSR webinar “AI Order Taker That Works: The Bojangles Model”, July 2025. Watch the Jose Armario franchise retention clip on Hi Auto’s videos page
A franchisee’s decision to keep a system is worth noting next to any vendor-run pilot.
As of October 2026, Hi Auto is live in 465+ Bojangles locations.
On the work itself, Richard Del Valle, Chief Information Officer and Chief of Staff at Bojangles, described what changed for each employee:
“We’ve taken employees that were doing three tasks before, order taking, fulfilling, and cashiering, and taken 33% of the work of the tasks away, but probably 50% of the work.”
Richard Del Valle, Chief Information Officer and Chief of Staff, Bojangles. Same QSR webinar, July 2025. Watch the Richard Del Valle clip on Hi Auto’s videos page
Hi Auto platform figures, kept separate
The figures below are Hi Auto platform figures. They are not any one customer’s result, and the labor, ticket and turnover figures are per store. Do not read them alongside the chain blocks above.
| Hi Auto platform figure | Value
|
|---|---|
| Completion rate and order accuracy, reported together | 93%+ completion and 96% accuracy across more than 1,000 stores |
| Labor hours saved | 3-8 hours per store per day |
| Average ticket | +1.5% (1-2% range) per store |
| Employee turnover reduction | Hi Auto customers report turnover reductions of 17-25% after deployment |
| Scale | 100M+ orders per year |
For illustration, 4 hours a day at a fully loaded $25/hr (wages, taxes and benefits) is about $3,000 a month per store. Actual savings vary by market and labor cost.
Completion and accuracy always travel together, because one without the other is an incomplete picture. Keep every figure per store, and do not multiply it by a store count. Each chain’s numbers stay with that chain.
How to read numbers from different chains
Lee’s and Bojangles do not share a menu, a store count or a start date. That affects whether their numbers apply to you. Three questions help:
- What was the baseline, and what menu did it cover? A lift on a focused menu may not carry over to a larger one. Ask what was measured before go-live and over what period.
- How long has the system been live? A chain that has run for a year and a half has had time to settle in. A chain in its first months has not. Ask for the go-live date and the window the result covers.
- Is it an average across all live stores, or a best-store number? A vendor that only shows a top performer is not showing scale. Ask for the average across every live store, and ask how it is measured. Hi Auto’s Buyer’s Guide advises asking every vendor for the measurement methodology.
A source, a date and an all-store average are the minimum for any number you plan to put in front of finance.
Collect the same proof in your own pilot
The strongest proof is the kind you gather yourself. Set the baseline for each pilot store before go-live, then track the same measures after, store by store.
Hi Auto reports completion, accuracy, average ticket and upsell consistency. The other rows are measured by you.
| Measure | How to track it
|
|---|---|
| Completion and accuracy, together | Report both for every store, as an average across all live pilot stores |
| Average ticket | Before and after, per store, split by daypart |
| Upsell consistency | The share of orders that received an offer, before and after |
| Labor hours | Scheduled and actual hours at the order taking station, before and after (you measure this) |
| Turnover | Hires and separations per store over the same period, against the store’s own history (you measure this) |
Build the pilot sheet from your own per-store data: labor hours at the order taking station, average ticket and turnover records, each kept per store.
The scorecard only works when the baseline comes first. Numbers gathered after go-live have nothing honest to be compared with.
The shift in thinking: proof is a source and a date
The bar for proof is simple. A source you can name and a date you can check make a number usable. A number without them belongs in a sales deck, not a business case.
Next step: plan your pilot
Gather each pilot store’s labor hours, average ticket and turnover history, then talk to the Hi Auto team about what a pilot would look like for your stores.