WaSparks On a Monday morning, a senior sales executive at a tile distributor hands in his notice. By Friday he is gone. Over six years he had built relationships with about three hundred contractors and architects, almost all of them over WhatsApp from his own phone. Quotes, site photos, payment reminders, a decade of “remember I like the matte finish.” The business owns the products and the brand. It does not own a single one of those conversations.
Within a month, a few of those contractors are still ordering, but now from him, at his new employer. Others drift away because nobody at the distributor knows what was promised or what they bought last time. The owner realises that the most valuable thing he lost was not a salesperson. It was the memory of every customer that salesperson served. If this sounds familiar, our solutions for your industry show how teams keep that memory with the business.
The real-world breakdown: what leaves with the employee
The contact list. Customers are saved on the employee’s personal phone, under the employee’s account.
The conversation history. Every quote, promise, complaint and preference is in chats the business cannot open.
The context. Even if the chat is somehow retrievable, the nuance is gone: who is a decision maker, who pays late, who needs a call rather than a message.
The relationship. The customer’s trust was built with a person. If that person leaves, the customer’s loyalty goes where the person goes, unless the business has built a relationship of its own.
The ability to follow up. Open quotes, pending deliveries and unanswered questions are suddenly invisible.
This is not a rare event. Staff turnover is normal, particularly in sales, retail and service roles. The risk is not that people leave. It is that the business has arranged things so that when they do, the customer record leaves with them.
Why the common fixes do not work
Asking staff to forward their chats on the last day. It depends on goodwill at the moment goodwill is lowest, and a forwarded export is a dead file, not a working conversation.
Giving employees a company SIM but keeping the same habits. Better, but chats still live on a device and a single WhatsApp account, and the phone has to be physically recovered and unlocked.
Telling staff to maintain a CRM or spreadsheet. Updating it is a second job. It is always out of date, particularly on busy days.
Relying on an exit conversation. The employee will tell you about the top ten customers, not the other two hundred and ninety.
Banning WhatsApp altogether. Customers use WhatsApp. Banning it does not stop it, it just moves the conversations out of sight.
The operational SOP: keeping customer history with the business
Rule 1: Customers talk to the business number, not a person’s number
Every customer conversation takes place on the company’s WhatsApp Business number. Staff never give out their personal numbers for business use. This one decision does most of the work.
Rule 2: Every chat has an owner on the system
The salesperson looking after a customer is recorded as the owner of that chat. Ownership can change, but at any moment the business knows who is responsible.
Rule 3: Handovers carry a reason
When a chat moves from one person to another, the reason is noted. This is the same discipline you would want for a customer going from sales to delivery, and it works just as well when a person leaves.
Rule 4: Save useful details on the contact record
Preferences, key decision makers and payment behaviour belong on the customer’s record, not in someone’s head. Agree a short list of things worth recording.
Rule 5: A leaver checklist
On the day someone gives notice:
1. List the chats they own.
2. Reassign each one to a named colleague, with a handover note.
3. Message key customers from the business number to introduce the new contact.
4. Remove the leaver’s access to the inbox.
5. Review the audit log for anything unusual during the notice period.
Rule 6: Control who can export or see what
Not everyone needs access to every number or every chat. Use roles so that access matches the job.
A handover note template
Customer: {name}. Business: {company}. Usually buys: {product}. Last quote: {amount} on {date}. Open items: {items}. Preferences: {notes}. New contact: {colleague}.
How WaSparks fits into this
WaSparks puts the whole team on one WhatsApp Business number, so customer conversations belong to the business from the start. You connect the number through Meta’s own signup flow and keep ownership of it.
Each chat in the team inbox is a work item that can be assigned to a teammate or transferred with the reason noted. When someone leaves, you reassign their chats and the full history stays with each conversation. Contact records are built from conversations and uploads, so a record exists for every customer, not just the ones someone remembered to save.
Roles and permissions decide who can see and do what. The audit log records every change, including who did it and when. Invite-based activation means access is granted by you and can be taken away by you. Each business’s data is kept separate from every other business’s.
You can see all of this on the features page.
FAQ
Is it legal for a company to keep customer conversations when an employee leaves?
Customers contacted the business, and conversations on the business’s own number are business records. For any specific legal question, such as data protection obligations or employment terms, speak to a qualified adviser, because the answer depends on your contracts and local law.
What if an employee has been using their personal WhatsApp for years?
Move the important customers over gradually: introduce the business number from the employee’s side where possible, and from the business number going forward. The sooner the conversations are on a shared number, the less there is to lose.
Do we still need a CRM if we use a shared inbox?
A shared inbox builds a record automatically from conversations. Many small businesses find that is enough to start. If you later need deeper reporting, you can connect other systems through webhooks and the API.
Keep the relationship when the person moves on
Move customer conversations onto a number the business owns, assign every chat and write the leaver checklist before you need it. Start free or look at the pricing.
Explore all solutions → wasparks.com/solutions
Found this useful? Share it with your team.