Customer service standards in a small business are a short document of promises to customers and working rules that apply no matter who happens to be replying. Customers notice the lack of one quickly: a fifteen-minute reply in the morning, a next-day reply in the afternoon, and the same request approved once and refused the next time. A written standard ends that lottery without a handbook.
This guide is the top layer: it shows what fits on one page and how to keep it alive in daily work. If you are still deciding which channels and tools to switch on at all, start with the article on customer service in a three-person company.
What the standards document should cover
A good standard answers six questions that customers and new hires ask, even when they do not say so out loud. Each item is a sentence or two, not a chapter. The table shows what to write and where the details go.
Scroll the table sideways to see all columns.
| Standard item | What you write down | Where the details live |
|---|---|---|
| Channels and hours | Where you reply, on which days and hours, in which time zone | Widget settings and team schedule |
| Response time | How much business time passes before the first human reply | SLA policy |
| Tone and language | Three writing rules, not a style guide | Plain language guide |
| Promise limits | What an agent never promises without approval | List of permissions and exceptions |
| Handoff | When and to whom you pass a case, and what the note contains | Escalation guide |
| Closing | When a conversation is finished and what the customer knows at the end | Team macros |
ISO 18295-1:2017 sets out service requirements for customer contact centres of any size, including performance metrics and indicators, and ISO is working on a revised edition. ISO 18295-1. The standard is paid and does not offer a ready one-page list for a small business; the six items above are our own proposal.
Channels, hours and the response time promise
List the channels where you genuinely reply and those where you do not handle cases. A sentence such as "for orders, write to us in chat or by email; we redirect post comments to chat" prevents misunderstandings on both sides. Separately note what customers see in the evening; ready-made messages are in the guide to after-hours website enquiries.
The response time promise should cover the first human reply counted in business hours, not an automatic acknowledgement. Pick a value the team meets on its hardest weekday, not on average. How to set the start, pause and stop of the measurement is explained in the guide to a customer support SLA; in the standard, one sentence with a number is enough.
"We reply in website chat and by email Monday to Friday, 9:00 to 17:00 Central European time (CET/CEST). During those hours, the first reply from a team member arrives within [X] hours. Messages from evenings and weekends are handled on the next working day in the order they arrived."
Tone as a principle, and the limits of promises
Three tone rules are enough, and each can be checked on a single message. The most important information goes in the first sentence. We say who will do something and by when, instead of "the case has been forwarded". We address customers the same way the company website does, formal or informal, but always consistently. Before-and-after examples are in the guide to plain language in replies; the standard should not repeat them.
ISO 24495-1:2023 establishes governing principles and guidelines for plain language documents and is aimed at anyone who writes texts for readers. ISO 24495-1. It does not address chat messages or customer service directly; the three tone rules above are our proposal.
Most trouble comes from promises made in good faith, not from poorly chosen words. List what an agent never promises alone, even when the customer pushes.
- A delivery or completion date you have not confirmed in the system or with the person responsible.
- A discount, free shipping or price exception outside the written rules.
- Accepting a complaint or refunding money before the case has been checked.
- The word "done" before the action has actually been carried out.
- An answer on a legal or personal data matter without consulting the person named in the standard.
When to hand a case on and how to close a conversation
Write handoffs down as conditions, not as a judgement of difficulty. An agent passes the conversation on when the decision exceeds their authority, when data must be checked in a system they cannot access, when the customer reports a technical fault or when the conversation stops being factual. That last case has its own rules, covered in the guide to an abusive customer in chat. In every case, the standard names a specific person or department rather than a vague "someone on the team".
A good handoff leaves an internal note with three facts: what the customer wants, what they have already been told and what they are waiting for. The customer gets one sentence saying who takes over and when they will hear back.
Closing a conversation needs a rule too. A conversation is finished when the customer has an answer or knows the next step with a date and an owner. The last message confirms what was agreed in one sentence and does not end with an empty "we are at your disposal" when something is still open. The case status in your tool should say the same thing as the final message to the customer.
A one-page template and how to prepare it
You can write it in one afternoon if you start from what the team already does, not from an ideal.
- Gather material.Pick twenty conversations from last month, including a few that went badly. List the promises made in them.
- Record what already works.Write six items based on the team's best replies rather than on wishes.
- Cut it to one page.Each item is two sentences at most. Move details into instructions and macros.
- Test it on hard cases.Read five problematic conversations and ask whether the standard says what should have happened.
- Add a version and an owner.Note the date, the person responsible for changes and the next review date.
Channels: website chat and email. Hours: Mon to Fri 9:00 to 17:00, Central European time (CET/CEST). Reply: first human reply within 2 business hours. Tone: informal, key point first, always who and by when. We never promise alone: repair dates, discounts, accepted complaints. Handoff: repairs to Kate, payments to the owner, always with a note. Closing: an answer or a next step with a date. Version: 1.0, owner: Ola, reviewed every quarter.
How to keep the standard alive in your tool
Every item needs a place in the tool the team works in, or it fades. In Meetlead customer service, you set the response promise as an SLA policy with first response and resolution targets, a time zone and a weekly working schedule. Replies from the AI assistant do not count as a human reply there, so the report does not inflate your result.
Move tone and closing into team macros with categories and variables, such as the agent's name; the guide to response templates explains how to build that library. Roles with access levels per module let you limit who changes shared settings. Reports show first response and resolution times as the median and the 90th percentile, and optional post-chat CSAT ratings alongside the number of ratings collected.
Numbers show whether you meet the deadline, not whether the answer was right. Once a month, review a few conversations with a customer support QA scorecard and check that its criteria match the items in your standard. When a rule keeps losing to reality, fix the standard and raise the version number instead of pretending it still applies. Once the standard works, choose a few measurable customer service goals for next year, each with an owner and a quarterly review.
Questions about service standards
Do I need to publish the standard on my website? Not all of it. Show customers the channels, hours and response time promise, because that is what they are waiting for. The public version must say the same as the team version, or customers receive two different promises. This article is not legal advice; if the standard goes into your terms or a contract, have the wording checked.
How often should I update the standard? In a small team, a quarterly review is enough, plus one after every change of hours, channels or staff. Introduce new people to the standard on day one, following the plan in the guide to onboarding a new customer service operator.
