Rolling out a messenger CRM in two weeks: a plan for the head of sales

A system isn’t rolled out on launch day. It’s rolled out on the day people stop writing the old way.

It happens like this. Something is bought, logins are handed out, one call is held. A month later half the team is writing from personal phones again, and the head of sales still learns about a client’s problem from the client.

The tool is rarely the problem. A rollout is a management task. It is carried by people, agreements and one date in the calendar. Below is a two-week plan: which decisions to make, in what order, and where people most often go wrong.

What to decide before you start

Three things, preferably in writing.

• Who owns the rollout. One person with the right to decide. Not a committee.
• What counts as a result. For example: every client conversation runs from company numbers, you know each rep’s reply speed, and the client base doesn’t depend on one person.
• What is out of scope. Perfect wording, combing through every old conversation, arguments over details: later.

CRM implementation steps: the two-week plan

Step 1. Name an owner and see the picture (days 1–2)

The owner starts with a simple table. Which numbers the company has. Who writes from which. In which messengers. Whose name each number is registered in and who pays for it. Which clients only one person knows.

Ask your reps directly, without punishment. The goal is a picture, not someone to blame. Almost always it turns out that part of the work runs from personal accounts you didn’t know about.

Step 2. Decide whose numbers they are (days 2–4)

One principle: the client writes to the company, not to a person. A number used for work is registered to the company and paid for by the company. That is not a formality. Under their own public rules, messengers can restrict a number after complaints. If that number belongs to a rep who quit yesterday, nobody is left to appeal or recover it.

Personal numbers are not used for work. If clients are used to a personal contact, move them gently to a company number: a short message from the rep, no fuss. If the team already juggles several work numbers, each of them needs an owner on paper.

Step 3. Agree on messaging rules (days 3–5)

Not a forty-page manual, but a few agreements the whole team reads the same way:

• what reply time we call fast, and what we call late;
• what is never written to a client, under any circumstances;
• what a rep doesn’t promise without approval;
• a client’s promise is a commitment, and it has an owner.

Discuss this with the team instead of handing it down. People keep the rules they talked through themselves.

Step 4. Contracts and consent (days 4–6)

Write it into the employment contract or internal policy: client conversations are held on behalf of the company, and the numbers and the client base belong to the company. This protects the rep too: nobody has to explain later why a client stayed in their phone.

Then look at the clients. Do you write only to people who agreed to receive messages? Messenger rules and the law agree here: writing without consent puts both the number and your reputation at risk.

Step 5. A leaving procedure (days 5–7)

The most expensive moment in messaging is the day someone leaves. Decide in advance how it goes:

• who prepares the list of open clients and promises;
• who takes over the work, and by when;
• who is responsible, on the last day, for making sure the person no longer has a way into work numbers and conversations;
• how the client is told that someone else is now talking to them.

The procedure is the same for everyone, managers included.

Step 6. Explain to the team why (days 6–9)

Resistance is almost always rational. A rep fears being watched, having more work, or losing personal clients. Don’t persuade. Answer each fear specifically: what exactly you want to know and why, why clients belong to the company, and how that protects the rep too.

Start with one or two strong reps and one skeptic. Let them work by the new rules for a week. Collect facts, not opinions. A skeptic is worth more than an enthusiast: if they accept the new order, the rest will.

Step 7. Measure the “before” (days 9–11)

Without a starting point, a month from now there will be nothing to compare against. Count by hand, on a sample of recent conversations:

• how many clients waited longer than you agreed;
• how many conversations died on the company’s side;
• how many clients only one person knows;
• how many client promises had no date and no owner;
• how much revenue each rep brings in.

The numbers will be unpleasant. They are the reason for all of this.

Step 8. The switch date (day 12)

Set a specific date and say from which moment personal numbers are no longer used for client conversations. No “gradually” and no “when there is time.” A soft transition without a date never ends.

Step 9. Review the first week with people (days 12–26)

This is the most important part, and the one most often skipped. At the end of the first week, a short meeting with the team. Not a report, a conversation:

• whose conversations still run from personal numbers, and why;
• who replies slowly, and what gets in their way;
• which promises to clients were left without an owner;
• which questions came up that no agreement covers.

At the end of the second week, repeat the “before” measurement and compare. Decide what to drop, what to add and what to keep.

Common rollout mistakes

• Rolling out for reporting, not for work. Reps sense it at once and find a way around.
• Moving everyone at the same time. Without a small first group, every failure becomes an argument against the whole thing.
• Keeping personal numbers “just in case.” The work leaks out through exactly those.
• Not naming an owner. If everyone handles the rollout, nobody does.
• Not writing down how people leave. The first person to quit proves the base still lives in someone else’s phone.
• Stopping the reviews after launch. The old habit returns within a week.

How to tell the rollout succeeded

Not by the number of logins. By signs from real life:

• reps write to clients only from company numbers;
• you know who replied in a minute and who in an hour, and you don’t have to ask in meetings;
• every promise to a client has a date and an owner;
• when someone leaves, they take neither clients nor history;
• the team proposes new agreements rather than looking for ways around them.

If at least three of these describe you, the rollout happened.

What to decide about your company before you choose

Comparing feature lists is easy. It is harder to answer a few questions honestly, and they decide whether any CRM for messengers takes root:

• who owns the numbers and the client base today, the company or individual people;
• what happens to clients on the day your best rep leaves;
• who in the company answers for numbers, messaging rules and staff logins;
• whether you write only to people who gave consent;
• whether you are ready to name a date and hold to it.

Some risks are never left to a vendor or a rep: ownership of numbers and the base, closing logins when someone leaves, client consent. Those are the leader’s decisions. How we handle them is a conversation for when we meet, not for an article.

Checklist: a two-week CRM rollout

• One person is named to own the rollout
• A picture exists: numbers, messengers, who writes where
• Work numbers are registered to the company and have an owner
• The team has agreed on messaging rules
• Contracts state that conversations and the client base belong to the company
• Clients are written to only with their consent
• There is a leaving procedure: who takes over, who closes logins
• A “before” measurement exists: replies, dropped conversations, revenue per rep
• A date is set after which personal numbers are not used
• A week after that date, the team review took place

Skip two of these, and there will be a launch but no rollout.

---

Quiet systems work better than loud ones. You just don’t hear them.