This article deals with the following areas of follow-up:

The Skills Builder has the following pre-configured follow-up skills, and you can add additional customized follow-up skills as required.

Pending Approval Follow-up: Luma can follow-up on the pending tickets for approval by fetching all the ‘Pending for Approval’ tickets. It can also fetch all the pending approvers for a ticket ID from a given ticket list. Luma follows up only in the last communicated channel instead of email. You are prompted to take any of the following actions from the communication channel, such as Skype for Business:

• Approve: In case the ticket needs to be approved
• Reject: In case the ticket needs to be rejected with rejection details
• Need more info: In case additional details are required to process the ticket

Create an Automated Follow-up Skill

To create a new automated follow-up skill, do the following:

1. On the Bots Dashboard, click the more optionsicon and select Bot Configuration.
   The Bot Configuration page appears with Bot Information, Welcome Skills, Channels, Follow-up and Satisfaction Survey tabs.
2. Click the Follow-up tab to view the list of created follow-ups as shown below.
   
3. Click New Follow-up to create a new follow-up skill.
   The New Follow-up page appears as shown below.
   
4. Enter the new follow-up Name. For example, Follow up on pending items.
5. By default, system automatically displays the Type of follow-up as Status.

6. Set the follow-up Status as Active or Inactive using the toggle button.

   1. Active: It is used to ensure the Follow up configuration is Active.

   2. Inactive: It is used to ensure the Follow up configuration is Inactive.

7. Enter the Initial Status of the ticket for the follow-up skill. This field must align to your connected Service Desk system and an existing ticket status, for example, Pending Info, Pending Approval and more. This field triggers the start of the follow-up process. For more details on the ticket management process, refer Modify the Status of a Ticket. Following is an example of the ITSM ticket, which shows the Status as Pending Info.
   

   Note

   Ensure that the Initial Status is unique, as multiple follow-up skills for the same Initial Status cannot be created. The following error appears if you try creating duplicate follow-ups with the same values.

   

8. Enter the Post Status of the ticket if required. Post Status makes the follow-up to go into a loop. If Post Status is blank, the follow-up cycle keeps repeating, that is, if the ticket status remains the same, Skills Builder continues to pick the ticket in subsequent attempts. 

9. Enter the Number of attempts on user's primary chat channel.
   This value determines the number of times Luma reaches out to the customer on the last channel they used to communicate with Luma. For example, if the value was set to 3, Luma will reach out to the user three times on Slack, which is the channel they last used Luma with. The allowed values are only between 1 to 10. By default, system automatically displays the value as 3, which can be changed.

10. Enter the Number of retries on the active channel.

    Note

    If a user is active in a conversation on their primary chat channel, Luma will wait and try again later. This setting defines how many times Luma should retry during each attempt. The allowed values are only between 1 to 9. By default, Luma will retry three times, which can be changed.

11. Enter the Follow Up Frequency and select the frequency duration from the drop-down list.

    Note

    The follow-up frequency defines the time between follow-up attempts. Once per day is a best practice. The allowed values are between 1 to 5 days. By default, system automatically displays the value as 1 day, which can be changed to Hours and Minutes. If you select Hours, you can select the frequency duration between 1 to 120 Hrs. If you select Minutes, you can define the frequency duration between 10 to 72000 Mins.

12. Select the Add Worklog check box to add the worklog details.

13. Enter the Worklog Text details.

    Note

    Worklog Text field appears only if Add Worklog check box is selected. If this check box is selected, the work log text will be logged to the ticket each time a follow-up is made. It can be used for auditing purposes.

14. In the Card Message section, enter the follow-up skill Message Text.
    The message text informs the user about the tickets they need to act upon when a follow-up is made. You can configure the text for the user, along with the actions to be taken during the follow-up attempts.
15. Enter the follow-up skill Title and Sub Title.
16. Select the follow-up skill Option Type as Text or URL from the drop-down list and enter the Option Title and Option Response. If you select URL, you can provide the URL to a page, while text allows you to provide the follow-up text for the Skills Builder. For example, you can select the Option Type as URL, specify the Option Title as View Ticket and the Option Response as @config.csm_app_url#ticket/@resp.items.ticket_identifier. This provides the Self-service user with a URL to view the ticket.
    If you select the Option Type as Text, specify the Option Title as Add Comments and Option Response as Add comments for @resp.items.ticket_identifier; this allows you to add comments for a given ticket. 
17. Click Save to save the new follow-up skill, else click Cancel to discard the process.

Search and Edit Follow-up Skill

To search an existing follow-up skill, enter the Name, Initial Status or Post Status in the search box and press Enter. The skills matching the search criteria appear.

You can select the number of items to be viewed per page, for example, 10. Click the arrows to navigate to the next and previous pages.

To edit an existing follow-up skill, click the skill and make the required changes. Click Save to save the edits.

During the chat conversation in a channel, the follow-up ticket cards are displayed in a batch of 10 without pagination.