The AI Already in Dynamics 365 CRM
Six AI capabilities are already inside your Dynamics 365 Sales Enterprise license. Most sales organizations are using one of them.
Every sales leader I speak to this year is having a version of the same conversation with their finance director. It is about how much to spend on AI for the sales team. What almost never comes up in that conversation is that an organization running Dynamics 365 Sales Enterprise has already bought six AI capabilities — and is, in most cases, actively using one of them.
That gap is worth sitting on, because it changes what the investment decision is. The question is not whether to buy AI for sales. It is why the AI already paid for has not reached the sales floor. In my experience the answer is almost never the technology. It is data, sequencing and ownership — three things no license can supply.
What is already in the license
Six capabilities ship with Sales Enterprise, without a Premium upgrade and without a custom build. The capacity column matters as much as the description, and I will come back to why.
Capability | What it does | Included capacity |
Copilot in Dynamics 365 Sales | Summaries records, catches up on changes, prepares for meetings and drafts of customer email — inside Sales Hub, Outlook and Teams. | No separate monthly capacity |
Predictive lead scoring | Ranks open leads 0–100 on likelihood to qualify, with the factors behind each score. | 1,500 records / month (shared) |
Predictive opportunity scoring | Predicts which open opportunities will progress and close; supports per-stage models. | 1,500 records / month (shared) |
Conversation intelligence | Call summaries, action items, sentiment, talk-to-listen ratios, and keyword, competitor and pricing signals. | No stated monthly limit |
Relationship intelligence (basic) | “Who knows whom” — surfaces colleagues who already have a relationship with a lead or contact. | No stated monthly limit |
Sales accelerator | A prioritized work list plus multi-step sequences that automate follow-up cadence across channels. | 1,500 sequence-connected records / month |
It is more useful to read that list as three pairs than as six products.
The first pair is judgement at scale. Predictive lead and opportunity scoring each train a model on your own closed history and return a score with the factors behind it. The value is not the high scores — sellers usually know which deals look good. It is the low score on a late-stage opportunity a seller has called commit. That is an early coaching signal instead of an end-of-quarter surprise, and it is the single fastest route to a more credible forecast.
The second pair is the intelligence your CRM has never captured. Conversation intelligence turns recorded calls into summaries, action items, sentiment and competitor or pricing signals, so managers coach against what was said rather than what was remembered. Relationship intelligence answers a question sellers ask constantly and CRM has never been able to answer: does anyone here already know this person? A warm introduction is a materially shorter path into account, and the relationship map stays with the company when a seller leaves.
The third pair is the seller’s day. Copilot removes the reading and the writing — record summaries, what changed since the last touch, drafted and summarized email. The sales accelerator removes the deciding, replacing a self-managed pipeline with a ranked work list and sequences that make dropped follow-up structurally difficult. Used together, with scoring supplying the ranking signal, they compound: the list is prioritized by the model, and Copilot briefs the seller on whatever sits at the top of it.
Why it sits unused
Three reasons, in the order I encounter them.
The data gate is real, and it is not a licensing problem. Predictive scoring needs history — at least 40 qualified and 40 disqualified leads, or 40 won and 40 lost opportunities, created and closed inside the training window. Plenty of organizations have the volume and still fail the test, because close reasons were never enforced, qualification was a formality, or the business process flow was redesigned midway through the period being trained on. The model then trains on noise and reports an accuracy grade that tells you so before you publish it. The uncomfortable reading of a failed model is that it is a diagnosis of CRM discipline rather than a fault in the AI, and that finding is worth having early.
Capacity gets discovered rather than planned. Sales Enterprise includes 1,500 scored records per environment per month covering lead and opportunity scoring together, and a separate 1,500 sequence-connected records per month for the sales accelerator. For most mid-market pipelines those allowances are generous. For a high-volume inside-sales operation they are a design constraint, and the right response is tighter filter criteria and connect rules rather than a surprised phone call about an upgrade. Both pools are per environment, so proving the models in a sandbox cost nothing in production.
Nobody owns adoption. Copilot and the accelerator change how a seller spends the first twenty minutes of the day, and that is behavior change, not configuration. It fails predictably when managers keep asking for the report for the work list to be replaced. Conversation intelligence stalls for a different reason: the blocker is consent, recording retention and local monitoring law, not setup. Microsoft is explicit that it must not be used for employment decisions such as pay or promotion, and the organizations that get value from it treat it as a coaching asset owned by sales enablement. Framing it that way, in writing, before the first call is recorded, is what keeps it alive.
A sequence that works
Order matters more than ambition. Start with what costs nothing to try: Copilot for a pilot group of willing sellers, and relationship intelligence, which is available out of the box with nothing to configure. These earn goodwill in weeks and give you something to point at while the harder work runs in parallel.
That harder work is unglamorous and non-negotiable — audit closed lead and opportunity history, fix close reasons and qualification discipline, and confirm the training thresholds honestly rather than hopefully. Only then train and publish the scoring models, reviewing the accuracy grade before publishing rather than explaining it afterwards. With scores in place, build sequences for your two highest-volume sales motions and set a monthly check on both capacity pools. Leave conversation intelligence until legal and HR have signed off, then introduce it as coaching, with recording consent handled in the meeting invitation.
What to measure
Resist the temptation to measure AI usage. Adoption dashboards tell you people clicked; they do not tell you whether the business changed. Four numbers are worth baselining before phase one and reviewing quarterly: seller administrative hours per week, lead-to-opportunity conversion rate, forecast accuracy at the stage where deals are committed, and time-to-first-closed-deal for new hires. If those four have not moved after two quarters, the problem is adoption or data, and no additional license will be fixed either.
An honest conclusion
There is a version of AI conversation that is mostly procurement, and a version that is mostly operational discipline. The first is more comfortable, because it converts an organizational problem into a budget line. The second is where the return sits.
The sales organizations that get real value from AI over the next two years will not be the ones that bought the most of it. They will be the ones that switched on what they already owned, in a defensible order, and did the quiet work on the data underneath it. If you run Sales Enterprise today, that work can start this quarter and it does not need a new license — only an owner, a sequence and an honest look at your own history.
