46 UK businesses trust us daily to support their websites in case of any emergency or failure. I want to describe what that actually means operationally, because “support” is the most devalued word in this industry, and the gap between support as a line item and support as a promise is where stores lose their worst nights.
Start with the honest baseline: emergencies are not the typical situation. Most of the time things run smoothly, because boring discipline upstream prevents drama downstream. We deploy updates twice a month, each release planned carefully, which removes the most common self-inflicted source of fires. But sometimes, especially where third-party providers are involved, failures happen without warning and without anyone on our side or the client’s side having touched a thing. That is where the policy earns its keep.
MageCloud Emergency Note
The Policy, In Two Rules
RULE ONE
Direct access, day or night
When a failure occurs, clients reach account managers, developers, and me directly. Not a portal, not a queue position, not business hours. People, immediately.
RULE TWO
Size does not buy the front of the line
It does not matter how big a client is or how much they pay. An emergency is an emergency, and every client gets the same response and the same respect.
THE TRADE EVERYONE ACCEPTS
Priorities can switch in a crisis
A developer on your project may be pulled to another client’s emergency, because when yours comes, the same cavalry rides for you.
Paul Ryazanov · MageCloud · deploy twice a month, answer at 3am
Why Direct Access Is the Whole Product
Every agency claims responsiveness. The structural question that separates claims from policies is: what stands between a panicking client and a person who can fix the thing? In most support models the answer is a stack, ticket form, triage tier, SLA clock, business hours, and each layer exists to protect the agency’s calendar from the client’s emergency. Reasonable economics, terrible 2am experience.
We inverted it on purpose. Our clients have my number, their account manager, and access to actual developers, and the response is almost immediate at any hour. That sounds unscalable until you notice what makes it scalable: the twice-monthly planned releases, the monitoring that catches silent failures early, and the patch discipline that keeps stores boring. Proactive hygiene is what makes a direct-access promise affordable. Agencies drowning in support tickets are mostly drowning in their own deferred maintenance, and hosting vendors who make you wait fifteen minutes on hold during their own outage are the cautionary version of the same choice.
The Fairness Rule Nobody Else Will Put in Writing
Rule two is the one that surprises prospects: it does not matter how big you are or how much you pay, the emergency response is identical. The £800-a-month store and the largest account get the same access and the same urgency. Most agencies run the opposite policy quietly, whale accounts get the senior engineer at midnight, small accounts get Monday, and everyone discovers their tier during their worst week.
The fairness rule has a price, and we state it up front rather than hiding it: in an emergency, a developer working on your project might switch priorities to help another client. Every client accepts that trade explicitly, because it is symmetric. The hours someone borrows from your roadmap this month are the hours that arrive for you, unbilled and instant, the night your payment gateway dies. It is insurance pooled across 46 businesses, and it is the same trust-shaped economics as the rest of how we run engagements: no contract forces any of it, which is exactly why it has to actually work.
What to Ask Your Own Support Vendor
If you are evaluating a support relationship, mine or anyone’s, three questions extract the truth faster than any SLA document. Who, by name, do I contact at 2am, and what happens in the first thirty minutes? Does my spend level change my place in the emergency queue, and will you say so in writing? And what does your release discipline look like, because an agency that ships chaos creates the emergencies it then bills to fix. The answers tell you whether support is a promise or a department.
If the answers you get are a portal, a tier, and a shrug, and your store earns real money at night, get in touch. There is room at the table, and the policy is exactly as described, whichever size you are.