June 29, 2026
Financial Cooperative Desjardins Gave Its Advisors a CRM Shared Memory With Microsoft Dynamics 365, and Customers Noticed
North America’s largest financial cooperative spent years hearing the same complaint: members were repeating themselves. At every touchpoint, whether branch visit, call centre, or online enquiry, the context from the last conversation had evaporated. Staff weren’t indifferent; it was just that the infrastructure didn’t let them know what had already been said. Desjardins, the Quebec-rooted cooperative with more than five million individual members, has spent the past two years addressing that with Microsoft Dynamics 365, deployed as a shared CRM adoption strategy across its distribution networks.
The results, published this month, are a useful case study in what CRM transformation looks like when it actually takes place.
- Microsoft Folds Workforce Management Into Dynamics 365, Gifting One Less Tool for Contact Centre Leaders to Juggle
- Copilot Cowork For Dynamics 365 is Now Generally Available: Microsoft Winds Up Its AI Clockwork for CX Teams
The Problem Was Memory, Not Channels
Before the project, Desjardins operated with business development tools that its own leadership described as outdated and dispersed. Advisors had no visibility into what had happened at another touchpoint. Call centre agents started every call cold. Mortgage renewals, a moment that should demonstrate relationship depth, instead revealed how little the organisation’s systems retained. As Julie Provencher, Senior Director, Service Delivery Modernisation at Desjardins, put it to Microsoft:
“In 2026, CRM is essential: you have to know the member’s history and what’s coming up in business opportunities.”
The fix was structural rather than cosmetic. Rather than overlaying a new interface on existing fragmentation, Desjardins made Dynamics 365 the common foundation. This became a single-member record visible across networks, integrated into daily workflows.
What Changed on the Ground with CRM Adoption
During mortgage renewals, multiple teams can now work from the same member record simultaneously. This is instead of duplicating effort or losing the thread between hand-offs. Call centre agents access notes from a member’s last branch appointment, resolve queries in a single call, and move on, rather than transferring and starting over.
Luc Vézina, Director of Member and Client Relationship Management Support, noted that generating a call list for 500 members, once a manual, one-by-one task, now takes seconds. The gains are modest in isolation. Cumulatively, across millions of interactions, they add up.
CRM usage hit 70% in February 2026 and is still climbing. The organisation is already seeing a correlation between early adopters and stronger performance against their commercial targets.
It Nearly Went Wrong
The more instructive part of the story is what happened in the first deployment cycle. The project stalled, not because the tech failed, but because it had been positioned as an IT initiative rather than a service delivery one. Frontline staff found the tool disconnected from their day-to-day reality. Adoption, as a result, lagged.
Desjardins recovered by reorienting the programme around the people using it. There was tailored training by network, stronger manager involvement, and a clearer articulation of what the system was actually for. Juliette Petit, Director of Transformation and Evolution, Member and Client Relationship Management, put the ambition plainly:
“Our ambition is to free up time so employees in service delivery can spend most of their working hours supporting members.”
That pivot, from deployment milestone to lived adoption, is arguably where CRM projects most commonly stall, and where this one eventually found its footing.
What Other Organisations Can Take From This Strategy
The broader lesson here has little to do with Dynamics 365 specifically. A CRM adoption strategy only works if the people it affects can see the point of it on an ordinary Tuesday afternoon. Organisations that treat adoption as something that follows automatically from a successful go-live tend to end up with expensive, underused platforms.
Building the training and management programme in parallel with the technical deployment, not after it, is arguably what distinguishes the implementations that stick from those that quietly regress.
For those considering AI capability in their CRM environments, Desjardins’ sequencing is worth fixing upon. The cooperative is explicit that AI is its next step, but has deliberately not rushed there. AI trained on fragmented or poorly adopted CRM data produces unreliable outputs. These are suggestions built on incomplete records that are confident in tone but wrong in substance. A clean, well-used shared data layer should be the precondition. Desjardins built the foundation first.
