easyJet Moves Customer Service to Dynamics 365 Contact Center: Reported Results and AI Plans

The scale of the operation​

Dynamics 365 Contact Center is a Copilot-first, cloud-based product. easyJet is using it at considerable volume. Microsoft's account says the airline carries more than 100 million passengers a year on a fleet of more than 350 aircraft. Its customer-service team of about 2,000 handles an estimated 15 to 20 million contacts a year in seven or eight languages.

The story does not say what period or method sits behind those contact estimates.

Before: five or six systems per enquiry​

Until recently, an adviser might need five or six systems to help one customer. A call arrived in one place and the contact was logged somewhere else. Moving to live chat or social media meant opening yet another platform.

Ayesha Walker, easyJet's global training manager, said training staff to navigate all this could take around six weeks. She described the old setup as requiring "a lot of movement" for the people helping customers.

What the new platform does​

The case study describes these adviser-facing features:

• A single view of the conversation. Advisers see the whole conversation whatever channel the customer used.
• Knowledge retrieval. Copilot can find an answer in easyJet's approved knowledge articles while the adviser is talking to the customer.
• Email drafting with human sign-off. Copilot can draft an email. The adviser reviews, personalises and approves it before it is sent. The story does not say Copilot sends emails on its own.
• Live summaries. These give context on why the customer is making contact.
• Live transcription. This helps advisers log the whole conversation faster.

John Leighton, easyJet's Customer Service Director, singled out live transcription as the most impactful feature. His reasoning was that teams can focus on the conversation instead of working across six systems.

Microsoft's product documentation shows these feature categories exist in the product. It lists using Copilot to summarize conversations, draft responses and emails, and surface relevant knowledge. That confirms the capabilities are real. It does not confirm which ones easyJet has switched on. The case study gives no configuration, licensing, hosting region or language coverage.

Microsoft's admin documentation also shows these features are not automatic. Administrators have to enable them in the Copilot Service admin center. When enabling the Copilot features, you must opt in to continue with the setup. The documentation lists some differences between the embedded and standalone versions of the product. For example, case summarisation is available in the standalone version but not the embedded one.

The reported results​

Leighton gave these figures:

Leighton also said customer feedback shows people feel they get a better resolution through live chat.

Several caveats apply. The story gives no baselines, definitions, measurement periods or survey samples. "Resolution results" is not defined, so it should not be read as a specific metric. The phone and chat percentages also don't add up neatly, because the story describes the live chat share as a range. Nor does the story establish that the platform alone caused the channel shift. Customers moving from phone to chat could reflect easyJet's own channel design as much as the software.

Why easyJet chose Microsoft​

easyJet picked Microsoft as its call-centre-as-a-service provider after a procurement process involving 10 providers. Leighton cited three deciding factors:

1. A working demonstration.
2. The ability to consolidate communication channels.
3. The ability to analyse customer contact data.

The story does not name the other bidders. It also gives no costs, contract terms or independent comparison of vendors.

Better data on why customers get in touch​

Leighton said the platform has given the airline a clearer view of why customers contact it. His example was customers asking to add extra assistance to a booking. He sees that as a source of business insight for improving service. The story does not describe any service change that has resulted.

What comes next​

easyJet's roadmap, as described, covers three things:

• Finer categorisation. A booking query would be broken into sub-categories, such as adding a bag or a seat.
• Automation of routine requests. Simple requests with simple answers would be handled automatically. Staff would then concentrate on complex queries where judgement and reassurance matter most.
• More AI agents. Leighton said the contact-centre platform is the foundation for further agents that carry out specific tasks with team oversight.

These are plans, not live features. The story gives no timeline, agent functions, safeguards or success measures.

Microsoft's documentation shows the tooling for this exists. It describes using agents to simulate human-like conversations for routine activities so representatives can focus on higher-value interactions. The same page says agents are built and governed in Copilot Studio. That is general product information. It does not tell us what easyJet is building.

Analysis: what to take from this​

The useful distinction here is between two things:

• Assistance already in use. This covers knowledge lookup, human-approved email drafts, summaries and transcription. Advisers stay in charge.
• Automation still to come. This covers automatic handling of routine enquiries and task-specific agents.

Leighton frames the aim as supporting staff and freeing them for harder cases. The story reports no job cuts. It also doesn't claim the platform has replaced any advisers.

For IT teams weighing a similar move, the most transferable point is the consolidation. Cutting five or six tools to one is plausible as a way to shorten training and reduce context switching. The six-week training figure is a concrete baseline against which other organisations could compare. The headline performance numbers are harder to carry over. Without baselines or methodology they work as claims from a vendor-published customer story, not as benchmarks you could expect to reproduce.