Status lives in WhatsApp threads
Who confirmed, who is delayed and who never replied is scattered across five group chats. Getting a true picture means scrolling, asking and hoping someone remembers.
An AI operations manager for small business gathers status from your team and vendors, chases whatever is late and escalates exceptions by rules you write. It does not replace your managers. It makes sure they hear about problems early, and it keeps the business running sensibly when you are off.
Who confirmed, who is delayed and who never replied is scattered across five group chats. Getting a true picture means scrolling, asking and hoping someone remembers.
A late job or a missed delivery goes unnoticed until the customer calls. By then the fix is an apology, and the damage to the relationship is already done.
Every approval routes to one phone. On holiday, or in a long meeting, decisions queue up and the team waits rather than risk a wrong call.
| When | The assistant | You or your team | Result |
|---|---|---|---|
| Every working day at 8:00 AM | Messages each supervisor, vendor and crew lead on WhatsApp to confirm the day's commitments, and asks a named backup if there is no reply within 30 minutes | The operations manager confirms the final roster from the replies | By 9:00 AM a confirmed plan for the day is posted in one shared channel, with gaps highlighted |
| A job is still open 45 minutes past its scheduled finish | Alerts the responsible manager in Slack with the job details, the likely delay and two options: extend the slot or send cover | The manager picks an option with one tap | The delay is handled while it is small, and the client is told only after the manager confirms |
| A spend request or exception crosses the limit you set | Assembles an approval request with the context, photos or documents attached and the policy that applies, and sends it to the named approver | The approver accepts, declines or asks a question | Decisions are made on facts in minutes, and the approval is recorded against the item |
| The owner marks themselves off-duty in the calendar | Routes approvals to two designated managers, sends the owner a short FYI of what was decided and holds any large decision for a 12-hour override window | The two managers decide within their limits; the owner can override within the window | Work continues during absence and the owner returns to a clear log, not a backlog |
| Friday at 3:00 PM | Builds the weekly ops scorecard from the job tracker and update logs: on-time rate, open exceptions, repeated delays and who is overdue on what | The owner reviews it and picks two issues to fix next week | A one-page scorecard in your inbox and the shared drive, ready for the Monday huddle |
Confirmation requests go out to every crew lead and vendor. Two do not reply, so the assistant contacts their backups.
The manager sees one plan for the day with a single red line: an unstaffed site, and a backup already pencilled in.
A job runs late. The manager gets an alert with two options and chooses cover; the assistant updates the schedule.
A replacement-part request goes to the approver with the supplier quote attached. It is approved in four minutes.
You are travelling. Two managers handle a rescheduling decision, and you receive a three-line FYI.
The scorecard shows on-time rate by team, three repeated delays and one vendor that keeps missing confirmations.
If a tool has an API or an export, it can usually be connected.
Each type of decision has a named person and a limit. The assistant routes by that table and never improvises, so authority is the same whether you are in the office or not.
Larger decisions made in your absence are held for a period you define. You can reverse them before they take effect, and you are told what happened.
Each alert, approval and escalation is logged with who, when and why. When a client questions something, you can show exactly how it was handled.
The assistant drafts. A person on your team sends.
This isn't a template with your logo on it. Every build starts from how your business actually runs — so there's no off-the-shelf demo, and we won't pretend otherwise.
We map how your week and your business actually run, and pick the first tasks worth handing over.
On the strategy call we build one of your real tasks with AI, on screen — your data, not a generic demo.
We scope the build with you on a strategy session and quote it in writing — agreed before a single workflow is built.
The assistant is wired into your tools, with inputs set up for each person on your team.
We go live, then tune reminders, reports and sign-offs as your team settles in.
An exception is anything that breaks your normal plan and crosses a threshold you define, such as a job running late, a vendor not confirming, a cost above a limit or a client complaint. We write these triggers down together during scoping, so the assistant escalates what matters and ignores the noise.
You do, through a simple authority table. Routine matters go to supervisors, spend within a limit goes to a manager and larger items go to you or a second approver. The assistant follows the table exactly, and every approval is recorded against the item.
Off-duty mode is a set of rules that applies when you mark yourself away. Decisions route to two designated managers, you receive a short summary of what they decided, and any large call waits through an override window you can use to step in. Nothing stalls, and nothing important is final without you.
Usually yes. If your scheduling, accounting or messaging tool has an API or an export, it can normally be connected, and WhatsApp, Slack, Sheets and email are common starting points. We confirm every connection during scoping and tell you plainly if one cannot be made.
Resistance is common at first, and it fades when the updates take less effort than the old group chats. We set up simple inputs for each role, keep reminders polite and make the managers, not you, the escalation point. It is introduced as a way to cut chasing.
Yes. Every confirmation, alert, approval and override is stored with a timestamp and the person responsible, in a sheet or database you own. You can filter it by job, person or date, which makes reviews and disputes much simpler to settle.