Servicing, MOTs, repairs, tyres and bodywork for private motorists and local business fleets, from four garages in Telford, Shrewsbury, Newport and Stafford. 74 staff.
Verdict: The plan watches 9 channels, each with an owner, a backup and a hand-over, and has rules for 7 of the 7 kinds of mention, each that replies in public with an approved template. The staff social media policy covers 9 of 9 required topics and 73 of 74 staff have signed it. 8 vulnerabilities are registered (3 rated high, the owner's assumption); 5 actions are open. In the baseline log (106 mentions), 19 of 102 mentions needing a reply were answered within their own target (19%), 18% of complaints within 24 hours, and 40 of 82 reviews needing a reply were left unanswered. How the value is shown (risk avoided, not a forecast): the largest event, “A key fleet account sees an unanswered complaint and moves its work”, would cost £22,944 from the owner's own figures. With the owner's assumed likelihoods, the 5 events cost £7,946 a year on average; if the plan works as assumed it cuts that by £3,260 (£1,630 if half as well), against £5,932 a year to keep up with the build spread over 3 years. If the plan works half as well, the reduction doesn't cover the yearly cost. Even as assumed, the reduction doesn't cover the yearly cost. Log the after period the same way: an early read on 28 Jan 2027 (direction only) and the re-measure on 30 Apr 2027.
| Channel | Owner, backup and hand-over | Alert | Checked every | Baseline mentions | Admin access |
|---|---|---|---|---|---|
| Map listing: Telford Map listing | Responder: Telford backup: Reputation lead; hands over to Reputation lead within 4 h | Alert set up | 24 h | 22 | Ours: two people |
| Map listing: Shrewsbury Map listing | Responder: Shrewsbury backup: Reputation lead; hands over to Reputation lead within 4 h | Alert set up | 24 h | 17 | Ours: two people |
| Map listing: Newport Map listing | Responder: Newport backup: Reputation lead; hands over to Reputation lead within 4 h | Alert set up | 24 h | 15 | Ours: two people |
| Map listing: Stafford Map listing | Responder: Stafford backup: Reputation lead; hands over to Reputation lead within 4 h | Alert set up | 24 h | 21 | Ours: two people |
| Review site A Review site | Reputation lead backup: Social media and inbox; hands over to Social media and inbox within 4 h | Alert set up | 24 h | 11 | Ours: two people |
| Social network A Social network | Social media and inbox backup: Reputation lead; hands over to Reputation lead within 4 h | Alert set up | 12 h | 10 | Ours: two people |
| Social network B Social network | Social media and inbox backup: Reputation lead; hands over to Reputation lead within 4 h | Alert set up | 24 h | 5 | Ours: two people |
| Community group: Telford Forum or community group | Social media and inbox backup: Responder: Telford; hands over to Responder: Telford within 8 h | Checked by hand | 48 h | 5 | Not ours to manage |
| News alerts on our name News or trade media | Reputation lead backup: Managing director; hands over to Managing director within 2 h | Alert set up | 24 h | 0 | Not ours to manage |
Platforms are named by kind. The community group is checked every 48 hours, above the 24-hour limit (noted): it isn't the business's to manage, and there is no alert.
| Kind | Who replies | Target | In public? | Take it offline when | Escalate to | Template |
|---|---|---|---|---|---|---|
| Praise | Social media and inbox | 72 h | Yes | Never needed | Reputation lead | T1 |
| Question | Social media and inbox | 8 h | Yes | When it needs the customer's registration, booking or account details | Reputation lead | T7 |
| Complaint | Reputation lead | 24 h | Yes | Always after the first public reply: invite them to call or message the reputation lead by name | Managing director | T2 |
| Fake or suspect review | Reputation lead | 48 h | Yes | If the person gets in touch and turns out to be a customer: treat it as a complaint | Managing director report to the platform | T5 |
| Abuse | Reputation lead | 24 h | No | Never reply in public; keep a copy | People lead report to the platform | T6 |
| Legal threat | Managing director | 24 h | Only to acknowledge | Straight away: acknowledge in public only to say we have their message and will reply directly | Legal adviser legal advice first | T8 |
| Media enquiry | Reputation lead | 4 h | Only to acknowledge | Always: take the journalist's name, deadline and questions, and call back | Managing director | T9 |
Targets run in elapsed hours, Monday to Saturday; anything posted on Sunday, or on Saturday after 18:00, starts the clock at 8:00 on Monday. Fake reviews are reported through each platform's own process with the evidence; a legal threat is acknowledged only, and anything more is approved by the legal adviser. Abuse gets no public reply: the member of staff named is told, supported and kept safe. A disputed MOT result is pointed to the DVSA appeal route. The rules rest on the DMCC Act 2024 and the CMA's fake reviews guidance (CMA208), the Defamation Act 2013, UK GDPR and the Employment Rights Act 2025, checked on 16 October 2026; not legal advice.
T3 · Complaint: damage to a customer's vehicle while with us, or a fleet account's complaint (approved by the managing director, 9 October 2026; 42 words)
We're sorry to read this, [first name]. We take any report of damage to a vehicle in our care seriously and want to look into it straight away. Please call me, Joanne, on [number] so I can arrange to see the vehicle.
Then: Call the same day and arrange an inspection. Tell the broker before agreeing anything: the policy says not to admit liability or settle without the insurer's agreement. Agree the outcome in writing. For a fleet account, the managing director calls the transport manager.
T5 · Fake or suspect review: a review we can't match to any visit or booking (approved by the managing director, 9 October 2026; 33 words)
We can't find a record of a visit that matches this review, and we'd like to look into it. If you've been to one of our garages, please call me, Joanne, on [number].
Then: Report it through the platform's own process with the evidence (no booking or job card at any garage for that name and date). Record the date reported and the outcome.
| # | Issue | Rating | Event cost | Action, owner and prepared reply | Status |
|---|---|---|---|---|---|
| 1 | Fleet Account B's van damaged in the Shrewsbury yard; the claim unpaid since July Unresolved complaint · public: no | High | £22,944 E3 | Settle the repair cost and call the transport manager Managing director, by 23 Oct; reply T3 | Open |
| 2 | Repeat repairs at Stafford: the same fault back within 30 days Service failure pattern · public: partly | High | £8,114 E2 | A second technician signs off every diagnostic job at Stafford; review comebacks weekly Managing director, by 27 Nov; reply T2 | Open |
| 3 | Bills above the estimate without the customer's recorded agreement Pricing complaint · public: partly | High | £8,114 E2 | No extra work above the estimate without agreement recorded on the job card (time, who agreed, how) Reputation lead, by 13 Nov; reply T2 | Open |
| 4 | A car released with wheel nuts not torqued (a near miss in 2025) Safety issue · public: no | Medium | £20,566 E1 | Torque check signed on the job card for every wheel removed, and a re-torque reminder card for the customer Managing director, by 30 Sep; reply T3 | Done |
| 5 | A technician replied angrily to a 1-star review from his personal account Staff conduct online · public: yes | Medium | £20,566 E1 | Staff social media policy briefed and signed at every site People lead, by 9 Oct; reply T4 | Done |
| 6 | Three 1-star reviews at Newport in June from names with no booking or job record Fake or suspect reviews · public: partly | Medium | £8,114 E2 | Report each through the platform's own process with the evidence; record the outcome Reputation lead, by 30 Oct; reply T5 | Open |
| 7 | A technician who left in August posts in a local community group that the business cuts corners Unhappy ex-staff · public: partly | Medium | £2,672 E4 | Separate any genuine concern from abuse: investigate what he says under the whistleblowing procedure; reply once with T11; the solicitor's view on anything abusive People lead, by 6 Nov; reply T11 | Open |
| 8 | An invoice emailed to the wrong customer (May 2026) Data incident · public: no | Low | £3,038 E5 | Address autocomplete switched off in the job system's email; check the address before sending Data lead, by 12 Jun; reply T10 | Done |
The ratings are the owner's assumptions, tested in the working session; three are high. The event costs come from the Value Case. The former technician's posts are treated as a possible concern to investigate, not as abuse.
First replies, public or private, to the 104 mentions in the baseline log that needed one (1 April to 30 September 2026).
| Measure | Baseline | Counted from | After |
|---|---|---|---|
| Lead: mentions needing a reply answered within their own target (unanswered counts as missed) | 19 of 102 (19%) | give or take 8 points | at the early read |
| Median hours to a first reply: praise; complaints; questions | 70.7; 30.8; 9.9 | 53 answered of 104 | at the early read |
| Complaints answered within 24 hours | 18% | 7 of 38, give or take 13 points | at the early read |
| Complaints resolved within 14 days | 43% | 16 of 37, give or take 16 points | at the early read |
| Reviews needing a reply left unanswered | 49% | 40 of 82 | at the early read |
Replies count up to 14 days after each period ends, the same both times. The after period is logged the same way on the same channels: an early read on 28 January 2027 (about 19 complaints expected, so direction only) and the re-measure on 30 April 2027 (about 39, give or take 12 points on the complaint share). The lead measure has the most cases and is the one to watch.
Without the plan With the plan (the owner's assumption)
| Event | Cost without the plan | With the plan | Reduction | Likelihood (assumed) | Expected cost a year | Break-even (half as well) |
|---|---|---|---|---|---|---|
| E1 A viral complaint replies only; 27% of the reduction | £20,566 | £11,873 | £8,693 | 1 in 10 owner's judgement | £2,057 | 1 in 1.5 yrs half: 1.4 a year |
| E2 A run of 1-star reviews at one garage replies only; 26% of the reduction | £8,114 | £4,693 | £3,421 | 1 in 4 own history | £2,028 | 1.7 a year half: 3.5 a year |
| E3 A key fleet account sees an unanswered complaint and moves its work replies and fixes; 44% of the reduction | £22,944 | £13,396 | £9,548 | 1 in 7 owner's judgement | £3,442 | 1 in 1.6 yrs half: 1.2 a year |
| E4 A staff or ex-staff post spreads replies only; 2% of the reduction | £2,672 | £2,094 | £578 | 1 in 10 owner's judgement | £267 | 10.3 a year half: 20.5 a year |
| E5 A data incident made public by the customer replies only; 1% of the reduction | £3,038 | £2,133 | £905 | 1 in 20 own history | £152 | 6.6 a year half: 13.1 a year |
Each event uses only the enquiries it touches (the run of 1-star reviews: Stafford's 140 a week, whose fall after spring 2026 is counted from the booking system; the ex-staff post: Telford's), × 64% becoming jobs × £142 gross profit a job × the 50% of lost jobs not refilled from the waiting list (assumed); plus fleet accounts' gross profit from the sales ledger times the share that would leave; direct costs; and staff time at £24 an hour. Only faster and better replies are credited, except for the fleet account, whose effect relies on settling its claim, costed in the build. With the owner's assumed likelihoods (not a forecast), the five events cost £7,946 a year on average; if the plan works as assumed it cuts that by £3,260 a year (£1,630 if half as well). Cost in full: £5,268 to build; £4,176 a year to keep up (174 hours); £5,932 a year with the build spread over 3 years; 1 event relying on costed fixes (£898 one-off, £0 a year), the rest on replies only. On these figures the plan does not pay for itself in money, even as assumed: its case rests on the measures, the share of mentions answered within target and the unanswered reviews; 44% of the expected reduction from A key fleet account sees an unanswered complaint and moves its work; half as well, £1,630 falls short of the yearly cost by £4,302.
The channels, roles, response rules, templates and policy are as agreed with the owner on 16 Oct 2026. The rules they rest on (the DMCC Act 2024 and the CMA's fake reviews guidance, the Defamation Act 2013, UK GDPR, the Employment Rights Act 2025, the Equality Act 2010, Acas, and GOV.UK whistleblowing and MOT guidance) were checked on official sources on 16 October 2026; they are not legal advice. The baseline measures are counted from 106 mentions read back from the channels between 1 Apr and 30 Sep 2026, with replies counted up to 14 days after; with 38 complaints, a share moves by chance by up to its give or take. Enquiries, conversion and gross profit a job are counted from the owner's records and accounts' gross profit from the sales ledger; each event's fall in enquiries and its direct costs are counted, estimated or quoted as its row says, and the share of lost jobs not refilled is assumed. The weeks and accounts each event would cost, how far the plan reduces them, the staff hours, and the vulnerability ratings are the owner's estimates and assumptions, not tested; so is each event's likelihood a year, which is never a fact, so the expected costs hold only with those likelihoods. Half as well, it doesn't cover the yearly cost.
The plan is finished when it is handed over and the staff have signed the policy; the after period is its first test. Review the channels, the rules and the register every quarter.
Fictional, continuing the example. After the plan was handed over, Yarrowby chose the guided route and set up the agent in an AI assistant the business already uses, connected read-only to the channels' alerts and notifications, the business's own inboxes, and the booking system and job cards (to check a suspect review), and able to save drafts and add rows to the Mentions log; its IT confirmed this before it committed. Because the agent reads posts by and about identifiable customers and staff, Yarrowby updated its privacy notice and completed a data protection impact assessment before switching it on (not legal advice). It checks every channel at least every 24 hours, logs each mention the same way as the baseline, drafts replies from the approved templates by the response rules, reminds who replies when 50% of a target has gone, and flags 3 negative mentions on one topic within 30 days as a possible pattern. Nothing left the business, and no decision changed, without one of its own people approving it: every reply was posted by a person from the business's account, and nothing was offered for a review.
| Date | What the agent prepared or found | Who decided, and what happened |
|---|---|---|
| 19 Oct Decision | 1-star review on Map listing: Stafford: a bill above the estimate (complaint; price). Logged on Mentions | Joanne P (reputation lead): Posted from the business's account at 10:15am Monday; she called the customer that day; resolved privately on 21 October |
| 26 Oct Decision | Complaint on Social network A still unanswered at half its 24-hour target (Inputs B39) | Joanne P: Replied at 7:50am on Tuesday from T2, within the target; taken private |
| 2 Nov Decision | Possible fake review: 1-star on Map listing: Newport from a name with no booking, job card or call at any garage | Mark T approved the reply; Joanne P confirmed the kind and submitted the report: Reply posted and report submitted on 3 November; the platform removed the review on 19 November (recorded) |
| 9 Nov Decision | Pattern: 3 negative mentions about price at Stafford in 30 days (Inputs B40), matching V5 (bills above the estimate without recorded agreement) | Joanne P: The agreement field went live on the job system at Stafford on 12 November and at the other garages on 13 November; V5 marked Done |
| 30 Nov Decision | Abuse naming a technician in a comment on Social network B | Claire D (people lead): Spoke to the technician that day and offered support; comment hidden under the platform's rules; no threat, so no police; recorded |
| 4 Jan Note | Weekly note: replies since 16 October against each kind's own target | No decision needed |
| 28 Jan Decision | Early read prepared from the Mentions log, the same way as the baseline | Joanne P: Checked and agreed. Fewer complaints than the 30 on Inputs, so direction only; judged at the re-measure on 30 April 2027 |
The 30-day check-in on 16 November read the first month of the log with Joanne P; after that the agent was Yarrowby's, and Geoff kept no copy and no access. The fake review was reported with evidence and removed by the platform, the price pattern at Stafford reached its owner days before V5's action was due, and abuse of a technician went to the people lead the same day. Confirming the kind of serious mentions and posting the drafted replies took the reputation lead about 20 minutes a day (estimate), within the extra hours on Inputs. The early read on 28 January shows direction only, as the plan says; the re-measure is the one to judge. The months after add nothing to the figures above, and no £ is claimed for them.