WhatsApp Usage Policy: Rules That Prevent Problems Before They Happen

The eight points of the policy

1. Which number to use for work and the explicit prohibition of serving customers via personal number.
2. Service hours, with instructions for outside those hours: automatic absence message and promised response time.
3. Maximum time for first response within working hours, with the agreed number — without a target, each person uses their own urgency criteria.
4. What can be promised: discount range, deadlines, payment conditions, exceptions, and who authorizes each.
5. Tone and form: use of audio, emojis, form of address, agent’s signature on the first message.
6. Customer data handling: what cannot be forwarded, printed, or sent to groups, aligned with LGPD.
7. Mandatory record: what must be written in the conversation or CRM — agreements, values, deadlines, and reasons for loss.
8. What happens on termination: access revocation, portfolio transfer, and the rule that the customer base belongs to the company.

One page covers all eight. A longer document is not read and, worse, gives the impression the company addressed the issue when in practice no one knows what’s inside.

Working hours: the rule that protects both sides

Unlimited service hours seem like a competitive advantage but come at a high cost:

• Creates permanent expectation. A customer served at 22h once expects it always and complains when it doesn’t happen.
• Wears out the team and creates labor liabilities when responses habitually occur outside working hours.
• Degrades quality. Responses given hurriedly, on the couch, without system access, are where promises the operation can’t keep are born.

The arrangement that works: published hours, automatic message outside them informing when there will be a return, and a defined on-call schedule when the business really requires it — as detailed in on-call schedule. Agreed and paid on-call is different from everyone being available all the time.

The cost of having no rules

Operation with 6 agents, 900 conversations per month, average ticket of R$ 540.

None of these numbers appear in reports. They dissolve into small individual decisions every day and only become visible when someone compares average discounts between agents or measures the proportion of recorded conversations.

How to enforce the policy

1. Present it live, not by email. Thirty minutes with the team, explaining the reason for each rule. A document sent without conversation is a document not read.
2. Make it accessible where work happens — in the CRM, pinned in the team group, printed on the office wall.
3. Include it on the first day of new hires. Policy presented during onboarding is accepted; presented after a mistake sounds like punishment.
4. Measure what the policy defines. Response time, average discount, registration rate. A rule no one measures is a suggestion.
5. Review every six months, with the team. Those who serve customers know which rules don’t work in practice — and impossible-to-follow rules erode respect for all others.

A one-page policy template

To get it off paper today, this skeleton covers the eight points and fits on one page. Adapt the numbers to your operation:

• Channel: customer service happens exclusively via the company number, accessed through the platform with individual login. Serving customers via personal number is prohibited.
• Hours: Monday to Friday, from 8h30 to 18h, and Saturday until 12h. Outside these hours, an automatic message informs the return on the next business day.
• Response: every first message must be answered within 10 minutes during service hours.
• Autonomy: discounts up to 5% and deadlines up to 15 days can be granted by the agent; beyond that, only with coordinator authorization.
• Form: the first message identifies the company and the agent. Audio only when the customer uses audio. Price, deadline, and address always in writing.
• Data: customer information is not forwarded to groups or external numbers. Documents remain in the system, not in the conversation.
• Record: value, deadline, condition, and reason for loss are recorded in the conversation or CRM on the same day.
• Termination: access is revoked on the last day, portfolio is formally transferred, and the customer base remains with the company.

Print it, discuss with the team, and put the next review date in the footer. A policy without a review date ages silently and becomes that document everyone signed but no one follows.

The policy on the first day of a new hire

Every onboarding is the best window to establish standards, and it lasts briefly. A two-hour integration script covers the essentials:

• Joint reading of the policy, with space for questions. A document delivered without conversation is a document not read.
• Access created in the person’s name, never shared. Shared login makes any later investigation impossible.
• Five real conversations read together, chosen as examples of the expected standard — including one that went wrong.
• First service accompanied, with an experienced person alongside, and review shortly after.
• Agreement on when to ask for help, so the person doesn’t improvise out of fear of seeming insecure.

The fifth item prevents the most costly mistake of beginners: promising something outside the policy to avoid losing the sale. Making it explicit that asking is the expected behavior — not a sign of unpreparedness — saves more money than any later corrective training.

What to do when someone breaks the rules

The response varies according to the type of deviation, and treating all the same is unfair and ineffective:

• Form deviation — tone, emoji, hours: individual conversation, with concrete example in hand.
• Authority deviation — discount or deadline beyond allowed: immediate correction, with case and reason review. Often the authority level is poorly calibrated.
• Record deviation — agreements outside the system: most common and most tolerated, and precisely what causes chaos when someone leaves or goes on vacation.
• Data deviation — improperly forwarding customer information: treat as a serious matter from the first time, because the consequence is not internal.

In all cases, the policy only supports correction if it existed beforehand. That’s why writing a page now is worth more than debating each case as it arises — and it’s what transforms WhatsApp from an improvised channel into a measured operation.