· Pauline Kolde · How-to  · 12 min read

Don't Wait for the Support Call: Proactive Engagement with Customer Insights – Journeys

What if the organiser reached out first, not with another reminder, but with a conversation about whether you need help? Here's how Customer Insights – Journeys and Dynamics 365 Contact Center can orchestrate that outreach.

A customer service agent on a headset, proactively reaching out to a customer

Please be aware: The content is accurate at the time of creation. It may be that Microsoft has made changes in the meantime.

Imagine this: You’ve registered for a technical workshop. The preparation email has arrived, and there’s a checklist of things to set up before the day.

But what happens if you get stuck?

You could contact the organiser. Or leave it until the workshop and hope someone can help you then. Neither is ideal when the first session needs an environment that’s ready to use.

What if the organiser reached out first, not just with another reminder, but with a conversation about whether you need help?

That was the scenario Kristine and I explored in our Nordic Summit session. In this post, I’ll focus on the Customer Insights – Journeys side: how to orchestrate that outreach and what happens next. Read Kristine’s companion post for the Contact Center side.

What is proactive engagement?

Proactive engagement means the business starts the conversation rather than waiting for the customer to get in touch.

That could be a workshop-readiness check, an appointment confirmation or a follow-up before a technician visits. The useful part isn’t simply that we contact someone first. It’s that their response can influence what happens next.

In our session, we connected Customer Insights – Journeys with Dynamics 365 Contact Center. Journeys handles the orchestration: who should be contacted, when, and which follow-up they should receive. Contact Center handles the conversation, with an AI agent, a representative or a combination of both. The conversation outcome then becomes input for the next journey decision.

Our example: getting participants ready for a workshop

For the workshop scenario, the goal is straightforward: identify preparation problems before the workshop starts.

The design has three stages:

  • An AI-led call five days before the workshop.
  • A conversational SMS follow-up if the initial call didn’t reach the participant.
  • A representative-led call if neither the AI call nor the SMS reached the participant.

The participant might be ready, might need the prerequisite checklist again, or might need someone to help with access and configuration. Those are different situations and they shouldn’t all lead to the same reminder.

Here’s the path through our demo:

  1. AI call: Five days before the workshop, an AI agent calls the participant.
  2. SMS follow-up: If the call reaches an answering machine, the line is busy, or there’s no answer, a second journey sends a conversational SMS.
  3. Registration update: If the SMS doesn’t reach the participant or they don’t respond, a custom trigger starts a Power Automate flow that updates their event registration.
  4. Representative call: The registration change starts a third journey, which adds context to the contact’s timeline before a representative calls.

Before opening the journey designer

There are a few dependencies to sort out first.

Our session highlighted that Customer Insights – Journeys and Contact Center need to be in the same Power Platform environment.

For the one-time integration setup in Customer Insights – Journeys, the only thing you need to do is enable the Contact Center integration feature switch. The remaining integration setup is configured in Contact Center.

Feature switches in Customer Insights – Journeys showing the Contact Center integration switch enabled

When you build the journey, you’ll still configure each conversation step in Journeys: select the proactive engagement and the relevant channel settings. For a voice step, these include a compliance profile, purpose, and quiet time; for SMS, the compliance profile is selected on the text message.

The audience matters too: conversational journeys are contact-based, rather than lead- or Customer Insights – Data profile-based journeys.

Microsoft’s prerequisites also distinguish conversational SMS: it uses Contact Center’s channel, not the standard Journeys SMS channel. AI-led conversations additionally require Copilot Studio.

Kristine’s companion post covers the Contact Center settings: Proactive Engagement in D365 Contact Center: From Reactive Support to AI-Led Outreach.

Journey 1: start with the readiness call

The first journey starts with the custom trigger Nordic Summit - Start 1st journey. Technically, I use a custom trigger here with an underlying Power Automate flow. The flow runs every day and looks for contacts who have registered for events taking place in five days. Of course, you can also choose a different approach to start the journey.

It then uses a Voice conversation step, connected to the proactive engagement Outbound Agent Dialling (or whatever you named the proactive engagement). This is the AI agent automatically calling the participant to ask if they prepared for the workshop or need help.

Journey with the Nordic Summit - Start 1st journey trigger, a Voice conversation step using Outbound Agent Dialling, and an If/then branch on the previous message's interaction

Just like with email and text messages, you can use an if/then branch based on an interaction with the previous message. Here, I check whether a voice call was attempted, then add an attribute branch for its result.

If/then branch with the Voice call attempted trigger selected, followed by an Attribute branch named A voice call is attempted

We can branch based on the call result returned by Contact Center. In our demo, the follow-up journey starts when the call reaches an answering machine, the line is busy, or there’s no answer. If the result is Live answer, we assume the agent reached and helped the participant.

Customer answered attribute branch with a condition on voice call results where Result equals Live answer, showing other options such as Answering machine, Busy and No answer

For those unanswered call results, the journey activates the custom trigger Nordic Summit - Follow Up Journey. The trigger passes two attributes to the next journey:

  • Event Registration: The ID of the registration that started the first journey. I use it later in Journey 3.
  • Result: The call result from Contact Center. I use it to tailor the follow-up SMS to what happened, for example, whether the line was busy or there was no answer.

Busy branch with an Activate a custom trigger step for Nordic Summit - Follow Up Journey, mapping the Event Registration attribute from the Start 1st journey trigger and the Result attribute to Busy

There’s an important design distinction here: a customer answering isn’t the same as a customer being ready.

For a production version, define the business outcomes you actually need. “Ready,” “needs the checklist” and “needs assistance” are more useful than treating every answered call as a completed readiness check.

