The whiteboard that updates itself
Every workshop has a board, and by Wednesday afternoon it is wrong. The cars that are actually stuck are stuck on parts, and the only place that is written down is a message somebody sent at half past four.
For a workshop, Bosun tracks jobs from what technicians and the front desk already type: what is on which bay, what is waiting on a part, which customer needs ringing and which MOT or service is promised for when. Anything blocked names what it is blocked on, and the owner is told the same morning rather than at the end of the week.
- Typical departments
- Front desk, bays, parts
- The critical status
- Blocked, with the reason
- Kept in job titles
- Registrations, part numbers
- Chases
- Overdue jobs and callbacks
- Installed by staff
- Nothing
Blocked, right now
- KX19 PTR
- Rotors, 3 days
- Bay 2 Transit
- Turbo, 5 days
- Focus, Mrs Ali
- Awaiting her approval
- Told the owner
- Every morning
- Chased the tech
- No
It is almost always a part
Ask any workshop owner what holds up a week and the answer is parts. A car goes on a ramp, something is missing, and the job sits. From the outside it looks like work in progress, so nobody escalates it - and the customer finds out before you do.
Bosun treats blocked as a status of its own, separate from late. The technician says "waiting on the rotors", that reason is recorded in their words, the owner is told that morning, and the technician stops being chased about something they cannot move.
- "Waiting on the rotors" is recorded as the reason, verbatim
- The owner is told the same morning, because it needs a decision, not a reminder
- The technician is not chased about a job they cannot progress
- When the part lands, saying so puts it back in the normal flow
The workshop week, tracked
Jobs on the bays
What is in, what stage it is at, and who is on it - from the messages they already send.
Waiting on parts
The status that matters most, with the reason recorded and the owner told the same day.
Customer calls
"Ring Mrs Ali about the extra work" - chased privately until it happens.
MOTs and services due
Dated jobs, reminded before the date rather than after.
Procedure questions
"What do we charge for a diagnostic?" answered from your own price list, quoted exactly.
How the week went
Jobs in against jobs out, average time to close, and how much of the week went on blocked work.
From nothing to running, in about a week
-
1
We talk for an hour
How your workshop is divided, who does what, and the three things that get dropped most often.
-
2
We install and connect it
Your server, your WhatsApp number, your AI account, your domain. On your accounts, with the passwords handed to you.
-
3
We load your procedures
Whatever you already have written, converted and indexed. Whatever you do not, we start from a template for your trade.
-
4
You send one message
Your team gets told the number exists and what to send it. There is no training session, because there is nothing to teach.
Built for busy teams
On this page
Does it replace our garage management software?
No. Your existing system holds the job cards, parts and invoicing. Bosun holds what people said they would do and whether they did it - which is the part that currently lives on a whiteboard and in messages.
My technicians barely text. Will this work?
Then they do not have to type. They can hold the button and say it - "rotors came in, KX19 done, Transit still stuck on the turbo" - and that voice note is transcribed and handled exactly like a typed message. It repeats back what it heard, so a mis-heard registration is caught before it becomes a job. Typing works the same way and takes about nine seconds. See <a href="/features/voice-notes/">voice notes</a>.
Can the front desk see everything?
Give them the manager role and yes - they can see and assign across the workshop. Technicians see and change only their own work.