Storage operator guides · Arrears & collections

Recovering overdue accounts: a practical arrears playbook for UK storage operators

Sturdy Ai · Updated 25 July 2026 · 7 min read

Every self-storage site carries some arrears — that's normal, not a crisis. What turns ordinary arrears into bad debt is an inconsistent chase: calls made "whenever someone gets a minute", no record of what was actually said, and no clear point at which a case moves from a friendly reminder to something more formal. Fix those three things and most arrears resolve themselves long before they become a problem.

Build a ladder, not a habit

Ad hoc chasing — a call here, a text there, whenever the front desk has a spare five minutes — feels like it's doing something, but it produces no consistent record and no fair, repeatable standard for every debtor. A written escalation ladder fixes that: a fixed sequence of attempts, on a fixed schedule, through named channels, with every attempt logged. It's fairer to the customer, easier to hand over between staff, and — if a case ever needs to go further — it's the paper trail that shows the account was chased properly and consistently before anything formal happened.

A working escalation cadence

The exact days matter less than having fixed ones. This is a reasonable default cadence to adapt to your own site — tighten it for high-value units, relax it for long-standing customers with a clean payment history:

1. Day 7 overdue — first voice call. Keep it short and neutral: which unit, how much is outstanding, how many days overdue, and how to pay or discuss options. No answer, leave that same information as a voicemail.
2. Day 10 — second voice attempt. If day 7 went unanswered, try a different time of day rather than repeating the same slot.
3. Day 14 — SMS follow-up. A short text repeating the unit reference, amount, and a callback number or payment link. Text reaches people who screen calls from unknown numbers.
4. Day 21 — third call plus a letter. Voice again, backed by a written letter — useful both as a further prompt and as part of the record if the case escalates later.
5. Day 28 — escalate flag, human review. Voice attempts are exhausted. The case gets flagged for a person to review before anything more formal happens — not an automatic next step.
6. Day 35+ — formal notice, solicitor-reviewed only. Any statutory notice at this stage is manual and reviewed by a solicitor before it goes out — never issued automatically. More on this below.

Keep every call factual and neutral

The most common way a collections call goes wrong is tone, not content. Stick to the facts every time: the unit reference, the amount outstanding, how many days overdue, and how to pay or get in touch — then leave a callback number or payment link. No threatening language, no mention of legal action or auction on the call itself; that's a conversation for the human escalation path, not the routine chase.

What to log after every attempt

A ladder is only as good as the record behind it. After every attempt, capture: the debtor, the unit, the amount overdue, which attempt number this was, the outcome (answered, voicemail, no answer), any payment promise made and its date, and whether the case has been flagged to escalate. That record is what turns "we chased them" into something you can actually stand behind later.

What not to do on a collections call

• Don't mention legal action or auction on a routine call. Leave that entirely to the human escalation path once a case has actually reached that stage.
• Don't agree a payment plan you can't honour. If a debtor offers a date or an instalment, only accept terms the business can actually track and enforce.
• Respect reasonable calling hours. Good practice is not to call before 8am or after 8pm — the standard we treat as the default for any outbound calling.

When it tips into formal enforcement

Most storage contracts give the operator a contractual right over goods left in an unpaid unit — commonly a lien — and a route to eventually sell those goods to recover what's owed if the account stays unresolved. In England and Wales, that route runs through the Torts (Interference with Goods) Act 1977, which sets out the framework operators rely on to exercise a sale of goods against unpaid storage fees, including formal notice requirements that have to be followed precisely before any sale or auction.

That's a genuinely different category of action from a chasing call or a text, and it's the point where the ladder above should stop being automatic altogether.

Where automation helps — and where it has to stop

The early rungs of the ladder are exactly the kind of work automation is good at: calling on schedule, sending the SMS follow-up, and logging every outcome consistently, every time, without a busy front desk letting a day 10 call slip to day 14. Outbound collections is regulated territory, though, so we treat it differently to our inbound agent: it is a separate module, in development, and it only ever rolls out with an operator's own templates and explicit sign-off — talk to us if you want to shape it early. The knowledge loop it inherits is already proven on the inbound side: when a caller asks something the agent doesn't have an answer for, it texts the operator, gets the answer once, and that fact becomes something the agent knows for next time. Whether a case actually escalates toward a formal notice stays a human decision, every time — that gate never moves to automatic.