What you'll learn in this article:
Why 100–300 tickets monthly is the tipping point for outsourcing
The specific scope a qualified support partner should fully own
Clear escalation boundaries so you know what stays with you
How to evaluate partners before signing anything
Realistic timelines for the first 60 days
You've crossed a threshold most small ecommerce founders don't talk about: the inbox isn't just annoying anymore. It's actively pulling you away from inventory decisions, marketing campaigns, and the hundred other things only you can do.
At 100–300 support tickets per month, you're past the "I can squeeze this into my morning" phase. You're firmly in "this needs a real solution" territory. But you're not big enough to justify a full-time hire, and you've probably heard horror stories about outsourced support that sounds nothing like your brand.
So what should a good outsourced ecommerce support partner actually handle at this volume? And more importantly, how do you know if someone's equipped to take over without making your customers feel like they've been handed off to strangers?
Why 100–300 Tickets Is the Inflection Point for Ecommerce Stores
This volume range sits in an awkward middle ground. Below 100 tickets monthly, most founders can white-knuckle it—reply during lunch, batch responses at night, maybe rope in a cofounder or VA.
Above 300 tickets, you're usually generating enough revenue to consider a dedicated hire or a more robust support infrastructure.
But 100–300? That's roughly 3–10 tickets per day. Not overwhelming on paper. Absolutely overwhelming when you factor in:
Response time expectations. Ecommerce customers increasingly expect replies within hours, not days. At 5+ tickets daily, one busy afternoon creates a backlog that compounds fast.
Ticket complexity variance. Some are quick "where's my order" questions. Others require investigating shipping delays, processing returns, or calming down frustrated customers.
The hidden time cost. Each ticket isn't just the reply time—it's the context-switching cost of pulling yourself out of whatever else you were doing.
Multi-channel fragmentation. Your tickets aren't just emails anymore. They're Instagram DMs, Facebook messages, and contact form submissions—each with different response expectations and workflows.
At this volume, you're spending roughly 8–15 hours per week on support. That's a meaningful chunk of your capacity disappearing into the inbox instead of toward growing the business.
What a Good Support Partner Should Handle (The Core Scope)
Not every outsourced partner will handle the same things. Some want to cherry-pick easy tickets. Others will overreach into areas that should stay with you. A well-matched partner should own the following completely at this ticket volume:
Order Status and Tracking Inquiries
These are your highest-volume, lowest-complexity tickets. "Where's my package?" "When will it ship?" "The tracking hasn't updated in three days."
A good partner should:
Access your order management system directly (Shopify, WooCommerce, BigCommerce, etc.)
Provide accurate, current tracking information without escalating to you
Proactively communicate when carriers show delays
Set appropriate expectations when shipping timelines are affected by external factors
Boundary check: If they're escalating basic tracking questions to you, something's wrong with their system access or training.
Return and Exchange Processing
Returns processing is where many outsourced arrangements fall apart. The partner needs enough access and authority to actually resolve these—not just collect information and punt it back.
A good partner should:
Process standard returns within your stated policy without approval
Issue return labels through your shipping integration
Initiate exchanges for size/color swaps
Document return reasons (this data is gold for inventory and product decisions)
Required field for your escalation plan: Define dollar thresholds for discretionary decisions upfront. For example: "Approve any return request under $75 without escalation, even if slightly outside the return window."
Pre-Purchase Questions
"Does this run true to size?" "Is this compatible with X?" "Do you ship to Canada?"
These tickets directly impact conversion. Slow or unhelpful responses cost you sales. A trained partner should handle:
Product specifications from your catalog
Shipping destinations and estimated delivery times
Basic compatibility or use-case questions (if you've documented them)
Stock availability and restock timing
Boundary check: Complex product questions requiring technical expertise should route to you. A good partner knows the difference.
Basic Troubleshooting and Issue Resolution
For ecommerce, this typically means:
Password reset and account access issues
Website navigation problems
Payment processing errors (guiding customers to retry or use alternative methods)
Discount code and promotional issues
Boundary check: Anything requiring backend system changes or administrative access beyond your support tools should escalate.
Billing Adjustments Within Defined Limits
Clear policies upfront are essential. Your partner should be empowered to:
Apply small courtesy credits for legitimate service failures (you define "small")
Adjust shipping charges when your error caused a problem
Issue partial refunds for damaged items per your policy
Required field for your escalation plan: What's the maximum credit or refund amount your partner can issue without approval? $25? $50? $100? This needs to be explicit before they handle their first ticket.
Multi-Channel Coordination
Your customers don't just email anymore. A partner equipped for modern ecommerce support should handle:
Instagram and Facebook DMs: These often require faster response times than email. Your partner should monitor these channels during business hours and respond with the same brand voice as email.
Contact form submissions: These should flow into the same ticketing workflow as email—not sit in a separate queue you have to check.
Platform-specific messaging: If you sell on Amazon or Etsy, those message systems have their own response time requirements and should be covered.
Boundary check: Confirm which channels your partner monitors and their response time commitments for each. "We do email support" isn't enough if 30% of your tickets come through Instagram.
What Should Stay With You (The Escalation Boundaries)
Outsourcing doesn't mean handing over everything. At 100–300 tickets monthly, certain categories should escalate to you or your internal team:
High-Value Customer Issues
Define "high-value" by your metrics. Maybe it's customers who've placed 5+ orders. Maybe it's anyone with a lifetime value above a threshold. These relationships warrant your personal attention, at least initially.
Complex Technical Problems
If a customer reports a bug or product defect that requires investigation, your partner should document thoroughly and escalate. They're not product engineers, and they shouldn't pretend to be.
Legal or Policy-Sensitive Situations
Anything involving threats, chargebacks, fraud suspicions, or regulatory compliance needs your eyes. A good partner will recognize these and route appropriately.
Major Exceptions to Standard Policy
When a situation genuinely requires bending your normal rules, you should make that call. Your partner should be empowered for small exceptions—not wholesale policy overrides.
Media or Influencer Contacts
If someone with a significant platform reaches out (even with a complaint), you want to know. The response carries outsized impact.
The Escalation Matrix: Making Handoffs Clean
Vague escalation rules create problems. Either everything escalates (defeating the purpose) or nothing does (leading to mistakes). Use this matrix framework and customize it for your business:
| Situation | Partner Handles | Escalates to You |
| Order tracking inquiry | ✓ All standard inquiries | Carrier confirms lost package |
| Return request within policy | ✓ Approve and process | Return value exceeds $X threshold |
| Return request outside policy | ✓ Up to 7 days past window | More than 7 days or unusual circumstance |
| Customer demanding refund + compensation | ✓ Standard refund only | Any compensation request |
| Product defect report | ✓ Document and issue replacement | Pattern suggesting batch issue |
| Upset customer (reasonable) | ✓ De-escalate and resolve | Threats or abusive language |
| Pre-purchase question | ✓ Standard product info | Technical compatibility requiring expertise |
| Billing dispute | ✓ Clear error on your side | Chargeback notification or fraud suspicion |
| Instagram DM complaint | ✓ Standard response protocol | Viral potential or influencer account |
The key is specificity—both you and your partner need to know exactly where the lines are before the first ticket arrives.
How to Evaluate Whether a Partner Can Handle This Scope
Before signing anything, verify these capabilities:
System Access and Integration
Your partner needs direct access to:
Order management system (Shopify, WooCommerce, BigCommerce, etc.)
Helpdesk or ticketing system (Gorgias, Zendesk, Help Scout, etc.)
Returns management platform if you use one (Loop, Returnly, etc.)
Basic shipping and tracking tools
Social media inboxes (if multi-channel support is included)
Red flag: If they want you to export data or relay information instead of accessing systems directly, that's a workflow bottleneck waiting to happen.
Training and Onboarding Process
Ask specifically:
How do they learn your products and policies?
How long before they're responding to real tickets?
What happens when they encounter something new?
A serious partner will want to review your past tickets, document common scenarios, and draft responses for your approval before going live.
Response Time Guarantees
At 100–300 tickets monthly, you should expect responses within 24 hours maximum on business days. Many situations warrant faster turnaround. Get specific commitments in writing, broken down by channel if you need multi-channel coverage.
Quality Control Mechanisms
How do they ensure responses match your brand voice? Options include:
Sample response review during onboarding
Periodic audits of random tickets
Customer satisfaction tracking
Regular feedback loops with you
Backup Coverage
What happens when their assigned agent is sick or on vacation? You need redundancy. A single person with no backup creates single points of failure—exactly what you're trying to escape by outsourcing.
Ecommerce Tech Stack Familiarity
If you're running Shopify with Gorgias for helpdesk and Loop for returns, your partner should already know these tools. Ask about their experience with your specific stack. A partner who's fluent in Gorgias macros and Shopify order editing will ramp up faster than one learning your systems from scratch.
The Documentation Investment (Don't Skip This)
Outsourcing support well requires upfront investment from you. Not forever, but at the start.
Your partner needs:
Product and Policy Documentation
Return policy with specific conditions
Shipping methods, carriers, and typical timelines
Common product questions and accurate answers
Promotional terms and common discount issues
Saved Replies and Templates
You likely have responses you use repeatedly. Share them. They're part of your brand voice, and they give your partner a head start.
Escalation Procedures
Who do they contact when escalating? How? What information must they include? Write it down.
Access Credentials
Create appropriate accounts with the right permission levels. Don't share your admin credentials—set up dedicated accounts with appropriate access.
The good news: a competent partner will help build this documentation as they learn. They'll create FAQ resources and saved replies as they encounter new scenarios. That documentation then belongs to you.
Realistic Expectations for the First 60 Days
Outsourcing isn't plug-and-play. A realistic ramp-up looks like this:
Week 1: Kickoff call, system access setup, policy review. Partner drafts initial responses for your feedback.
Weeks 2–3: Partner begins responding to tickets with heavy oversight. You're reviewing most responses initially—this is normal.
Weeks 4–6: Partner handles increasing volume independently. Escalations decrease as they learn edge cases.
Weeks 7–8: Routine operation. You're reviewing escalations only, plus occasional spot-checks for quality.
If a partner promises instant results with no ramp-up, be skeptical. Learning your business takes time.
Warning Signs During the Evaluation Process
Watch for these during conversations with potential partners:
Vague pricing tied to unclear deliverables. You should know exactly what you're paying for.
Reluctance to discuss specific processes. Good partners are transparent about how they work.
No questions about your business. If they don't ask about your products, customers, and challenges, they're not preparing to do this well.
Promises that sound too good. "We'll cut your response time to 5 minutes!" might mean they're sending canned responses without reading the ticket.
Long-term contract requirements. At your volume, month-to-month arrangements are reasonable. Annual contracts with heavy cancellation fees should raise questions.
No experience with your platforms. If they've never used Shopify or your helpdesk software, factor in a longer learning curve.
What Good Looks Like (Practical Examples)
A well-trained partner handles common ecommerce scenarios like this:
Scenario 1: "Where's my order? It was supposed to arrive yesterday."
Partner checks order status, sees tracking shows delivery attempted but customer wasn't home. Responds with specific redelivery options from the carrier, explains how to schedule redelivery, and offers to monitor the situation. No escalation needed.
Scenario 2: "I want to return this. I've worn it once but it doesn't fit right."
Partner checks return policy (30-day window, unworn condition required). Worn item is technically outside policy. Partner has authority for small exceptions—assesses situation, offers store credit instead of full refund, generating positive outcome without escalation.
Scenario 3: "Your product broke after one week. This is unacceptable."
Partner validates purchase, confirms timeframe, apologizes sincerely. Offers immediate replacement shipment. Documents the defect report in your tracking system. Escalates to you with summary because this might indicate a product quality issue worth investigating.
Scenario 4: "I'm a blogger with 50K followers. I'd like to discuss a collaboration."
Partner responds professionally, thanks them for reaching out, and explains someone from the team will follow up directly. Escalates with full context. Does not attempt to negotiate or commit to anything.
Scenario 5: Instagram DM complaint about shipping delay.
Partner responds within 2 hours (faster than email SLA given platform expectations). Acknowledges the frustration, checks order status, provides specific update. Offers to continue conversation via DM or email—customer's choice. No escalation unless the complaint escalates.
The Bottom Line
At 100–300 monthly tickets, outsourced support isn't about finding someone to mindlessly clear your inbox. It's about finding a partner who can genuinely own customer relationships on your behalf—with clear boundaries about what they handle independently and what comes back to you.
The right partner will:
Handle the full scope of routine support (orders, returns, pre-purchase questions, basic troubleshooting)
Cover the channels your customers actually use—email, social, and beyond
Operate within defined escalation boundaries without constant hand-holding
Maintain your brand voice so customers don't feel the difference
Build documentation that makes everything run smoother over time
Give you back 10–15 hours weekly to focus on growing the business
That's not a small thing. For a founder at your stage, those hours might be the difference between staying stuck and actually scaling.
Ready to Stop Living in Your Inbox?
If you're handling 100–300 support tickets monthly and want a partner who can own the scope described above—with real humans who learn your business and protect your brand voice—we should talk.
Book a call with Evergreen Support to see if we're the right fit. Or start with a $1 onboarding trial that lets you test the process before committing.
Frequently Asked Questions
How do I know if 100–300 tickets is enough volume for outsourcing to make sense?
At this volume, outsourcing typically costs less than the equivalent hours of a dedicated hire when you factor in benefits, training, and coverage gaps. The real question is whether support is pulling you away from higher-value work. If you're spending 8–15 hours weekly on tickets and that time could generate more value elsewhere, the math usually favors outsourcing.
What if my products are complicated and require specialized knowledge?
Good partners invest time learning your products during onboarding—reviewing past tickets, studying your documentation, and drafting responses for your approval. Complex technical questions should route to you, but a trained partner can handle far more than you might expect if you invest in proper knowledge transfer upfront.
How quickly can an outsourced partner get up to speed on my business?
Expect 2–3 weeks before they're handling routine tickets independently, and 6–8 weeks before the relationship hits full stride. Partners promising instant results without a learning curve are either oversimplifying or planning to use generic responses that won't match your brand.
What happens if my outsourced partner makes a mistake with a customer?
Mistakes happen with any team—internal or external. The question is whether your partner has processes to catch errors, learn from them, and prevent repeats. Ask about quality control during evaluation. A partner who claims they never make mistakes isn't being honest; one who explains how they handle and learn from issues is being realistic.
Can I try outsourcing without a long-term commitment?
You should be able to. Month-to-month arrangements at this volume are reasonable, and trial periods help both sides confirm the fit before committing. Be cautious of partners requiring annual contracts with significant cancellation penalties—especially if they're unwilling to prove their value first.
About Evergreen Support
Evergreen Support is a US-based customer support agency built specifically for small SaaS and ecommerce businesses. Founded by Emma Fletcher and Ellis Annichine after working together at a startup, we understand what it's like to juggle support alongside everything else. Our team handles your email support with real humans—no bots, no scripts, no overseas call centers—so you can focus on growing your business while your customers still get the personal attention they deserve.
Cited Works
[1] Zendesk — "Customer Experience Trends Report 2024." https://www.zendesk.com/blog/zendesk-customer-experience-trends-report-2024/
[2] Forrester Research — "The Business Impact Of Customer Service." https://www.forrester.com/report/the-business-impact-of-customer-service/RES179581
[3] Help Scout — "The Complete Guide to Outsourcing Customer Support." https://www.helpscout.com/blog/outsourcing-customer-support/
