In February 2024, a B2C e-commerce company noticed something weird in their ticket data. Mondays had higher volume than Fridays (expected). January had higher volume than August (expected). But when they overlaid weather data from their primary customer markets, a new pattern appeared.

Rainy days had 15% more tickets than sunny days in the same city. Snow days had 22% more. And the composition of tickets changed: bad weather days had more "impulse" tickets (password resets, account recovery, "how do I..." questions) and fewer considered tickets (feature requests, integration questions).

The theory: when people are stuck indoors, they finally deal with the digital housekeeping they've been putting off. That includes contacting your support.

The Indoor Effect

The correlation between bad weather and digital engagement is well-documented in adjacent fields. Retail analytics firms have shown that online shopping spikes during rainy weekends. Social media usage increases during storms. Mobile app downloads correlate with snowfall.

The support version of this: customers who've been meaning to fix that thing, reset that password, or ask that question finally do it when they're stuck inside with nothing else to do.

For B2C companies, this means support volume is partly a function of how many of your customers have free time today. Bad weather creates free time. So do holidays, long weekends, and school closures.

For B2B companies, the effect is weaker because business users contact support during work hours regardless of weather. But it still exists: WFH days (which correlate with bad weather) tend to have slightly higher ticket volume because employees have fewer office distractions and more time to deal with tool problems.

What Changes by Season

Winter (December to February in the Northern Hemisphere):

Peak ticket volume for most businesses. Holiday gift returns, subscription renewals from holiday purchases, new-device setup questions, and account recovery (people got new phones and can't log in). Combined with the indoor effect from cold weather, winter is typically the highest-volume quarter for support.

Spring (March to May):

Volume normalizes. The post-holiday spike subsides. Steady-state volume with occasional spikes around spring break (B2C) and end-of-quarter (B2B).

Summer (June to August):

Lowest B2B volume of the year. People are on vacation. Decision-makers are unavailable. Projects slow down. Support volume drops 10 to 20% for most B2B SaaS.

B2C is more mixed. Travel and hospitality see summer peaks. Retail sees a summer dip. Subscription services see higher churn in summer (people cancel subscriptions they're not using while they're busy with outdoor activities).

Fall (September to November):

Back-to-school and back-to-work create a volume spike in September. Black Friday through Cyber Monday creates the single highest-volume week for e-commerce support. B2B sees a push in Q4 as budgets are spent before year-end.

Staffing to Weather

You obviously can't staff based on the weather forecast. But you can:

Build weather-adjusted baselines. If you know that rainy Mondays have 20% more volume than sunny Mondays, your staffing model should account for weather as a variable. Pull historical data, overlay weather, and build a regression model. It doesn't need to be sophisticated. "Add one agent on days when the forecast for our top 5 markets shows rain" is a reasonable heuristic.

Pre-position AI for weather-correlated ticket types. If snow days drive password resets and account recovery, make sure your AI auto-responses for those intents are tuned and tested. The incremental volume from a snow day is almost entirely in categories AI can handle.

Adjust SLAs on known high-volume days. If you know January Mondays are your busiest, set realistic expectations. A slightly longer SLA that you consistently meet is better than a tight SLA you miss every January.

The Sentiment Shift

Weather affects not just volume but sentiment. Tickets submitted on gloomy days tend to have slightly more negative language than tickets submitted on sunny days. The effect is small but measurable across large datasets.

This doesn't mean you should treat rainy-day tickets differently. It means your CSAT scores on rainy days may be slightly lower for reasons that have nothing to do with your support quality. If you're analyzing CSAT trends, control for weather. A CSAT dip during a week of winter storms might not mean your support got worse. Your customers might just be in a worse mood.

The Fun Part

If you want to do this analysis yourself, it takes about 2 hours.

Export your ticket data with timestamps. Group by day. Pull historical weather data for your top 5 customer zip codes (NOAA has free historical data, Weather Underground has city-level archives). Merge on date.

Chart ticket volume against daily weather conditions (clear, rain, snow, extreme heat). Run a simple correlation.

The patterns will surprise you. And if nothing correlates, you've still done an interesting analysis that demonstrates data literacy to your team and leadership.

Supp's analytics export (CSV or JSON) gives you the ticket data with timestamps and intent classifications. Cross-referencing with weather data takes the analysis from "how many tickets" to "what types of tickets correlate with what weather." Maybe password resets spike on snow days but billing disputes don't. That insight lets you pre-staff the right expertise on the right days.

It's not a game-changing insight. But it's the kind of analysis that makes your support operation smarter at the margins, and the margins compound.