Here's how support scales as you build toward $100K/month and beyond: at $30K/month, it's 4–5 hours a day and you're already behind. At $100K/month, it's full-time for two people — and if you haven't built a system yet, reviews are getting worse and chargebacks are climbing. The goal is to have the support infrastructure in place before you need it, so scaling ad spend never hits a service ceiling.
The "support wall" is where most stores stall — the founder can't scale because they're doing 80 tickets a day, and they can't hire because they don't have a system for someone else to follow. Here's how the top 7-figure operators break through.
The ticket-volume cliff
Support ticket volume scales faster than revenue because:
- Order volume scales linearly with revenue.
- Ticket rate per order is relatively constant (typically 8–15%).
- But ticket complexity scales with brand age — more returns, more edge cases, more long-tail issues.
The founder-only model dies around the $30K–$50K line. Past that, it's systems or burnout.
The 3-tier ticket model
The single biggest mental shift: not all tickets are equal, and they shouldn't all get the same level of response.
Tier 1: Fast human triage (60–70% of tickets)
Order tracking, "when will it arrive," return policy questions, basic product questions. These are simple but volume-heavy — the goal is speed and consistency, not cleverness. Hire a VA from the Philippines (we go into detail on where to find them below), and you can get a great one for around $3/hour. Have them check the inbox 3 times a day — morning, midday, and evening — so no ticket sits longer than about 8 hours. That's usually faster than the "within 24 hours" promise most stores make and it costs almost nothing.
For access: at the very start, password sharing is good enough. Just give your VA the Shopify login and inbox credentials — you're not SOC 2 compliant yet and you don't need to be. Once you're doing real volume, upgrade to a Shopify plan that supports multiple staff accounts so you can add them with their own email and revoke access cleanly. Before they start, hop on a 1-hour call and screen-share a walkthrough: where orders live, how to look up a customer, how to issue a refund, where the macro library is, and how to escalate anything weird to you. One hour is enough — if it takes two, you're over-explaining.
Tier 2: Human standard (25–35% of tickets)
Address changes, lost packages, product questions needing judgment, minor complaints. A trained support agent handles these with macros (pre-written response templates) for efficiency. Target: 90%+ resolved in one reply.
Tier 3: Human escalated (5–10% of tickets)
Angry customers, chargebacks, major quality issues, potential PR problems. These get human judgment and often founder attention. These are also the tickets where a thoughtful reply can turn a detractor into a loyal advocate.
| Tier | Volume | Response time | Who | Cost per ticket |
|---|---|---|---|---|
| 1 — Triage | 60–70% | <8 hours | VA (3 check-ins/day) | $0.25–$0.50 |
| 2 — Standard | 25–35% | <4 hours | VA with macros | $0.80–$1.50 |
| 3 — Escalated | 5–10% | <12 hours | Senior agent / founder | $4–$8 |
Total blended cost at $100K/month: roughly $800–$1,200/month for 500 weekly tickets. Compare to founder time at $50/hour: $800+/month without the system, and you're the bottleneck.
Macros and canned responses
A macro is a pre-written reply that a support agent can customize in 30 seconds. The best macro libraries cover 80%+ of Tier 2 tickets. Build yours over the first 200 support tickets you handle personally — every time you type a response, save a version as a template.
The 15 macros every store needs
- Order confirmation (shipping ETA)
- Delayed shipping (with apology + guarantee)
- Address change request
- Cancellation request (before shipping)
- Cancellation request (after shipping)
- Return authorization + instructions
- Refund processed (with timing)
- Product usage question (with FAQ link)
- Wrong item received
- Damaged item received
- Size/fit question
- Lost package (investigating)
- Lost package (replacement shipping)
- Complaint acknowledgment (empathy + next step)
- Chargeback response template
Each macro should have a placeholder for personalization — the customer's name, order number, and one specific detail about their situation. Never send a macro that reads like a macro.
Before finalizing any macro, read it out loud. If it sounds like a robot or a legal disclaimer, rewrite it until it sounds like a person who cares. At scale, the macros are the brand voice. Generic macros create generic support, which creates generic customer relationships.
When to hire and from where
Timing is almost always "later than you should." Here's the right sequence:
At $25K/month: Hire your first VA from the Philippines
Go to OnlineJobs.ph (cheapest, biggest pool), post a listing for a part-time customer support VA, and pay around $3/hour to start. You'll get solid English speakers with e-commerce experience. Have them check the inbox 3 times a day and follow your macro library. Password-share at first; upgrade to a Shopify plan with staff accounts once volume justifies it. One hour of onboarding screen-share is all it takes.
At $40K/month: Hire part-time VA (20 hrs/week, ~$500/month)
Look at OnlineJobs.ph, OkayRelax, or Virtual Staff Finder. Filipino VAs in this price range are typically excellent English speakers with e-commerce experience. Hand them your macro library. They handle Tier 2.
At $75K/month: Scale VA to full-time (~$1,000/month)
Same VA, 40 hours. Add SLAs: 4-hour response for Tier 2, all tickets resolved within 24 hours.
At $100K/month: Add a second VA + rotate coverage
Two VAs at 20 hours each covering weekends lets you offer faster response times. You still handle Tier 3 but it's now 3–5 tickets a day, manageable alongside running the business.
At $250K+/month: Hire a CS manager
US-based or senior Filipino manager ($1,500–$3,000/month) who manages the VAs, owns the macros, and handles Tier 3. You're fully out of support at this point.
The KPIs that matter
Three numbers to track weekly:
- First response time: Target <4 hours during business hours. Over 12 hours and you'll see review and chargeback impact.
- One-touch resolution rate: Percentage of tickets resolved in one reply. Target 70%+. Lower = your macros aren't covering enough cases.
- CSAT (customer satisfaction): Post-resolution survey. Target 90%+. Under 85% and something is broken in the response quality.
Turning support into a revenue center
The top 1% of support operations aren't cost centers — they're revenue drivers. Three tactics:
- Save offers on cancellation: When someone requests to cancel pre-shipment, offer 20% off to keep the order. Recovers 25–40% of cancellations. Pure margin.
- Complementary product on lost packages: When you ship a replacement for a lost package, include a small complementary sample. Drives cross-sells and turns a negative into a positive.
- Win-back discount on Tier 3 resolutions: After resolving a complaint, include a "thank you for your patience" discount for their next order. 30–40% redemption rate, and the customer who was about to leave becomes a repeat buyer.
Support isn't a cost center in a well-run store. It's the most efficient channel you have for turning ambivalent customers into evangelists — at roughly $2 per conversion.
The $100K/month operators solved support on the way up. It's the boring, unglamorous infrastructure that lets them stay at $100K instead of hitting the wall at $40K and bouncing off. Build it before you need it.
