Systems / WhatsApp
WhatsApp systems
The staff side of a system that runs inside the chat your team already has open.
An app your staff must install is an app most of them never open. When the people doing the work are field staff, shop floor, drivers or members, the system meets them in WhatsApp: numbered menus that work without approvals, sessions that never trap someone, and a web dashboard for the one person who needs a dashboard.
The work that proves it
You need this when
- The people who need to use the system will not install, log in to, or remember a new tool.
- Attendance, leave, orders or requests already arrive as messages and nothing captures them.
- You need two sides: a chat for staff and a screen for management.
You do not, when
- If every user sits at a desk with a laptop, a web app is simpler and cheaper.
- WhatsApp's 24-hour window and template rules are real constraints. Marketing blasts are not what this is for.
What it is built from
A provider-agnostic bot engine (Twilio or the Meta Cloud API by configuration), session state in Postgres via Prisma, handlers per conversational surface with tests, a cron layer for scheduled sends.
Related
- Operational dashboardsThe one screen a manager opens in the morning, built around the decisions they actually make.
- Platforms and social productsMulti-user products where the thing being modelled is people and how they connect.
- Commerce and point of saleStorefronts, tills and wallets that keep working when the network does not.
- Everything on the site
All whatsapp work
Need a WhatsApp system to run on?
A thirty-minute call, then a written scope within five business days. No obligation either way.
Start a project
- Call
- 30 minutes
- Scope
- 5 business days
- Build
- Weeks, in the open