Moving work off WhatsApp without losing the client
Don't ask the client to switch channels. Leave them texting the same number they always have and change only what happens behind it: every request gets logged in a system, with an owner and a date, the moment it comes in. The client should never notice a thing, and whoever answers stops running on memory and scrollback.
Your client isn't attached to WhatsApp, they're attached to getting an answer
When someone says "just text me," they're almost never talking about the app. They're telling you something else: that they get a fast answer there, that they don't have to explain the whole job again, that they know who's on the other end. That's what they don't want to lose. The app is just where it's been happening.
That's why most attempts to get the work off WhatsApp fail the same way. You hand the client the job of moving. Log into a portal, create an account, open a ticket. That's where the direct line actually dies, because you put paperwork in front of something that used to take them ten seconds.
One rule holds the whole thing together: you never touch the client's channel. Same number, same person answering, same tone. Everything that changes happens on your side, and the only thing the client should notice is that nothing falls through the cracks anymore.
You move the record, not the conversation
WhatsApp isn't the problem. The problem is that it's the only place your business information lives. The price is in a three-minute voice note. The gate code is in a photo. The install date is in a message sent at eleven at night that nobody ever read again. The day the person who handled it is out sick or quits, you don't have an operation, you have a scroll bar.
Log very little, and only what moves the deal: who they are, what they asked for, what you promised, at what price, by when, and what's still missing. Five or six fields, not thirty. If logging a job takes more than a minute, nobody is doing it at seven on a Tuesday evening, and in three weeks you're back where you started.
The same person who replies logs it, right then, not in a spreadsheet dump at the end of the day. The rule that makes it stick: you don't send a "got it, I'm on it" until the record exists. If you want the tell for when this stops fitting in a spreadsheet, here are the signs a business actually needs a CRM.
It goes cold the moment the system starts talking
What kills the relationship isn't the record. It's the vocabulary. The day your client gets "your request has been received, case #4432," they understood exactly what happened: they stopped talking to a person and started talking to a counter. Internal numbers stay internal. The client never sees them.
Three tone rules cover it. Keep answering like a human and sign your name, even when the message goes out from a shared inbox. Auto-replies only outside business hours, and they name a real time, something like "I'll get back to you before 10 tomorrow," never "we'll respond shortly." And no numbered menus. If the person texting already knows you, a menu is a demotion.
Announce the change once, in one sentence, and frame it as good news: there's more than one person watching requests now, so nothing sits. No asking permission, no apologizing. If it sounds like an apology, the client assumes they lost something, and from that point on they will look for proof that they did.
Three weeks, without pausing the work
Week one, change nothing and just watch. For five business days, write down everything that came in through the thread and turned into money, plus everything that died. That's where your real fields come from, and they're almost never the ones you'd have guessed beforehand. This is one page, not a project.
Week two, the number becomes the business's number instead of one person's, on a business line with more than one user. Short labels in your own language: new, quoted, waiting on them, won, lost. One record per client with the history attached. Two people with access from day one, never just one.
Week three is the real test. Pull the person who always answers for two days and let someone else run the thread. If the backup can reply without texting anyone privately for context, it worked. If they have to call to find out what was promised, you're not there yet and pushing further only makes it worse. Once you clear that bar, it's the right moment to look at where a small team should start automating.
Frequent questions
Can I put a bot in front of me?
Yes, but keep it short and limited to things that commit you to nothing: hours, service area, address, whether you do that type of work at all. Anything with a price, a date, or a promise gets answered by a person. A bot trying to close a deal is the fastest way to make a client feel demoted.
What do I do about the personal cell phone people already text?
You have two options: move that same number onto a business line with multiple users, or forward it to the new line for a few months until clients drift over on their own. What you can't do is run two live numbers answering the same thing, because that's exactly where jobs get dropped. Settle that the number belongs to the business, not the person, before there's a dispute about it.
How do I know if the client felt the change?
Two signals show up in the thread itself. One is that they start repeating context you already have, with lines like "as I mentioned last time." The other is that they ask who they're talking to. Either one means there's no longer a recognizable person on your end, and the fix is tone, not more software.