Your restaurant's agent staff
Your restaurant's operations,
on autopilot.
Luke is your restaurant's agent staff. One agent per area runs the business's processes, with human control where you put it, in the WhatsApp your team already uses.
Customers
- Piso 1
- YOU
Where it starts
The POS says one thing. The location lives another.
The POS measures sales. The ERP holds the core. Everything else lives in Excel, in a WhatsApp group and in scattered systems. Nobody reconciles them in time.
Who runs a restaurant
Three people look at the same business and none of them sees the same thing.
The owner
Wants margin and sees revenue.
They want to buy exactly right, exact inventory, precise staffing. But the business is so operational they never get there: they get by on revenue.
The manager
Wants to solve and drowns in hygiene.
Payroll takes a week and comes out with errors. A supplier issue eats another. The week goes into what they shouldn't even touch.
The location manager
Executes without tools.
They carry the day and put out fires with nothing behind them. The result depends on who's on shift.
The staff
Seven agents, one per area.
Each one runs its area's processes and they talk to each other. Your team stays on the floor: the staff carries what nobody gets to today.
You still decide. Luke makes it happen.
How it runs
The agent carries the process from start to finish.
Every step is executed by the agent. The team steps in only when the agent asks for something.
- 1
Starts
Opens every process on a schedule, an event or a rule. Nobody has to remember to kick it off.
- 2
Requests
Asks the person in charge for the evidence the process needs, over WhatsApp or Telegram.
- 3
Reads
Interprets photos and documents: temperatures, counts, invoices, delivery notes.
- 4
Records
Stores the data structured and traceable.
- 5
Detects
Compares what was recorded against what was expected and flags deviations.
- 6
Escalates
Routes exceptions to the right person, with the full context.
- 7
Reports
Delivers results and reports without anyone assembling them.
The team answers. The agent does the rest.
The path
From an operation in chaos to an agentic restaurant.
Four steps, and they have to be climbed in order. Today's systems aim at the second and, with effort, scrape the third.
- 01
Chaos
The operation lives in the head of whoever is on the floor, and only in part. Whatever catches fire gets put out.
Where most of the industry is today
- 02
Reliable, traceable data
The data exists, it's current and it can be audited. What happened in the location was recorded with its evidence.
As far as today's systems go
- 03
Automation, reconciliation, integration
Processes run on their own and the systems agree with each other. Nobody types the same thing twice.
With effort, some scrape this step
- 04
Prediction, proactivity, optimization
The agent gets ahead of it: buys exactly right, anticipates the stockout, adjusts the shift and defends every point of margin.
Where Luke takes you
Control tower
The whole business, in one place.
What Luke collects from the operation, what lives in your POS and what your ERP records, consolidated into a 360° view of the business. Every location at once, no spreadsheets in between.
The right decisions, at the right time.
Operation · Luke
94 %
compliance today, 5 locations
Sales · POS
+6 %
vs. same day last week
Costs · ERP
31.4 %
food cost this month
Compliance by location
- Brickell100 %
- Wynwood96 %
- Coral Gables92 %
- Doral88 %
- Kendall83 %
Your own use case
Luke learns and evolves with you.
You describe your processes in a conversation, with your rules, exceptions and systems, and Luke builds them and hands them to the agent of the area they belong to.
Every Monday at 8, ask the manager for the storeroom count and tell me if anything is below minimum.
- Walk-in temperature checks
- What happens when a guest complains
- Making sure the linens arrive before Friday
Integrations
Integration with your systems in minutes.
Luke reads from and writes to your POS, your ERP and your channels. With the industry's systems, and with anything that has an API.
The data lands where it has to land, with nobody typing it twice.
Point of sale
- Clover
- Fudo
- Justo
- Lightspeed
- Oracle Micros
- Square
- Toast
- Toteat
- FX6
ERP and accounting
- Defontana
- SAP
- SIGO
- Softland
Channels
- Telegram
The architecture
The best of language models, on top of deterministic engines.
The agent talks, understands and decides with the best models on the market. What it executes are engines built so the same process gives the same result every time.
We verticalized in restaurants. Before taking it to another industry, we want it to be the best solution for this one.
Agent staff
They talk over WhatsApp and Telegram, understand what's going on and decide what comes next.
Language models
The best on the market, swapped by task.
- Understand text, photos and documents
- Reason with each location's context
- Answer in the team's language
Deterministic engines
Tools that always do the same thing, the same way.
Workflows
States, owners and transitions, fully traceable.
Forms and evidence
Checklists, photos and readings, by link and without an app.
Scheduler and rules
Triggers by schedule, by event or by data condition.
Data collections
Inventory, recipes, suppliers and shifts: one master list.
Document reading
Invoices, delivery notes and photos turned into structured data.
Calculation and reconciliation
Differences, matches and alerts on what was recorded.
Analytics and reports
Control tower and reports that build themselves.
Integrations
Reading from and writing to POS, ERP and channels.
MCP
Your data, connected to Claude or other models.
Your systems
- Point of sale
- ERP
- WhatsApp and Telegram
Powered by Cotalker
Behind it are more than ten years running critical processes in large LATAM companies.
Luke comes from a platform that has spent years running companies in retail, banking, energy, mining, healthcare and logistics. What's new is who we bring it to.
The Luke podcast · Episode 1
A restaurant opens at 8. Before that, there are 40 things to check.
Nicolás Durán opens the first episode: why a restaurant's operation can run on autopilot, and what changes when the agent lives in the same WhatsApp the team already writes in.
Episode opening · 1:30Full episode · 12 minEpisode in Spanish.
The full episode goes out on LinkedIn and Instagram.
In this episode
The car that drives itself
The parallel that frames it all: you say where to go, the agent plots the route.
Nobody checks all 40
Why opening a location breaks in the same place every time.
Where the team already writes
The agent operates over WhatsApp and Telegram, in the channels of the everyday.
Where Luke comes from
Years running critical processes in large LATAM companies, packaged for a single location.
What's next
One real case per episode, told by the people who run it.
Talk to Luke
Message Luke and book your demo on WhatsApp.
A live agent, not a form. Tell it about your operation, ask what it checks when a location opens, or just ask for a demo: it books it.
- I want to book a demo for my locations
- What do you check when a location opens?
- I have a receiving process. How would you build it?