Implementing Proactive Digital Engagement Triggers based on Customer Journey Milestones

How-To-Articles
1

Implementing Proactive Digital Engagement Triggers based on Customer Journey Milestones

What This Guide Covers

  • Architecting proactive engagement models using Genesys Cloud Predictive Engagement (Journey Management).
  • Moving beyond simple “time-on-page” web chat popups to complex, multi-milestone intent mapping.
  • Building an Action Map that only triggers a Web Chat offer when a high-value customer stalls at a critical conversion point, effectively deflecting low-value traffic while rescuing high-value revenue.

Prerequisites, Roles & Licensing

  • Licensing: Genesys Cloud CX 2 or 3 with the AI Experience add-on (Predictive Engagement).
  • Permissions: Journey > Action Map > Edit, Journey > Segment > Edit, Journey > Outcome > Edit.
  • Infrastructure: The Genesys Cloud journey.js tracking snippet deployed on your website, and a configured Web Messaging widget.

The Implementation Deep-Dive

1. The Annoyance of “Dumb” Proactive Chat

Historically, proactive chat is driven by a single, rudimentary trigger: “If the user is on the homepage for 30 seconds, pop a chat.”

The Trap:
This strategy is disastrous. It annoys customers who are just casually browsing, and more importantly, it floods your contact center with low-value, zero-intent chats (e.g., “Hi, what time do you open?”). If you have a queue of 50 people waiting to buy a $5,000 product, and your agents are busy answering “dumb” proactive chats, you are losing revenue.

2. Defining Journey Milestones and Outcomes

To execute intelligent proactive engagement, you must first define what a “High Value Journey” looks like.

Architectural Reasoning:
We will define an “Outcome” (e.g., Purchased Premium Insurance) and a series of “Milestones” that lead up to it. We only want to trigger a chat if the user hits Milestone 3, but fails to reach Milestone 4.

Implementation Steps:

  1. Navigate to Admin > Predictive Engagement > Outcomes.
  2. Create a new Outcome named Premium_Insurance_Conversion.
  3. Create the Milestone track:
    • Milestone 1 (Awareness): URL contains /insurance/premium.
    • Milestone 2 (Interest): Clicks the “Get Quote” button. (Configure an Event trigger for this CSS selector).
    • Milestone 3 (Stalled - The Danger Zone): URL contains /quote/checkout AND idle time > 45 seconds.
    • Milestone 4 (Success): URL contains /quote/thank_you.

3. Architecting the Segment and Action Map

Now we build the logic that says “Engage the customer when they get stuck at Milestone 3.”

Implementation Steps:

  1. Navigate to Admin > Predictive Engagement > Segments.
  2. Create a Segment named High_Value_Stalled.
  3. Set the condition: If User achieves Milestone 3 AND has NOT achieved Milestone 4.
  4. Navigate to Action Maps. Create a new map tied to the High_Value_Stalled segment.
  5. The Action: Select Web Messaging. Choose your production widget.
  6. The Payload: Customize the proactive greeting. Do not say “Can I help you?”. Say: “Hi there! I noticed you’re reviewing your Premium Insurance quote. Our licensed agents are available right now if you have any questions about the coverage limits.”

4. Routing based on Journey Context

When the customer clicks “Yes, I want to chat,” the interaction must be routed to a specialized closer, not a general tier 1 agent.

Implementation Steps:

  1. In the Action Map, configure the specific Inbound Message Flow that this proactive chat should hit. Do not send it to your generic inbound flow.
  2. In Architect, use the Get Journey Session action to extract the Outcome.Probability score (the AI’s prediction of whether they will convert).
  3. If Outcome.Probability < 0.20 (they are very unlikely to buy even with help), route them to an automated Bot.
  4. If Outcome.Probability >= 0.20, route them to the Sales_Closers_Tier2 queue with a Priority of +50, ensuring they skip the line.
  5. Agent UI: Ensure the Agent workspace is configured to display the Journey History panel, so the agent can see exactly which insurance options the customer clicked before the chat started.

Validation, Edge Cases & Troubleshooting

Edge Case 1: The Cookie Consent Blocker

  • The Failure Condition: You spend hours building a complex Action Map. You deploy it to production. Engagement rates are 0%. No proactive chats are firing.
  • The Root Cause: In the EU (GDPR) or California (CCPA), your website must suppress cookies until the user explicitly clicks “Accept”. If your web team blocked the execution of journey.js behind the cookie banner, Predictive Engagement cannot track the milestones.
  • The Solution: Work with your web dev team. journey.js can be executed in a “cookieless” mode where it tracks the session statelessly, or you must ensure that your Action Maps only target users who have explicitly accepted tracking cookies. Alternatively, rely on authenticated user data (logging in) rather than anonymous cookie tracking.

Edge Case 2: Action Map Collision

  • The Failure Condition: A user adds a product to their cart. Suddenly, three different chat widgets pop up, overlapping each other on the screen.
  • The Root Cause: You created a “Cart Abandon” Action Map, an “Idle Time” Action Map, and a “High Value” Action Map, and the user qualified for all three segments simultaneously.
  • The Solution: Action Maps in Genesys Cloud support Prioritization. Navigate to the Action Maps overview screen. Drag and drop the Action Maps to rank them. If a user qualifies for multiple maps, Genesys Cloud will only execute the highest-priority one. Always set your most specific, highest-revenue outcome maps to Priority 1.

Official References