Everything a busy team keeps dropping
Bosun is built around how small teams actually communicate: in messages, in a hurry, in their own words. Thirteen capabilities, one assistant, and nothing for anyone to install.
WhatsApp task management software turns the messages a team already sends into a job list somebody can trust. Bosun reads a plain-language daily plan and creates tracked jobs from it, reads the end-of-day update and moves the right ones, reminds whoever is late, escalates to the owner when reminding stops working, answers staff questions from the business's own written procedures, and reports on the week without anyone compiling anything.
- Where staff work
- WhatsApp - nothing installed
- What they type
- Plain language, no commands
- Who can assign work
- Owner and managers only
- Answers come from
- Your own documents, cited
- When it cannot answer
- It says so, and records the question
Everything a busy team drops, caught in one place
Bosun is WhatsApp task management software that reads what your team already writes - the morning plan, the end-of-day update, the question about a rule - and turns it into a job list that stays true without anyone maintaining it.
Reads the daily plan
Someone types what they are doing today, the way they always have. It becomes separate tracked jobs with owners and deadlines - no forms, no commands to learn.
Learn moreListens to voice notes
A technician holds the button and talks. It is transcribed, handled exactly like a typed message, and repeated back so a mis-hearing is obvious straight away.
Learn moreCreates the work that repeats
Temperature logs, cleaning, safety checks, calibration, a weekly recall list. You describe the pattern once and the job appears on its own, chased like any other.
Learn moreReads the end-of-day update
"The rotors came in, the Ford is stuck waiting on parts." Matched against that person's open jobs by meaning - one closed, one blocked with the reason recorded.
Learn moreChases what is late
Escalating reminders to the person, never the group. After your chosen number of attempts it stops nagging and tells the owner instead.
Learn moreBriefs the owner
Ask for today and get a prioritised list: blocked first, then overdue, then due today, plus who has not reported. Built from the data, not written by a model.
Learn moreAnswers from your procedures
Staff ask what the approval limit is, or how long a job should take. Answers come only from your own documents, with a citation - and it refuses what they do not cover.
Learn moreTurns meeting notes into work
Paste the notes however you typed them. Decisions are kept as a record; the actions become tracked jobs, chased like everything else.
Learn moreWeekly review & advice
Throughput, ageing, close times and per-person figures every week, against the week before - with recommendations that carry the number behind them.
Learn moreKnows who is who
Identity is the phone number, checked against your roster. Reports and commands are owner-only, enforced in code - not asked for politely in a prompt.
Learn moreOne message, what happens
- Staff types a plan
- In their own words
- Jobs created
- One per deliverable
- Assigned to
- The sender
- Deadlines
- Only where stated
- Owner sees it
- Immediately
The list is only useful if it is true
Every business has tried a job list. The list is not the hard part - keeping it true is. It goes stale the moment updating it becomes a separate chore from doing the work, and a stale list is worse than none, because people stop trusting it and go back to asking each other.
Bosun removes the chore. Your staff describe their work in the place they already describe it, to each other, on WhatsApp. The list updates itself from what they said. Nobody is asked to maintain anything.
- No app to install, so there is no adoption to win
- No forms, no commands, no reference numbers to quote
- The people who hate software never find out they are using any
- The owner sees a list that matches reality, because reality is what wrote it
Who each capability is for
| Capability | Staff | Manager | Owner |
|---|---|---|---|
| Daily plans | Send one | Sees the team's | Sees everything |
| End-of-day updates | Send one | Sees the team's | Sees everything |
| Automatic follow-up | Gets reminded | Gets the escalation | Gets the escalation |
| Owner briefing | No | Yes | Yes |
| Answers from procedures | Yes | Yes | Yes |
| Voice notes | Can send them | Can send them | Can send them |
| Recurring work | Gets the job | Can set them up | Can set them up |
| Meeting notes | No | Can file them | Can file them |
| Weekly review | No | Yes | Yes |
Every one of these limits is enforced in the code on the sender's phone number, not requested in a prompt. See roles and permissions for why that distinction matters.
On this page
Does my team have to change how they message?
No. That is the whole design. They write the way they already write - "today I'm ordering the rotors and calling Mrs Diaz" - and the assistant does the structuring. There are no commands to learn and no forms to fill.
What happens in a group chat?
Bosun works in one-to-one chats with each person, not in your group. Group chats are where things get lost: a message scrolls past and everyone assumes somebody else picked it up. Each person having their own thread is what makes a job traceable to a name.
Can it read voice notes or photos?
Both are kept. A voice note is transcribed and handled exactly like a typed message, and it repeats back what it heard - see <a href="/features/voice-notes/">voice notes</a>. A photo is stored and attached to the job the same message created, so the picture of the damage sits on the job about the damage. What it does not do is interpret what is in the photo; a person still reads it.
What if it misreads something?
Anything the assistant is unsure about is flagged for the owner to review rather than quietly filed, so low confidence never becomes a confident-looking entry. Nothing is ever deleted either, so the full history of every job stays on the dashboard.