Supporting a customer you will never meet

The deal is signed, onboarding went well, and then it goes quiet. For months the only time you hear from your first offshore customer is a support ticket that lands at 2am your time, written by someone you have never met, in a city you have never visited. How you handle that ticket is now the whole relationship.

Onboarding gets all the attention because it is where the deal feels won. But the first 90 days end, and what keeps an offshore customer is the ordinary Tuesday eighteen months later. That is a different job, and distance changes almost every part of it.

Support is the relationship now

For a customer down the road, the relationship is built in the gaps around support: the coffee, the conference, the quarterly review in their boardroom. Offshore, none of that happens. You will never read the room and never shake a hand. Every contact the customer has with you is a support contact, and every one is a small vote on whether to renew.

That raises the stakes on something small teams treat as a cost centre. CEB analysed more than 97,000 customer service interactions and found any single one is four times more likely to push a customer towards disloyalty than towards loyalty. For an account you only ever meet through a queue, that ratio is the whole relationship.

The clock breaks first

The first thing distance does is scramble your support hours. When the customer is at their desk with a problem, you are asleep. A four-hour response promise means one thing in your own time zone and something very different when those four hours land in the middle of your night.

The fix is not to pretend you run a 24-hour desk you cannot staff. It is to be honest about when you answer, publish it in the customer's time zone, and decide in advance what counts as urgent enough to wake someone. A customer who knows you are a New Zealand team, and who sees a clear rule for critical issues, will forgive the gap. A customer who was promised fast and got silence will not.

What actually has to change?

CEB's larger finding is that customers do not become loyal because you delighted them. They found almost no loyalty difference between customers whose expectations were exceeded and those whose expectations were simply met. What drives customers away is effort: having to chase, repeat themselves, wait. 96 percent of customers who had a high-effort experience reported being disloyal, against 9 percent of those whose experience was easy. Distance makes effort the default setting, so removing it is the job.

A few things separate offshore support that holds from the kind that leaks:

• Honest support hours. State them in the customer's time zone, not yours, and never promise cover you cannot staff.
• Self-service that actually works. Good documentation, a status page and clear error messages do the night shift you cannot. It is the cheapest lever you have.
• A severity ladder both sides agree on. Define what critical means before the outage, not during it, so a real emergency reaches a person and a cosmetic bug waits until morning.
• Async by default. Write updates the customer can read when they wake, rather than forcing a live call across a 12-hour gap.
• One named owner. Even if you never meet, the customer should know whose account this is and who to escalate to.

The advantage nobody puts in the pitch

Being 12 or 13 hours ahead of your United States or United Kingdom customer feels like a handicap until you design for it. A ticket raised at the end of their day can be solved while they sleep and be waiting in their inbox at breakfast. Overnight turnaround, done on purpose, is something a local competitor in their own time zone cannot match.

The same distance that makes support hard is the thing that can make your support memorable, if you build the rhythm around it deliberately rather than apologising for it. So before you sign your next offshore customer, ask the quieter question behind the celebration: once the onboarding glow fades and you are a support queue in a distant time zone, is that queue good enough to be the whole relationship?

Sources. Service interactions and loyalty: an analysis of more than 97,000 customer service interactions found any single interaction is four times more likely to drive disloyalty than loyalty, that 96 percent of customers with high-effort experiences became disloyal against 9 percent with low-effort experiences, and that exceeding expectations produced almost no loyalty gain over simply meeting them - Matthew Dixon, Nick Toman and Rick DeLisi, The Effortless Experience, CEB (Corporate Executive Board), 2013. The guidance on support hours, severity ladders, async updates and using New Zealand's time-zone position as an overnight advantage draws on my own experience helping New Zealand tech companies support offshore customers, not a single study.

Nick Burns is a fractional CRO for New Zealand B2B tech companies, at home and expanding internationally. He co-founded Emendo and sold it to McKesson, then the 14th-largest company on the Fortune 500, and has since helped 60+ tech companies grow sales.