Client chat policy for a sales team: what it must include (with a template)

A rule that isn’t on paper exists only until the first dispute.

Within a week a new sales rep promises a client a discount nobody approved. An experienced one answers at night and gets annoyed at people who write on weekends. A third leaves and takes half the chats along.

None of this is about bad people. It is about chat rules that were never written down. Below: what a sound policy consists of and how to write it so it is followed. At the end there is an outline you can copy.

What it is for

A policy does three things. The client gets the same treatment from any rep. A newcomer quickly learns how things are done here. The head of sales can hold people to a document, not a feeling.

It is not a guide to “writing nicely.” It is an agreement about boundaries: what is allowed, what is not, and what to do when you don’t know.

Sections of the policy

Reply times

Write down how fast the first message is answered and the ones after it. Use working hours, not days. Separately: what to do when there is no full answer yet. The rule is simple: it is better to tell a client “I’ll check and get back to you today” than to go silent.

Working hours

When a rep is reachable and what happens outside that time. Whether they must answer in the evening and on weekends, or the client is told in advance during which hours they will get an answer. If this isn’t written down, some people burn out and others ignore clients.

Tone and address

Formal or informal address, how to name the client, whether jokes, emoji and voice messages are acceptable. A couple of examples of good and bad wording explain more than a paragraph of description. Separately: how to write when the client is irritated.

What must not be promised

Deadlines that depend on other departments. Discounts outside the approved ones. Results the rep doesn’t control. Product features they aren’t sure about. Say it plainly: if you don’t know, say so and find out. Every promise to a client is a commitment of the company.

Handling objections

Not ready-made scripts but principles. Listen and clarify first, then answer. Don’t argue and don’t press. Don’t answer a “price” objection with an instant discount. Describe when a rep keeps the conversation going and when they close it politely.

Handing a client over

How a client is passed to another rep or department. What must go into the handover: the substance of the conversation, what was promised, the next step. The client should not have to explain everything again. A handover without a note is lost context.

Escalation to the head of sales

When a rep brings in the head of sales: a complaint, a threat to leave, legal questions, a large amount, an unusual request. And how fast the head of sales replies. Escalation is not weakness but a normal move. If people are scolded for it, they start hiding problems.

Forbidden topics and warning phrases

What is not discussed with clients in chat: the company’s internal affairs, other clients, opinions about competitors, personal views on politics and religion. Separately, the client phrases after which a rep doesn’t argue alone but hands the conversation to the head of sales within the hour: threats, complaints, mentions of courts and inspections. The team adds to this list after every difficult case.

Personal data and access

Which client data may be requested and stored. What must not be forwarded to personal chats and outside services. Who has access to work numbers and conversations. Work numbers and chats belong to the company, not the person. Moving clients to personal accounts is forbidden.

Leaving the company

What happens on the day a sales rep leaves: access closes at once, conversations are passed on, promises to clients are checked, and clients receive a message from the new owner. This protects the client base and keeps clients from being left without an answer.

What it should not contain

Don’t put anything in the policy you don’t intend to check. A rule nobody enforces teaches the team that the other rules are optional too. Don’t copy someone else’s document whole: it was written for other clients and other products. And don’t turn the policy into a list of bans. Half its value is in explaining how to act well, not only what not to do.

How to write it so it is followed

1. Start with real cases. Take conversations where something went wrong and ask which rule would have helped.
2. Discuss it with the team. Imposed rules get bypassed. Understood rules get followed.
3. Write short and concrete. “Reply quickly” is not a rule. “Reply within a set time during working hours” is.
4. Add examples. A good and a bad reply side by side.
5. Give the reason. One sentence next to each rule: why it exists.
6. Revisit it. Every six months or after a significant case.

What the head of sales decides before any tool

A policy works when it can be checked. And you can only check what you decided to count in advance. Many start by picking a CRM for messengers, but no software will answer these questions for you:

• Which three or four numbers you want to know every week. For example: each rep’s reply time during working hours, how many conversations were left unanswered, how many promises to clients were kept on time.
• Whose numbers and whose chats. If the answer is “the company’s,” it has to be written down and signed, not assumed.
• Who may read other people’s conversations, and why. That is the head of sales’ decision, and it goes into the policy instead of being left to each person.
• How often you review chats with a rep one-on-one, and what you do with the conclusions.
• What you are prepared to change in the team if the numbers turn out unpleasant.

Until you have these answers, any tool will simply lock in the order that already exists. How such rules live on our side is something we show to those who make it to the introduction.

The policy outline

Copy it, replace the points with your own and discuss it with the team.

1. Purpose of the document and whom it covers.
2. Reply times: first message, follow-ups, when there is no answer yet.
3. Working hours and what to do outside them.
4. Tone and address: formal or informal, acceptable formats, examples.
5. What must not be promised: deadlines, discounts, results, product features.
6. Handling objections: principles, when to continue, when to close.
7. Client handover: what to record, whom to pass to, how to inform the client.
8. Escalation to the head of sales: cases, procedure, response time.
9. Forbidden topics and warning phrases: the list and who takes over the conversation.
10. Personal data: what to request, what to store, what not to forward.
11. Access: who can reach what, ban on personal accounts.
12. Leaving the company: closing access, passing conversations, checking promises.
13. Responsibility and how the document is revisited.

Checklist: client chat policy

• The policy is written and available to every rep
• Reply times are set in working hours
• There is a list of what must not be promised
• Handover and escalation are described
• Reps know which client phrases send a conversation straight to the head of sales
• It is stated that chats and numbers belong to the company
• The procedure for a departure is written down
• The head of sales knows which chat figures they look at every week
• The policy was discussed with the team and is revisited

If three of these are missing, the first dispute will be with your own team, not with a client.

---

Rules are not for those who write them. They are for the one who arrives tomorrow.