Curious how other store owners are managing this stage of growth.
Once support volume goes past what you can handle solo (or with one part-time
person), what did you switch to? A few options I keep seeing discussed:
What worked, what didn’t, and roughly what point in growth did you make the switch?
Trying to figure out the right stage to make this move.
@philanichade
I think it depends more on ticket complexity than store size.
If most questions are repetitive order status, shipping times, returns, FAQs first invest in a good help desk and some automation before hiring more people. That can eliminate a surprising number of tickets.
Once support starts taking several hours every day a dedicated VA is usually the next logical step. Its a relatively low-risk way to extend coverage while keeping costs under control.
only move to a full outsourced team or build an in house support department when the volume is consistent enough to justify it or when you need extended hours and multiple agents.
One thing that made the biggest difference for us was documenting common responses and creating clear SOPs early. Whether the work is done by a VA, an agency, or an employee having consistent processes makes onboarding much easier and keeps the customer experience consistent.
This is really helpful, thank you. The “ticket complexity over store size” point
makes a lot of sense, I hadn’t thought about it that way.
Quick follow-up: when you made the jump from VA to a full outsourced team, how did
you handle quality control? That’s the part I’m most nervous about, worried about
losing the consistency you mentioned once more people (or an agency) are involved.
Also curious, did you write your SOPs before or after bringing someone on? Trying
to figure out if I should have all of that documented first or if it’s something
that gets refined once you actually see where people get stuck.
Hi @philanichade
I think having your SOPs documented before bringing someone on makes the transition much smoother, even if they’re not perfect. The first few weeks will naturally highlight gaps, and you can refine the documentation based on real scenarios.
For quality control, it also helps to review a sample of tickets regularly, provide feedback, and keep a shared knowledge base that everyone follows. That way, as the team grows, responses stay consistent and new team members can get up to speed much faster.
From what I’ve seen, the transition usually happens when customer support starts taking time away from running and growing the business rather than just fulfilling orders.
Many merchants take a staged approach:
the biggest lesson is to optimize the support process before adding more people. If the same questions keep coming up, improving your help center, automating common workflows, or simplifying the customer journey can significantly reduce ticket volume. That way, when you do hire, your team can focus on higher-value customer interactions instead of answering the same questions repeatedly.
Before you decide between a VA and an outsourced team, spend twenty minutes categorising your last 100 tickets. The answer usually falls out of that, and it is often “neither, yet”.
@rshrivastava63 is right that complexity beats store size. I would push it one step further: the categories are not equally worth solving. Most stores at this stage find the pile splits roughly three ways. Pre-purchase product questions — will this fit, is it compatible, what is it actually made of, when will it arrive. Order status. Then the genuinely one-off problems.
Only the third group needs a person. The first group is the one worth attacking first, because those questions repeat almost word for word between shoppers, and every one you answer privately over email gets asked again next week by someone else. Answering them where they are asked — on the product page, publicly — removes the ticket and helps the next shopper at the same time. Order-status volume mostly goes away with a tracking page and a shipping-confirmation email that actually says when it ships.
Do that first and the hiring question gets much easier, because you are staffing the real remainder instead of the raw number. The stores I have seen jump straight to a VA end up paying someone to retype the same six answers.
On the SOP follow-up: those ticket categories are your SOP outline. Write one canned answer per repeated question before anyone starts, and quality control gets concrete — you are checking whether the person used the right answer, not judging tone in the abstract.
One caution on tooling: be careful with anything that promises to deflect tickets with AI before you have looked at what your tickets actually are. If 60% of them are one sizing question, the fix is a sizing answer on the product page, not a bot.
We build a product Q&A app for exactly that first bucket, if it is useful — AC ‑ Questions & Answers - Showcase product questions and answers directly on product pag | Shopify App Store — but the categorise-your-last-100-tickets exercise is worth doing whatever you end up using.