We asked Jonathan Burton, Senior Functional Consultant to share his perspective on Dynamics 365 Customer Insights – Journeys in Release Wave 1. Jonathan works closely with teams designing and running journeys day to day, so his focus is on what holds up once things are live, where maintenance gets easier, where risk reduces, and where teams gain confidence using the platform over time.

Customer Insights – Journeys succeeds or fails on maintainability. This release wave focuses on reducing the friction that emerges after go‑live. The changes aren’t dramatic in a demo, but teams running real programmes will notice the difference. The direction of travel is clear: more orchestration, less rework, and tighter links between engagement, operations, and downstream action.

This release wave shows its value more clearly in live environments than in demos.

Updates that stand out

Conversational text messages

(GA April 2026)

Customer Insights – Journeys can now support two‑way SMS, allowing responses to influence what happens next rather than treating messages as one‑way broadcasts.

What matters here isn’t SMS itself, but the shift Microsoft is making towards Customer Insights – Journeys reacting to what customers actually say, not just what they click. That becomes particularly useful where journeys overlap with service scenarios, allowing replies to change the path, trigger follow‑up, or move responsibility elsewhere without bolting additional logic around the journey design.

Message expiry logic

(Preview March 2026 | GA May 2026)

Teams can now define when a message in Customer Insights – Journeys should stop being sent.

That sounds basic, but it addresses a real credibility issue. Few things undermine trust faster than receiving a reminder or offer that no longer makes sense. Clear expiry logic makes Customer Insights – Journeys easier to live with. Event communications, service reminders, renewal prompts and time‑sensitive messages all benefit from clearer stop conditions, without relying on manual clean‑up.

Jonathan’s point resonates with our own experience running Customer Insights – Journeys internally. Knowing messages will stop when they should, makes it easier to trust journeys once they’re live, without constant oversight.

Shared content that behaves like shared content

(Preview April 2026 | GA July 2026)

Customer Insights – Journeys now supports referenced content blocks, so updates apply everywhere they’re used.

This closes a long‑standing maintenance gap. Central teams can update legal copy, headers, footers or offer details once, without hunting through individual emails built in Customer Insights – Journeys.

The governance benefit here is as important as the time saving. Reuse becomes practical without losing control, which is where many marketing platforms struggle in larger or multi‑brand setups.

Creating records directly from Customer Insights – Journeys

(Preview April 2026 | GA date TBC)

Customer Insights – Journeys can now create records and activities directly, including custom ones.

This removes a lot of avoidable dependency on automation or custom code for simple hand‑offs. Journeys don’t stop at communications, they often need to trigger tasks, cases or follow‑up actions. Doing that natively makes Customer Insights – Journeys designs cleaner and easier to reason about. When Customer Insights – Journeys logic can create exactly what the business needs downstream, orchestration becomes more practical and less brittle.

Branded links

(Preview September 2026 | GA December 2026)

Customer Insights – Journeys will support branded links instead of generic platform URLs.

This matters less as a marketing feature and more as a trust signal. Links are often the first thing a customer judges in a message and unfamiliar domains can undermine otherwise good communications. Branded links help journeys feel intentional and credible, particularly in service, renewal, and transactional scenarios where confidence matters.

Given the timing, this is more of a second‑half planning item than a dependency for this release wave, but it reinforces the broader direction towards journeys that feel deliberate rather than automated.

Business impact

For end users, the benefit of these updates is relevance. Fewer stale messages, better maintained content, more responsive interactions, and cleaner hand‑offs all contribute to journeys feeling more deliberate and less automated.

For organisations, the value is scale without proportional effort. Customer Insights – Journeys allows central teams to run more complete journeys without layering additional process or constant manual oversight.

In practice, these improvements to Customer Insights – Journeys land well in welcome programmes, service reminders, event communications, upsell journeys and follow‑up flows where a customer action should trigger something concrete.

Implementation perspective

Based on Jonathan’s delivery experience, record creation stands out as the first opportunity for simplification in this release wave. If a current solution relies on Customer Insights – Journeys plus additional automation just to create operational records, it’s worth revisiting that pattern once this preview is available.

The shared content update is another practical governance improvement. Larger organisations, franchise models and multi‑brand teams should see clear value from this enhancement to Customer Insights – Journeys.

As ever, data and consent design still matter. Conversational messaging in Customer Insights – Journeys only works when opt‑in, quiet times and reporting expectations are clearly defined.

Taken together, this release wave strengthens Customer Insights – Journeys in the areas teams feel most once things are live. Messages stay relevant for longer, shared content becomes easier to govern, and operational hand‑offs are simpler to design without extra automation. It’s not headline‑heavy, but it makes journeys easier to trust, easier to run, and easier to scale.

Journeys in practice

If you’re implementing Dynamics 365 Customer Insights – Journeys, or reviewing an existing implementation that’s becoming harder to maintain, contact us. We work with teams responsible for designing and running journeys in live environments.

Timing varies across the wave, with a mix of General Availability (GA) and preview features; all dates are indicative for Release Wave 1 2026 and may change as Microsoft updates the release plan.

Scale Smarter. Perform Better

Streamline operations, enhance efficiency and drive profitability with Dynamics 365 Business Central.

DOWNLOAD THE GUIDE

Privacy Preference Center