Your Technician Quits. Who Keeps the Customer?

Your Technician Quits. Who Keeps the Customer?

When a technician leaves and takes customers, a non-compete will not help: it is void in Malaysia. The customer stays with whoever holds the saved number.

Tan Wei LinTan Wei LinHome Services
22 Oct 26
14m
Part of the series:CRM Automation for Malaysian SMEs: The Complete 2026 Guide to Replacing Manual Processes

A technician leaves and takes customers with him for one boring reason: the customer saved his number, not yours. Not loyalty, not a secret client list, not a plan. Three years of "message Faizal direct lah" means the only aircon contact in that household's phone is a person who now works for himself. The non-compete clause you made him sign is void under Malaysian law, so the protection has to be operational, and it has to be in place before anyone resigns.

Key Takeaway

When a technician leaves and takes customers, the customer is not choosing him over you. They are messaging the only number they have. A post-employment non-compete is void under Section 28 of the Contracts Act 1950, so the real defence is making the company the contact: one shared number the customer saves, the service history in a record the owner can see, and the annual reminder sent by the company before the technician's new business sends his.

Why does a technician leaving take customers with him?

Because the customer relationship was built on his phone, not in your business. Think about how a home-service job actually runs. The office books the first visit. From the second visit on, the customer has a problem at 9pm, remembers the friendly technician, and messages him directly. He replies because he is helpful. The office never sees that chat. By year three the office is not in the relationship at all.

What we have seen across small service businesses is that before there is a shared system, nobody has decided what gets recorded or where. Each technician keeps his own customer chats on his own phone, in his own format, and the owner cannot see any of it. That is survivable while everyone stays. It becomes the problem on the day someone leaves.

Take a six-technician aircon servicing company in Shah Alam. Faizal has been there five years and handles most of the Setia Alam and Klang jobs. He resigns, politely, to "try something on his own." Nobody panics, because the company has a few hundred customers and he was one of six. Four months later the owner notices the annual-service bookings from Setia Alam have gone quiet. Nobody calls to complain. Nobody says "we moved to Faizal." The customers simply did what they always did: they messaged the aircon guy, and the aircon guy now has his own van.

The uncomfortable part is that Faizal did not have to steal anything. He did not copy a customer list or send a mass announcement. The customers came to him, because his number was the one saved under "Aircon Faizal" in 200 phones.

Why won't a non-compete clause protect you in Malaysia?

Because it is void. Section 28 of the Contracts Act 1950 says every agreement that restrains someone from exercising a lawful profession, trade or business is, to that extent, void. Malaysian courts have read this strictly: a clause that restricts an ex-employee after the employment ends is unenforceable even if it is short and looks reasonable, and the court has no discretion to rescue it (Thomas Philip Advocates & Solicitors). The three exceptions in the Act cover the sale of a business's goodwill and partnership arrangements, none of which apply to a technician on payroll.

Void
status of a post-employment non-compete clause in Malaysia

So the clause most owners reach for first is the one tool that is guaranteed not to work. Restrictions during employment are fine, because an employee owes you a duty not to compete while you pay him. Once he hands in his notice and serves it out, the restraint falls away.

There is a narrower tool that can survive. Employment lawyers in Malaysia point out that a confidentiality clause and a non-solicitation clause, drafted separately from the non-compete, can be upheld after employment for a reasonable period, provided the wording is clear and you can produce evidence of the breach (Donovan & Ho). Note the last condition, because it is the one that catches small businesses. "Evidence of solicitation" means proof that he contacted your customers. If every chat he ever had with those customers lives on his personal phone, you have nothing. If the customers contacted him, that is not solicitation at all.

Talk to your own lawyer about the clauses. But understand what they can and cannot do. A non-solicitation clause is a fence around a field. If the customers were never in your field to begin with, there is nothing for the fence to protect.

What actually keeps the customer when a technician leaves?

