Guidance, not advice. General information on running customer comms as a system. As at May 2026.
Running customer communication well is about systems, not heroics — clear channels, clear expectations, and a simple way to track and follow up so you're not effectively on call 24/7. Build the framework first; plug specific apps in later.
Channels — in layers, not everywhere
- Primary channel (one — usually email or a messaging app) for the official stuff: quotes, bookings, changes, important updates. It's searchable and easy to template.
- Secondary channel (phone, SMS) for quick questions and "running late" — with the rule that anything important gets summarised back via the primary channel ("I'll confirm that in writing so we both have it").
- Marketing channel (optional) kept separate from job threads, so nothing critical gets buried in a newsletter.
Response-time norms (without being on call)
Publish what you'll do and then meet it. A workable shape: enquiries answered same day or within a few working hours in business hours, with a "next working day" for evenings and weekends; an auto-response that sets the window and gives an emergency number; same-day replies on active jobs, with a holding message ("got it, I'll confirm by tomorrow") when you need time. Define what actually counts as an emergency (a live leak, no power, an unsafe structure) and put a price on out-of-hours call-outs — which naturally filters the non-urgent. The norm is what you publish and consistently do, not what a customer demands at 9pm.
Boundaries and out-of-hours
Publish your hours everywhere (website, email footer, messaging profile, voicemail, quote PDFs), use auto-replies and an away message, and set your own rule of no non-emergency replies after a certain time (schedule-send anything you write in the evening). If you do reply late, add a line that normal hours are X-Y so you don't train people to expect 11pm answers. And use pricing as a boundary — an out-of-hours call-out fee.
A follow-up rhythm for quotes and bookings
Treat it as a simple pipeline: capture the enquiry (and send an immediate "received" with the next step); send the quote with a validity period and a note that you'll send one reminder; follow up once at 3-5 days and once just before expiry, then stop unless they re-engage; confirm a booking in writing (date, scope, price basis, cancellation terms); and send a short post-job message ("completed on [date], any issues let us know by [date]") with an optional review request. That gives you predictable touchpoints without the mental load (see Managing Customer Expectations).
A minimal CRM and templates
You don't need fancy software — you need a record per customer (name, address, contacts and preferred channel, job type, stage, key dates, and consent flags for marketing and privacy) in a spreadsheet, a basic CRM or your job-management software. Then a handful of reusable templates (enquiry acknowledgement, quote cover, booking confirmation, reminder, post-job check-in, out-of-hours auto-reply) with placeholders. Log the gist of calls and messages against the record — a brief note, not a transcript — so you have a defensible history if a job ever turns sour.
The privacy hook
Collect only what you need to do the job, tell customers briefly what you do with it, don't send sensitive data (like card details) over insecure channels, and keep personal and business messaging separate. Every channel and template should point to your privacy explanation rather than repeating it — see Privacy Act & the APPs for Builders.
Common mistakes
- Letting every channel be a primary channel, so important things get lost in chat.
- No published hours or auto-replies, training customers to expect instant replies.
- Quoting and never following up (or chasing forever) instead of a fixed rhythm.
- No record of what was said, so a dispute becomes your word against theirs.
Know someone who needs this?
Keep reading
Was this guide useful?
Didn't find what you were looking for?
Spotted something wrong or out of date? Email us at hello@kilnguides.co.uk.
In crisis? Lifeline 13 11 14 ·