Our client success teams have people from different countries. Four things make that work: very good guidelines, SOPs, structure and check-ins.
None of them involves watching anyone's screen. A remote coaching team is managed through what clients receive. In a coaching back end, almost all of that is visible on the client board.
What do you manage if you cannot see the work?
The board. Every client sits on it as on track or overdue, with notes from the last contact. If the overdue list was worked today, the notes show it. If a chat waited since lunch, the chat shows it.
So the daily question is not whether someone was online. It is whether the five priority clients were handled and every overdue client heard from the team. Those are facts on a screen you already own.
How do you set up a remote hire to work alone?
How good a person turns out depends on the onboarding. A worksheet for the role, the SOPs, Loom recordings of the work done well and a few training sessions. Then freedom to learn, regular check-ins and reporting back.
No KPIs in the first month. Every person has a learning curve, and early KPIs are pressure for no reason. Check in often in month one and less after it, the same rhythm we use with new clients.
Make the first days concrete. Day one is the worksheet and access to every tool. Then the SOPs, each with its Loom, then shadowing real client work before doing it alone.
Which numbers do you hold a remote team to?
Client results, from month two. The client success rate, the on-track rate and the share of winners who give proof. Every third winner should give a success interview, testimonial or Trustpilot review, and ideally every second.
Numbers tied to results keep people on the work that moves results. A team member judged on messages sent will send more messages. One judged on overdue clients brought back on track will call them.
Put those numbers where the team can see them, per person and over time. A team member who watches their own overdue count fall needs fewer check-ins from you.
Offshore works, with very good guidelines, SOPs, structure and check-ins. We have people from different places. It works if they speak good English. And every meeting has a meeting note they fill in beforehand, so it is never a random call. I hate random calls.
How do you talk to a remote team without endless calls?
Keep three channels, each for one thing. Slack is good for team chat inside a company and bad for client communities. Clients reach the team on WhatsApp, Telegram or Skool. Anything longer than a few lines becomes a Loom.
Write these channel rules into the onboarding worksheet. A new hire then learns them on day one instead of by mistake.
| Need | Channel | Rule |
|---|---|---|
| Quick team question | Slack | Reply in the thread, link the client on the board |
| Explaining a task or a change | Loom | Under a few minutes, linked in the SOP afterwards |
| A decision with two or more people | Call | Meeting note filled in before it starts |
| Client messages | WhatsApp, Telegram or Skool | Answered in the morning, lunch and evening waves |
What goes wrong with remote coaching teams?
Three things, and they are the same three we see in any client success team. People send long messages; write like a friend, professional, never send books. They make things complicated; send links and make it easy. And they do not fully understand the offer, which regular trainings fix.
Time zones are the fourth. Clients are most active in the evening, so somebody has to be on chat then. Plan who covers each wave before the hire, not after the first complaint.
The fifth is silence. A remote team member who is stuck often says nothing, because asking feels like admitting a mistake. Regular check-ins and reporting back exist for that: a short Loom on what moved and what is stuck.
Diego Miescher
