Owner console
The moment a call ends, it turns into something you can actually look at. Orders, exceptions, and completed calls land on one screen as they happen — searchable afterward, and honest the whole time about what’s live, what’s still waiting on a decision, and what simply hasn’t refreshed yet.
One screen, three named regions —
and nothing sits in two at once.
A call still in progress shows as active — not as a transcript scrolling in real time while it happens. The transcript is what a finished call leaves behind. What you see while a call is running is the plain fact that it’s happening: which location, roughly how long it’s been going, nothing invented beyond that.
Nothing lands in a region because it looks urgent — only because it actually is one of these three things. Right now holds calls currently in progress and how the most recent ones actually ended. Needs a decision holds anything sitting in front of a manager, an open callback, or an order running later than expected. Today so far holds the totals covered further down this page.
Two mechanisms —
never one setting wearing two names.
The transcript
Every completed call keeps a text record of what was actually said — on by default, the same as every other call, not a box someone has to remember to check.
- Reading it back requires the right staff role.
- How long it sticks around follows the account’s own configured retention window — not a fixed number this page states.
The recording
Audio stays off unless a restaurant has turned it on for a specific location and disclosed that on the call itself.
- Most completed calls will have a transcript and no recording at all.
- That’s the ordinary case here — not a gap in what’s showing.
Deliberately equal columns — neither is a stricter version of the other, and recording being off is not a failure state. Whichever of the two exists for a given call, neither one ever holds a card number, an expiration date, a security code, or the tones someone dials in to pay. Those stay out from the moment they’d arrive, not stripped out afterward. The fuller legal specifics — the actual retention window, who exactly can read a transcript — live there, not here.
Never reduced to one flat word
like “done.”
Each moves on its own schedule — see orders for the complete set of values each one can actually take. If an order changes after it’s accepted, the original stays exactly where it was and the new version sits next to it as its own clearly marked change, never a silent overwrite. Every order also keeps its own link back to the call it came from, so a question about what a caller actually asked for doesn’t need a second lookup somewhere else.
An order that landed in front of a manager carries the specific rule that put it there, never a plain “needs review” tag with nothing behind it. The same view tracks whether a manager’s been notified, whether they’ve answered, and whether it reached an owner fallback — and nothing is marked resolved until it actually is: approved, and exactly what happened as a result; denied, and what the caller was offered instead; or a callback still open, tracked as open for as long as it actually is. None of this implies most orders end up here — a queue that’s usually empty is the ordinary case, not a sign something’s broken. See escalation for the full mechanism.
Merging categories is exactly how
a number stops meaning what it says.
The screen totals up the day the way a manager would actually want it closed out — but keeps categories separate that are tempting to merge. Orders accepted, completed, and cancelled, plus the average value across them — separate counts, not one running total. Gross sales, tax, delivery fees, and any phone-captured tips, broken out rather than folded into a single line. Cash due and cash actually marked collected — two different facts about the same order. Discounts and refunds, each its own figure. Calls, split between the ones that became orders and the ones that didn’t, plus transfers and calls that failed or never connected. Orders and revenue by hour and by fulfillment type. Upsell offers made against upsell offers accepted, with the value that actually added — shown as what happened, not proof of what caused it.
Every one of these carries a time range, and every one shows plainly when it hasn’t refreshed recently rather than quietly standing in for the current total.
MERGE EITHER SIDE OF ANY PAIR AND THE NUMBER STOPS TELLING YOU WHAT ACTUALLY HAPPENED
Twenty minutes away.
One glance to catch up.
A manager steps away for twenty minutes mid-shift and comes back to check in before the next rush. Right now shows one call still in progress and two that just ended — one an order, one a question about delivery range. Needs a decision shows a single order, carrying the specific rule that put it there: a handwritten instruction outside the ordinary pattern, not a vague notice. Today so far is still showing the numbers from twenty minutes ago, marked plainly as not yet refreshed rather than presented as current — a small distinction that matters, because a stale number doesn’t get mistaken for a slow shift. Opening the flagged order shows the reason, who’s been notified, and whether they’ve answered — all without a second screen or a second question to anyone else on the floor.
Questions worth asking before you trust a screen
Can staff see a caller's transcript?
Only staff whose role actually needs it. That specific gate is real; the exact role isn’t named on this page, because it isn’t published anywhere on the site.
What if the screen shows an old number during a network hiccup?
It’s marked stale, not silently passed off as current — the same distinction the twenty-minutes-later example above relies on.
Does this replace my point-of-sale reports?
No. Getting an order onto the restaurant’s own point-of-sale system is still a person’s job today — orders covers that honest limit in full. What this screen replaces is the guesswork in doing it quickly, not the keying-in itself.
Can I compare today to last week here?
Not on this screen. Intelligence is where you look at your own numbers across a stretch of time you choose; this page is built around one day at a time.
An active call shows as active, nothing more — no live transcript feed while it’s still running. Every number here describes this restaurant’s own calls and orders; nothing compares one restaurant’s numbers to another’s. A number that hasn’t refreshed recently is shown as stale, not silently passed off as current. An accepted order still goes into the restaurant’s own point-of-sale by hand — this screen shows it clearly enough to do that quickly; it doesn’t submit it anywhere else on its own. And transcript and recording access follows staff role and the account’s retention setting, not a blanket “everyone can see everything.”
RELATED READING
Staff view
The tablet by the pass: queue, wait, 86 board — zero training course.
OPEN →PLATE Nº 013Intelligence
Every call becomes data you own: demand, asked-and-missing, the closeout ledger.
OPEN →PLATE Nº 004Calls
Answered as it rings, identified as AI out loud, and closed one of four honest ways.
OPEN →See your own calls land here.
Request access to watch a real shift fill this screen.