By Sajad, Co-founder at cellbot — 25 years in the tech repair industry
Published: 30 January 2026 · Editorially reviewed: 26 August 2026
Evidence basis: UK repair operating method; current Consumer Rights Act and ICO guidance; no response-time, open-rate, review-rate or channel-cost benchmark is presented as an industry fact.
Reliable repair-shop communication tells the right customer what changed, what has not changed, what decision is needed and when the next update will arrive. It begins with a recorded job event, uses an approved channel and template, and returns the delivery and customer response to the same repair record.
Do not send messages merely because a timer elapsed. A false “your repair is progressing” update damages trust. Send an accurate event, an explicit no-change exception or a promised review time.
Start with one communication record
Keep these fields together:
- customer and authorised contact;
- exact device and repair reference;
- event that justified the message;
- current status and prior status;
- message purpose: service, decision, reminder, complaint or marketing;
- approved channel and accessibility need;
- template and version;
- factual variables inserted;
- sender or automation identity;
- sent, delivered, failed and response timestamps; and
- next action, owner and promised update time.
Download the repair-shop communication event register. It includes the job event, recipient authority, purpose, lawful/consent check, template version, delivery state, customer response and next action. Blank message fields are deliberate: customer data does not belong in a shared template.
Map the repair events before writing templates
Use a compact event map:
| Event | Customer needs to know | Required shop action |
| Booking accepted | exact service request, location/channel, preparation and cancellation route | create repair reference and confirm the agreed intake |
| Device received | identity, recorded condition, custody start and diagnostic scope | preserve intake evidence and authorisation |
| Quote ready | fault found, proposed work, part description, total price, timing and choice | wait for explicit approval or decline |
| Scope changed | new evidence, changed price/time and what remains untouched | stop affected work until authorised |
| Part or diagnosis delay | verified cause, effect and next review time | assign owner and update the promise only with evidence |
| Repair ready | work completed, final-test result, balance, collection/delivery route | preserve readiness and payment state |
| Repair cannot proceed | reason, diagnostic work, customer options and charges already agreed | record decline, return or safe disposal path |
| Complaint or return | issue reported, acknowledgement, evidence needed and next review | open a linked case without overwriting the original repair |
The repair-shop operations playbook owns the status and custody model. This page owns the messages produced by those events.
Separate service messages from marketing
A message required to perform or administer a repair is not automatically permission to send promotions. Keep purpose explicit.
The ICO's electronic-mail marketing guidance explains the PECR rules for email and text marketing, including consent and the limited “soft opt-in” conditions. Check the current guidance and obtain advice for the campaign.
Practical controls:
- do not add an offer to a service update merely because the shop has the phone number;
- preserve when, how and for what the customer chose marketing;
- make the sender identifiable and provide the required opt-out route;
- apply suppression before campaign selection, not after send;
- keep operational opt-outs distinct from an inability to deliver necessary repair information; and
- never turn a review request into a condition of receiving a receipt, warranty or remedy.
The email-marketing guide owns campaigns. Keep job communication focused on the repair unless the marketing control has independently passed.
Write messages that expose the decision
Use five parts:
- Identity: shop name and repair reference.
- Verified event: what changed or what remains unresolved.
- Customer impact: price, timing, function or collection effect.
- Required choice: approve, decline, provide information, collect or wait.
- Next update: owner or time, plus a contact route.
Quote ready
Cellbot Repairs — job R-1042. We found recorded fault]. Proposed work: exact scope and part description]. Total price: approved consumer price]. Estimated ready time after approval: time or stated dependency]. Reply APPROVE or DECLINE, or ask a question at contact route]. We will not start the changed work until you approve it.
Verified delay
Cellbot Repairs — job R-1042. The repair is waiting for verified reason]. Your previous ready estimate no longer applies. We will review this at date/time] and update you even if there is no change. If this timing no longer works, contact route] to discuss the available options.
Ready for collection
Cellbot Repairs — job R-1042 is ready. Completed work: scope]. Final test: recorded result or stated limitation]. Balance: amount]. Collection: location and hours]. Bring required proof if applicable]. Reply if another authorised person will collect.
These are structures, not legal terms. The exact price, remedy, storage, collection and identity wording must agree with the approved job and current shop policy.
Make quote and timing changes explicit
Information said or written to a consumer can become binding where the customer relies on it. Consumer Rights Act 2015, section 50 addresses information about the trader or service, while section 52 covers reasonable time where no time is fixed.
Do not quietly edit the original promise. Record:
- original scope, price and expected time;
- new evidence;
- proposed change;
- customer response and timestamp;
- work paused or allowed; and
- revised promise and owner.
If the customer does not respond, follow the agreed escalation path. Silence is not approval for additional chargeable work.
Use channel rules, not channel folklore
Choose a channel based on the customer's recorded choice, message sensitivity, urgency, accessibility and ability to preserve the exchange.
| Channel | Good fit | Control |
| SMS | brief event and required action | avoid sensitive detail; provide a trusted contact route |
| quote, terms, itemised detail and documents | verify address; preserve attachments and version | |
| Phone | complex diagnosis, distress or negotiation | write an immediate factual call note and confirm material decisions |
| Portal | status, documents, approvals and history | authenticate appropriately; do not expose another customer's job |
| In person | intake, collection and accessibility needs | record the decision and provide a durable receipt or summary |
Do not assume SMS is read, email is delivered or a phone message reached an authorised person. Delivery state is evidence, not certainty of understanding.
Design the exception before the happy path
For every automated message define:
- missing mobile or email;
- failed delivery;
- duplicate event;
- status corrected after send;
- disputed recipient;
- vulnerable or distressed customer;
- translation or accessibility need;
- data that must not appear in a notification preview;
- out-of-hours customer response; and
- automation unavailable.
The fallback should create an owned task. It should not silently drop the message or retry indefinitely.
Handle complaints without rewriting history
Create a linked complaint or return record. Keep the original intake, quote, approvals, status events, tests, collection and messages unchanged. Add later evidence as later evidence.
An acknowledgement should state the issue recorded, what the shop will review, who owns it and when the next update will arrive. Do not admit a technical cause before inspection, blame the customer, or make a remedy conditional on withdrawing a review.
Use the customer-disputes guide for the full evidence and remedy workflow, and the warranty policy guide for commercial-warranty boundaries.
Protect customer data in messages
Apply the ICO's data-protection principles: use data for a stated purpose, minimise what appears in a message, keep it accurate, retain it only as justified and secure it appropriately.
Avoid sending passcodes, intimate fault descriptions, full identifiers or other sensitive details in message previews. Use the repair reference and a secure route for anything that requires stronger identity checking. The GDPR guide for repair shops owns the wider data-control method.
Measure reliability rather than vanity
Track:
- eligible events with a message generated;
- messages blocked by missing authority, channel or template data;
- delivery failure by channel and reason;
- customer decisions received and linked to the right job;
- promises that passed without an update;
- duplicate or factually corrected messages;
- status enquiries by underlying event; and
- complaints in which the communication record was incomplete.
Do not import an “industry open rate” or review-request benchmark. Establish a clean shop baseline using fixed definitions, then change one part of the system and measure a comparable future cohort using the repair-shop KPI method.
How Cellbot fits
Cellbot can connect customer, device, job, quote and message history and support workflow-based communication. The shop remains responsible for recipient authority, purpose, consent, factual status, template approval and exception handling. Confirm the current channel and plan scope on the features page.
Do not claim that every message is automated or delivered. Test one journey from event to delivery failure, customer response and audit record before relying on it.
Frequently asked questions
How often should a repair shop update a customer?
At each material change and at every promised review point. If nothing changed by the promised time, say so, explain the current verified blocker and set the next review. Do not invent progress to satisfy a cadence.
Should quotes be sent by text or email?
Use the channel that preserves the complete scope, price, timing, terms and customer response. A brief text can link to or request confirmation of a durable quote; the full evidence must remain attached to the repair.
Can repair updates include promotions?
Not by default. Test the service purpose and the independent marketing permission under current PECR/UK GDPR guidance. Keep suppression and evidence of choice.
What should happen when a message fails?
Create an owned exception using another approved route, check the contact data and preserve the failed attempt. Do not mark the customer informed merely because a send was attempted.
Should staff use personal phones?
Avoid unmanaged personal channels where the business cannot control access, retention, customer identity or the record. If an emergency process permits one, define and test how the communication is returned to the official repair record.
Bottom line
Good repair communication is a controlled consequence of a real job event. Preserve the customer, device, purpose, message, delivery, decision and next action in one chain. When the chain breaks, create an owned exception instead of sending a plausible but untrue update.
Continue with the operations playbook or SOP design guide to control the events beneath the messages.
What changed on 26 August 2026
The former channel percentages, SMS prices, response-time anecdotes, review-rate benchmarks and blanket timing rules were removed. The replacement adds a job-event map, service-versus-marketing boundary, message anatomy, quote-change record, channel and exception controls, privacy rules, reliable metrics, templates and a downloadable event register.
Sources and method
- Consumer Rights Act 2015, section 50
- Consumer Rights Act 2015, section 52
- ICO: Electronic-mail marketing
- ICO: Data-protection principles
The event map, templates and register are original Cellbot editorial operating methods, not industry benchmarks. Obtain qualified UK legal and data-protection review before publication.
