Look at your inbound volume by hour. If less than 10% of tickets land outside business hours, you don't need 24/7 — you need a well-designed 16-hour US+EU shift with AI-assisted off-hours triage.
"We need 24/7 customer support" is the most common request we hear from prospects, and it's almost always wrong. The right framing is: what hours do my customers actually need a human? For a typical SaaS or e-commerce business that's usually 14–16 hours, not 24 — and the cost difference is enormous.
This guide walks through how to model the question properly, how to design shifts that don't grind your team down, and the real cost difference between 24/7 and the "extended hours" model most businesses actually need.
Do you actually need 24/7 customer support?
Pull your support volume from your help-desk tool for the last 60 days. Group by ticket-creation hour in your customers' time zone. Now answer three questions:
- What % of tickets land outside your current coverage window?
- Of those, how many are urgent (defined as: customer would churn if we don't answer within an hour)?
- What's the revenue at risk from delayed response on those urgent tickets?
If urgent off-hours tickets are below 5% of volume and below your acceptable revenue-at-risk threshold, you don't need 24/7. You need a clear off-hours auto-reply that sets expectations, plus a fast morning catch-up.
Modeling your support volume properly
Three numbers drive your staffing model:
- Tickets per day, by channel — email, chat, voice. Different tickets-per-agent ratios per channel.
- Peak-hour multiplier — your busiest hour vs. your average hour. Usually 2–3x.
- Service-level target — e.g., "answer 90% of chats within 5 minutes." This drives required concurrency, not just headcount.
For chat especially, peak concurrency drives headcount more than total volume. An agent can comfortably handle 3–4 concurrent chats — push to 6 and CSAT collapses. Plan to peak.
Shift patterns that work for outsourced support
The patterns we see succeed for US + EU coverage:
Pattern A — "Follow the sun" (full 24/7)
Three regions, three shifts: Asia-Pacific covers Americas overnight, Americas covers Europe overnight, Europe covers Asia overnight. Highest cost, highest complexity, only worth it above 800 daily tickets or in regulated industries with hard SLAs.
Pattern B — "US + EU split" (16 hours, the sweet spot)
Two shifts: 06:00–14:00 UTC and 14:00–22:00 UTC. Covers 7am–11pm CET and 1am–5pm EST with a generous overlap at the boundaries. Works for 80% of businesses. Cost-effective, low burnout, easy handover.
Pattern C — "Extended hours" (12 hours)
One stretched shift covering 06:00 EST to 18:00 PT. Covers all US business hours plus EU afternoons. Right answer for US-focused businesses with a small EU long tail.
Pattern D — "Business hours + overnight on-call"
Full coverage during business hours, a single overnight on-call agent for urgent only, defined by a triage threshold (e.g. order failures, payment issues). Cheap and effective when off-hours volume is genuinely low.
How many agents do you actually need?
| Channel | Tickets / agent / day | Notes |
|---|---|---|
| 60–100 | With saved replies + AI assist, top end achievable. | |
| Chat | 3–4 concurrent | Plan for peak concurrency, not average. |
| Voice (inbound) | 30–45 calls | Including after-call work. |
| Mixed | ~70% of single-channel | Context-switching reduces throughput. |
Add a 15% buffer for breaks, holidays and unplanned absence. For a US+EU 16-hour coverage on 300 daily tickets, that's roughly 4–5 dedicated agents with one team lead.
What 24/7 vs extended hours actually costs
- Extended hours (12 hr) — $4,500–$8,500 / month for a small dedicated team.
- US + EU split (16 hr) — $8,000–$15,000 / month for a mid-volume team.
- 24/7 follow-the-sun — $12,000–$25,000+ / month for the same volume.
- Overnight on-call only — +$1,200–$2,500 / month on top of any business-hours model.
Want a coverage plan based on your volume?
Send us your ticket volume by hour and we'll model the right shift pattern and team size for you.
Avoiding burnout on a 24/7 team
Shift design is also a retention problem. Three rules that work:
Sustainable shift design
- Consistent days. An agent who always works Mon–Fri 9am–5pm stays. Rotating weekly shifts double attrition.
- No more than two consecutive night shifts. Health and quality both fall off a cliff after night 3.
- Real handover. A 30-minute paid overlap between shifts. Tickets handed off in writing. No "find out yourself".
- Quiet-hour staffing. Off-peak hours don't mean alone — at minimum, two agents on at any time so neither is the only human awake on the account.
24/7 coverage is a math problem. Sustainable 24/7 is a people problem. The teams that get both right keep customers and agents.
For more on agent retention, see outsourced customer support. For language coverage on top of hours, see multilingual customer support.
Frequently asked questions
Do I really need 24/7 customer support?
Probably not. Most businesses need extended hours (12–16 hours) plus off-hours triage. Only go 24/7 if more than 10% of urgent tickets land outside your current coverage.
How many agents do I need for US and EU coverage?
One agent per 60–100 email tickets per day, or per 25–40 concurrent chats. Plus a 15% buffer. A US-EU 16-hour split typically needs 3–5 dedicated agents minimum.
What shift patterns work best for outsourced support?
Consistent 8-hour shifts with stable days. Rotating shifts double attrition. Use 30-minute paid overlap between shifts for handover.
How much does 24/7 customer support cost?
$12,000–$25,000+ per month for true 24/7 outsourced coverage on low-to-mid volume. Extended hours starts at $4,500 per month.
Can AI handle off-hours support instead of human agents?
For FAQ triage and acknowledgement, yes. For escalations, no. Best model: AI for first response and routing, humans for resolution.