How to scale customer support as your store grows
At an illustrative contact rate of 5%, 80 orders a month would mean four support conversations, 500 orders would mean 25, and 3,000 would mean 150. Your workload will also depend on the products you sell and how long each question takes to resolve.
This guide covers four broad stages by monthly order volume: 0–100, 100–1,000, 1,000–5,000, and 5,000+. Use these ranges as a guide, not hiring thresholds. Time spent on support and missed replies are better reasons to change your setup.
Stage 1: handling support yourself
0–100 orders / monthWhen you handle support yourself, customer questions compete with packing orders, updating products, and keeping the store running.
Those early conversations can reveal missing product details or unclear delivery terms. Keep a short list of recurring questions and use it to improve your product pages and policies.
A few conversations a month may fit comfortably into your day. If they keep interrupting other work, set aside time to answer them and tell customers when to expect a reply.
What works at this stage
Shared inbox
A single address ([email protected]) can be enough to start. Mark messages that still need a reply and check them at set times.
FAQ and chatbot basics
Write clear answers about shipping, returns, and sizing. If these questions keep coming up, try a chatbot using the same information and review its answers.
Product discovery
Use your catalog to answer product questions and suggest relevant items. Review unanswered questions to find details missing from your product pages.
Set response expectations
Choose a response window you can meet, such as one business day. Make clear when a person will reply, including over weekends.
Stage 2: sharing the workload
100–1,000 orders / monthIf someone else starts helping with support, agree who checks the inbox and who follows up. Otherwise, two people may answer the same question while another customer waits.
Track the hours support takes each week, including follow-ups. If unresolved cases keep delaying replies, consider part-time help. The right time to hire depends on workload, coverage, and budget, not a fixed order count.
Look for repeated questions you can answer with clearer content or automation. Keep complaints, damaged deliveries, and exceptions with someone who can make a decision.
What changes at this stage
Give customers a route to a person
For disputes, damaged goods, or requests outside your policies, explain how to reach your team and when to expect a reply. Assign someone to follow up.
Review unanswered questions
Check which questions come up often, which answers need correcting, and when replies are late. Use those findings to update your content and coverage.
Make order status easy to find
Send tracking links and delivery updates through your order system. Customers may still need help with a missing parcel or an unclear status.
Follow up on unresolved problems
Keep track of promised refunds, replacements, and callbacks. A conversation is not finished just because your team has sent a reply.
Stage 3: coordinating a team
1,000–5,000 orders / monthOnce several people answer customers, each conversation needs a clear owner. Shared notes and agreed return and refund procedures help colleagues pick up where someone else left off.
Measure the time your own cases take before estimating staffing needs. In the earlier example, 150 conversations at an assumed six minutes each would take 15 hours a month. That is only an illustration: follow-ups, complex cases, and time spent reviewing answers add work.
If you sell in Dutch, French, or other languages, check that customers can get accurate product and policy information in each one. Decide who reviews translated answers and handles questions the chatbot cannot resolve.
What to put in place
Multilingual support
Check delivery, return, and product answers in each language you offer. Arrange a review by someone who knows the language and your policies.
Multi-store management
Keep each store’s catalog and policies separate. Check that the chatbot uses the right store’s prices, delivery terms, and return instructions.
Team collaboration
Assign an owner to each open conversation. Leave a short note when handing it over so the next person knows what has been promised.
Written procedures
Write down how to handle returns, refunds, and complaints, including who can approve an exception. Update the instructions when your policies change.
Delivery updates
Send tracking updates automatically through your order system so customers can check progress. Keep a route to your team for delays and missing parcels.
Customer data
Check what customer data your support tools store, who can access it, and how to delete it. Read the provider’s data processing agreement for processing locations and subprocessors.
Stage 4: preparing for busy periods
5,000+ orders / monthAt higher order volumes, plan for busy periods and absences as well as an average week. You may need dedicated support staff, but the number depends on case complexity and the hours you cover.
Before a promotion or holiday rush, review last season’s workload and expected orders. Check that delivery information is current, decide who handles urgent cases, and arrange extra cover where needed.
During the peak, watch the oldest unanswered conversations and check a sample of automated replies. Adjust staffing or answers when you see delays or repeated mistakes.
Before the next peak
Check these five things against your expected workload:
- Capacity: check message and product limits, and what happens if you reach them.
- Provider support: know how to report an outage and what response time is offered.
- Connected tools: check that order and customer details reach the people who need them.
- Extra cover: plan who handles overflow, weekends, and staff absences.
- Consistent answers: use the same current policies across chat, email, and social media.
Comparing the stages
These are examples, not required upgrades. Compare plans by catalog size, messages, users, and languages rather than orders alone.
| Solo founder | Small team | Growing team | Larger operation | |
|---|---|---|---|---|
| Orders / month | 0–100 | 100–1,000 | 1,000–5,000 | 5,000+ |
| Common concern | Finding time | Sharing work | Clear ownership | Peak coverage |
| Useful tools to consider | FAQ and saved replies | Handoff and conversation review | Shared notes and language support | Order updates and channel coordination |
| Mikabot option (monthly) | Free €0 | Regular €13 | Webshop €29 | Business €99 |
Start where you are. Scale when you are ready.
Whether you are packing your first orders or managing a team across four countries, there is a support setup that fits your stage. The main downside is not choosing a system, but waiting until service quality is already visible to your customers.
No credit card · Set up in minutes