Microsoft’s setup guide distinguishes call results, representative disposition codes and AI-agent attributes when designing branches.

For production, also plan what should happen when a call is not attempted or is blocked. Those are different from an attempted call that wasn’t answered. For example, a call can be blocked because of consent or quiet-time settings, so don’t automatically treat it as a reason to retry through another channel.

Journey 2: offer another way to respond

Not answering a call doesn’t necessarily mean someone doesn’t want help. They might simply be busy.

The second journey starts with Nordic Summit - Follow Up Journey and includes a Text message conversation step using Outbound SMS Engagement.

Because we pass on the call result from the first journey, we can use an attribute branch to tailor the SMS to what happened.

Follow-up journey with the Nordic Summit - Follow Up Journey trigger and a Check call result attribute branch with branches for Answering machine, Busy and No answer

The follow-up message explains that we’ve tried to reach the participant about the workshop and invites them to reply if they need help with the prerequisites.

Note
SMS conversations turned out to be a bit more complex. We’re still working out which result the system returns when a contact replies to the SMS or starts a conversation with a representative in Contact Center. We aren’t 100% sure yet, so test these outcomes in your own environment before relying on them in your branches.

We can also branch based on the SMS conversation. In our demo, if sending fails or the participant doesn’t answer, we activate the custom trigger Nordic Summit - Update Event Reg, passing on the Event Registration ID.

Other branch of the conversation outcomes with an Activate a custom trigger step for Nordic Summit - Update Event Reg, mapping the Event Registration attribute from the Follow Up Journey trigger

The trigger starts a Power Automate flow. The flow uses that ID to update a custom field on the corresponding event registration, for example, a yes/no field called Contact Center call initiated. A Dataverse trigger detects the field change and starts Journey 3.

Decide in advance how long to wait, whether another attempt would be useful, and when to stop. Those are journey-design decisions, not details to leave until someone receives their fourth reminder.

Journey 3: bring in a person, with context

The third journey starts with the Dataverse trigger Nordic Summit - Event Reg Change, when the custom field on the event registration changes. In our demo, it brings in a human representative because we couldn’t reach the participant through the AI call or the SMS conversation. But before the representative calls, we need to give them some context.

When we use proactive engagement with Contact Center, a call activity is created so the representative knows whom to call. In our setup, however, Customer Insights doesn’t pass on the details of where the call came from or why it was initiated. The representative can see whom to call, but not necessarily why. That’s confusing for both the representative and the customer.

Why pass on the event registration ID?

A contact can be registered for several different events. Passing the Event Registration ID through the journeys lets us identify the specific registration this call is about, rather than leaving the representative to guess.

Our workaround: add a note to the contact’s timeline

Before the Outbound Representative Dialling voice conversation, the journey uses a Create a record step to add a note to the contact’s timeline. The note includes details from the specific event registration, such as the event name and start date.

Third journey with the Nordic Summit - Event Reg Change trigger, a Create a record step for a Note with a personalized title and description including event name and start date, and an Outbound Representative Dialling voice conversation

The representative can see the note in their workspace and understand why they’re calling before speaking to the participant. That makes it easier to provide relevant help without asking the customer to explain the situation from scratch.

For your own implementation, consider including:

  • Which workshop the participant registered for.
  • What preparation help they requested.
  • Which outreach has already happened.
  • What the representative should do next.

The note is a simple workaround, but the principle is important: don’t assume the journey context automatically follows the call. Make sure the person picking up the conversation has what they need.

What else could we build?

The same pattern can support other situations where a reply changes the next action:

  • Appointment preparation: confirm attendance, then provide preparation instructions or a route to rescheduling.
  • Field-service visits: check access arrangements before a technician arrives.
  • Travel preparation: identify missing documents while there’s still time to help.
  • Onboarding: check whether someone has the access they need before they get stuck.

These were among the additional scenarios in our session. The common thread is that a two-way conversation adds something a one-way notification cannot.

For the workshop example, useful extensions could include a checklist follow-up, a separate assistance journey and an exit condition when a registration is cancelled.

Those would be extensions to the design, not claims about what the demo already implemented.

Start with the outcome, not the call

Before building the journey, decide what “helpful” looks like.

For a workshop-readiness check, the goal isn’t to place a call. It’s to discover whether someone needs support while there’s still time to provide it.

Plan consent, appropriate contact times, fallback paths and human ownership alongside the happy path. Our session’s closing advice was to start small: one use case, one voice journey, and test by calling yourself.

Proactive engagement becomes useful when the response changes what happens next. Customer Insights – Journeys gives us a place to design that next step without making every customer follow the same path.

Personally, I really like the connection between Customer Insights – Journeys and Contact Center. I must admit that, as a Customer Insights person, Contact Center can feel like a bit of a black box. There are a lot of options and settings to get right, so I was glad to have Kristine on board.

My advice: involve a Contact Center expert when setting up conversational journeys. Once the foundations are in place, the integration opens so many new doors.

Explore more guides in the customer journeys and triggers topic guide.

Do you have questions, ideas or remarks? Feel free to get in touch.

Back to Blog

Related Posts

View All Posts »
Quiet Times in Real-time Marketing

Quiet Times in Real-time Marketing

Quiet times in real-time marketing help you avoid spamming contacts by controlling when messages are sent across channels in Dynamics 365 Customer Insights.

Power Fx in Customer Insights Emails: A Practical Guide

Power Fx in Customer Insights Emails: A Practical Guide

Power Fx has landed in email personalization for Dynamics 365 Customer Insights - Journeys. Here's what the supported functions do, a set of copy-paste formulas for common marketing scenarios, and why I still don't think marketing users should be the ones writing them.