| Table of Contents |
|---|
Overview
...
When Luma has a conversation with a user through a skill or FAQ there is a point of fulfillment. That fulfillment creates a conversation transaction which is the billable or licensable entity. Organizations buy transactions based on their need and use them up over time.
The following scenarios create a conversation transaction:
...
Automated workflows are licensed by tenant or customer. Each execution of a workflow is considered as one transaction. These automated workflow transactions are in addition to conversation transactions. If a Luma skill is fulfilled by an Automated Workflow, two transactions are involved, a conversation transaction and an automated workflow transaction.
The following scenarios create an automated workflow transaction:
- Invocation of an automation workflow at any place in (as the fulfillment) the process of skill execution.
What will not be considered as an automated workflow transaction:
- Automation workflows executed on a Staging (non-production) Luma environment.
Luma Usage Alerts
Usage alerts are sent to the technical and billing contacts via email at various stages, specifically when the usage of transaction approaches to 75%, 85%, and 95%. Alert is also sent when the contract approaches its due date.
...
- Select the From date. By default, a period of 30 days is displayed in the calendar. A maximum of three months (90 days) can be specified to download the transaction history.
- Select the To date.
- Click Download
The file will be downloaded in .csv format as shown below:
The following columns are displayed.:
Transaction ID: The unique identifier of the transaction.
Transaction Date & Time: The date and time when the transaction occurred.
Bot Name: The name of the Bot where the transaction occurred.
Associated Skill Name: The skill associated to the transaction such as FAQ, View Ticket, and Add Worklog.
Transaction Type : Indicates the type of transaction that occurred either a Automated Workflow transaction or a Conversation transaction. This relates to the transaction licenses.
Fulfillment Type: The type of fulfillment that was used on the Skill associated with the transaction. This could be Automation Workflow, Web Services, Text, Email, Pre-Conversation Action, or FAQ.
Fulfillment Details: Fulfillment details includes the Automation workflow name, Web services connector and operation, Text ( and No need of Text response with actual output), Email-Template Name ( and for custom templates have "Email" only), or Pre-conversation action.
User Name: The username of the user chatting with the Luma bot that initiated this transaction.
Role: Role of the user who initiated the transaction.
Channel: The chat channel used to initiate this transaction. For example, MS Teams, Skype for Business, Web Widget, Slack and so on.
...