If you staff your support team the same way at 9am and 3pm, you're either overstaffed in the afternoon or understaffed in the morning. Ticket volume isn't evenly distributed across the day, the week, or the year. It follows patterns, and those patterns are remarkably consistent across industries.

The Daily Pattern

For most B2B SaaS companies in the US, ticket volume follows a double-hump pattern:

First peak: 9am to 11am local time. People arrive at work, open their tools, discover things aren't working, and contact support. This is the biggest volume spike of the day.

Lunch dip: 12pm to 1pm. Volume drops 30 to 40% as people eat lunch.

Second peak: 2pm to 4pm. Smaller than the morning peak but still above average. People are deep in their work, hitting edge cases and needing help.

Evening decline: 5pm to 8pm. Volume drops steadily. By 8pm, it's 10 to 20% of peak volume.

Overnight: 9pm to 7am. The lowest volume, typically 5 to 10% of peak. But for companies with international users, overnight volume can be 20 to 30% of peak because it's daytime somewhere else.

For B2C companies, the pattern shifts. Peak volume is often 6pm to 9pm, when people are home from work and finally have time to deal with the thing that's been bothering them all day. E-commerce peaks on weekends, especially Sunday evenings.

The Weekly Pattern

Monday is almost always the busiest day. Tickets that accumulated over the weekend hit the queue first thing Monday morning. Users who discovered problems on Saturday and waited until "business hours" all submit at once.

Tuesday through Thursday are steady, at about 80 to 90% of Monday volume.

Friday dips slightly (85% of Monday). People are wrapping up their week and less likely to start a support conversation they can't finish.

Saturday and Sunday vary by industry. B2B sees a 60 to 70% drop. B2C sees maybe a 30% drop. E-commerce might see higher weekend volume than weekday (people shop on weekends).

The Seasonal Pattern

January: spike. New Year, new budgets, new tools. Companies onboarding new software generate tickets. New Year's resolutions drive sign-ups in fitness, education, and productivity. January is typically the highest-volume month for SaaS.

March/April: steady. Normal volume.

June through August: dip. Summer vacations reduce B2B volume by 10 to 20%. B2C holds steady or increases (travel and hospitality see summer peaks).

September: spike. Back-to-school, back-to-work. Similar to January but smaller.

November/December: split. E-commerce explodes (Black Friday through Christmas). B2B drops (end-of-year wind-down, holidays).

What to Do With This Data

Staff to the pattern, not the average. If your Monday morning volume is 2x your Wednesday afternoon volume, don't staff them equally. Put your best agents and your highest staffing on Monday morning.

Set SLAs by period. Your 1-hour response time SLA might be achievable on Tuesday afternoon but impossible on Monday morning. Either staff Monday morning to meet the SLA, or set a different expectation: "Response times may be longer on Mondays."

Use AI for the predictable spikes. Monday morning and the September onboarding rush are predictable. AI handles the simple queries during the spike so your human team can focus on the complex ones.

Schedule maintenance and deployments for low-volume periods. Don't push a major update on Monday morning. Do it Tuesday afternoon or Wednesday evening. If something breaks, the support impact is lower.

Plan PTO around volume patterns. Your support team all wants the week between Christmas and New Year off. If you're a B2B company, that's your lowest-volume week of the year. Let them go. If you're e-commerce, that's your highest-volume week. Plan accordingly.

Your Specific Data

These are general patterns. Your specific data might differ. A company serving Australian customers from a US team will see a different distribution. A company with a developer-heavy user base might see late-night volume (developers work odd hours).

Supp's analytics dashboard shows your actual ticket volume by hour, day, and week. After 30 days of data, the patterns become clear. Use them.

The companies that match staffing to volume patterns (instead of staffing evenly) typically reduce costs by 15 to 25% while improving response times during peak hours. You're not spending more. You're spending smarter.