The customer stays with whoever owns the three things that make a service relationship: the number they message, the history of their equipment, and the reminder that tells them it is time. If all three sit with the company, the technician's departure is an HR event. If all three sit with the technician, it is a sales event, and you lose it.

Relationship on the technician's phoneRelationship in the company
Number the customer savedTechnician's personal numberOne company number, shared by the team
Service historyIn his memory and his chat scrollIn the customer record, visible to the office
Annual reminderWhoever remembers first (usually him)Sent by the company on schedule
Photos, quotes, model numbersOn his phoneAttached to the customer record
When he resignsCustomers follow the numberRemove his login; nothing else changes
Proof if he solicits customersNoneChat and activity history on record

The most important row is the first one. Everything else follows from which number the customer has saved. If the company number is the one that confirms the booking, sends the technician's arrival time, follows up after the job and sends next year's reminder, the customer saves it. If the company number only ever sends an invoice, they save the technician.

That is also why "ban technicians from giving out their numbers" fails as a policy. A customer standing in their kitchen asks "can I WhatsApp you if it leaks again?" and no decent technician says no. You cannot police that conversation. What you can do is make the company number the more useful one to have, so the personal number is a backup the customer never needs.

The customer is not being disloyal

A household that follows a technician is not rejecting your company. They are doing the lowest-effort thing: messaging the number that worked last time. Make the company number the one that works, and the same low-effort instinct keeps them with you.

Frequently Asked Questions

No, not after employment ends. Section 28 of the Contracts Act 1950 makes any agreement that restrains a person from a lawful trade or profession void, and Malaysian courts apply it strictly to post-employment restrictions regardless of how short or reasonable the clause looks. Restrictions during employment are allowed. Check your own situation with an employment lawyer.
A clearly worded non-solicitation clause, kept separate from the non-compete, can be enforceable in Malaysia for a reasonable period after employment, but only if you can prove the ex-employee actively solicited your customers. If the customers contacted him, or the chats only exist on his personal phone, you will struggle to show a breach.
It rarely works. Customers ask on site and technicians do not refuse. A better rule is that every booking, confirmation, follow-up and reminder goes out from the company number, so the company number is the one customers save and the personal number is a backup they do not need.
Reassign his open jobs and customers in the CRM, remove his login, and send the next scheduled reminder to his customers from the company number as normal. If the relationship already lives in the company, that is the whole process. If it lives on his phone, start by asking for the customer list and service history while he is still on notice.
Compare bookings from his former customers before and after he left. If you track last service date per customer, the ones who did not rebook when their reminder went out are the ones to call. Without a per-customer record you will only see a drop in total bookings months later, with no way to tell who left.

How do you move the relationship from the technician to the company?

You do it in the normal course of business, one booking at a time, and you start now, not on the day someone resigns. There are four pieces: one number, one record, one reminder, one handover.

How to Keep Customers When a Technician Leaves

Put the whole team on one company WhatsApp number. Use the official WhatsApp Business API so several people can reply from one number and every chat is stored centrally. From today, bookings, "technician on the way" messages, after-service follow-ups and reminders all go out from this number, so it is the one customers save.
Give every customer a record the office can see. Name, address, unit models, last service date, the technician who went, and any photos or quotes from the visit. The technician fills this at job close-out, the same way he already collects payment. Keep it to a handful of fields or it will not get filled.
Send the annual reminder from the company, on schedule. Filter customers whose last service was 11 months ago and send the reminder as a campaign from the company number. The reminder is the single most valuable message in a service business, because it is the one that triggers the rebooking. It must come from you before anyone else sends it.
Route repeat customers by area, not by person. When a Setia Alam customer rebooks, the job can go to whichever technician covers Setia Alam that week. Customers who have met two or three of your technicians over the years think of your company as the provider, not one man.
Make the handover an afternoon, not a crisis. When a technician gives notice, reassign his customers in the CRM, remove his access on his last day, and let the next reminder go out as normal. Every chat he had on the company number stays with the record, which is also the evidence a non-solicitation clause needs if you ever have to use one.

