The office phone rings because the customer does not know what is happening.
Has the booking gone through? Is the skip still coming today? Did the driver collect it? A useful notification answers one of those questions before the customer needs to ask.
Useful is the important word. Automated noise does not improve service. It gives customers more messages to ignore and the office more promises to explain.
Send messages around moments that matter
Start with the points where uncertainty creates calls or failed jobs.
- Booking confirmation
- Reminder before delivery or collection
- A meaningful change to the agreed date or window
- Driver unable to complete the job
- Collection or exchange confirmation
- Action required from the customer
Do not send a message simply because the software has a status available. Ask whether the information helps the customer prepare, decide or stop worrying.
Make the booking confirmation do some work
A confirmation should repeat the facts most likely to cause trouble: delivery address, skip size, date, placement assumption, hire period and waste restrictions. Give the customer a clear way to report a mistake.
This is not the place for a wall of legal text. Link to full terms, but put the operational essentials where people will see them.
Be careful with arrival times
A message saying “your skip will arrive at 10.03am” looks impressive until a tipping delay makes it wrong. If the operation cannot support live accurate estimates, use a sensible window and update customers when something material changes.
False precision creates more chasing, not less. Say what you know and avoid pretending the road follows the plan.
Tell customers when they need to act
Reminders are most valuable when they prevent a failed movement. Ask the customer to clear access, open a gate, move a vehicle or confirm that the skip is ready for collection.
Make the requested action obvious. A general “your collection is tomorrow” message is weaker than “please make sure the skip is accessible from 7am”.
The best notification changes what happens next.
Handle failed jobs honestly
If the driver cannot complete a delivery or collection, silence is rarely the right answer. The customer should know that the job has not happened and what the next step is.
Automation can acknowledge the failure, but unusual cases often need a person. Do not send a blunt charge notification before the office has checked the driver’s notes and evidence.
Keep the message tied to the live job
Notifications become risky when they run from a separate calendar. The date changes in operations, but the old reminder still sends. The customer receives yesterday’s promise from today’s system.
Trigger messages from the current booking status and record what was sent. Staff should be able to see the communication when the customer rings.
Give customers a sensible reply route
A message that says “do not reply” may reduce inbox work and increase phone calls. Decide which messages need a response route and make ownership clear inside the office.
For routine changes, a short self-service action may help. For access, waste or complaint issues, give customers a route to a person who can make a decision.
Measure fewer problems, not more sends
Choose the channel to match the message
SMS is hard to miss and useful for short operational updates. Email can carry fuller booking details and terms. A phone call is still better when the situation needs a decision or apology. Do not force every event through the same channel because it was easiest to configure.
Keep service messages separate from marketing. A customer giving a mobile number for delivery updates has not necessarily asked for promotional texts. Your consent, privacy and opt-out process should reflect the actual purpose of each communication.
Write like a person who knows the booking
Include the information needed to recognise and act on the message: the delivery postcode or order reference, the movement, the relevant date and the next step. Avoid internal status labels that mean nothing outside the office.
“Job moved to exception state” is system language. “We could not collect your skip because access was blocked; please call us to rearrange” is useful customer language. Keep it direct and avoid pretending an automated message is a personal conversation.
- Calls asking for delivery or collection status
- Failed jobs caused by blocked access
- Customers correcting booking details before dispatch
- Complaints about late or confusing messages
- Manual messages sent by office staff
Customer notifications are part of Locovo’s planned connected workflow rather than a feature we present as fully live today. The right foundation is accurate booking and job status data inside the Locovo Dashboard; messages should follow that truth, not race ahead of it.
