Black Friday and Cyber Monday are the call center Super Bowl. Volume spikes, new agents are on the phones, queues get long and everybody's tired by Monday.

That's exactly when most QA programs go quiet. Evaluators get pulled to the phones, scoring stops and nobody looks at calls again until January.

I think that's backwards. Your busiest days show you more about your operation than any other week of the year. On the podcast I put it this way: "when you have high call volume, when your systems are stressed, you can learn the most" (Advice from a Call Center Geek, "Mastering Black Friday and Cyber Monday," November 20, 2024, 13:47).

Here's how I'd run QA before, during and after peak.

Before Peak: Freeze the Form

My first rule for peak readiness has nothing to do with QA: "So number one is, is easy on the IT updates, whether it's your CRM, whether it's any AI stuff." (November 20, 2024, 04:28)

The same goes for your QA form. Don't launch a new scorecard, reweight questions or add a section in the weeks before your busiest days. If scores move, you want to know it was the calls, not the form.

Do this instead:

During Peak: Change What You Sample

A normal random sample is built for fair agent scores over a month. Peak is different. You care about the calls that break under volume. Adjust your sampling plan for the rush:

Label these as targeted samples in your reports. They'll score lower than your random sample, and that's the point.

What to Score on Peak Days

This is an example layout, not a standard form. Use questions that already exist on your form wherever you can:

Peak risk Question to watch
Long queues Did the agent acknowledge the wait without making it a long apology?
Callbacks When the call was a callback, did the agent explain why they were calling and pick up where the customer left off?
Rushing Did the agent resolve the reason for the call before closing?
Transfers Was the transfer needed, and did the agent tell the customer who they were going to and why?
Bot or IVR handoff Did the agent use what the customer already gave the bot or IVR instead of starting over?
Promotions and policies Did the agent give the correct offer, return or shipping terms?

The callback point matters. I'm a big believer in virtual callbacks on busy days: "make sure that you're offering virtual callbacks" (November 20, 2024, 09:47). And "it's a cost saver for you because you don't just, you're not paying for people in queue." (November 20, 2024, 10:23) But a callback only helps if the call that follows is a good one. Score it.

Same with self-service. If you're adding bots this year, make sure "that it's easy to get to an agent" (November 20, 2024, 16:18). The first minute after a handoff tells you whether that's working. For your own bot's side of those calls, see how to score your AI voice bot's calls.

Feedback: Same Day or It Doesn't Count

Peak lasts days, not months. A coaching note that shows up two weeks later is useless.

The rest of the year, follow the coaching routine I'd use. During peak, keep it short.

After Peak: Write It Down

Don't let the lessons disappear. "document the day" (November 20, 2024, 13:29) is one of my standing peak rules.

Within a week, pull together:

That document is your starting point next year.

Where OttoQA Fits

OttoQA scores calls against your own QA forms. So your peak questions are the ones that get scored, on the form you already use.

The easiest way to see how your calls look through OttoQA is our 200 to 500 call proof of concept: we score 200 to 500 of your calls against your form.

API integrations with all CCaaS platforms. No seat licenses, no IT, and setup takes about 2 weeks. There's a $1,000 one-time setup fee. If you want to plan around peak, start well before it.

Bottom line... your busiest days are the best data you'll get all year. Don't stop scoring.

FAQ

Should you keep doing QA during peak season?

Yes. Peak days show you where quality breaks under volume, which you can't see in a normal week. Shift your sample toward the calls most likely to go wrong, such as long-queue intervals, callbacks, transfers and new agents, and keep feedback short.

Should you change your QA form before Black Friday?

No. Finish any form changes well before peak or wait until after. If you change the form right before your busiest days, you can't tell whether a score change came from the calls or the form.

What should you score on peak season calls?

Focus on the risks that grow with volume: handling the wait, callbacks, rushing to close, unneeded transfers, bot or IVR handoffs, and giving the correct offer or policy. Use questions already on your form wherever you can.

How fast should QA feedback be during peak?

Same day if you can. Peak lasts days, so pick one behavior per agent per shift, use one real call, and send floor-wide updates when many agents miss the same thing.

What should you do after peak season ends?

Write it down within a week. Pull scores by interval, targeted sample results, the top process fixes and any form changes you want to make. That record is your plan for next year.

About the author

Tom Laird is the founder of OttoQA and CEO of Expivia, with about 30 years in contact centers. He hosts the Advice from a Call Center Geek podcast. Connect with Tom on LinkedIn.