The order matters. Step one changes nothing about how customers behave until step three runs, because the reminder is the moment they decide who to book. A company that gets the number right but still relies on technicians to remember whose service is due has moved the chats and left the relationship where it was.

What does this look like six months in?

Go back to the Shah Alam company, but with the pieces in place. Faizal still gives out his number, because customers still ask. But the booking confirmation came from the company number. The "Faizal is 20 minutes away" message came from the company number. Two days after the service, the "any issues with the unit?" check-in came from the company number. Eleven months later the reminder came from the company number, with the customer's own unit models in it. In that household's phone, "Aircon Faizal" sits next to a company contact that has sent eight useful messages. Faizal's has sent none.

When Faizal resigns, the owner spends an afternoon reassigning his customers to the two technicians who cover the same area and removes his login. The following month, the Setia Alam reminders go out as scheduled. Most customers rebook without noticing anything changed. A few ask for Faizal and are told he has moved on and that Hafiz will come instead. One or two follow him anyway. That is the difference between losing a handful of customers and losing a territory.

The repeat-business maths is what makes this worth the effort. The probability of selling to an existing customer is 60 to 70 percent, against 5 to 20 percent for a new prospect (Marketing Metrics, Farris et al.). Every customer who leaves with a technician is one you have to replace with ads, at the harder rate. Our post on why 60% of aircon customers do not come back in year two covers the reminder side in detail, and it is the same mechanism here: the company that sends the reminder gets the booking.

60-70%
probability of selling to an existing customer, vs 5-20% for a new one

Where does the owner usually get this wrong?

By treating it as a trust problem instead of a structure problem. Owners who have been burned once tend to respond by trusting technicians less: tighter contracts, warnings about giving out numbers, suspicion of anyone who is popular with customers. That makes good technicians leave faster and does nothing about the number saved in the customer's phone.

The second mistake is adding the system only for new customers. The customers most likely to follow a technician are the long-standing ones, the ones who have had him in their house six times. They need to be brought onto the company number first, and the easiest way is the next reminder: send it from the company number with their unit details in it, and they will save it, because it is the message that got them a booking.

The third mistake is thinking a shared number alone solves it. It does not, if everyone can see every chat but nobody has decided what to record. We wrote about that in WhatsApp for multiple users: the device limit was never the real problem, ownership of the reply was. The same applies here. The record has to say which unit, which date and which technician, or the office is just looking at chats it cannot act on.

If you run a home-service business and have already hit the point where the owner is the bottleneck, this is the same fix seen from a different angle. The company has to own the customer relationship for the owner to step back and for a technician to be replaceable. Our home services page shows how a shared number, a customer record and scheduled reminders fit together for cleaning, aircon, plumbing and electrical teams.

Every customer-facing message (booking, arrival, follow-up, reminder) goes out from one company number
Each customer has a record with unit models, last service date and the technician who went
Annual reminders are sent by the company on schedule, not by whoever remembers
Repeat jobs are assigned by area and availability, not "ask for the same guy"
Confidentiality and non-solicitation clauses are drafted separately from any non-compete, by a lawyer
Resignation checklist exists: reassign customers, remove login, let the next reminder run
Key Takeaway

A technician who leaves takes the customers whose only contact is his number. A non-compete will not stop it, because post-employment restraints are void in Malaysia, and a non-solicitation clause only helps if the evidence sits in your records rather than on his phone. Make the company number the one customers save, keep the service history in a record the office can see, and send the annual reminder from the company. Then a resignation is an afternoon of reassigning jobs, not a territory walking out the door.

Ready to grow with Raion

The customer saves your company number, not your technician's

Every service chat, reminder and booking runs through one shared number in Raion HUB, so when a technician resigns the customer record, the chat history and the next reminder all stay with you.