We design and run automated WhatsApp workflows for teams that are spread across outlets, sites and shifts — rostering, daily IC and outlet reporting, inbox monitoring and management reports. Your staff keep using the app they already have open. Nobody chases anybody.
Built on the official WhatsApp Business Platform — not a phone plugged into a server.
What we build
Every one of them replaces the same thing: someone typing information into a chat, someone else chasing whoever didn't, and a third person compiling it into a report by hand.
The roster goes out on WhatsApp and comes back confirmed. Swaps, leave and last-minute cover are requests in a thread, not phone calls at 6am.
Supervisors send a photo of the closing receipts. The system reads the figures, does the arithmetic, asks only what a person can answer, and files the report.
A mailbox nobody watches becomes a WhatsApp alert somebody acts on. We watch the inbox, read the attachment, and message the person who needs to know.
A day, automated
This is a real daily reporting cycle for a multi-outlet F&B group. Every time below is configurable, and none of it needs a human to start it.
08:00
Each supervisor gets the request for yesterday's trading and answers where they were. No roster to keep in sync, no wrong person messaged.
09:00
A private nudge to whoever hasn't sent anything. Anybody who already submitted is left alone for the rest of the day.
10:00 & 10:30
Ops and management see exactly which outlets and which people are still missing — twice, so it is acted on rather than noticed. These groups are deliberately small: the official platform allows up to 8 people in one.
11:00
A consolidated PDF is generated and posted to the management group, with a portal link for anyone who wants to download it later.
Capabilities
Each one is production-tested. A new workflow is usually a new arrangement of these, not a new system.
Closing receipts, Z-reports, invoices and statements read from a phone photo, with confidence thresholds and a re-send prompt when a scan isn't clean enough to trust.
Structured, multi-screen forms that open inside WhatsApp. Answers arrive complete and in the same shape every day — no free-text to interpret.
Time-based triggers per tenant and per timezone, with reminders that target only the people who still owe you something.
Outstanding lists and exception alerts posted into your ops and management group chats, so accountability is visible without anyone playing messenger. The official platform caps a group at 8 people, so these stay small and senior by design.
Consolidated PDF reports delivered on schedule, plus a simple download portal. Layouts are designed with you and signed off before anything is built.
Wrong figure? We correct it on request, and the original value, the new value, who changed it and why are all retained.
POS exports, Google Workspace and Microsoft 365 mailboxes, spreadsheets, cloud storage and internal APIs — wherever the data already lives.
Built multi-tenant from the start: separate outlets, brands and groups with their own schedules, recipients and reports, on one platform.
WhatsApp Business account setup, sender verification and Meta template approval are our job, not a form we hand you.
Working with us
We start with one outlet. If it doesn't hold up in the real world with real staff, rolling it out to thirty won't fix that.
Step 01
We sit with the people doing the work now — what gets sent, who chases, what breaks. You get a written spec of the workflow and every message it will send, to mark up.
Week 1Step 02
We build the workflow, set up your WhatsApp Business sender and put the message templates through Meta's approval. Report layouts are signed off before rendering.
Weeks 2–4Step 03
One stall, real staff, real receipts, running alongside whatever you do today. We watch every submission and tune the wording until it is boring to use.
2–3 weeksStep 04
Outlets are added in batches. From then on we operate it — monitoring, corrections, config changes and new questions are handled by us, on request.
OngoingWhy WhatsApp
Every operations tool has the same failure mode: the people on the floor don't open it. WhatsApp is already open, already understood, and already where the work is being discussed. We stopped fighting that and started building on it.
That is the whole specialisation. Not a chatbot bolted onto a dashboard — the workflow itself, living in the thread.
No account creation, no password resets, no "have you downloaded it yet". A new supervisor is productive on day one.
A reminder in WhatsApp lands where staff already look. An email to an outlet address does not.
In-chat forms and validated photo capture mean you get clean, comparable records — not a scroll of free-typed messages.
We run on Meta's WhatsApp Business Platform with approved templates and a verified sender — so your number doesn't get banned mid-rollout.
Pricing
Not per user, not per message, not per report. Add an outlet and the price moves by one outlet — which means the workflow scales with the business rather than with headcount.
S$15per outlet / month
Indicative rate for a daily reporting workflow on an annual subscription. Final pricing depends on outlet count and workflow scope.
Not at signature. You start paying for the workflow when the first outlet is actually using it in production.
20% on confirmation, 30% when the first outlet goes live, and the balance after six months of the subscription running.
WhatsApp conversation charges are billed by Meta at their published rates and borne by you directly — we don't mark them up.
Reporting times, wording, recipients and thresholds are configuration and we change them on request. New workflows are quoted separately.
Questions
Still something unanswered? Message us — it's a WhatsApp thread, appropriately enough.
Ask on WhatsAppNo. They receive a normal WhatsApp message from a verified business number and reply with taps, a photo, or a short form that opens in the chat. There is no app, no login and no training session — which is exactly why it gets used.
It is not. We build on Meta's official WhatsApp Business Platform: a verified business sender, message templates submitted for Meta's approval, and conversation charges billed transparently by Meta. Unofficial automation risks the number being cut off — we don't use it.
Each slip is checked several ways before anything is stored: every meal period must be present, the scan must clear a confidence threshold, the header must match a brand that outlet trades, the date must be the right trading day, and gross minus discounts must equal net. If any check fails, the supervisor is told which set and why, and re-sends that one photo. Nothing partial is ever stored.
Whoever hasn't submitted gets one private reminder, and the outstanding list goes to the ops group twice before the report is produced. An outlet that didn't trade simply doesn't submit and shows as missing for the day — we suppress named outlets for a date on request rather than making every supervisor declare a closure.
Eight. That is the official WhatsApp platform's limit for a group we can post into, not ours, so the ops and management groups are set up small and senior — the people who act on a missing report rather than everyone who might glance at it. Anyone outside that group reads the same report from the download portal.
Usually, yes. If it involves asking a distributed team the same thing on a schedule, collecting something back, chasing whoever didn't respond, and turning the result into a report — that is the shape we build. Tell us the current process and we'll tell you honestly whether WhatsApp is the right place for it.
We do. There is no admin console for you to staff. Setup, configuration changes, corrections and monitoring sit with us; your side of it is a reporting portal for downloading reports, and a WhatsApp thread when you want something changed.
In a dedicated, access-controlled database per deployment, hosted in the cloud with encrypted transport and backups. Submissions, corrections and their history are retained so figures stay auditable. Happy to go through the specifics with your IT team.
Typically four to six weeks from kickoff to a pilot outlet running, with Meta's template approval usually the longest single wait. Rollout across the rest of the estate is a matter of days per batch once the pilot is stable.
Let's talk
Twenty minutes on a call is usually enough for us to say whether this is worth automating, roughly what it costs, and how long it takes. If it isn't a fit, we'll say that too.
