Genesys Cloud - Developer Community!

Hi Team,

I have been working on flow outcomes and flow milestones, and I would like some clarification.

• What is the role of the "Initialize Flow Outcome" activity node? From my observation, even without adding Initialize Flow Outcome, simply setting the flow outcome to Success or Failure allows us to capture data in the interaction reports.

• How is the outcome related to a milestone? When we use the Flow Milestone activity node to analyze journey paths, the outcome appears to be a mandatory field that must be added.

Could anyone please help clarify the relationship between these two and the specific purpose of Initialize Flow Outcome?

#Architect

------------------------------
Yogesh Mungekar
(GCX-ARC, GC-GCP)
I mostly available in IST time
------------------------------

Hi!

Great questions. Here is how these two work together in Architect:

The Role of Initialize Flow Outcome: The main difference comes down to duration tracking.

• When you use Initialize Flow Outcome, Genesys captures the exact start time when that node runs, and the end time when Set Flow Outcome (Success/Failure) is executed. This allows you to measure how long the user spent in that specific self-service operation.

• Without Initialize Flow Outcome, both the start and end timestamps get set to the exact same moment (when Set Flow Outcome triggers). You still get the Success/Failure status in reports, but you lose the time duration metrics.

Relationship Between Outcomes and Milestones: Flow Milestones need an outcome associated with them because they track checkpoints within a process:

• Flow Outcomes track the overall result of a self-service task (Success vs. Failure).

• Flow Milestones mark key steps or touchpoints along that journey.

For example, if a customer makes three payment attempts before succeeding:

• The Flow Outcome is Success (for the overall payment process).

• The Flow Milestones track each payment attempt along the way.

This is why the outcome field is mandatory in the Milestone action - milestones need that context to build meaningful journey paths.

In short:

• Use Initialize Flow Outcome whenever measuring the duration of a self-service process matters.

• Use Milestones to track key checkpoints within that outcome's scope.

Hope this helps clear things up!

------------------------------
Jhonatan Engel
------------------------------

Hi Yogesh,

The Role of Initialize Flow Outcome:

The key difference is duration tracking. When you use Initialize Flow Outcome, Genesys Cloud captures the exact start time (timestamp) when an interaction begins that outcome. This creates a starting point for measuring how long it takes to reach the final outcome (success or failure).

Without Initialize Flow Outcome:
When you use Set Flow Outcome directly without first using Initialize Flow Outcome, both the start and end DateTime values are set to the same time-the moment when the Set Flow Outcome action runs. This means you won't have accurate duration metrics for how long the outcome took.

With Initialize Flow Outcome:
The system records a separate start time (when Initialize is encountered) and end time (when Set Flow Outcome is encountered), giving you accurate duration metrics for the self-service operation.

Relationship Between Outcomes and Milestones:

Flow milestones must be associated with a flow outcome-this is why the outcome field appears mandatory when adding a Flow Milestone. Milestones provide granular tracking points within a customer journey for a specific outcome.

However, if you add a Flow Milestone without first using Initialize Flow Outcome, the system will automatically initialize the outcome for you at that point. This explains why you can set outcomes to Success or Failure and capture data without explicitly using Initialize Flow Outcome.

Best Practice:
Use Initialize Flow Outcome at the beginning of a self-service operation to get accurate duration tracking, then add Flow Milestones at key touchpoints, and finally use Set Flow Outcome to mark success or failure. The milestones help you analyze the customer journey path and identify specific points where customers succeed or drop o

------------------------------
Narasimha Valluri
------------------------------