ECHO EMISSARY

Choosing9 min

CRM for messengers: 12 questions to ask before you buy

Short answer

Choosing a CRM for messengers starts with your company, not with a vendor. Twelve questions an owner asks themselves: whose numbers and conversations they are, what happens when someone leaves, who owns promises made to clients, what an hour of silence costs, who actually brings revenue, where the law allows your data to sit, and who decides on access. Until you have the answers, any purchase is a blind bet.

The window for chatting is visible at once. Everything else you learn six months later.

Almost any CRM for messengers looks the same in a demo. Neat, fast, clear. The trouble comes later. A sales rep leaves and takes the clients along. A number gets limited in the middle of an important conversation. The promise “I’ll pay on Friday” gets lost, and nobody remembers who heard it.

None of these problems starts with software. It starts with decisions the company never made. So the questions worth asking before you buy are not for the vendor. They are for yourself.

If you are choosing a CRM for Telegram, a CRM for WhatsApp, or one for all messengers at once, below are twelve questions in four groups. For each one you should have an answer you could say out loud to your team. If you don’t, that is the main result of the exercise.

Client base and people

This is where you decide who your work actually belongs to.

1. Whose numbers and conversations are they

Open the list of the numbers your team writes from. Who are they registered to? How many are the reps’ personal phones? If a number belongs to an employee, the whole history with your clients is legally and practically theirs.

Ask yourself plainly: what stays with the company if three key people leave tomorrow? If the honest answer is “nothing,” it is too early to choose a tool. Put the numbers in the company’s name first.

2. What happens here when someone leaves

This is the most common way a client base is lost. The person quits, and the clients, agreements and the whole history stay on their phone. A month later some of those clients are writing to them again, only at another company.

Think back to the last exit in your team. Who closed the access? On what day? Who told the clients that someone else is now looking after them? If the answer is “it sort of happened,” there is no order. Write into the contract that numbers and conversations are company property. And agree who picks up the clients of someone who left, and by when.

3. Who decides who reads which conversations

Sales don’t need to read collections conversations. An intern doesn’t need the whole client list on day one. But someone has to decide that and write it down.

Answer for yourself: who in the company is responsible for access to conversations? Who can export the whole base? Who would find out if that happened? That is where leaks most often come from. Not a break-in, but a person nobody ever told “no.”

4. What lives only in a rep’s head

A price agreed by word of mouth. A discount promised “as an exception.” A relative who always pays for the client. If only one person knows all this, it is not their experience. It is the company’s risk.

Count how many clients you would lose if a rep were replaced tomorrow. If the answer is “most of them,” the problem isn’t the people. It is that a conversation with a client has no owner except the person having it.

Numbers and the law

A number is both a consumable and the main asset. Treat it the way you treat money in the bank.

5. What a limited number costs us

Limits in Telegram and WhatsApp are not an exception but everyday reality. The messengers say openly that they restrict numbers for complaints and for messages people didn’t expect. The question isn’t whether it will happen, but what you lose on that day.

Count it: how many clients rest on one number? How many conversations break off? Who in the company notices first: the manager or a client nobody answered? Decide who is responsible for your numbers and who they report to.

6. Do the people we write to agree to it

The recipient’s consent is not a formality. It is what separates a conversation with a client from spam. And it is a number’s main protection against complaints.

Answer for yourself: where did each contact in the base come from? Did the person leave the number themselves, or was it bought? Is there a record of consent? Who in the company is responsible for that? If the base was collected “however it worked out,” any limits are the price of that choice, not bad luck.

7. Where the law allows our data to sit

Conversations with clients are personal data. Different countries have different rules: where it may be stored, for how long, and who has the right to read it. The company pays for a breach, not the vendor.

Ask your lawyer which requirements apply to you specifically. In which country the base may be kept. How long it may be stored after you stop working with a client. Whether you need consent to process it. These answers shape the choice more than any interface.

Team and promises

