Signup to access
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Creating Task Flow Best Practices

Types of Task Flows

1. Service Catalog/Smart Tickets: gathers specific information for an issue from the end-user and routes to the appropriate team 

2. Troubleshooting and Triage: guides end-users through troubleshooting steps and if issue is not resolved routes to the appropriate team 

3. Automation Tasks: the bot gathers the information required for a task and then completes it with the use of APIs 

Why Consider Creating a Task

Tasks can result in a bot creating tickets that have: 

· Pertinent issue details 

· Appropriate categorization 

· Route to appropriate queue along with a copy of the chat transcript. 

This saves time for agents because there is: 

1. No need to create a ticket 

2. No need to gather information for initial triage 

3. No need to touch tickets at L1 for those that require only routing to L2 or L3 

Choosing a Task Flow to Create

An ideal task flow: 

· Is a high volume driver 

· Will make a complex process simpler for the end user 

· Will saves agent/analyst time and effort 

Creating a Task Flow Process

Step 1 

Build a decision tree to outlining: 

· What details would you like the bot to communicate? 

· What information would you like the bot to collect? 

· How should the bot behave to user’s responses? 

· What do you want to happen after the user has completed the flow? 

Step 2 

Provide your decision tree to REZOLVE.AI to review. 

Step 3 

REZOLVE.AI will set up a meeting if there are any questions or suggestions on changing the task flow. 

Step 4 

REZOLVE.AI team will build the task flow in Staging environment. 

Step 5 

REZOLVE.AI will have a meeting with you to review the task flow in the bot. 

Step 6 

You review and provide feedback. If any changes are needed REZOLVE.AI will make them and give back to you for review. 

Step 7 

Once you are happy with the task flow and approve it for production, the REZOLVE.AI team will push to PROD. 

Response Field options

When gathering data from the end user the following response fields are available:

NOTE: The bot can display multiple fields in one prompt or sequential.

Multiple

Single

Best Practices

Set user’s expectations at the beginning of a flow

Give them an idea on how long the task will take

Notify them that approval is needed

When collecting information

Don’t put more that 4-5 response fields on the screen at the same time

If giving the end user more that 3-4 options – make response field a dropdown

When listing items and there is potential you didn’t cover all the options include “Other” in list

Give the end-users an exit option in case they are unable to continue

Give the end-user an “Additional Comment” field, to get any additional details

After collecting required information

Allow end users the opportunity to review what information they provided and Modify/Submit or Cancel

Don’t forget to define what you want the bot to do with the info gathered (i.e. Create a ticket, Send an email, Request approval, preform task etc)

Inform the end-user on what the bot has done and what are the next steps if any i.e. I have created ticket . Someone from the IT Helpdesk will be contacting you shortly.

Download Document
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.