Ben sends the crew list.
Ben, a site supervisor, sends today's list on WhatsApp: six names, the yard and the hours, typed the way he always types them.
Yard 3 today 8 to 6
Arun, Dev, Farid, Lim, Rahman, Sam
Every message your team sends takes a route you can follow.
Operator runs the routine work of your company from the messages your team already sends on WhatsApp, Telegram and email. AI reads each message. Tested code makes every change and reads it back before Operator calls it done. When something is unclear, Operator asks the right person and waits for the answer.
In daily use at a marine contractor in Singapore since September 2026.
Service status Example data
- All routes running
- 1 question waiting for Ben
- Payroll waiting for Asha
How a message becomes a record
One crew list, from a supervisor's phone to the timesheet. An enquiry, an expense claim or an invoice goes through the same steps.
AI reads it.
Operator's AI pulls out what the timesheet needs: who worked, where, and from when to when. Nothing is saved at this step.
- Who
- Arun, Dev, Farid, Lim, Rahman, Sam
- Where
- Yard 3
- When
- Fri 24 Oct, 08:00 to 18:00
Prepared by AI. Not saved.
Operator asks about Dev.
Two workers are called Dev. Operator asks Ben which one he means, and the list waits until he answers.
OperatorTwo people are called Dev. Which one worked at Yard 3 today?Dev A.Dev R.
Dev R.
Example dataCode writes the shifts.
A compiled skill, tested before it went live, records six shifts and works out overtime from your company's rules. Only this code writes records.
- Arun ExampleYard 308:00 to 18:00 · 9 h
- Dev R. ExampleYard 308:00 to 18:00 · 9 h
- Farid ExampleYard 308:00 to 18:00 · 9 h
- and 3 more shiftsExample data
Each shift is checked.
Operator reads every shift back from the database and compares it with what it meant to write. Then it tells Ben the list is recorded.
- 6 of 6 shifts read back and matched
- Overtime matches your rules
- Reply sent to Ben at 08:05
Asha sees it.
The six shifts appear on Asha's week grid, each linked to Ben's original message.
Timesheet weekMon 20 Oct to Sun 26 Oct
| Worker | Wed22 Oct | Thu23 Oct | Fri24 Oct |
|---|---|---|---|
| Arun Example | 18:009 hours | 17:008 hours | 18:009 hoursBen 08:02 |
| Dev R. Example | 17:008 hours | 17:008 hours | 18:009 hoursBen 08:02 |
| Farid Example | 17:008 hours | 17:008 hours | 18:009 hoursBen 08:02 |
Workflows built on Operator so far
Each company's Operator is built around its own work. These are the workflows built and tested so far. Amber stops are where a person steps in.
Crew lists to timesheets
Supervisors send who worked where. Operator records shifts and absences and works out payable hours from your rules and public holidays.
- ReadAI
- Askif unclear
- Writecode
- Check
- Week grid
Payroll
Operator builds each pay period from approved hours and pay items. An Owner approves the period before Operator makes the payslips.
- Approved hours
- Buildcode
- Check
- Approvean Owner
- Payslips
Customer enquiries
Enquiries by email and WhatsApp get a drafted reply. Someone on your team approves it before it is sent.
- ReadAI
- DraftAI
- Approveyour team
- Reply sent
Invoices and cash
Invoices, bills, loans and bank lines sit in one Cash view. Ask what comes in this month and get the figure with the lines behind it.
- Bank lines
- Suggest linksAI
- Reviewan Owner
- Cash view
Expense claims
Staff send a claim from their phone. Operator records it against their name for review.
- Telegram
- ReadAI
- Writecode
- Check
- Review
Answers from your documents
Ask a question in chat. Operator answers from your company's documents and names the document and page it used.
- Question
- Searchyour documents
- AnswerAI
- Source named
What Operator leaves to your people
Operator stops and hands the work to a person at these points. On the map, they are the amber stops.
Unclear input
When a name, date or amount could mean two things, Operator asks the person who sent it. Related work waits for the answer.
Approvals
Payroll periods, shift rejections and customer replies wait for the people you name.
Sources
Every record links to the message it came from, who sent it and when.
Access
Each person sees and edits only what you allow, dashboard by dashboard and field by field.
Changes
A new version goes live only after it passes your saved test cases. The previous version stays ready to roll back to.
Your company gets its own Operator
Each company runs its own installation of Operator, with its own database and its own address.
yourcompany.oper.run
Your own installation
Your own database
Your keys, encrypted
Or on your own computer or server
yourcompany.oper.run
Hosted for you as a separate installation. Your channel keys and settings stay encrypted inside it.
Or on your own machine
Run the same tested build on a computer in your office or a server on your network.
Sign in from your phone
Scan the code on the screen, then tap Yes in WhatsApp or Telegram. Add a passkey to skip the code next time.
Sign in to yourcompany 482 913Scan with your phone or send the code. It changes every minute.
Example dataSign in to yourcompany on the screen you scanned?YesNoBackups
Every upgrade starts with a backup. We test a restore before your real records arrive.
Office files
Operator Bridge reaches files on your office computers and shares only the folders a person approves.
Start with one workflow
FourLabs builds your Operator with you. Every new line opens the same way.
We map it with you.
Who sends what, who checks it, and the rules your business already follows.
We build and test it.
Operator turns the design into a database and code, then runs it against saved cases from your business before it touches live records.
It goes live at your address.
Your team keeps using WhatsApp, Telegram or email. You follow the work on your dashboards.
It changes when your business does.
New rules go out as a new tested version. The one before stays ready if you need it back.
The pilot on one workflow has no fee.
Bring one workflow to a 30-minute call
Show us how the work runs today, and we will show you how it would run on Operator.