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
| 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.
To download the transaction history log:
- 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 transaction ID.
Transaction Date & Time: Date and time when the transaction occurred.
Bot Name: The Bot name.
Associated Skill Name: Skill associated to the transaction.
Transaction Type : Transaction type includes Automation transactions and Skill transactions
Fulfillment Type: The skill fulfillment using Automation Workflow, Web Services, Text, Email, Pre-Conversation Action, and FAQ.
Fulfillment Details: Fulfillment details include 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), Pre-conversation action.
User name: Name of the logged in user.
Role: Role of the user who initiated the transaction.
Channel: Channel using which the transaction was done.
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 skill transactions and automation transactions. As a tenant administrator in skill builder, you can view the total number of transactions (skill transactions and automation 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 skill transactions and automation transactions.:
Skill transaction rules
The following scenarios create a skill transaction:
- A user completing a custom skill conversation and receiving a text response or calling a Web service, Email Fulfillment.
- A user completing an ITSM Skill conversation such as “view my tickets”, “show me the backlog report” or “unassigned tickets”.
- A user-initiated response to a Luma notification or follow-up which executes a Skill.
- Pre-Conversation Action that executes user prompts and flow goes for the user responses other than Continue/Exit, the transaction is counted.
- Simple Skill Text Fulfillment
- FAQ that gets answered through Luma.
What will not be considered as a skill transaction:
The following scenarios are NOT skill transactions
- Leaving a Skill conversation prior to fulfillment (previously Action) being called. This includes if a user is using an abort word such as “exit”, or the user sitting idle, or not responding before the session timeout.
- Using the Test Bot feature within the Skills Builder Interface.
- Using System Skills such as the Welcome Skill, Registration Skill, or Fallback Skill.
- Triggering the Transfer to Agent Skill to chat with a live support team member.
- An external system using the Luma API to send a notification to a user through Luma. Note: user-initiated skills executed as their response to the follow-up, are counted as billable skill transactions.
- An automated follow-up sent to a user through Luma. Note: user-initiated skills executed as their response to the follow-up are counted as billable skill transactions.
- A pre-conversation action that does not execute an external web service call after prompting the user. For example, a knowledge article is displayed to the user and then asked, "if the article resolves their request". They respond that no it does not resolve their issue and the skill conversation continues.
- Using “small talk” phrases such as “good morning”, “thank you”, and “I like you”.
- Skills executed on a Staging (non-production) Luma environment.
- A Pre-Conversation Action that executes user prompts and user responds to the prompts which are not expected for the user response options defined. These scenarios are considered as aborted skill category.
Automation transaction rules
Automation workflows are licensed for each user. Each execution of a workflow is considered as one transaction. These automation transactions are in addition to skill transactions. If a Luma skill is fulfilled by an Automated Workflow, two transactions are involved, a skill transaction and an automation 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 automation transaction:
- Automation workflows executed on a Staging (non-production) Luma environment.