Solution · Chains with several locations
All locations, the day as it happens.
Kentor understands how each location really works, writes the chain's standard in one place and puts AI on ordering, restocking and closing. The manager sees the store's day on their phone, and you see the whole chain.
Kentor Bot
- Restock order loggedOwner and deadline · via WhatsApp08:30 · Done
- Morning shift dashboard updatedOrders, average ticket and pace11:00 · Done
- Checking yesterday's sales2 of 3 channelsnow · In progress
- Expense above the location's limitNeeds the manager's OKWaiting for your OK10:20
- Lunch shift below paceManager notified12:40 · Done
- Inventory checked2 items to restock07:15 · Done
Chains with several locations today
Where the chain loses control.
The pain
You only find out at month-end.
Each location's day on one screen: orders, average ticket and pace by shift. The store that fell out of rhythm shows up while there's still time to act.
How Kentor does it
Kentor Bot's agents read each location's systems and build the at-a-glance management view by store and shift, which the manager opens on their phone.
Kentor Bot- Reading the locations' orders4 of 6 locationsnow · In progress
- Morning shift dashboard updatedAll locations11:00 · Done
- Norte Location below shift paceAlert the manager now?Waiting for your OK12:40
- Centro Location restock orderOwner and deadline08:30 · Done
- Yesterday's sales checked5 of 6 locations with no discrepancy07:30 · Done
The pain
Every location does it its own way.
Recipe, procedure, exchange policy, register opening and closing: the chain's standard is written down, up to date, and each person gets the right answer on the spot, the chain's way.
How Kentor does it
Kentor Brain brings together manuals, spreadsheets and conversations and delivers that standard to people and AI, with each role's permission.
Kentor BrainHow we work · Procedure
Store opening
Cash checked, inventory counted and shift checklist done before opening.
3 sources · 4 calls
Historyprevious values are kept
- 03/11Updated by operations: inventory count before opening.
- 12/09Two-person cash check added.
- 20/07Record created from the chain's manual.
The pain
The WhatsApp group became the system.
You see, location by location, what now moves through the group chat: restocking, shift handoffs, expense approval. And what to take out of there first, with the math.
How Kentor does it
Kentor OS talks with managers and teams at each location, in parallel, and maps the processes as they actually happen in each store.
Kentor OSProcess map
Location operations · 4 processos
| Process | Steps |
|---|---|
| Inventory restock | 3 |
| Shift change | 3 |
| Expense approval | 4 |
| Cash close | 4 |
Inferred from the conversations, with who mentioned it
Inventory restock
OperationsR$ 24.960 per year
6 h per week · 5 interviews
The pain
Closing the month for the chain takes days.
Each location's sales, expenses and bonuses checked automatically. The month closes with data, not with each manager's memory.
How Kentor does it
Implementation gets the close running on the chain's tools, location by location, and Training takes each manager to everyday use.
Implementation and TrainingImplementation · Chain
Plan with your team
- Location mapDone
- Orders by store and shiftDone
- Close with automatic checkingIn progress
- Manager trainingNext
Case
A real chain, running.
Orders by store and shift, restocking out of the WhatsApp group and the close checked.
Restaurant · iFood operation
Pé de Sopa
Inventory, restocking and finance off WhatsApp and the spreadsheet.
View caseThe chain's routines
The routines already running at a chain.
Four routines from the Pé de Sopa case. Each took a task off WhatsApp or the spreadsheet.
The pain
The manager only sees the result afterward.
Every store and shift, at a glance.
Each location's and shift's orders, average ticket and pace, on a screen the manager opens on their phone.
What goes out
- Month's report
- Call to ask how the store is doing
- Orders, average ticket and pace by store and shift
- On the manager's phone
- The location out of rhythm shows up the same day
How Kentor does it
- Reads each location's orders
- Builds the dashboard by store and shift
- Alerts when a location falls out of rhythm
Visual management by store and shift · running in Case Pé de Sopa
Before and after
What changes in the team's day.
The store's day
Without Kentor: You see the month's result, not the day as it happens
With Kentor: Each location's and shift's orders, average ticket and pace, on the phone
Restocking
Without Kentor: Photo of the stock and order in the WhatsApp group; whoever wasn't online missed it
With Kentor: Low stock triggers the order, with an owner and a deadline
Standard
Without Kentor: Each location does it its own way, and nobody opens the manual
With Kentor: The chain's standard written in one place, and the answer on the spot for whoever asks
Closing
Without Kentor: Days pulling together sales, expenses and each store's spreadsheet
With Kentor: The month closes with automatic checking, location by location
Team
Without Kentor: Bonus calculated by hand at each store
With Kentor: Bonus calculated by the chain's rule, ready to check
New people
Without Kentor: Whoever joins learns by watching a colleague
With Kentor: Whoever joins asks and gets the chain's way, with the source
How we implement
One location, then the chain.
We start with one location in shadow mode. Once the yardstick is met, the others follow the same standard.
Assessment
A conversation and an X-ray of the chain's operation.
Implementation
Map
Kentor OS talks to location managers and teams, in parallel.
Kentor OS
Construction
Brain and agents on the chain's processes, in 4-to-6-week cycles, starting with one location.
Kentor Brain and Kentor Bot
Routine
Shadow mode, then the other locations, with adoption measured.
Training
Implementation · Chain
Plan with your team
- Location mapDone
- Orders by store and shiftDone
- Close with automatic checkingIn progress
- Manager trainingNext
Governance
Every role sees its own part.
Each team sees what it is allowed to see, and anything outside the rules waits for an okay from whoever is accountable.
Everyone sees what they can see. Including the AI.
Permissions apply by team. Whoever couldn't see a piece of data in the source system can't see it in Kentor either, person or agent.
What matters waits for your OK.
Customer message, discount, posting: the agent prepares and asks first. You define what needs approval and from whom.
Every action, logged.
What the agent did, in which tool, who approved and what the rules blocked: it's all in the log, to check whenever you want.
Data handled according to LGPD.
Each connection is enabled by the company, team by team, and can be turned off at any time. Data handling follows LGPD.
- Everyone sees only what their team is allowed to see
- Expenses and discounts outside the rule await approval
Connections
Inside the tools the team already uses.
Kentor works with what you already have, with the permissions you grant.
- Google Sheets
- Excel
- Omie
- Google Drive
- Gmail
- Notion
- Typeform
- Slack
- Microsoft Teams
- Google Calendar
- Outlook
- HubSpot
- Pipedrive
- Google Docs
- Google Meet
- Zoom
- Salesforce
- ClickUp
- Trello
- Asana
- Monday
- Jira
- OneDrive
- SharePoint
- Dropbox
- Canva
- Figma
- Google Ads
- Google Analytics
- Mailchimp
- Calendly
- Airtable
- Zendesk
- Intercom
- Stripe
- QuickBooks
- Fathom
- Fireflies
- Granola
- tl;dv
Frequently asked questions.
Does it work for a franchise, with locations owned by different people?
Yes. Permissions apply per team, to people and to agents, and the network decides who sees what. We go over each network's details in the first conversation.
Do I need to switch the stores' system?
No. Kentor works with the systems and spreadsheets the locations already use, and with the WhatsApp the team already has.
Does the manager have to learn a new system?
No. The dashboard opens on the phone and restocking continues over WhatsApp. We train each manager on their own work.
What about location and team data?
Every person and every agent sees only what they can see. What matters goes through approval, every action is logged and data handling follows LGPD.
Can we start with one location?
This is what we recommend: one location in shadow mode, the yardstick met, and then the others, with the same standard.
See your whole chain, every day.
We map the locations with the managers and show what leaves WhatsApp and the spreadsheet first.