Customer communication policy: channels, response times and escalation

A customer asks on WhatsApp whether a feature can be delivered by month end. The account manager says yes, meaning probably. Two weeks later the customer quotes that message to the delivery head, who had never heard of it. A customer communication policy exists for exactly this gap: what we say, through which channel, how fast, and who has to agree first.

The purpose is professional, timely and reliable communication with customers. It covers every employee who talks to a customer, in sales, support, delivery and finance. It sits beside the social media policy, which covers public posts, and the confidentiality and non-disclosure policy, which covers what may be shared.

Start with the list of authorised customer-facing roles. A junior developer may join a call and answer technical questions, yet not agree a delivery date. Write down which roles may commit to dates, discounts or scope, and which must check first.

• Official channels: company email, the helpdesk, the company phone line and scheduled video calls.
• Messaging apps: allowed only if the customer started the thread, the account is a company-managed one, and key points are copied to the CRM.
• Not allowed: personal email, personal social messages and voice notes for commitments.

Messaging apps are the real decision. Banning them makes you hard to reach. Allowing them freely means promises live on private phones. Most companies choose a middle path: permit them for quick coordination, and require a written follow-up by email for anything that binds.

Keep etiquette short and concrete. Greet by name, answer the question asked, avoid slang and jokes with new contacts, and use the language the customer prefers. On the phone, say who you are and the company name. Meetings start on time, with an agenda sent beforehand and minutes sent within a day. Quote the ticket number in every reply, keep one thread per issue, and use a signature block with the sender's name, role and direct line. A shared helpdesk inbox needs a rota so one named person owns each hour. Out-of-office replies name a backup person and a return date, never just an absence.

A response is an acknowledgement with a next step, not a solution. Decide targets by channel and by priority. A system outage might need a reply within minutes, a pricing question within a working day. These are numbers the company sets from what its team can actually meet; promising faster than you can deliver is worse than a slower, honest target. Say when the clock pauses, for example while the ticket waits for the customer to send logs, and which hours count for a support desk that does not run overnight. A weekly breach report from the helpdesk, with the longest-waiting tickets at the top, shows whether the targets are real.

1. 1

   Receive and log

   The first person to see the message records it in the CRM or helpdesk with the customer, channel and time.

2. 2

   Acknowledge

   They reply within the target for that channel and priority, with the owner's name.

3. 3

   Resolve or hand over

   The owner answers, or hands to the right team with the full thread so the customer need not repeat it.

4. 4

   Confirm in writing

   Any decision on scope, price or dates is emailed back and saved.

5. 5

   Escalate

   If the target is missed or the customer asks, the case moves up one level: team lead, then department head, then director.

6. 6

   Close and ask

   The owner closes the case and sends a short satisfaction survey, and the score goes to the monthly service review.

Prices and proposals are approved before they leave. Define who signs off a quote, what discount needs a second approver and which template to use. In delays, tell the customer early with a new date and the reason, then confirm it in writing. Use the same discipline for scope changes that the project management policy sets out.

A complaint is logged the same day, acknowledged by someone other than the person complained about, and given an owner and a date for reply. Train people to stay calm, restate the problem, avoid blaming colleagues and never argue about who said what; check the record instead. Disputes about money or contract terms go to the director, with finance involved.

Record calls, key emails and decisions in the CRM. Keep a communication log, complaint register, meeting minutes and the signed acknowledgement of this policy. Customer information stays confidential, and employees should not forward customer threads to personal accounts. Missing a target once is a coaching matter; making an unauthorised commitment or sharing a customer's data is more serious, and the company decides the consequences with HR. Review the policy yearly and whenever a channel or service level changes. See where it fits in the order of the 30 policies and in HR policies and governance.

1. Purpose and scope: all staff who communicate with customers.
2. Authorised roles: [roles] may commit on dates; [roles] on price.
3. Channels: approved list [list]; messaging apps [conditions].
4. Etiquette: greeting, language, meeting agendas and minutes within [number] day(s).
5. Response targets: [number] hours for priority one, [number] for priority two, by channel.
6. Pricing and proposals: approval by [role]; discounts above [limit] need [role].
7. Written confirmation: scope, price and date changes emailed and logged.
8. Complaints: logged same day; owner [role]; reply within [number] days.
9. Escalation: level one [role], level two [role], level three [role], each after [number] hours.
10. CRM use and templates: [fields]; delay notice, apology, minutes and handover-note templates.
11. Breaches: [consequence ladder].
12. Acknowledgement and review: name, date, version; reviewed every [number] months.