Rangefront Waste

Septic service reminders that customers can act on

A reminder should tell the customer what is happening and what they need to do. Decide whether you're asking them to book or reminding them about a visit already arranged.

Property owner reading a service reminder on her phone at a rural front gate

A message saying your septic service is due can mean two different things. The office might want the customer to call and book, while the customer assumes a truck is already coming. That misunderstanding doesn’t become obvious until somebody rings to ask where the driver is.

Give each message one job, and write the wording around the booking state that triggered it.

Separate booking prompts from visit reminders

A due-service prompt asks the customer to arrange work. It needs the property, the service concerned and a clear way to respond. Don’t include an appointment date unless the office has actually offered or confirmed one.

A booking confirmation records an agreement already made. It should repeat the date, arrival window and any access arrangement. A short pre-visit reminder then checks that those arrangements still work.

Keep the distinction in your templates and in the office process. If the business sends both a maintenance prompt and an appointment reminder, label them separately where staff configure messages. Otherwise somebody eventually switches on the wrong one.

Your recurring schedule should establish when work is due. Messaging shouldn’t quietly create a different cycle because a template happens to run on a convenient date.

Include the details that prevent a failed visit

Name the property, particularly when one account covers several sites. Use a recognisable business name and a callback or reply method the office actually monitors. A message sent from an unfamiliar number with no context is easy to ignore.

Say what the customer needs to do about access. If someone must open a gate or meet the crew, make that request explicit. Keep unusual site instructions on the job as well; the customer’s text isn’t a substitute for the technician’s briefing.

Use an arrival window that dispatch can honour. An automated message shouldn’t promise 8:00am when the schedule only says morning. Check the preview with a real-looking sample booking to see whether the date, time and address placeholders read naturally.

Decide where replies go

Before asking customers to reply YES, test a reply from an ordinary phone. Check which inbox receives it, whether staff can identify the booking and what counts as confirmation. Don’t assume a sender name or provider account supports inbound messages.

Give cancellations and access problems a different path from simple confirmations. A customer who writes gate broken needs someone to act, even if the message contains the word yes elsewhere. Assign someone to check the inbox throughout the day, with cover during leave.

An unread reply should remain visible until it’s dealt with. Opening it is different from rescheduling the visit or telling the driver. Record the resulting action against the booking so the next office worker can see what changed.

Review exceptions before dispatch

Check failed deliveries, missing mobile numbers and visits still waiting for access confirmation. A message marked sent doesn’t prove the customer has read it. Decide which jobs need a follow-up call based on the access arrangement and the consequence of a failed visit.

If the appointment changes, check what messages have already gone out and how the customer will receive the correction. Some systems send each event once per job; moving the booking may need an explicit update rather than another identical reminder.

Respect the customer’s channel preferences and opt-outs. Keep service messages relevant to the booked or due work instead of inserting unrelated promotion. Staff should be able to recognise the purpose of the message without reading a marketing paragraph first.

Test with a small group

Start with a few upcoming appointments and follow them through. Check the recipient, timing, reply and what happens if delivery fails. Review the wording with the person who answers the office phone, because they’re the one who hears which part confused customers.

Once the process works, turn on the wider rule. Keep a short change record when timing or templates change, so an unexpected message can be traced back to a deliberate setting.

Messages in Rangefront Waste

Rangefront Waste uses templates and event rules for booking confirmations, pre-visit reminders and other messages. Rules must be enabled and configured. Preview templates before switching them on and check the delivery log for failed messages.

Two-way replies depend on the SMS provider and reply configuration. With supported inbound messaging, YES or Y can confirm a recent booking or reminder, while STOP opts the customer out. Test that path on the service your business actually uses.

The messages documentation lists the supported behaviour. Combine it with a consistent phone booking process so written messages repeat what the office has already agreed.

Related guides

All guides

Try it with your own jobs.

Fifteen days free with your customers, your councils and your crew. Add a card to start, and cancel before day 16 if it's not for you.

A vacuum truck pumping out a tank at a rural property