Customer Service During Strikes: Business Continuity with AI in the UK

In 2026, customer service during strikes has become a hot topic — and for good reason. While Spain faces its fifth week of doctors striking over the Estatuto Marco, alongside teacher and rail strikes, thousands of businesses are discovering, to their shock, that their operations grind to a halt. In this guide, I'll show you, with real-world cases, how to keep your operation running when a strike disrupts teams, channels, and logistics.

TL;DR

• Strikes don't give much notice: the Spanish doctors' strike (15–19 June) has already lasted five weeks, and the FGV transport strike in Valencia runs from 22 June to 2 October 2026.
• The first thing to break in a strike isn't delivery — it's customer service: no one answers clients, orders, or queries.
• WhatsApp automation + AI agents can maintain 70–100% of first-line service without relying on striking staff.
• Continuity isn't about breaking a strike; it's about shielding the end customer from operational collapse.
• Build your plan before the walkout — improvising on the day is costly.

Why "strike" searches surged in 2026

The wave began in Spain and rippled across social media. The State Confederation of Medical Unions (CESM) called strikes against reforms to the Estatuto Marco, with the fifth week of action taking place from 15 to 19 June 2026, culminating in a protest outside the Ministry of Health in Madrid. Agreed minimum services maintain 100% in A&E but reduce primary care to between 25% and 75%, depending on the autonomous community.

This wasn't an isolated case. On 9 June, five teaching unions suspended classes in Catalonia, with a demonstration in Barcelona on the 14th. And drivers at Ferrocarrils de la Generalitat Valenciana (FGV) went on strike from 22 June, with a calendar extending to 2 October. Healthcare, education, and transport all paralysed at once — the knock-on effect on any business is immediate.

For UK businesses, the lesson transcends borders. Strikes by bank staff, Royal Mail, public transport, or even an internal walkout by your own team produce the same symptom: the customer knocks on the door and finds no one there. And anyone searching "strike" worried is, in effect, asking the same question: how do I not stop too?

Sectors most exposed when staff are scarce

Not every business feels a strike with the same intensity. The risk of customer service during strikes collapsing is highest in sectors with high contact volumes and sensitive deadlines. From my experience working with companies in the UK and abroad, the most vulnerable are:

• Healthcare and clinics: they rely on appointments. A strike forces mass rescheduling, exactly the bottleneck seen in the Spanish doctors' strike.
• Education and online learning: suspended classes generate a flood of queries from students and parents.
• E-commerce and logistics: delivery delays trigger a barrage of "where's my order?" messages.
• Appointment-based services: salons, garages, offices — any operation that runs on bookings.

The pattern is clear: the more your business depends on conversation and deadlines, the sooner you feel the absence of staff. And that's precisely where automation makes the biggest difference.

What actually stops when a strike begins

There's a myth that strikes only affect "production." In practice, the first thing to collapse is the communication layer. I've seen this for over 15 years serving clients at Agathas Web: when staff are absent, the phone rings into the void, WhatsApp accumulates hundreds of unread messages, and the customer, without a response, takes their business to a competitor.

Typical effects of a strike on operations:

• First-line service disappears: simple queries (opening hours, order status, duplicate invoices) go unanswered.
• Logistics slow down: deliveries dependent on public transport or striking teams grind to a halt.
• Schedules fall apart: appointments, meetings, and booked services need mass rescheduling.
• Reputation suffers: negative reviews and complaints on social media spike when silence sets in.

The key point: much of this damage is avoidable, because a large portion of the service that stops during a strike is repetitive and automatable. Think about how many of the messages arriving at your business today actually need human judgement. In most businesses I analyse, 60% to 80% of volume is repeated questions — and it's precisely this chunk that sustains customer service during strikes when the team isn't available.

Customer service during strikes: what can be kept running

Here's the practical part. Customer service during strikes doesn't have to be all-or-nothing. The right strategy is to separate what requires a human from what an automation layer can handle alone — and protect the end customer from the impact.

Layer 1 — Automated responses and triage

An AI agent on WhatsApp resolves, without human intervention, the questions that make up the majority of volume: order status, opening hours, policies, location, duplicate invoices. In a strike, this layer alone absorbs the peak of messages that would normally overwhelm a reduced team.

Layer 2 — Scheduling and rescheduling