This is where you see whether a department works or only chats.

8. What an hour of silence costs us

A client wrote in the evening. Someone replied in the morning. They had already bought elsewhere. How many such clients a month? How much money is one such hour worth?

Take an ordinary week and count it yourself: who answers in a minute and who in an hour. How many conversations were never answered at all. If a manager cannot name these numbers, they don’t manage reply speed. They hope for it. Decide what reply time is normal for you and tell the team.

9. Who owns the promises we make to clients

Every “I’ll pay on Friday,” “I’ll call you tomorrow,” “I’ll send the contract by lunch” is a commitment. Not the rep’s, the company’s. A commitment needs an owner and a deadline.

Ask yourself: if the payment doesn’t arrive on Friday, who finds out? Today or a month from now? This matters most where money depends on a client’s word. If the whole memory of the department lives in people’s heads, it walks out with them.

10. Who decides what clients receive in the company’s name

Every message a client receives speaks for the company. Even a template. Even a follow-up written in advance. The client doesn’t care whether a person typed it. They only remember that it arrived at the wrong moment.

Agree within the team: who approves the texts clients receive? Who answers for a text the company would rather not have sent? The company’s tone is a rule too, not one rep’s taste.

Revenue and the decision

The last group answers why you are doing all this.

11. Do we know which person brings the revenue

Sent and read are not a result. The result is deals and money. Do you know who on the team brings them? Not who writes the most, but who sells the most?

If the answer is “roughly,” you are paying for activity, not for money. Decide what a result means for each department: a deal, a payment, a client kept. Then count it per person, at least for last month.

12. Who decides on access to our conversations

For a company that sells with words, conversations are its most valuable asset. They hold clients, prices, agreements and weak spots. Who in the company decides who they can be trusted to? Employees, contractors, the vendor, any program that reads them?

If nobody ever made that decision, it was made for you. Name one person responsible for access to conversations, and write the rule down.

What you cannot leave to chance

Any tool is only an extension of your decisions. If the numbers belong to employees, no software will bring them back after someone leaves. If nobody tracks promises, no interface will do it in the manager’s place. If there is no consent, limits will come.

Three things the owner decides alone and never delegates. Who owns the base. Who answers to the client for the company’s word. Where, and under which law, the conversations sit. Everything else is detail, and details are best discussed face to face, once you already know your own answers.

Is the company ready to choose

  • Numbers are registered to the company, not to employees
  • The contract states that conversations belong to the company
  • There is an order for the day someone leaves: access, clients, owner
  • One person is named to decide on access to conversations
  • You know where each contact came from and whether there is consent
  • A lawyer has told you where and how long client data may be kept
  • Every promise to a client has an owner and a deadline
  • The team knows what reply time counts as normal
  • You have counted what an hour of silence costs the company
  • You know who on the team brings revenue, not just who writes
  • It is decided who approves the texts clients receive
  • You have counted how many clients rest on one number

If more than three boxes are empty, start with order inside, not with a purchase. The rest belongs to the introduction.


A choice is made once. It is paid for every day.

Questions and answers

What should you ask before choosing a CRM for messengers?

Start with yourself, not the vendor. Answer the questions about your numbers, your people, promises to clients, revenue and the law. Once you have the answers, you know what you are protecting and what to talk about next.

What should be decided about an employee leaving, in advance?

A rule before the first exit: numbers and conversations belong to the company, access is closed on the day someone leaves, and every client gets a new owner. It goes into the contract and the internal rules, not into a last-day conversation.

What should you do if a number gets limited or blocked?

It is a fact of the market: messengers limit numbers for complaints and unwanted messages. Count in advance how many clients rest on one number, check that the people you write to agreed to it, and decide who is responsible for your numbers.

Where to start if you don't have these answers yet?

With three: whose numbers they are, who owns promises made to clients, and who decides on access to conversations. The rest is easier to discuss in person, at the introduction.

All signals