The AI that runs
An executive briefing on how Iris — Zentallio's AI decision agent — runs the floor plan, the coursing, the servers and every split bill, table by table.
8 FORMATS · 17 AI SOLUTIONS · L1 ZEN RULES → L2 ZEN MODELS → L3 ASK IRIS
USE ← → OR CLICK TO ADVANCE
THE CASUAL DINING REALITYIn casual dining,
the turn is the P&L.
Table turn time is the number that decides a Saturday. Iris seats, fires and paces against it rather than hoping.
Covers / night0
Table turn0m
Course accuracy0%
IrisWatching
THE CASUAL DINING STORYFull tables are a system,
not luck.
Casual dining wins on turns and dies on friction: slow coursing, split-bill chaos, comps nobody can explain.
most of them are lost by morning
A thousand signals a night — seating, firing, comps, voids — and.
for the table
Starters, mains and desserts fired to arrive together — not for the ticket.
which section is drifting
Every comp and void is attributed, and Iris names before the guests feel it.
Seven live products.
One data spine.
One data spine — from the till to the ledger. Everything below reads from, and writes back to, the same floor.
Balanced Scorecard
FINANCE · L2
Point of Sale
LIVE TILL · IRIS UPSELL
Numerus
CFO · BALANCED LEDGER
Nexus
SUPPLY CHAIN
Motus
OPERATIONS
Manus
WORKFORCE
Vision
COMPUTER VISION
THE SCREEN YOUR STAFF ACTUALLY RUNPoint of Sale
Orders, modifiers, stock depleting as you sell — and Iris upselling every ticket without adding a second to the queue.
Order, course and settle on one screen.
Server takes the order, courses it to the kitchen and splits the bill without switching terminals.
Stock depletes as you sell.
Every modifier rung up moves inventory in the same second — no end-of-night reconciliation.
Iris prompts the server, too.
A course upgrade or add-on surfaces on the till, timed to what's already on the table.
284
Covers / night through this till
1
Screen, order to settlement
LIVE TILL · IRIS UPSELL
THE WHOLE BUSINESS ON ONE BOARDBalanced Scorecard
Covers, turn time, comps and course accuracy — live, with Iris naming the section where the evening actually slipped.
Four perspectives, one board.
Financial, customer, operational and learning — every number live, not compiled next week.
Every module feeds it.
Floor plan, kitchen, workforce and supply chain all post into the same view.
Iris names the cause.
Not just the number that moved — the section, the shift and the server behind it.
68m
Table turn, live
97.2%
Course accuracy
FINANCE · L2
ONE LEDGER. AND IT TIES.Numerus
P&L, balance sheet, cash and close on a single balanced ledger — a month-end that is a review rather than a rebuild.
Sub-ledgers that reconcile.
AR, AP and inventory tie out automatically — not chased down at close.
Comps and voids carry attribution.
Every one posts with the server, section and reason attached to the entry.
Ask Iris for any number.
Any site, any period — answered in the conversation, not a week after month-end.
1
Balanced ledger, till to close
−18%
Comp & void leakage*
CFO · LEDGER
THE CHAIN, PLANNED END TO ENDNexus
Forecast to prep plan to purchase order to the cold-chain van — eighteen modules, one supply chain.
The cover forecast drives the order.
Expected covers by hour become prep quantities and purchase orders, not a manager's guess.
Vendor pricing, centralized.
Cost and lead times tracked across the group rather than negotiated site by site.
Cold chain included.
The van is part of the plan — eighteen modules from forecast to delivery.
18
Modules, forecast to van
By hour
Cover forecast into prep
SUPPLY CHAIN
THE EXCEPTIONS, NOT THE NOISEMotus
The operations layer — surfacing exceptions and incidents across the estate, and leaving the rest alone.
Course timing, tracked per table.
Time between courses rolls up by section, shift and site.
Surfaces what needs a human.
Not a report on every site — the sections that actually slipped tonight.
Feeds Zen Rules and Zen Models.
The operational data Iris's other two layers run on comes from here.
68m
Table turn, estate-wide
Exceptions
Surfaced, not every row
OPERATIONS
THE PEOPLE PLAN, AND WHAT IT REALLY COSTSManus
Rostering built from the forecast — attendance, payroll, working-time compliance, and the retention risk hiding behind the labour ratio.
Rosters follow the cover forecast.
Section coverage is built from expected covers by hour, not from last Saturday's rota.
Compliance is a guardrail.
Working-time rules and breaks are enforced in the roster, not audited after payroll.
Retention risk, surfaced early.
The pattern behind the labour ratio — before a good server hands in notice.
+0.6
Table turns per service*
By hour
Rostered to the forecast
WORKFORCE
L1
Iris · Intelligence layer 01How Iris enforces the rules.
Deterministic thresholds under the hood (the “Zen Rules” layer) — catch a known problem the instant it crosses a line. Split billing and open tabs run on this layer.
TONIGHT · 21:07
LIVE ALERT
High-spend tab flagged
Table 14 — running tab has crossed the configured threshold. Surfaced to the duty manager while the table is still seated, not at settlement.
IRIS · L1 TABLE 14
Iris · L1 01 / 02Split Bill — By Item or Equally
A table's bill can be split any way the guests choose — equally per head, by individual items ordered, or a custom combination. No mental arithmetic for staff.
Equal split — total divided by number of guests, each paying their share by card or cash.
Item-by-item — each guest selects their own items and pays exactly what they ordered.
Multi-tender per split — Guest A pays cash, Guest B taps card, on the same bill.
Service charge distributed proportionally across splits — no manual calculation.
RULE ENGINE · L1
3 ways
Equal, by item, custom
At bill
Split before payment starts
Iris asks — “What percentage of our tables use split billing on weekends?”
Formats — Chinese · BBQ & grill · Korean BBQ · Italian · Thai & Asian
Open Tab Management
A tab opened when guests are seated stays open until they ask for the bill. Staff add items at any time without re-opening an order.
Tab is created automatically when a table is assigned — no separate step.
Additional orders join the running tab — no new order, no duplication.
A high-spend tab approaching a configurable threshold is flagged for manager awareness.
Tabs transfer between tables or to the bar, and accept partial payment mid-service.
RULE ENGINE · ANOMALY
At seating
Tab opens automatically
Live
Updates on every item
Iris asks — “What is the average tab value on Saturday night vs Sunday lunch?”
Formats — BBQ & grill · Korean BBQ · Seafood · Lebanese · Turkish
L2
Iris · Intelligence layer 02How Iris predicts the turn.
Forecasting and regression under the hood (the “Zen Models” layer) — predicts table availability, covers and no-shows before the service starts. Four solutions run on this layer.
Covers by Service Hour — Forecast vs Actual
Forecast Actual
Iris · L2 01 / 04Table Management & Floor Plan
A live digital floor plan showing every table's status — occupied, free, reserved, or being cleared. The host always knows where to seat the next guest without checking physically.
Drag-and-drop floor map matches the actual layout, updating as orders are placed and bills paid.
The turn predictor estimates when each occupied table frees up — availability seen 15 minutes ahead.
Colour-coded at a glance: free, occupied, reserved, cleaning — on any device.
Indoor, terrace and private dining on one screen; tables merge for large parties and split for separate bills.
REGRESSION · FORECAST
15 min
Availability, seen ahead
68m
Average table turn
Iris asks — “What is the average table turn time on Friday dinner service?”
Formats — Pakistani/desi · Chinese · BBQ & grill · Seafood · Italian
Server Assignment & Multi-Course Coursing
Tables assigned to specific servers. Orders coursed to the kitchen in sequence — starter, main, dessert — the kitchen receives each course only when the previous one is cleared.
Every table is assigned to a named server — sales, tips and performance tracked per server.
Starter fires at order time; the main fires when staff course it. The kitchen never gets ahead.
The KDS shows course number and sequence — no confusion between tables' starters and mains.
The scorer tracks AOV, upsell rate and tip% per server — coaching opportunities without bias.
SCORING · REGRESSION
97.2%
Course accuracy
Per table
Course timing logged
Iris asks — “Which server had the highest average order value this week?”
Formats — Pakistani/desi · Seafood · Italian · Lebanese · Indian
Reservation & Waitlist Management
Phone and walk-in reservations captured in one system — with deposit tracking, no-show flags, and a live waitlist for busy periods. The host is always in control.
Bookings taken by phone or online — date, time, covers, special requests and contact recorded.
The no-show predictor scores each reservation 0–100, allowing an intelligent overbooking buffer.
Deposits are linked to the booking for large parties and peak nights, then deducted at billing.
The cover forecast by hour lets the kitchen plan prep quantities in advance.
CLASSIFIER · FORECAST
0–100
No-show risk score
24h
Re-scored before arrival
Iris asks — “Which day of the week has the highest reservation no-show rate?”
Formats — Pakistani/desi · Seafood · Italian · Lebanese · Indian
Tip Handling & Service Charge
Tip prompts on the card terminal at checkout — with staff tip allocation, pooling options, and full reporting. Service charge applied per your policy and distributed correctly.
Configurable tip options appear on the terminal at checkout — 10%, 15%, 20% or custom.
Cash tips are logged against the server and included in their performance report.
Fixed-percentage service charge is added automatically, with exempt categories excluded.
Tips per server, per shift, per week — a full audit trail for payroll integration.
SCORING · REGRESSION
Per server
Tip rate tracked with AOV
Audit
Trail into payroll
Iris asks — “What was the average tip percentage by server this month?”
Formats — Seafood · Italian · Lebanese · Thai & Asian · Sushi
L3
Iris · Intelligence layer 03 — liveAsk Iris
Not a screenshot — the actual agent. Natural-language answers over the live floor.
ASK IRIS — CASUAL DINING
Live Balanced Scorecard
0m
Table turn
0
Covers / night
0%
Course accuracy
+0.0
Turns per service ▲
Iris · L3 01 / 01Dietary Preference Profiling AI
The guest, remembered. Dietary restrictions and preferences are held against the guest profile and surfaced to the host and server before they reach the table.
The profile is surfaced at check-in — before the host or server approaches the table.
Guests are clustered by preference pattern, not by broad demographics.
Recommendations respect the restriction on record rather than relying on the server remembering.
RECOMMENDATION · CLUSTERING
At check-in
Profile surfaced to the host
Remembered
Across every visit
Iris asks — “How many of our regular guests have a dietary restriction logged?”
Formats — Indian · Thai & Asian · Lebanese · Sushi · Ethiopian
Seventeen solutions,
four bundles.
Every card opens a live guided demo. Seven are detailed in this briefing; the remainder run on the same three layers.
At the Counter — I WHERE THE ORDER IS TAKEN, AND
At the Counter — I
WHERE THE ORDER IS TAKEN, AND MADE
At the Counter — II
AND THE REST OF THE COUNTER
The Guest
THE GUEST, REMEMBERED
Kitchen & Stock
WHAT YOU MAKE · WHAT IT COSTS · WHAT YOU LOSE
Detailed in this briefing Table Management & Floor
Table Management & Floor Plan
L2 · REGRESSION · FORECAST
Server Assignment & Coursing
L2 · SCORING · REGRESSION
Split Bill — Item or Equally
L1 · RULE ENGINE
Reservation & Waitlist
L2 · CLASSIFIER · FORECAST
Open Tab Management
L1 · RULE ENGINE · ANOMALY
Tip Handling & Service Charge
L2 · SCORING · REGRESSION
Dietary Preference Profiling
L3 · RECOMMENDATION · CLUSTERING
Implementation,
run by Iris.
You configure a sector playbook, not a custom project. Iris applies it herself — agentically, from day one.
Onboarding is agentic.
Iris connects the POS, the floor plan and the reservation book directly — no manual data mapping.
The playbook applies itself.
Sector thresholds go live immediately, then tune from real service data, site by site.
Live in weeks, learning from day one.
There's no bespoke build to wait on — go-live is a configuration, not a project plan.
Support starts
with Iris.
The first line of support is agentic — Iris resolves most of it herself. Our engineers pick up from there.
Layer 1 — Iris, 24/7.
Configuration questions, anomalies and routine issues resolved directly, instantly.
Layer 2 — our engineers.
Anything Iris can't close escalates automatically to a Zentallio engineer.
No blank tickets.
Every escalation arrives with Iris's own diagnosis — engineers start from an answer.
Managers watch guests,
not tickets.
“Coursing runs itself. Managers finally watch guests, not tickets.” GENERAL MANAGER · CASUAL DINING GROUP
Zentallio keeps the floor moving: table-turn prediction paces seating, coursing runs itself, every comp and void is attributed, and Iris tells the manager which section is drifting before the guests feel it. Underneath sits the same platform every sector runs — one data spine from the till to the ledger, three layers of intelligence, and an agent that narrates every screen, flags what needs a human, and acts on the rest.
WHAT AN OPERATOR CAN EXPECTThe turn, measured.
+0.0
Table turns per service
+0%
Covers per night
−0%
Comp & void leakage
+0.0pt
Net margin
* Modelled from pilot assumptions & comparable F&B benchmarks — not yet a deployed-client result. We show real numbers as founding pilots conclude.
WHERE IT LEAKS, HOW IRIS RESPONDSWhere the dining room
actually loses margin.
Where it leaks 01 Slow coursing — the kitchen runs
Slow coursing — the kitchen runs ahead of the table and the turn stretches past plan.
Split-bill chaos at settlement, with staff doing arithmetic while the next party waits.
Comps and voids nobody can explain — and a no-show table nobody backfilled.
How Iris responds L1 Split rules and tab thresholds
Split rules and tab thresholds fire deterministically — at bill request, at seating, every time.
Turn prediction paces seating and the no-show score sets the overbooking buffer.
“Which section is drifting tonight?” — answered in seconds, while service is still running.
+0.0
more table turns per service — while course accuracy holds at 97.2%. *
ONE PLATFORM, TEN SECTORSCasual Dining is
sector two of ten.
Every Zentallio sector runs the same three-layer intelligence, tuned to how that format actually loses margin.
01 Quick Service 02 Casual Dining 03 Fine Dining 04 Café & Bakery 05 Ice Cream & Desserts 06 Beverages & Drinks 07 Health & Wellness 08 Cloud Kitchen 09 Institutional & B2B 10 Niche & Experience
Let's put Iris on
your floor.
Book a call with our consultant — a pilot walkthrough on your own dining rooms, your own numbers.
INFO@ZENTALLIO.COM
0327 0000901 · zentallio.com · 142-C, D.H.A. Commercial Broadway, DHA Phase 8, Lahore 54940
← → NAVIGATE · F FULLSCREEN
⭳ DOWNLOAD PDF
01 / 14