Peak season is a rerun, not a surprise
Whatever your peak is — Black Friday, enrollment week, tax season, launch day — last year's transcripts already contain this year's questions. Peak planning is mostly the discipline of reading them in October instead of rediscovering them in December.
Four weeks out: pre-write everything
- Pull last peak's transcripts and list the top questions. Shipping cutoffs, availability, returns windows, seasonal pricing — the list is shorter than you fear.
- Write or refresh one KB article per question, dated for THIS season (a "2025 holiday shipping deadlines" article surfacing in 2026 is worse than none).
- Retrain the AI on the refreshed articles so the seasonal tier is absorbed before it arrives — peak volume is disproportionately the repetitive tier, which is exactly what the AI layer is for.
- Update the canned library with the season's specifics, so agents answer the cutoff question in one keystroke instead of forty.
Two weeks out: tune the widget
- Narrow proactive invitations to the money pages only. Peak traffic makes every trigger fire more; an invitation that was pleasantly rare in April is wallpaper in December.
- Set honest operating hours for the season — extended if you are extending, unchanged if you are not. The offline layer carries whatever you do not staff.
- Put the cutoff answer on the page itself. The cheapest peak conversation is the one your checkout page prevented.
Borrowed help only works pre-trained
Colleagues drafted in for the rush follow the same onboarding arc, compressed: read transcripts now, shadow this week, answer the routine tier during the peak — with their own scoped logins created in advance, not at 9am on the busiest Monday. A helper answering with wrong information at peak costs more than the queue they shorten.
During: watch two numbers, drop the rest
Missed chats (your honesty gauge — if it climbs, shorten displayed hours or add a body) and first-response median (your saturation gauge — if it doubles, agents are over their honest concurrency cap). Everything else can be reviewed after; these two you steer by daily.
The day after matters as much
Peaks end with a debt: the offline messages and unfinished follow-ups of the last big day. Schedule the morning-after triage shift in advance — oldest first, before the widget goes online — and hold one short retro while it is fresh: which question surprised you, which article was missing, which trigger misfired. Write it down; that document is next year's four-weeks-out list, already done.