What exactly is Dynamics 365 Customer Insights - Journeys? Is it simply Microsoft's tool for sending marketing emails, or is it something much larger? In many organizations, Marketing sends emails from one system, Sales manages opportunities somewhere else, website forms create another collection of customer information, and Customer Service maintains its own history. The result is a fragmented customer conversation where messages arrive too late, customers receive irrelevant information, and employees cannot see what other teams have already done. Dynamics 365 Customer Insights - Journeys connects customer information, communication, customer actions, and business processes so organizations can decide who should hear from them, what message they should receive, and when that message should arrive.
WHY BUSINESSES NEED CUSTOMER INSIGHTS - JOURNEYS
Customers do not experience your organization as separate departments. They experience one company. They do not care that Marketing uses one application, Sales works in Dynamics 365 Sales, Customer Service manages cases somewhere else, and the website has another system behind it. But disconnected systems create disconnected communication. Somebody downloads information about one product and receives a generic email promoting something completely different. A prospect books a demonstration online and then receives another message asking them to book a demonstration. A salesperson calls somebody without realizing that person already submitted a detailed request. None of these experiences necessarily happen because employees are careless. They happen because information is scattered and people cannot manually react quickly enough. Customer Insights - Journeys provides a connected system for planning customer communication around the customer's situation rather than around whichever campaign a department happens to be running.
FROM MASS COMMUNICATION TO THE NEXT SENSIBLE MESSAGE
The objective is not simply to send more messages. It is to determine the next sensible message. Imagine somebody visits your website and downloads a guide about a specific product. That action tells the organization something about their current interest. Instead of putting that person into a generic monthly mailing list, the business can respond with information related to the guide they requested. Sales can also gain context from that interaction. When somebody eventually contacts the prospect, they do not need to begin the conversation without knowing what the person has already done. Customer communication becomes part of a continuing relationship rather than a sequence of disconnected campaigns.
DIFFERENT CUSTOMER MOMENTS NEED DIFFERENT COMMUNICATION
Customers move through different stages in their relationship with an organization. Somebody might only have discovered the company yesterday. Another person is comparing solutions. Somebody else has requested a demonstration. Another customer purchased last week and now needs help getting started. Those people should not necessarily receive the same communication. A new prospect may need an introduction. Someone requesting a demonstration needs confirmation and useful next steps. A new customer might need onboarding information rather than another sales promotion. A customer experiencing a support problem may need help before receiving another marketing message. Customer Insights - Journeys allows communication to reflect these different moments.
WHAT IS A CUSTOMER JOURNEY?
A journey is a visual plan describing how communication should progress. The organization determines who can enter the journey, what should happen first, how long the system should wait, which customer actions matter, and what should happen next. One customer might receive one email and stop. Another customer could click a link, wait two days, receive another message, and eventually move into a completely different branch. The journey provides the map. Customer behavior determines which route through that map is appropriate.
THREE QUESTIONS BEFORE BUILDING A JOURNEY
Before creating a complicated automation, the episode recommends answering three fundamental questions: Who should enter? What should they receive? When should each message arrive? These questions sound basic, but they force teams to define the actual purpose of the communication. If nobody can clearly explain who the journey is for, why those people should receive the communication, and what outcome the organization expects, adding more automation will not solve the underlying problem.
SEGMENT-BASED JOURNEYS
One way customers can enter a journey is through a segment. A segment represents a defined group of people who satisfy particular conditions. This works well for planned communication such as an event invitation, product announcement, or newsletter. The organization determines the audience and starts communication according to a planned schedule. The important distinction is that the business determines the starting moment. Customers qualify because they belong to the relevant audience.
TRIGGER-BASED JOURNEYS
Trigger-based journeys work differently because they begin when something happens. A customer submits a form. Someone registers for an event. A prospect clicks a particular link. A customer reaches another stage in a business process. That event becomes the signal that starts the journey. Instead of waiting for an employee to discover the activity and respond manually, Customer Insights - Journeys can immediately begin the appropriate process.
THE HOTEL RECEPTION ANALOGY
The transcript compares triggers to the bell at a hotel reception desk. When a guest arrives, the bell tells the receptionist that somebody needs attention. The hotel does not tell the guest to return next Tuesday because that is when the next scheduled campaign happens. A customer trigger works similarly. Something relevant just happened, and the organization can respond while that action still has context. The important part is not simply automation. It is timing.
BUILDING THE JOURNEY
Once somebody enters, the journey can contain communication steps, waiting periods, conditions, branches, and exit rules. The business might send an email immediately, wait two days, determine whether the customer performed an action, and then choose the appropriate next step. This creates a process that employees can see visually instead of maintaining a long collection of manual reminders and disconnected activities.
BRANCHES MAKE JOURNEYS RESPONSIVE
Customers do not all behave the same way. Imagine an online event. Everyone who registers receives a confirmation. A reminder goes out before the event. Afterward, however, attendees and people who missed the event should not necessarily receive the same follow-up. Attendees might receive the slides and additional information. People who registered but did not attend could receive the recording with a different message. The journey started the same way for both customers, but their actions created different paths.
DO NOT TURN A JOURNEY INTO A MAZE
The ability to create branches does not mean every possible customer action needs its own branch. A journey with dozens of conditions quickly becomes difficult for employees to understand, test, troubleshoot, and improve. The transcript recommends concentrating on the moments where a different customer action genuinely requires a different business response. Start with the important decisions. Complexity can be added later when actual customer behavior demonstrates that it is needed.
EVERY JOURNEY NEEDS AN END
A customer should not remain inside an automated communication process forever. The organization needs to determine when somebody should leave. Perhaps the customer registers for the event, purchases the product, schedules the demonstration, or no longer satisfies the relevant conditions. Clear exit criteria prevent customers from continuing to receive communication designed to convince them to perform an action they have already completed.
CUSTOMER DATA PROVIDES THE CONTEXT
A journey can only make useful decisions when the customer information underneath it is meaningful. Sales may know about an opportunity. Customer Service may know about a recent support problem. A website form reveals what somebody requested. Purchasing systems contain transaction information. Customer Insights can use relevant information from these different business processes to provide additional customer context. The objective is not to replace every source system. Sales continues managing opportunities. Customer Service continues managing cases. Journeys uses relevant customer information to determine whether particular communication makes sense.
CUSTOMER INSIGHTS - DATA AND JOURNEYS
Customer Insights - Data can complement Customer Insights - Journeys by bringing information from connected sources together into richer customer profiles. Those profiles and the groups created from them can then support communication in Journeys. Instead of knowing only someone's name and email address, the organization might understand that the person recently purchased a product, visited a particular part of the website, and currently has an open support request. That context can completely change which message should come next. ㅤ
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
