Design Service Dispatch Around the Right to Disconnect

02The contradiction appears each evening as routine quote requests, missing job notes and customer questions arrive alongside real breakdown calls.

03Fair Work states that employees can refuse to monitor, read or respond outside working hours unless refusal is unreasonable.[

041] Its guidance records the small-business commencement date as 26 August 2025.

05Treat that as an existing framework to assess, not an upcoming implementation deadline.

06Our recommendation is to make responsibility explicit before configuring notifications.

07Identify the person or role expected to respond under the agreed arrangements.

08Do not infer availability from a green status icon, an earlier reply or somebody carrying a company phone home.

02Have appropriate managers approve these categories.

03A customer's use of the word urgent is useful context, but should not be the sole trigger for contacting an entire crew.

04Keep the legal assessment distinct.

05Fair Work identifies several factors relevant to reasonableness, including the reason for contact and the employee's circumstances.[

061] An automated severity label cannot evaluate those facts or override an applicable award, agreement or individual arrangement.

07Ask customers to use a central service route after hours.

08That makes the service request visible to the agreed responsible role and reduces dependence on personal numbers.

09Retain an approved emergency path where needed, with clear instructions appropriate to the business and site.

02Unassigned, offered, accepted, handed over and closed are different events.

03Notifications should follow those states so the system can stop contacting people once a responsible person has accepted the work.

04Plan for a missed handover before it happens.

05The system should escalate to the agreed cover role, not repeatedly contact an unavailable employee.

06If no cover is available, display the service limitation to the authorised coordinator rather than pretending the dispatch process succeeded.

07Include work actually performed in the record flow.

08The Ombudsman's record guidance distinguishes required records and recommends keeping hours for all employees as best practice.[

092] The dispatch design should support the employer's assessed obligations without assuming every notification creates the same payable event.

02These are recommended routing choices, not statutory rules.

03The final settings must reflect agreed service commitments, individual circumstances and applicable employment arrangements.

04Give coordinators a visible override route for exceptional circumstances, with a reason and authorised owner.

05An unrestricted override available to every customer-facing employee will quickly become the ordinary route whenever somebody wants a faster response.

02On Saturday evening, the customer reports a stoppage through the service portal.

03The agreed coordinator receives the request, confirms the service category and contacts the rostered technician through the approved route.

04The technician accepts the job, so reminders to the cover role stop.

05The coordinator records the handover and later ensures the work performed enters the appropriate timesheet process.

06A request to update a non-urgent job description remains in the next working queue.

07Now suppose the customer also messages a different technician directly.

08The company directs future service requests back to the central route and reviews what happened with the relevant people.

09The example does not determine any employee's rights; it illustrates how a coherent process reduces accidental, repeated contact.

02Public leaderboards for fastest replies may create pressure to respond while off duty.

03Measure service performance through agreed coverage and accepted assignments instead of raw responsiveness across the workforce.

04Another failure is deleting deferred messages rather than queueing them.

05Employees need to see the work when they return, with its original time and context.

06The system should make silence outside agreed responsibility compatible with a reliable handover inside working time.

07Start by reviewing one week's notification categories and recipient roles, using appropriate access and privacy controls.

08Identify the broadcasts that could become targeted assignments or deferred tasks.

09Update the workflow and staff instructions together so the technical behaviour and the employment process tell the same story.