A customer service process for small business is a short written record of how enquiries get answered: the replies you already give most weeks, what the person answering is allowed to promise, what has to come straight back to you, and who signs off a refund. It is one page, not a manual. Write it before you hand the inbox to anyone — an employee, a part-timer, a family member helping out on Saturdays — because the day you hand it over is the day you find out how much of it only existed in your head.
What is a customer service process for a small business?
It is the answer to a question every owner eventually has to face: if I am not the one replying, how does the customer get the same answer I would have given?
Most small businesses never write this down. The owner has answered the same fifteen questions for three years, so the answers live in their head and in a thousand sent emails. That works perfectly until it has to leave the building — until someone is off sick, until the shop gets busy, until the business grows past one person’s inbox.
It is one page, not a manual
The version that gets used is short enough to read in four minutes. A long document written once and never opened is worse than nothing, because everyone assumes the answer is in there somewhere. Aim for a single page you would be happy to hand a new starter on their first morning.
Why it has to exist before the first handover
Writing it afterwards means writing it from complaints. You find out what was missing when a customer is told the wrong delivery date, or is promised a refund that was never yours to give. Writing it first costs an hour. Writing it afterwards costs the customer.
What should you write down before someone else answers your customers?
Four things, in this order. Everything else is detail.
1. The answers you already give five times a week
Go through your last fortnight of messages and count the repeats. Opening hours. Whether you deliver to that postcode. How long the quote takes. What happens if the part is out of stock. Most businesses find that a handful of questions account for the bulk of the inbox, and every one of them has a settled answer you have simply never typed out twice.
Write the answer, not a summary of the answer. “Explain the delivery policy” is not usable by someone who does not know the delivery policy.
2. The limits — what they may promise, and what they may not
This is the part owners skip and then regret. Be explicit about the edges:
- Can they quote a price, or only a price range?
- Can they commit to a date, or only to “we will confirm by Friday”?
- Can they offer a discount to calm someone down? Up to what?
- Can they agree to a change in scope on a job already booked?
A promise made by anyone in your business is a promise made by your business. If the limits are not written, they will be guessed — usually generously, because the person answering wants the conversation to end well.
3. The escalation rule — what comes straight back to you
Decide what nobody else answers. The usual list is short: anything about money owed, anything legal, anything from a journalist, anything where the customer is already angry, and anything that sounds like a new piece of work worth having. Those do not get a helpful holding reply invented on the spot. They get acknowledged and passed to you.
The acknowledgement matters as much as the escalation. “I have passed this to Muhammad, he will come back to you today” is a complete, honest answer. Silence while it sits in a queue is not.
4. The tone
Two or three lines is enough. Do you apologise straight away or establish the facts first? Do you use first names? Do you sign off with the business name or a person’s? Customers notice when the voice changes, and they read a change of voice as a change of company.
Who is allowed to give a refund?
Write the refund rule down separately, because it is the single decision most likely to be made badly under pressure. Say who can approve one, up to what value, and what happens above that value.
Note that some of this is not yours to decide. In the UK, a customer’s right to a refund, repair or replacement is set by law rather than by your policy, and the government’s guidance on accepting returns and giving refunds is the place to check what you must do before you decide what you will do as a goodwill gesture. Your written rule sits on top of the legal minimum; it never replaces it.
There is a second obligation worth a line in the same document. The moment someone else reads your customer emails, they are handling other people’s personal information on your behalf, and the ICO’s advice for small organisations covers what that means in practice. Who has access to the inbox, and what happens to that access when they leave, belongs in writing next to everything else.
What does this look like in practice?
We run one of these on ourselves, and it is deliberately strict.
Codeora’s marketing runs largely unattended — posts go out, comments get written, conversations get answered, without anyone approving each one. But there is one hard rule written into it: a real enquiry is never answered automatically. If somebody asks about hiring us, asks for a price, reports a bug, proposes a partnership or asks to move to a DM, the reply does not get written. The message is logged as a lead, a notification goes to my phone, and it waits.
Then I say what the answer is, and my words go out — tidied, never rewritten.
That is the escalation rule from earlier, applied to a system rather than a person, and the reasoning is identical. Routine questions have settled answers, so they can be handled by whoever or whatever is in front of them. A question that could start a commercial relationship has no settled answer, so it belongs with the person who can actually commit. Writing that boundary down is what let us stop reviewing everything else.
It is worth saying what this is not. It is not a policy for what software is allowed to do on your behalf — that is a related but separate document, and we wrote about an AI usage policy for small business elsewhere. This one is about people, and it should read like something you would say out loud.
When should you automate part of it?
Only after it is written, and only for the part that repeats.
The first list you made — the answers you give five times a week — is the part worth handing to a tool, because those answers are settled and identical every time. They belong on a page of your website, in an autoresponder, or in an assistant that can quote them exactly. Everything under “escalation” should never be automated at all; the point of that list is that a person decides.
This is the same boundary as human in the loop automation: the tool handles the settled cases and stops at the ones that need judgement. Get the order right and automation removes tedium. Get it backwards and it makes commitments you have to honour.
If you already know which replies repeat and want them handled properly rather than approximately, that is the kind of work our workflow automation service exists for. Tell us what your inbox looks like and we will tell you honestly which part is worth automating and which part is not.
Frequently asked questions
How long should a customer service process for a small business be?
One page. If it runs longer, the repeated answers have been mixed in with the rules — split them into two documents: a short rulebook and a longer list of standard replies people can copy from.
Do I need this if only I answer customers?
You need the refund rule and the standard answers, because both save you time immediately. The escalation and tone sections only start earning their keep when a second person is involved — but writing them while the business is small is far easier than reconstructing them later.
What is the first thing to write down?
The five questions you answer most often, with the exact wording of your answer. It takes twenty minutes, it is useful the same day, and it makes every later step obvious.
Should a chatbot handle customer enquiries for a small business?
It can handle the settled, repeated questions well. It should not handle pricing, complaints or anything that commits you to a date or an amount, unless you have written down exactly what it may say — which brings you back to the same document.
How often should it be reviewed?
Whenever something goes wrong, and once when anyone new starts. A process that is only updated on a schedule drifts away from what the business actually does.