Monday morning. The all-hands call. The CEO announces layoffs. Your support team of 8 is now 4. The laid-off agents clear their desks by noon. By 1 PM, the ticket queue is the same size it was at 8 AM, but you have half the people to handle it.

The remaining 4 agents are in shock. They just watched their coworkers get let go. They're wondering if they're next. They're processing grief and anxiety while staring at a queue that's growing faster than they can work it.

Ticket volume doesn't know about layoffs. Customers don't know (yet). The work is the same. The capacity is halved.

This is one of the hardest management challenges in support, and it happens more often than anyone talks about publicly.

The First 48 Hours

The immediate priority is stabilization. Not optimization. Not "doing more with less." Stabilization: keeping the operation functioning while the team recovers from the shock.

Triage ruthlessly. For the first 48 hours, only handle urgent tickets: billing errors, account access issues, service outages, and anything with chargeback risk. Move everything else to a "deferred" queue. How-to questions, feature requests, and non-urgent bugs can wait 3 to 5 days without significant damage.

Extend your SLA temporarily. If your normal SLA is 4 hours, temporarily change it to 24 hours. Update your auto-reply: "We're experiencing longer than usual response times this week. We'll respond to your message within 24 hours. For urgent issues, mark your message as urgent." Honesty about capacity is better than broken promises.

Turn up AI automation. If you're using Supp or any AI classification tool, this is when to expand automation aggressively. Move every intent category that can be auto-resolved to automatic. Password resets, order status, FAQ questions, pricing inquiries. Every ticket AI handles is one your skeleton crew doesn't have to touch.

At $0.20 to $0.30 per AI-handled ticket, even tripling your AI resolution rate costs $100 to $200/month. That's trivial compared to the labor cost you just lost.

Taking Care of the Team

Your surviving agents need two things: information and permission.

Information: "Your jobs are safe. The layoffs are over. Here's what the plan is for the next 30 days." If you can't say their jobs are safe (because you don't know), say that honestly: "I don't have confirmation about further changes. I'll share what I know as soon as I know it."

Uncertainty is worse than bad news. An agent who thinks they might be laid off next week can't focus on tickets today.

Permission: "It's okay to feel upset. It's okay to take a 15-minute break after a tough ticket. It's okay to not be at 100% this week. We're going to get through this, and I don't expect peak performance right now."

This permission matters more than any operational change. Agents who feel pressured to perform at full capacity immediately after watching half their team get fired will burn out within weeks. And then you'll lose them too.

The First 2 Weeks

After the initial shock, the operational challenge sets in: you're permanently staffed at half capacity (until you hire, which takes months).

Restructure the queue. With 4 agents instead of 8, you can't cover the same hours, channels, or complexity tiers. Make choices.

Cut coverage hours if needed. Instead of 12-hour coverage (8 AM to 8 PM), drop to 8-hour coverage (9 AM to 5 PM). AI covers the off-hours with auto-responses and queuing. Tell customers about the change.

Reduce channel count. If you were covering email, chat, and phone, drop to email and chat. Phone support with 4 agents is functionally impossible during peak hours. Route phone to voicemail with a message: "For fastest support, email us at [address] or use the chat on our website."

Simplify the escalation path. With half the team, complex escalation chains don't work. Two tiers max: agent handles it, or agent escalates to the lead. No one else is available.

Communication With Customers

Customers will notice. Response times are longer. The chat is offline more often. The phone goes to voicemail.

Don't hide it. A brief status update: "We're making some changes to our team this month, and response times may be slightly longer than usual. We appreciate your patience. For urgent issues, please mark your message as urgent." You don't need to explain the layoffs. You need to set expectations.

Customers are generally understanding if you're honest. They're not understanding if you promise 4-hour responses and deliver 48-hour responses with no explanation.

Hiring (Eventually)

You'll need to replace some of the capacity. But hiring takes time (4 to 8 weeks from posting to productive new hire). In the meantime, the combination of triage, extended SLAs, expanded AI automation, and reduced coverage hours keeps the operation afloat.

When you do hire, consider hiring fewer agents at higher skill levels (the $80K approach from our earlier post). Combined with AI handling the simple tickets, 5 skilled agents with AI assistance can handle the same volume as 8 less-skilled agents without AI.

The layoff, as painful as it was, might be the forcing function for building a leaner, more AI-assisted support operation that's more resilient in the long run. That's the silver lining, though it's hard to see in the first 48 hours.

One Last Thing

Check on your team. Not their metrics. Them. In the days after layoffs, have individual conversations. "How are you doing? What do you need from me? Is there anything that would make this week easier?"

The agents who survive layoffs and feel cared for become your most loyal employees. The ones who survive and feel exploited start job-hunting on day two.

You lost half your team. Don't lose the other half through neglect.