Field notes › Product
Letting a client see you're working on their shift before anyone is named
A site supervisor raises a request for a crew next Tuesday. Then, as far as they can tell, nothing happens. The office has seen it, someone is already ringing around and two workers have been pencilled in, but none of that is visible from the site. So around lunchtime the supervisor rings to ask whether anyone got the request. The next morning they ring again.
Those calls aren't impatience. The supervisor has a job to plan around that crew, and from where they sit a request with no response looks exactly like a request that went missing.
The quiet stretch between the request and a name
Most requests go through a stretch where the office is flat out on them and the client has no sign of it. Finding people with the right tickets who are free on those dates takes time. Confirming them takes longer, because workers don't always answer straight away and some say yes on Monday and change their mind on Wednesday.
The usual response is to send names early. That creates a worse problem. A name given to a client before the worker has confirmed is a promise, and when that person drops out the client hears it as a change at best and a let-down at worst. Names are better kept back until they're real, which means finding another way to show the request is being handled.
What the client needs in that stretch is small. They want to know the request landed with someone who is working on it. They don't need a running commentary on the phone calls.
Acknowledge fast, even before you can answer
Whatever tools you use, the first habit is speed of acknowledgement. A short reply saying the request is in and being crewed takes a minute and heads off the first chase-up call. That only works if the right people see the request quickly, which is harder than it sounds when requests arrive by text and email to whichever admin the supervisor happens to know.
Putting every request through one channel fixes most of that. It also means a request doesn't sit unseen because the one person who received it is on leave or buried in a busy morning.
Show the shift, not the names
Mustr handles the stretch by letting the client see the shift take shape. When the office enters a shift for a client's site, it appears on that client's roster straight away as an unassigned, dashed shift, while it is still an office draft. The client can see it but can't change it. At a glance they can tell their request has become a shift with dates and a day or night pattern, and that it isn't crewed yet.
Crew never see a shift that hasn't been released, and drafts notify nobody. The office can move people around, try a different combination or wait on a confirmation without workers getting notices about a shift that might still change. Nobody on the crew side gets an expectation the office can't yet keep.
On the office side, the whole admin team is told the moment a client raises or amends a request, and requests sit in a queue with the ones needing action at the top. A request doesn't depend on one person noticing an email. When the shift is crewed, the client is told, with names.
Tell clients what the dashed shift means
A visible draft only cuts calls if the client knows how to read it. When you set up a site's logins, spend a couple of minutes explaining the difference. A dashed shift means the office has it and is crewing it. Names appear once people are confirmed. Supervisors who understand that stop ringing for status and ring when something about the job itself has changed, and those are the calls worth taking.
Be honest with yourself about how long drafts sit, too. If a client watches a dashed shift for days on end with no update, the visibility starts working against you. Some offices set themselves a rough internal standard for how quickly a draft either becomes an assigned shift or gets a note to the client explaining the hold-up.
What changes in the office
The obvious gain is fewer status calls. The less obvious one is that the office no longer has to sound certain before it is. A rosterer who knows the client can already see progress doesn't feel pushed to name someone just to get off the phone, and that pressure is how unconfirmed names end up in emails that later have to be walked back.
It also changes the tone of the relationship. A client who can see their request moving tends to give the office the benefit of the doubt when a shift is hard to fill, because they've watched it being worked on rather than wondering whether it was forgotten.
The client portal page shows how a draft shift looks from the site's side, or you can book a demo and we'll walk you through both views.