| Table of Contents |
|---|
Overview
This article describes the tenant subscription information which includes Entitlement details, Transaction History Log, and Refill History. This section helps the tenant administrator view subscription information, when to renew the subscription, how many transactions are left, and the transactions log. All this information gives the Administrator transparency into their usage of Luma.
Transaction Settings
On the Settings page, click the Subscription Information tab to view the tenant subscription details as shown below.
Entitlement Details
Entitlement details displays the following information.:
| Field | Description |
|---|---|
| Purchased Transactions | Displays the number of transactions the tenant purchased. |
| Used Transactions | Displays the number of transactions the tenant used to date. |
| Available Transactions | Displays the remaining transactions which can be used by the tenant. |
| Contract Start Date | Displays the contract start date of the subscription. |
| Contract End Date | Displays the contract end date of the subscription. |
| Technical Contact Email | Email addresses of the technical contacts who manages the tenant. You can edit the information if required. Note: You can add multiple email addresses. |
| Billing Contact Email | Email addresses of the billing contacts who manages the tenant subscriptions. You can edit the information if required. |
Transaction History Log
You can download the transaction history data for your tenant environment. You can specify the duration of the transaction history by selecting a date range.
...
- 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.
Transaction Refill History
As a tenant administrator you can view the list of transactions refill history of the tenant. A refill is done automatically if opted during tenant provisioning. Else, can be done manually by requesting the Support from Serviceaide. The refill history displays the number of transactions added on a specific date either manually or automatically.
| Field | Description |
|---|---|
| Refill Type | Displays the refill type, whether the transaction is refilled manually or automatically. |
| Refill Date | Displays the date when the transaction is refilled. |
| Added Transactions | Displays the number of transactions refilled. |
Luma Transactions
Luma transactions include conversation transactions and automated workflow transactions. As a tenant administrator in skills builder, you can view the number of transactions that are processed through Luma since the contract start date. As a result, you can ensure compliance with license agreements and purchase more transactions if necessary.
The following section describes rules that define conversation transactions and automated workflow transactions.:
Conversation transaction rules
The following scenarios create a conversation transaction:
...
What will not be considered as an automated workflow transaction:
- Automation workflows executed on a Staging (non-production) Luma environment.