Administrators and contact center managers use flow outcomes to gather data about self-service success. This information helps determine how well Architect flows service the customer interaction and includes:
For example, if a customer tries to make a payment three times and only succeeds on the third attempt, then flow outcomes reporting sees this as an overall successful outcome and reports it as such. Flow milestones reporting tells you that that multiple payment attempts occurred.
Use flow outcomes with Architect’s and to determine whether customers successfully complete the self-service operation.
An organization can include up to 1,000 flow milestones. You can edit the name and description, and you can delete a flow milestone. An organization can include up to 100 flow outcomes. You can edit the name and description of a flow outcome, but you cannot delete it. Because of these limitations, best practice recommends that you carefully consider flow outcome use before you create them.
In Architect flows, only the last 20 milestones per outcome and the last 100 milestones per flow is reported in analytics.
To add a flow outcome, follow these steps:
Get user feedback about articles.