Solution · Operations
The operation runs without you putting out fires.
Kentor understands how your operation really runs, pulls out of people's heads what only they know and puts AI on order tracking, restocking and customer service. The team approves, and you stop being the company's reminder.
Kentor OS
Discovery
Your company
JUJulianaOperations
Process map
From order to delivery · 5 processos
| Process | Steps |
|---|---|
| Order received | 3 |
| Picking | 4 |
| Confirmation with Fulana | 2 |
| Inventory restock | 5 |
| Delivery to the customer | 4 |
Inferred from the conversations, with who mentioned it
Operations today
Where the operation depends on someone remembering.
The pain
If Fulana goes on vacation, the operation stops.
The exception rule, the right supplier for each emergency, each customer's way: it's all written down, with a source and an owner. Whoever joined yesterday finds the answer without interrupting anyone.
How Kentor does it
Kentor Brain brings together procedures, spreadsheets, conversations and the OS map in a record per process, always up to date. People and agents consult the record, each with their own permission.
Kentor BrainHow we work · Procedure
Urgent restock
The store requests, the manager approves up to the limit, and above it, leadership.
3 sources · 4 calls
Historyprevious values are kept
- 06/11The limit without approval changed to small purchases.
- 19/10The new packaging supplier was added.
- 30/08Record created from the OS interviews.
The pain
You know it jams. You don't know where.
The process shows up as it happens: the side spreadsheet, the urgent-purchase shortcut, the stage that waits on one person. Each bottleneck comes with the evidence and the math on how much time it costs, and the most urgent goes to the top.
How Kentor does it
Kentor OS interviews the team with AI, in parallel and without stopping the operation, and draws the map of who does what, in which tool.
Kentor OSProcess map
Order operations · 4 processos
| Process | Steps |
|---|---|
| Order and picking | 6 |
| Restocking | 3 |
| Delivery | 4 |
| After-sales | 3 |
Inferred from the conversations, with who mentioned it
Inventory restock
PurchasingR$ 24.960 per year
6 h per week · 4 interviews
The pain
The customer finds out about the delay before you do.
The stalled order shows up before it becomes a complaint, with the reason and who needs to act. Low stock already becomes a restock order, with an owner and a deadline, without getting lost in the group.
How Kentor does it
Kentor Bot's operations agent tracks orders and inventory in your tools, alerts the owner and writes the message to the customer. It asks before sending.
Kentor Bot- Reading the day's orders3 of 5 locationsnow · In progress
- Inventory checkedAll locations07:10 · Done
- Order stalled in picking for 2 daysCustomer notice ready · needs your OKWaiting for your OK09:45
- Restock requested from the supplierWith a deadline · delivery tomorrow08:30 · Done
- Daily dashboard updatedBy location and shift08:00 · Done
The pain
One more system, and the team goes back to WhatsApp.
Nobody switches tools. AI comes into the WhatsApp, the spreadsheet and the system the team already uses, and each person learns on their own routine.
How Kentor does it
Implementation gets everything running alongside your team, and Training takes each person to everyday use.
Implementation and TrainingImplementation · Operations
Plan with your team
- Operation map with Kentor OSDone
- Records for each process in BrainDone
- First agent on the restocking routineIn progress
- Tracking by teamNext
How Kentor comes in
First understand. Then automate.
The same path in any area: AI knows the business before acting, and people approve what matters.
- 01
Understand
We map how the area really works, with AI interviews, and point out where AI pays back most.
Kentor OS - 02
Organize
We connect the systems and bring together what the company knows, with rules on who sees what.
Kentor Brain - 03
Automate
We put agents on the routines that weigh most. They act in the team's tools and ask for approval when it matters.
Kentor Bot - 04
Track
We stay on until the routine sticks: adjustments, training by area and tracking of what changed.
Implementation and Training
The operation's day
The day, from 7 a.m. to 6 p.m..
- 7 a.m. · Opening
Without Kentor: You call to find out how the operation started
With Kentor: Day dashboard open on the phone, by location and shift
- 9 a.m. · Inventory
Without Kentor: Photo of the stock in the group, and whoever didn't see it missed it
With Kentor: Low stock becomes a restock order, with an owner and a deadline
- 11 a.m. · Exception
Without Kentor: Only one person knows how to fix it, and they're busy
With Kentor: The rule is written down, and anyone can find the answer
- 2 p.m. · Customer
Without Kentor: The customer asks about the order, and the team stops everything
With Kentor: Lead time and status answered; the rest goes with context
- 4 p.m. · Delay
Without Kentor: The delay shows up when the customer complains
With Kentor: Stalled order flagged early, with the reason
- 6 p.m. · Closing
Without Kentor: The day closes in the head of whoever was there
With Kentor: Summary of what came in, went out and stalled
Routines
The routines that take the operation out of your head.
Routines already running in the Pé de Sopa case and in Kentor's own operation. Each one solves an operations pain.
The pain
You see the month's result, not the day as it happens.
The operation's day, on one screen.
Each location's and shift's orders, pace and value, updated throughout the day and opened on the manager's phone.
What goes out
- Call to ask how it's going
- Close only at month-end
- You see the day while it happens
- The drift shows up on the shift, not in the month
- Everyone looks at the same number
How Kentor does it
- Reads each location's and shift's orders
- Updates the dashboard throughout the day
- Sends the summary of what stalled
Visual management by store and shift · running in Case Pé de Sopa
Guarantees
AI works. The team decides.
Nothing goes out without your OK.
The agent prepares and asks. Messages, discounts and proposals only go out when someone on the team approves.
Everything is logged.
Every agent action goes in the history: what it did, in which tool and who approved.
You choose what the AI sees.
Each connection is enabled by team. What hasn't been enabled, the agent doesn't read.
Connections
Inside the tools the team already uses.
Kentor works with what you already have, with the permissions you grant.
- Google Sheets
- Excel
- Google Drive
- Omie
- Trello
- Asana
- Monday
- ClickUp
- Airtable
- Slack
- Microsoft Teams
- Gmail
- Google Calendar
- Outlook
- HubSpot
- Pipedrive
- Notion
- Google Docs
- Google Meet
- Zoom
- Salesforce
- Jira
- OneDrive
- SharePoint
- Dropbox
- Canva
- Figma
- Google Ads
- Google Analytics
- Mailchimp
- Calendly
- Typeform
- Zendesk
- Intercom
- Stripe
- QuickBooks
- Fathom
- Fireflies
- Granola
- tl;dv
Other areas
Kentor works across the whole company.
- Sales and pre-salesProspecting and account agents
- Marketing and contentPiece, campaign and report in the brand's voice
- Customer service and after-salesAnswered on the spot and the customer stays
- Finance and administrationReconciliation and collections every day
- People and HROnboarding, team questions and training
- Leadership and managementHow the company runs and where AI pays off
Frequently asked questions.
Do I need to stop the operation to map it?
No. Kentor OS interviews happen in parallel, and each person answers in their own time.
Will I have to switch systems?
No. Kentor works in the WhatsApp, spreadsheets and systems you already use, each with the permission you grant.
Does the agent talk to the customer or the supplier on its own?
Only if you want. By default, it writes the message and asks before sending. Every action is logged with time, tool and who approved.
What if the process changes?
The record in Brain changes with it and keeps the history of what changed and when. The agents start following the new rule.
Who looks after this day to day?
Your own operations team, with no IT needed. Kentor implements, trains each team and follows the adjustments until the routine sticks.
Fix the process. Then automate.
We start with the operation map and prioritize by what gives back the most time.