Context
...
ups in Luma Virtual Agent are designed to eliminate the manual effort
...
spent by Administrators and Support Analysts to
...
follow up with users and other routine tasks. You can create an actionable Follow-up in Luma Bot Builder to send smart notifications to end-users automatically from the bot, based on defined conditions such as ticket updates, approaching SLAs, etc. This
...
significantly
...
saves the analysts time and
...
In this example, we will talk about configuring Follow-ups on the Resolved tickets in ISM and encourage the user to close the ticket.
In the example below, we will fetch a list of all the resolved tickets for a specific user and present the tickets that need closure with action in Cards in the channel.
...
Fetch all the resolved tickets for every 11th Minute from ISM System.
...
Format the data if required
...
Define the list of users for whom the follow-up is configured. This can be either an individual User or Group as well. For now, we will use our own Username.
...
Define the message format on how it will be shown to the users. Select Cards and enter the required details.
...
Select the Channel in which you want the follow-ups to happen. As we are testing on the Test Widget, we will select Test Widget as channel.
...
in turn, cost spent by your Organization.
Follow the below steps to configure a Follow-up:
Navigate to Tenant menu → Settings → Follow-ups.
Click on Create Follow-up.
In the Follow-up details section, add Name and set Status to Active.
Click Next to add Data Extraction information.
Define the Polling Frequency at which the data should be fetched from the External system.
In Conditional Data Extract add the Web Service Operations to fetch the data and set the values using in Global, Local, and Custom User Attributes as required.
Define Data Reconciliation fields.
Looping element is the data received from the Operations to be processed.
Data Reconciliation ID is used to reconcile the data record on subsequent follow-ups.
Select the response type in Individual Record Data Type.
Click Next to configure the Recipients list.
Add a Web Service Operations call to fetch recipient information from an external system
Define Recipients reconciliation fields. Map the recipient fields extracted from the Data Extraction step to Luma VA User or Group Field to reconcile.
Click Next. Configure the Message to be notified to the end-user in the chat channel. Use the context variable @{followup.data} to refer to the list of records.
Select the Channel where the end-user should be notified. By default, it is set to the “Last Used” channel. This sends the follow-up message to the channel last used by the recipient.
The Next step is to define the notification frequency.
On the Notification Schedule, define the frequency and number of Follow-up attempts to be done with the recipients.
Click Next to configure Post Follow-up Actions. These are predefined actions to be executed after the follow-up is executed. You may add Integrations to connect to a target system or Set Attribute to transform that should be executed After each follow-up attempt or After all follow-up attempts i.e. upon completion of the follow-up activity. The step is optional.
Click Create.
Your Follow-up is now ready and is triggered automatically based on the scheduled frequency. You may view the follow-up sent by your Bot on Conversation History.
| Info |
|---|
|