When a strike forces cancellations (think of the doctors' strike and suspended appointments), an automated flow can offer new slots, confirm rescheduling, and update the customer in real time — without anyone on the phone.

Layer 3 — Intelligent escalation

What the AI can't resolve, it forwards. Sensitive cases go to the reduced number of available humans, already with the conversation context summarised. This way, the lean team focuses on what matters instead of drowning in "what are your opening hours?"

It's exactly this layered logic that I apply in my clients' WhatsApp automation projects. To understand why the right channel matters, it's worth reading WhatsApp Business App vs Official API: which makes sense in 2026.

Manual vs automated: what changes in practice

The difference between facing a strike on the fly and having an automated layer ready shows up in operational numbers. The table below summarises the contrast I see in the field.

Dimension	100% manual operation	Operation with automation + AI
Capacity during strike	Drops with the team	Maintains 70–100% of first-line
Response time	Hours or days	Seconds, 24/7
Marginal cost per interaction	High (overtime, emergency cover)	Near zero
Risk of losing customers	High	Low
Time to activate	Reactive, on the day	Already in place

The message from the table is simple: automation doesn't replace the team — it ensures that the team's temporary absence doesn't bring the business down. A good plan for customer service during strikes doesn't try to clone the human team; it isolates what can run alone and keeps that minimum viable service running while the situation normalises.

Playbook: preparing continuity before the strike

Strikes are rarely a complete surprise: unions announce calendars in advance, as CESM did in Spain. Use that time. A plan for customer service during strikes built with a buffer costs a fraction of what it costs to fight fires on the day of the strike. Here's the step-by-step I recommend:

1. Map repetitive service tasks. List the 10 most common questions. They are obvious candidates for automation.
2. Choose the right channel. In the UK, WhatsApp is widely used for customer service. Use the Official API to scale without risk of being blocked.
3. Build the AI flows. Configure responses, triage, and scheduling before the critical date.
4. Define escalation. Decide which cases go to a human and who covers the minimum duty rota.
5. Test with real volume. Simulate a peak before the strike — discovering a failure in the middle of it is the worst scenario.
6. Communicate proactively. Tell customers that service will continue via the automated channel.

When NOT to automate everything

Automation has limits. Serious complaints, contract negotiations, emotionally charged situations, and high-value decisions require a human. Forcing AI on these cases worsens the experience and reputation. The rule: automate the volume, preserve the human for what is sensitive. On the limits and the cost of charging per employee, I wrote in Unlimited Agents on WhatsApp: why paying per employee failed.

The role of AI agents in operational continuity

The difference between 2026 and previous years is the maturity of AI agents. We're no longer talking about rigid decision-tree chatbots, but agents that understand natural language, consult data, and make micro-decisions. This changes the game for continuity: the agent handles a strike, a Black Friday peak, or a night shift with the same consistency.

For businesses, the gain is strategic. An agent that operates 24/7 doesn't take holidays, doesn't get sick, and doesn't go on strike. It doesn't eliminate human value — it frees the team for relationships and complex problems. I explored this transition further in AI Agents: what Gemini Spark changes for businesses.

In practice, it's this consistency that makes customer service during strikes reliable. Unlike an improvised emergency cover, where two or three staff try to handle the volume of an entire team, the agent maintains the same response time in the first minute and the fifth hour of operation. The customer on the other end doesn't realise there's a strike happening behind the scenes — and that invisibility is, ultimately, the best indicator that the plan worked.

There's also the risk dimension. Concentrating all service on a personal WhatsApp number is fragile: one block can stop the operation — a self-imposed "strike." Migrating to the official infrastructure is part of the protection, as I detail in How to avoid WhatsApp business number blocking in 2026.

Continuity isn't about "breaking a strike" — it's about protecting the customer

An important ethical distinction is worth making. Automating customer service during a strike does not mean replacing workers in protest or weakening a legitimate cause. The Spanish doctors' strike, for example, discusses working hours, professional classification, and pay — human issues that no software can resolve.

What technology does is different: the goal of customer service during strikes is to prevent the end customer — the patient who needs to reschedule, the consumer waiting for an order — from being left in limbo while the labour negotiation runs its course. Operational continuity protects those at the sharp end, without taking sides in the conflict. That's the benchmark I advise adopting.

Conclusion: prepare today the plan you'll need tomorrow

The 2026 strikes in Spain are a cheap reminder of an expensive lesson: an operation that depends entirely on human presence is fragile. Customer service during strikes — or any unexpected disruption — only stays up for those who built the automation layer before the crisis.

If your business still responds to customers 100% manually, the next step is simple: map the repetitive questions and move them to an AI agent on WhatsApp. Not to fire anyone, but to ensure that no customer is left without a response on the day the team can't serve. Want help designing that flow? That's exactly the kind of project we run at Agathas Web.