Remote support isn’t a temporary arrangement for a lot of teams anymore, so build a remote-first help desk, one designed to stay remote. That means writing things down, onboarding people on a screen, watching for burnout deliberately and hiring from a wider pool than one commute radius. The teams that treat this as a stopgap will pay for it twice.
The signals from large employers are clear. In May, TechCrunch reported that Twitter would let staff who could work from home keep doing so permanently. In late July, Google extended its voluntary work-from-home option through June 30, 2021, according to a report covering the announcement. A support manager at a much smaller company doesn’t have to copy either decision. But you should notice what they’ve admitted: the question stopped being “when do we go back?” and became “what do we want the work to look like?”
This is the long view of a year I’ve been writing about piece by piece: reducing a support team by 60%, keeping a team motivated when everyone is scared, handling client escalations with limited resources and non-work activities that drive team engagement. I asked last year whether remote working is a fad or here to stay. I think the answer has arrived faster than anyone planned. This is how I’d approach a help desk that expects to be at least partly remote for a long time.
What changes when remote becomes the default?
The things you improvised in March become the things you maintain. The emergency VPN setup needs an owner and a budget. The chat channel that grew organically needs rules. The knowledge base that people filled in a panic needs an editor. None of this is exciting, and all of it decides whether the team is still functional in a year.
Start with a review of what you built. List every workaround you put in place since March: the shared spreadsheet, the personal phone numbers, the screenshots passed around in chat. For each, decide whether to formalise it, replace it or stop doing it. A workaround that survives six months without a decision becomes a process by default, and a default process is usually a bad one.
Be honest about what isn’t working. Some tasks that were easy in an office are expensive at a distance: onboarding, training, escalations that need three people looking at one screen. Find those and invest in them directly, rather than hoping they’ll sort themselves out.
How do you onboard a new agent who never visits the office?
With a structured plan, because nobody will absorb it by sitting nearby. In an office, a new agent picks up a lot by listening. Remote, they pick up only what you deliberately show them. Build a first-month schedule: day one for access and tools, the first week shadowing recorded and live calls, the second week taking calls with a named buddy listening, the third week on their own with daily check-ins.
Give them a person, not just a document. A buddy who’s available for a fast question through the first month makes more difference than any training deck. Pair them with someone who explains things well rather than whoever has the lowest handle time. Protect that person’s time, because mentoring is real work and it shouldn’t be an extra on top of a full queue.
And lean on the knowledge base. A new starter’s questions are the best audit you’ll ever get of what’s missing. Ask them to flag every gap they hit in the first month, and fix those as a team. By the end of it, you’ll have better documentation and a new agent who has already contributed.
How do you spot burnout in a team you don’t see?
Look at patterns, not moments. Burnout rarely announces itself. It shows up as a slow drift: more sick days, shorter messages, a drop in quality that has no other explanation, an agent who used to volunteer for escalations and now doesn’t. In an office you’d notice most of that without trying. Remote, you have to build the noticing into your routine.
Use your one-to-ones for it. Ask about the work, then ask about the rest: how are the hours, are you getting a break, is there anything in the way? Listen for what’s left out. And track a few simple things at team level, such as overtime, schedule adherence and sick leave, so you can see a trend before it becomes a resignation. The numbers won’t diagnose anything, but they’ll tell you where to ask.
Buffer’s 2020 State of Remote Work report found communication, collaboration and loneliness at the top of remote workers’ struggles, with about one in five naming loneliness. That’s a survey of people who chose the arrangement. People who were sent home have less preparation. Plan for it. Build in time that isn’t about work: a virtual coffee, a team channel for non-work chat, a regular slot where nobody’s allowed to talk about the queue.
Also set limits on hours. A remote support team without clear shifts drifts toward the whole day, because the laptop is on the kitchen table. Make the end of the shift a real end. If someone is on call, say so and give them time back. Your best agents are the likeliest to overwork, and they won’t tell you.
Does remote work change how you measure the team?
It shouldn’t change the definitions, only the care you take reading them. Choose measures from the customer’s side, as in choosing the right KPI. Keep the targets from your first call resolution and response-time measures. If the numbers move, work out why before you decide it’s about location. A drop in resolution time might be a tooling problem, a knowledge base problem or a staffing problem, and remote work might be none of those.
Add measures that reflect the new risks. How long does a new agent take to reach full productivity? How many escalations sit without an update time? How often do people use the knowledge base, and how often do they flag it as wrong? These tell you whether the remote model is working, in a way that headline response times won’t.
Compare like with like when you look back. Many teams will have a before-and-after picture of the move. Keep the definitions the same on both sides, and say clearly what changed in the same period: volume, staffing, product. Otherwise the comparison will be used to argue for whatever someone already believed.
What opens up when you can hire from anywhere?
A much larger pool, and some new problems. A remote help desk can recruit people who can’t commute, who live in different time zones, or who simply live somewhere your office isn’t. That helps with coverage: a team spread across time zones can staff an overnight shift in someone’s daytime, which solves the awkward problem of the person on call at 2am.
It also adds work. Different regions have different employment rules, different holidays and different expectations. A shift pattern that works for one country doesn’t for another. Get advice early, and don’t assume a hire in another jurisdiction is simple. And think about the career path for people who never meet their manager, because people who feel invisible leave.
Security deserves a second look at this point. A temporary home setup that was acceptable for a few weeks needs proper controls when it becomes permanent: managed devices, access based on role, regular reviews of who can see which customer data. The HDI community has useful practical material if you’re formalising the arrangement.
None of this means every team should stay remote. Some work really is better in a room, and some people are miserable at home. A hybrid arrangement, with set days together and the rest apart, suits a lot of teams. Decide on purpose and tell people the reasoning. What goes wrong is leaving it undecided, because an undecided arrangement is a different arrangement for every person on the team.
There’s also a cultural point that gets lost. A remote team builds its identity from what it writes and what it does, not from a building. Be deliberate about recognising good work in public: a note in the team channel when someone handles a hard escalation well, a shout-out for the person who fixed three knowledge base articles in a week. In an office, praise travels by overhearing. At a distance it only exists if you put it somewhere people can see it.
Plan your reviews of the arrangement on a calendar, too. Three months, six months, a year. At each one ask the same three questions: what’s working, what isn’t, and what would we do differently if we were starting today? Keep the answers short and act on them. A remote model that gets reviewed twice a year improves. One that’s left alone just drifts.
You built a remote help desk in a hurry. The next job is deciding what to keep.
Hutch Morzaria is a Director-level CX and Support Leadership professional with 19 years of experience building global support organizations across SaaS, Fintech, and enterprise technology. He has hired dozens of support and CX leaders across his career and holds ITIL Expert certification across V3 and V4.
