Storage operator guides · Unmanned & remote-managed sites

The unmanned storage trend: what it means for independent operators

Sturdy Ai · Updated 25 July 2026 · 7 min read

"Self-storage" used to mean a manned office, or at least someone in one for most of the working day. Increasingly it doesn't. New sites are being built with no office at all — access code, camera, app, done — and existing operators are cutting staffed hours as leases come up for renewal. The physical model is genuinely changing. What doesn't change is that a customer with a booking, a query or a late payment still expects someone, or something, to respond. This guide is about what actually needs replacing when the desk goes — not what a vendor's slide deck says it does.

What "unmanned" actually means

It isn't one thing — it's a spectrum, and most independents sit somewhere along it rather than at either end:

• Fully staffed — someone on site most opening hours, answering the phone and the door.
• Manned hours, unmanned rest — a desk during set hours, self-service (gate code, app) outside them.
• Remote-managed — no one on site most or all of the time; access, CCTV and payments run centrally, often by one manager covering several sites.
• Fully unmanned — access, viewing, booking and payment are all self-service from the first enquiry onward.

The direction of travel across the sector is the same regardless of where a given site starts: fewer staffed hours, more of the estate covered remotely, one person doing what used to take several separate desks.

Why operators are moving this way

Two forces, not one. First, cost: a person on site all day is a much bigger line item per unit at a small independent site — say a few dozen units — than at one ten times that size, and margins at the smaller end of the market are already tight. Second, the technology genuinely caught up — access control, remote CCTV and PMS-driven online booking now handle most of what a front desk used to do by hand. Going unmanned isn't really a shortcut any more; for a large slice of this market it's close to the only way the economics still work.

What actually breaks when the desk disappears

Three jobs don't go away just because there's no longer someone behind a counter to do them.

The phone still rings

Whether or not anyone's on site, someone somewhere is still picking up a phone to ask about a unit. In our experience, callers tend to rent from whichever facility answers first — not necessarily the cheapest, or the nearest, just the one that picked up. An unmanned site with an unanswered line doesn't lose that enquiry to "no decision" — it loses it to whoever's next on the caller's list.

Arrears don't chase themselves

A friendly, well-timed nudge on a late payment recovers business that a stiff automated email doesn't. That's a genuinely human skill when there's a person at the desk to apply it — it doesn't stop being needed just because there isn't one; it has to be built into whatever replaces them, not quietly dropped.

Something eventually goes wrong

A gate that won't open, a customer locked out, a genuine emergency on site. Unmanned doesn't mean unreachable — it means the reachable person is somewhere else, which makes how fast they can actually be reached matter more, not less.

Technology should fill the desk, not replace your booking system

The instinct with any of this is to reach for a wholesale platform swap. Resist it. The steadier pattern — the one already used by operators running lean — is to leave whatever runs bookings, payments, Direct Debits and access control exactly as it is, and add a communication layer on top of it rather than under it or instead of it. The PMS keeps doing the boring, critical jobs it's already good at; the new layer just answers, follows up and chases on its behalf, around the clock, whether or not anyone's physically on site that hour.

In practice that layer needs to cover roughly the same ground the desk used to:

• Answering enquiries the moment they arrive — phone, SMS, web chat — not "we'll get back to you."
• Following up instantly on any new lead, since whoever replies first usually wins it.
• Chasing overdue accounts on a fixed cadence, in a way that still sounds like a person, not a template.
• Producing a plain-English daily summary — occupancy, revenue, who's overdue — so a manager covering several sites isn't logging into five different screens to find out what's happening at each one.

Integrations vary by vendor — Sturdy Ai's own build connects to Stora today, others on request — but the shape of that layer should look roughly like this whoever builds it.

Where "AI answers the phone" breaks down — and the honest questions to ask

Every vendor pitching this will tell you it works. The useful question isn't whether it answers calls — most modern systems can — it's what happens the moment it hits the edge of what it knows. Ask three things of anyone selling you this, and expect a straight answer to each:

1. Where does an unknown question actually go? Not "the AI figures it out" — a real, named escalation path to a real person, with a defined way back to the customer.
2. Does the answer get remembered, or just used once? A system that has to ask an operator the same question every week isn't learning — it's just routing.
3. What's allowed to change on its own, and what isn't? A fact updating itself — a price, a unit size, an opening hour — is one thing. A workflow changing itself — how arrears get chased, what triggers an escalation — is another, and should stay human-approved rather than self-editing. Any vendor should be able to tell you, without hedging, which side of that line each part of their system sits on.

A checklist before you go — or stay — unmanned

1. Coverage — is every enquiry channel (phone, web form, walk-up) actually covered every hour the site is technically open for business, including evenings and weekends?
2. Escalation — if the front line, human or automated, hits something it can't resolve, is there a named person and a maximum response time, or does it just sit unanswered?
3. Arrears — is chasing overdue accounts on a fixed cadence, or does it only happen when someone remembers to look at the list?
4. Incidents — who's reachable, and how fast, if the gate fails or a customer's genuinely stuck on site outside hours?
5. Self-service — can a customer actually complete a booking, payment or access issue end to end without a human — or does it quietly still need someone anyway?