SaaS founders and CX leads treat the in-house or outsourced SaaS help desk decision as a yes-or-no choice. That framing leaves out the hybrid option. A team that picks one side can hire ahead of need or send in-house work to an outside provider.
The better question is, “Which support belongs inside the company, and which works just as well outside it?” Volume outpaces a small in-house team, and coverage gaps open across time zones. Some tickets are too closely tied to the product to outsource.
Most teams land on a hybrid model by necessity, after a coverage gap or a hiring miss forces the decision. The scorecard below lets a team reach it on purpose.
How do SaaS teams choose between an in-house and an outsourced help desk?
SaaS teams score ticket volume, compliance, the feedback loop, and coverage from 1 to 3. The total points to in-house, hybrid, or outsourced.
Most companies stuck in the decision-making process ask, “Does outsourcing hurt the customer experience? Does in-house slow down workflows?” But these questions skip the real issue: fit. For instance, a password reset does not need the same handling as an escalation related to a live data migration.
A more useful strategy is to score the company on four dimensions before making any decisions. Each dimension scores:
- 1 (favors in-house)
- 2 (favors hybrid)
- 3 (favors outsourced Tier 1)
Together, the scores form a SaaS help desk decision framework.
1. Ticket volume and company stage set the size of the team
With roughly 250 Tier 1 tickets per month, one in-house agent can cover the queue. Intercom’s analysis of 5,280 early-stage workspaces finds no current SaaS benchmark and cites a 2026 Gorgias figure of 254 tickets per agent per month for e-commerce.
This article uses 250 as a planning figure that teams should replace with their own data. Unity starts with a core team of three to five agents, so a queue under 250 tickets leaves that team underused.
In any SaaS help desk staffing model, outsourced SaaS support cost is measured against the in-house baseline. The math for one U.S. hire runs in five steps:
- Monthly pay is $3,700, according to the outsourced help desk pricing guide, which uses Indeed data.
- The Bureau of Labor Statistics reports that benefits account for 28.5% of total compensation for sales and office workers, so wages account for 71.5%.
- Total monthly cost is $3,700 ÷ 0.715, or about $5,175.
- At the planning figure of 250 tickets per agent per month, the cost per ticket is $5,175 ÷ 250, or about $21.
- Tools and supervision add to that figure.
Unity’s pricing page lists outsourced Tier 1 support starting at $10.25 per hour in the Philippines or Mexico. At 2,080 hours a year, that is about $1,777 per agent per month, or $7 per ticket at 250 tickets per month.
High Alpha’s 2025 SaaS Benchmarks put customer success and support at 11% of employees below $1M in ARR and 19% from $1M to $5M.
How to score: 1 below 250 tickets, 2 from 250 to 750, and 3 above 750. Volume outranks ARR.
2. Compliance and data sensitivity narrow the vendor list
The Health Insurance Portability and Accountability Act of 1996 (HIPAA) and the General Data Protection Regulation (GDPR) do not rule out outsourcing. But they narrow down who can receive the work.
HIPAA requires a business associate agreement (BAA) before a vendor handles protected health information. GDPR requires a data processing agreement. A System and Organization Controls 2 (SOC 2) Type II report shows that a vendor’s controls have held over time. A vendor without signed agreements and access controls is a liability regardless of the cost.
Tier 1 work without regulated data, such as how-to questions, can move first. Tickets containing health records or EU personal data are transferred after the agreement is signed.
How to score: 1 if most tickets carry regulated data, 2 if some do, and 3 if few do.
3. The product feedback loop decides what stays in-house
Support tickets are one of the sources of product insight for a SaaS company. But the question is how tightly that insight needs to feed back into the product team, and how fast. If the product team relies on support to flag bugs and catch churn risk early, that loop needs to stay tight.
A BPO team can be part of this loop, but only with a clear escalation path and a shared system of record. Agents tag every ticket to the client’s taxonomy in the existing platform, and a weekly review passes patterns to the product team. Without that structure, feedback stays in a ticket queue that the product team never sees.
How to score: 1 if product ships fixes from daily support input, 2 if a weekly review is enough, and 3 if monthly reporting is enough.
4. After-hours and geographic coverage favor outsourcing
If the customer base spans multiple time zones or the company has committed to 24/7 support, in-house coverage quickly becomes expensive. One always-staffed seat takes 168 hours a week (24 × 7). A full-time agent works 40 hours, so coverage takes 168 ÷ 40, or 4.2 agents, before leave. At $62,100 with benefits a year, that is about $260,000 in the U.S. Staffing nights and weekends with in-house hires means paying overtime or building a second shift.
This is one of the clearest answers to the question of when to outsource SaaS support, as explained by SaaS outsourcing for enterprise scalability. After-hours and weekend coverage is exactly the kind of Tier 1 volume that BPO teams are built to absorb. In Unity’s IT company case study, a U.S. client with a 24/7 contract could not find enough applicants for overnight shifts. Unity built a dedicated Tier 1 team and developed APIs to coordinate ticketing and reporting
How to score: 1 for one time zone, 2 for two regions or extended hours, and 3 for 24/7 or multilingual commitments.
Add the four scores. Totals of 4 to 6 favor in-house, 7 to 9 favor a hybrid model, and 10 to 12 favor SaaS customer support outsourcing with a small in-house escalation team.
How does a hybrid help desk model divide the work?
In-house keeps product-adjacent and relationship work. Outsourced handles Tier 1 volume, after-hours coverage, and multilingual support.
For SaaS help desk support, these are the workflows that stay in-house
- Product-adjacent escalations that require deep familiarity with the roadmap or recent releases
- Customer success relationships with high-value or enterprise accounts
- Engineering handoffs where a ticket needs to become a bug report or a feature request
What typically gets outsourced
- Tier 1 volume, such as password resets, billing questions, how-to requests, and other high-frequency, low-complexity tickets
- After-hours and weekend coverage
- Multilingual support for international customers
At 750 tickets a month, three Tier 1 agents and one in-house specialist cover the work. Annual cost by model:
| Model | Tier 1 (3 Agents) | In-house Specialist | Annual Cost |
| All in-house, U.S. | $186,300 | $62,100 | $248,400 |
| Hybrid, Tier 1 outsourced to Unity in the Philippines and Mexico, from $10.25 an hour | $63,960 | $62,100 | $126,060 |
Note: In-house figures are pay plus benefits, before tools and supervision. The Unity figure is the starting rate × 2,080 hours × 3 agents. The specialist costs the same in both rows.
Unity Communications provides the outsourced half of the model
This is where an outsourced partner such as Unity Communications fits in. Unity provides technical support outsourcing services, with trained agents handling Tier 1 volume, after-hours coverage, and multilingual support from offices in Manila and Guadalajara. The client’s in-house team keeps the product-adjacent and relationship-sensitive work.
Unity agents work inside the client’s existing ticketing platform and escalation workflow, such as Zendesk or Freshdesk. Tickets move from Tier 1 to an in-house specialist without the coordination overhead that makes some outsourcing arrangements feel disjointed. Unity starts with a core team of three to five agents. Teams weighing an outsourced SaaS help desk can add agents as volume proves out.
In the offshore IT help desk team for an e-learning company, Unity ran the help desk on Zendesk for a client facing about 700 tickets a day, and reported an increase in user satisfaction up to 92%.
How does AI change the help desk calculation?
AI removes the simplest requests before an agent sees them, so the human queue gets smaller and harder to clear.
Chatbots and self-service tools can now resolve the simplest tickets before a human ever sees them, a process known as Tier 0 deflection. It works best on proven, repeatable workflows, and each team should measure its own deflection rate before changing headcount. A March 2025 Gartner poll of 163 service leaders found that 95% plan to retain human agents.
That supports a people-first design. AI runs in the background to support agents, and people handle the conversations that carry the customer relationship.
AI does not replace outsourced Tier 1 support. It narrows the work to tickets that need a person. With AI, in-house agents can spend more time on complex, relationship-sensitive cases. The BPO team handles what remains after AI deflection: tickets that need a human, but not necessarily one with deep product context. The result is a leaner, more cost-efficient support stack, whether that headcount is in-house or outsourced.
What mistakes do SaaS teams make when building a help desk model?
SaaS teams most often hire in-house too early, outsource without an escalation path, or leave the BPO team out of the feedback loop. The following common mistakes can still catch SaaS teams, even those with a good scorecard.
- Going fully in-house too early. Hiring a dedicated support team before ticket volume warrants it locks in fixed costs that a growing company does not need yet.
- Outsourcing without a clear escalation path. A Tier 1 handoff with no defined route back to engineering or customer success leaves hard tickets stranded.
- Treating the BPO team as separate from the product feedback loop. If outsourced agents cannot flag patterns back to the product, the company loses one of support’s most valuable functions.
- Skipping the compliance check. Assuming that any outsourced vendor can handle regulated data without a signed agreement and audited controls is a compliance risk.
Each mistake has the same fix. Settle the escalation path, the shared ticket data, and the compliance record before the first ticket moves.
