Ecommerce customer service: a one-page playbook for a store with 1 to 10 people
Yevhen Kurapov, co-founder · Updated Oct 15, 2026
Ecommerce customer service for a 1 to 10 person store: offer email, website chat and one messaging app. Answer chat within 2 minutes when online, DMs within an hour, email the same business day, never past 24 hours. Publish shipping, returns, FAQ and contact pages. Weekly, track first response time, time to resolution, contacts per 100 orders and repeat contacts.
For a store run by one to ten people, good ecommerce customer service is a handful of decisions written down once: where customers can reach you, how fast you answer in each place, what your policies say, which replies you reuse, who takes over what, and four numbers you check every week. This page is that playbook, with starting targets and a weekly checklist, and it links the templates that fill in the details. Which questions to hand to software is covered in the automation guide. The product notes are from ChatPal, which we make; the playbook works with any tools.
The playbook on one page
| Decision | Starting point for a 1 to 10 person store |
|---|---|
| Channels | Email, website chat, and the one messaging app your customers already write on |
| Reply targets | Chat under 2 minutes while it shows as live, DMs under 1 hour, email the same business day, nothing past 24 hours |
| Published policies | Shipping, returns and refunds, an FAQ page, a contact page with your hours |
| Saved replies | 10 to 15, one per recurring situation, the same text on every channel |
| Handoffs | One owner per conversation, a written refund limit, the whole chat passed on |
| Metrics | First response time, time to resolution, contacts per 100 orders, repeat contacts |
| Routine | 45 minutes every Monday, plus an empty inbox at the start and end of each day |
Which channels to offer
Every channel you list on your site is a promise to answer there. Three channels answered within the hour serve customers better than six answered whenever someone gets to them. Look at where last month's messages came from before adding one: customers show you which channels they want by using them.
| Team | Offer | Leave out for now |
|---|---|---|
| 1 person | Email, website chat, and Instagram DMs or WhatsApp, whichever your customers already use | A phone line you can't pick up during the hours you post |
| 2 to 4 people | The second messaging app if customers already write there, and one shared inbox per channel so everyone sees who has replied | Any channel nobody is assigned to watch |
| 5 to 10 people | A phone line for order problems if you can staff it, a named owner for each channel on each shift, and a help desk such as Zendesk once email needs assigning | Separate tools per channel that give separate answers |
Close the doors nobody watches: a Messenger button on a Facebook Page you stopped posting on, an old address in the footer, a contact form that lands in a forgotten inbox.
Live chat for ecommerce
Live chat reaches shoppers while they're still on the product page. For a small team the risk is a bubble that says "We're online" with nobody behind it, which is worse than an email form. Two setups work: show the chat only during staffed hours and reply within 2 minutes, or let an AI assistant answer first at any hour and pass the chat to a person when the shopper asks for one or the question needs a decision.
ChatPal's website chat works the second way. With Hand off to a human when needed switched on (Configuration, Handoff & leads tab), a chat the assistant passes on gets no more AI replies, appears in Chats under Handed off to a human, and every member of your workspace gets an alert by email or Telegram. If ChatPal is open in a browser tab, the alert also plays a sound, once you have clicked anywhere on the page. Because a visitor can close the tab, the chat also asks for a phone number or email at the hand-off. Here is an example conversation we wrote for this page:
Customer: The jacket I got is the wrong size. Can I talk to someone?
Assistant: Our team has your message and will reply to you here in this chat. In case you leave the page, you can leave your phone or email in the form below.
[Contact form: Phone or email, with Send and No thanks]
The default line never promises a reply time. To tell customers when a person will reply, write your own escalation message, such as "Our team is back at 9 am ET, Monday to Friday, and will reply here." ChatPal sends it exactly as written, and Copilot can rewrite or translate it for you.
Response-time targets
First response time runs from a customer's first message to the first reply that deals with it. An automatic "we got your message" doesn't count; a person's reply does, and so does an assistant's answer that settles the question.
These are the targets we'd start a small store on. They are our recommendation, not an industry average:
| Channel | While you're open | Outside your hours |
|---|---|---|
| Website chat | Under 2 minutes, if it shows as live | An assistant answers, or a form promises a reply by a stated time |
| Instagram, Messenger, WhatsApp | Under 1 hour | First thing next morning, never past 24 hours |
| Same business day | Next business morning | |
| Phone, if you offer it | Picked up during the posted hours | Voicemail returned by the next business day |
| A damaged, wrong or missing order, any channel | Within 4 business hours | First thing next business morning |
On messaging apps, 24 hours is also a platform rule. Chat tools connect to WhatsApp, Instagram and Messenger through Meta's platform, where a business can send a WhatsApp customer a regular reply only within 24 hours of their last message, and only a pre-approved template after that. On Instagram and Messenger the standard window is also 24 hours, and a later message needs a tag for an allowed purpose. A DM left from Friday evening to Monday morning is outside that window.
Publish your targets on the contact page and in your away message: "We answer chat and DMs within an hour, 9 am to 6 pm ET, Monday to Friday, and email within one business day." A promise you keep beats a faster one you miss. These auto-reply examples include away and holiday messages that name your hours.
The policies to publish
Every question a policy page answers clearly is one fewer message, and the same page is what you, your team and any assistant quote from. Five pages cover most of it:
- Shipping policy. Processing time and order cutoff, carriers, costs, the free-shipping threshold, delivery estimates, and what happens when an order runs late. In the US, the FTC's Mail Order Rule requires a reasonable basis for the shipping time you state, or for shipping within 30 days if you state none; when you can't make it, you must ask the customer to accept a revised date and offer to cancel for a full refund. Start from the shipping policy template.
- Return and refund policy. The return window, the item's condition, who pays return shipping, exchanges, refund timing, and what can't come back. The return policy template walks through these choices and the US, EU and UK rules.
- FAQ page. The questions customers actually send, in their words, each with one answer in figures. The FAQ page template has 40 to start from.
- Contact page. Every channel you answer, your hours, your reply targets, and a line asking for the order number.
- Privacy policy and terms. Few messages are about them, but your checkout links to them.
On Shopify, the shipping, return, privacy, terms and contact information policies live under Settings > Policies and are linked in the checkout footer once added.
Write figures, not adjectives. "Orders placed by 2 pm ET ship the same day" can be quoted by a person, a saved reply and an assistant alike; "fast shipping" can't. When a policy changes, update every copy the same day: the page, the saved replies and whatever your assistant reads. In ChatPal, open the ⋮ menu next to that page's link and choose Reindex.
Saved replies
Saved replies mean everyone on the team gives the same answer, and a reply from your phone takes a few taps. Start with 10 to 15, one per situation that keeps coming back:
- Where is my order, with the tracking link
- A parcel that is late or stuck in transit
- A damaged or wrong item, asking for the order number and a photo
- How to start a return
- When the refund will arrive
- Sold out: when it's due back, and an alternative
- A discount code that won't apply
- Cancelling or changing an order
- A new delivery address after ordering
- A complaint: acknowledge it, name the next step and when it will happen
Personalise the first line and keep the policy part word for word. Keep one master copy in a shared document and paste the same text into each inbox's saved-reply feature; in the WhatsApp Business app, quick replies hold up to 50 and appear when you type "/" in a chat. Thirty copy-ready replies cover these situations and mark which ones need a person.
If you answer from ChatPal's inbox, the sparkle button next to Send drafts the reply the assistant would give from your knowledge and instructions. Nothing goes out until you press Send, and each draft counts as one message.
Handoffs: who answers what
A small team doesn't need a process manual, but it needs four rules written where everyone can see them:
- One owner per conversation. Whoever replies first owns it until it's resolved or passed on by name. In ChatPal, Take over at the top of a chat tells the others you're handling it.
- Pass the context, not the customer. Hand over the order number, what has been promised and the next step. The customer should never type their order number twice.
- A written limit for decisions. Say what anyone can do without asking, for example a refund or store credit up to [$50], or one free replacement per order, and who decides above that. Nobody should wait a day for the owner to approve a $12 refund.
- Cover your hours, or say you don't. Name who watches the inbox on weekends and holidays. If nobody does, your away message says when you'll be back.
The same rules hold when an assistant replies first. ChatPal hands a chat to your team when the customer asks for a person, or when a message matches a category you set to Human escalation, such as "Damaged or wrong item". It stays silent while you reply from ChatPal, and Return to AI hands the chat back. The chatbot guide covers that setup step by step.
The four metrics worth tracking
Help desks offer dozens of customer service KPIs. A team of one to ten needs four, checked weekly:
| Metric | How to measure it | Starting target | When it slips, look at |
|---|---|---|---|
| First response time | Median per channel, in business hours, plus the longest wait of the week | The targets above | Channels without an owner, or hours nobody covers |
| Time to resolution | Median time from the first message until the customer has the answer or the fix | Questions settled in the first reply; order problems with a fix under way within 2 business days | Decisions waiting on one person, a carrier or a supplier |
| Contacts per 100 orders | Conversations in the week, divided by orders in the week, times 100 | Your first month as the baseline, then lower | Whichever topic grew: an unclear policy, a late batch, a product page missing a fact |
| Repeat contacts | Share of customers who wrote again about the same thing within 7 days | Falling month to month, with every one read | Answers that sounded complete but didn't settle it |
Use the median because one email left over a weekend pulls an average up; the longest wait shows that worst case on its own. Use contacts per 100 orders because total messages rise with sales. Skip satisfaction surveys and NPS at this size, since a handful of answers a week is too few to show a trend, and average handle time, which rewards short replies over complete ones.
You don't need a help desk to measure this. Each week, take 20 conversations and note the channel, the topic, the times of the first message, the first real reply and the resolution, and whether the customer came back within 7 days. Chats an assistant settles alone get a first response in seconds, so time the gap between a hand-off and your own first reply instead. In ChatPal, Analytics shows conversations by channel and how many were handed to a person. Add Categories for your main topics (the Analytics only type counts a topic without changing what the assistant does) and it shows how many conversations matched each one.
The weekly routine
Forty-five minutes every Monday, in this order:
| Step | Time | What to do |
|---|---|---|
| 1. Update the numbers | 10 min | Sample 20 of last week's conversations and fill in the four metrics |
| 2. Read every repeat contact | 10 min | Find why the first answer didn't settle it, then fix the page, the saved reply or the assistant's instructions |
| 3. Read the handoffs | 10 min | For each, decide whether it needed a person or showed a missing fact, and write that fact where it belongs |
| 4. Check the top three topics | 5 min | Make sure a page answers each one; if not, add it to the FAQ or the product page |
| 5. Sync the answers | 5 min | Any policy, price, carrier or cutoff that changed goes into the page, the saved replies and the assistant |
| 6. Look at next week | 5 min | Holidays, sales, restocks, carrier delays: write the message now and update your away message |
Every day, empty each inbox at the start and the end of the day and check the hand-off queue before you log off. Every month, reread your policies and rerun your key test questions; in ChatPal, Assistant Tests checks them against the answers you expect, and each graded reply counts toward your monthly messages.