You are here:
Learn About the Template Bot: Check Issue Status
The bot uses dialogs such as Check the status of an existing issue, Case look up, Case found, Case not found, and Add case comment to check the status of a case and add a case comment.
You are here:
The bot uses dialogs such as Check the status of an existing issue, Case look up, Case found, Case not found, and Add case comment to check the status of a case and add a case comment.
| View supported editions. |
The Check Issue Status dialog skill helps users check the status of an issue they previously reported. Then they can add more comments to the case to update the service rep.
To capture the response to the question about whether the user has a case number, a boolean system entity and corresponding boolean variable are used. The boolean system entity enables the bot to correctly capture and understand more responses than just the standard yes and no.
The bot also asks for an email address. This check provides an extra layer of security and prevents bad actors from looking up cases if they were able to obtain only a case number.
Within the Case look up dialog, we invoke a flow that returns a case based on the case number and email. If multiple cases match, the flow returns the most recent case created.
The bot takes two different paths based on whether an existing case was found. If a case was found, the user can add comments to the case. If the case wasn’t found, the user can speak directly with a service rep who can help.
If the case was found, case details such as subject and status are reported to the user. You can use merge syntax in bot messages to pull out subject and status fields from the variable that contains the matched case.
If users want to update their case, this dialog contains the action that adds their comment to the case they just looked up.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.