Feature

Progress reported the way people talk

"Rotors are ordered and confirmed. The Ford is stuck, we're waiting on the parts department." One job closes, one goes blocked with the reason recorded - and nobody typed a reference number.

Matched by meaning Blocked reason captured No reference numbers

Book a free demo See pricing

An end-of-day WhatsApp update and the job statuses it changed

In short

An end-of-day update is the message a staff member sends describing what happened. Bosun matches it against that person's open jobs by meaning rather than by reference number, moves each one to done, in progress or blocked, and records the stated reason on anything blocked. Where two jobs fit equally well, it asks rather than guessing.

Matched by: Meaning, not reference numbers
Statuses: Done, in progress, blocked, open
Blocked: Reason recorded, owner told
Ambiguous: Asks instead of guessing
Not matched: Becomes a new job

What it does

The status update, without the admin

Closes what is finished

"The rotors came in" closes "Order 4 brake rotors for the Civic". Nobody quoted a reference.

Blocks what is stuck

Waiting on a part, a person, an approval or a decision - the reason is recorded, not just the status.

Tells the owner about blocks

Blocked work needs a decision from somebody. The owner is told without having to ask.

Asks when unsure

If two open jobs fit the sentence equally well, it asks which - rather than closing the wrong one quietly.

Catches new work

Something mentioned that matches no open job becomes a new one, so the day's extra jobs do not vanish.

Only their own jobs

Nobody can close a colleague's work by describing it. An update only ever moves the sender's own list.

One update, four outcomes

"Rotors ordered and confirmed": Closed
"Ford stuck on parts": Blocked + reason
"Couldn't reach Mrs Diaz": Still open
"Also booked the Civic in": New job
Owner notified: About the block

Why blocked matters most

The jobs that quietly stop

Overdue work is visible; everyone knows it is late. Blocked work is the dangerous kind, because from the outside it looks like work in progress. The job sits waiting on a supplier, an approval or somebody else's decision, and nobody notices until the customer calls.

Bosun treats blocked as different from late. The reason is recorded as the person said it, the owner is told the same day, and the person who is stuck stops being chased about something they cannot move.

"Waiting on the supplier" is recorded as the reason, in their words
The owner is told without asking - blocked work needs a decision, not a reminder
A blocked job is not chased as if it were simple lateness
When it is unblocked, it goes back into the normal flow

Works together with

More of the assistant

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. Keeps the photo with the job A picture of the damage, the reading or the finished work is attached to the job that message created - not lost in a chat nobody can search. Listens 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. Creates 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. Chases 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. Briefs 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.

See every feature