No, and I would be sceptical of anyone selling it that way.
Compensation is triggered by operational failure. A missed appointment, a late start, an unrepaired fault. None of those are caused by how you communicate, and none of them are fixed by a better conversation.
What automation changes is what that failure costs you beyond the credit.
The rates, so the arithmetic is concrete
From 1 April 2026: £32.31 for a missed engineer appointment, £6.46 for each calendar day a new service starts late, £10.34 for each calendar day service stays broken after two full working days. Bill credit within 30 days, rates rising each April with CPI.
For a growing altnet, a hundred delayed installs running five days each plus fifty missed appointments is roughly five thousand pounds in a month.
That is the visible cost, and it is the smaller one.
Where the real cost sits
A delayed install means a customer who has paid and has no service. They contact you, repeatedly. Each contact costs support time. If they cannot get a straight answer about the new date, frustration compounds into a complaint, or a switch, or both.
Their acquisition cost has not been recovered. The £6.46 a day is close to incidental next to losing them in month four.
So the useful goal is not reducing payouts. It is stopping one operational failure becoming three commercial ones.
What automation genuinely does
Absorbs the chase. The dominant contact during a delayed install is "where is my order". An agent reading real provisioning data answers instantly, at any hour, with the actual date. In our own deployment this was the surprise finding: we expected billing to be the win and the install-status chase turned out to be what was consuming the team.
Flags at-risk orders earlier. A slipped date is knowable before the customer notices. A triggered message with the new date and what happens next changes the emotional shape of the whole thing, even though the failure still happened.
Explains the credit. Customers who discover they were owed money and never told react badly. An agent that can say what was credited and why turns a grievance into evidence you deal straight.
The limit, stated plainly
It does not stop your engineer being late.
If field operations are under-resourced or provisioning is genuinely slow, no conversational layer fixes that. It handles the consequences better and surfaces the pattern sooner. The cause is untouched.
What to measure instead of total payouts
Total compensation moves for too many reasons to be a clean signal.
Watch contacts per delayed order. If a slipped install used to generate four inbound touches and now generates one, that is measurable within weeks.
Then watch ninety-day churn for customers whose install slipped against those whose did not. That gap is the number that actually matters, and most operators have never calculated it.
The longer version, with the full arithmetic, is in Ofcom automatic compensation: what each failure costs.
