Customer service policy: how to write one

A customer service policy is a short written set of rules for how your business treats customers: how fast you reply, what you refund, and when a problem goes to the owner. Most small businesses don't have one, so every answer depends on who happens to read the email. This guide shows you how to write a customer service policy in an afternoon, with a plain template you can copy.

What a customer service policy is (and isn't)

Think of it as the answer key. When a customer asks for a refund on day 31, or writes at 10 p.m., or is angry about a late order, your team shouldn't have to guess what you'd want. The policy already says.

It is not a mission statement and it is not a 40-page manual. If nobody reads it during a busy week, it isn't doing its job. One to two pages is plenty for a small shop.

It also isn't the same thing as a customer service SLA. An SLA is a promise about response and resolution times. Your policy includes those times, but it also covers tone, refunds, and what to do when something goes wrong.

Why your business needs a customer service policy

The short answer is consistency. Two customers with the same problem should get the same answer, whether you or a new part-timer wrote it.

• Faster replies. Nobody stops to ask the owner about every refund or exception.
• Easier training. A new hire can read two pages on day one and start answering by day two.
• Fewer arguments. "Here's our policy" lands better than "that's just how I feel today."
• Something to improve. You can't fix a rule you never wrote down.

It also protects you. If a customer disputes a charge, a written policy that was posted before the sale is far easier to stand behind than a verbal promise.

What to include in a customer service policy

Keep each section to a few sentences. These are the parts most small businesses need:

1. Who you serve and how. List the channels you actually answer: email, live chat, your help center. Say which ones you don't offer, so nobody waits on a phone line that doesn't exist.
2. Hours and reply times. For example, "We answer email within one business day and chat during business hours." Only promise what you can keep.
3. Tone. Two or three sentences on how you talk to people. Plain, polite, and direct works for most shops.
4. Refunds, returns, and exceptions. The exact window, the conditions, and who can approve an exception. Our guide to writing a refund policy for a small business goes deeper on this part.
5. Escalation. Which problems go to the owner or a senior person, and how fast. See how to set up a ticket escalation process.
6. Saying no. What your team can decline, and how to decline kindly. More on that in how to say no to a customer.
7. How you learn. How you collect complaints and feedback, and who reviews them.

How to write a customer service policy in six steps

1. Look at what customers already ask

Open your inbox and read the last 50 messages. Sort them into piles: shipping, refunds, how-to questions, complaints. Your policy should answer whatever shows up most.

2. Write down what you already do

Don't invent new rules yet. Write what you do today when a customer asks for a refund or a late order arrives. You'll often find you already have a policy. It just lives in your head.

3. Fix the gaps and the surprises

Now look for places where you've given different answers to different people. Pick one answer and make it the rule. If you can't decide, pick the one you can keep doing on your worst day.

4. Put numbers on it

Replace "we reply quickly" with "we reply within one business day." Replace "we accept returns" with "we accept returns within 30 days if the item is unused." A rule with a number is easy to follow and easy to check. Our post on customer service response time can help you pick a realistic target.

5. Keep it short and plain

Use short sentences and everyday words. If a 12-year-old can't follow it, rewrite it. Cut anything that doesn't change what someone does.

6. Share it, then test it

Post the customer-facing parts on your site or in your help center. Give your team the internal parts. Then run three real past tickets through it. If the policy doesn't settle them, it's missing something.

A customer service policy template you can copy

Swap in your own details. Delete anything that doesn't apply.

Our promise. We treat every customer the way we'd want to be treated. We're clear, polite, and honest, including when the answer is no.

How to reach us. Email [address] or use the chat on our website. We don't offer phone support.

When we reply. Email: within [1] business day. Chat: [9 a.m. to 5 p.m., Monday to Friday]. Messages sent outside those hours are answered the next business day.

Refunds and returns. You can return unused items within [30] days for a full refund. Items damaged in shipping are replaced or refunded at no cost. Anything outside these rules can be approved by [the owner] only.

When something goes wrong. We apologize once, plainly, and fix it. If we can't fix it within [2] business days, we tell you why and what happens next.

Escalation. Anything involving a chargeback, a legal threat, or a safety problem goes to [the owner] the same day.

Feedback. We read every complaint. We review patterns once a month and change the policy when the same problem keeps coming up.

That's about 150 words, and it already answers most of what customers ask. You can grow it later.

Customer service policies for common situations

A few situations trip up small teams again and again. Decide them ahead of time.

Late or delayed orders

If you sell physical goods online in the U.S., the Federal Trade Commission has a rule on shipping times. In short, you must ship within the time you state, or within 30 days if you state none, and you must tell customers and get their consent if you can't. Check the rule for your exact case, then write the same timing into your policy.

Angry or rude customers

Write down what your team should do, and what they don't have to put up with. A good line is: "Stay calm, fix the problem, and hand the ticket to the owner if the customer becomes abusive."

Requests outside the policy

Give your team a small amount of room. For example, "Any rep can approve a refund up to $25 without asking." That one sentence saves hours of back and forth.

Keeping the policy alive

A policy goes stale fast. Put a reminder on your calendar to read it every quarter. Ask two questions: did we break it, and did it stop us from helping someone we wanted to help? Fix the rule in either case.

It also helps to keep it where your team works. In SupportifyGPT, you can save your approved answers in the knowledge base, so replies to common questions follow your policy every time. Hand-written rules find the right articles, then the support bot writes a reply in its own words using only what you've written. If your articles don't cover a question, it says it doesn't know. Any new answer it drafts is saved as a draft for you to approve first, so nothing goes out that you haven't read.

The full feature list shows how the shared inbox, help center, and bot fit together. Every feature is on every plan, from $15 a month, and there are no per-answer fees. You can check the plans and pricing or start a 14-day free trial and load your policy into your first few articles.