diff --git a/ai-for-service/channels/add-sunshine-conversations-channel.mdx b/ai-for-service/channels/add-sunshine-conversations-channel.mdx index 714eec137..17b8f1e7d 100644 --- a/ai-for-service/channels/add-sunshine-conversations-channel.mdx +++ b/ai-for-service/channels/add-sunshine-conversations-channel.mdx @@ -6,248 +6,81 @@ noindex: true [Back to Available Channels](/ai-for-service/channels/adding-channels-to-your-bot#available-channels) -AI Agents built on the Platform can be deployed on the **Sunshine Conversations** platform. This channel integration supports conversations with AI Agents and provides a seamless hand-off to agents on **Zendesk**. -## Authorizing the Kore.ai Integration to Sunshine Conversations +AI Agents built on the Platform can be deployed on the Sunshine Conversations platform. This channel integration supports conversations with AI Agents and provides a seamless hand-off to agents on Zendesk. -To enable the integration, you need to provide authorization using your Zendesk credentials. Follow the steps below to complete the **OAuth-based authorization**: -1. Log into the Platform. -2. Navigate to **Channels & Flows** > **Channels** > **Digital** > **All** > **Sunshine Conversations** Channel. -3. Click the **Authorize** button under **Configurations** on the **Sunshine Conversations** panel. - ![Sunshine Channel](/ai-for-service/channels/images/Sunshine-1.png) -4. On the **Zendesk subdomain** page, provide the subdomain and click **Sign in**. -5. On the Zendesk sign-in page, provide your login credentials and click **Sign in**. -6. After you have signed in successfully, a pop-up window will appear asking you to allow Kore.ai to access your Zendesk account. Click on **Allow**. -7. Once the integration is created successfully, you’ll be redirected to the Platform to complete the channel enablement process. +## Configuration On Zendesk -## Switchboard Integration for Agent Handoff +Follow the steps below to configure the Sunshine Conversations channel on Zendesk. -The Platform lets you hand off the conversation to your Zendesk agents via **Zendesk Switchboard** using the **Agent Transfer** node. +1. Sign in to your Zendesk account and navigate to Admin Center > Apps and integrations > Integrations > Conversations integrations. -The **Switchboard Integration API** is used to route the user’s conversations from Zendesk to the Platform. This API has a pass control system to decide whether the conversation is to be routed to an AI Agent or a live agent. -The **Pass Control** action is triggered as a part of the event where the conversation is switched to the App or the agent helpdesk, and also during conversation closure. +2. Click Create an integration. +3. On the Platform, from the Sunshine Conversations channel configuration page, copy the Webhook URL and paste it into the corresponding field in Zendesk. -Developers can define custom metadata to be sent with the existing metadata from the Platform to Zendesk. The additional metadata can also be used to create a Zendesk ticket. -**Capturing the Session Closure Metadata** -The Zendesk Sunshine Configuration flow lets you enable the **Session Closure Metadata** field to let Kore.ai capture the metadata and share it with Zendesk as part of the pass control event triggered when the conversation is transferred to the agent’s helpdesk, or when closing a conversation session. The metadata is captured using the **key-value** pair you provide during the configuration. +4. Under Subscriptions, select the following events: + 1. Switchboard pass control + 2. Switchboard release control + 3. Conversation message -However, providing the key and value inputs when you enable **Session Closure Metadata** is **optional**. -For example: When you provide `SessionKey` as **key** and `apikeyvalue` as **value**, Kore.ai generates the field variable `SessionKey.apikeyvalue` to fetch the **session API key** and pass it to Zendesk as metadata. +5. Click Save to create the integration. +6. After the integration is created, click the three-dot menu next to the integration and select View details. +7. Copy the App ID displayed in the integration details. You will need to enter this ID in the Sunshine Conversations channel configuration in the Platform. -**Important Information on Session Closure Metadata** -* The Platform doesn't trigger the session closure message when the Agent transfer is initiated, and the conversation isn't handed over back to the platform again. -* When the Conversation is handed over to the Platform after the agent transfer, the session closure functionality works as usual. -* For all the new Apps or existing apps that don't have at least one **SessionClosure** metadata tag, the **SessionClosure** switch is turned off by default. -* For all the existing apps that have at least one **SessionClosure** metadata tag, the switch is turned on by default. -* The Platform introduces the [KoreUtil.getSunshineConversationsMetadata](/ai-for-service/apis/automation/koreutil-libraries#koreutil-closeconversationsession) function to let a App developer fetch the stored metadata (Get API operation), and use it for the following: - * Entities where JavaScript is supported like advanced messages for a prompt, script nodes, etc. - * Simple messages like plain text prompts. -* Any additional changes or updates to the channel configurations should go through the [Publishing your App](/ai-for-service/deployment/publishing-app). - -**Selecting the Default and Next Integrations for Transferring Control** - -When you have a pre-existing switchboard integration, the Platform allows you to configure it as the default for the initial pass control during conversation initiation. Alternatively, you can select the Kore switchboard integration to designate the pass control. - -You can review and edit these Switchboard integrations for newly created or pre-existing channel configurations in the **Switchboard Configuration** window. The Switchboard Configuration includes the **Default Switchboard Integration** for initiating conversations and the **Next Switchboard Integration** to transfer control after conversation session closure and the completion of agent conversations. - -### Steps to Set up Agent Handoff - -1. Enable the **Enable Agent Handoff** option under **Configurations** in the **Sunshine Conversations** panel. -2. From the[ Zendesk Admin Center,](https://support.zendesk.com/hc/en-us/articles/4581766374554#topic_hfg_dyz_1hb) navigate to **Apps & Integrations** and click the **Conversations API** menu option to get your **API Key** and **API Secret**. Please get in touch with your Zendesk sales representative if you don’t see this menu. -3. Paste these values in their respective fields on the Platform under **Sunshine Conversations** > **Configurations** > **OAuth** > **Enable Agent Handoff** section. - ![alt_text](/ai-for-service/channels/images/sunshine-(1).png) - -4. Click **Configure** for Switchboard Integration to set up the integrations available in your Sunshine Conversations account app. - ![alt_text](/ai-for-service/channels/images/sunshine-(5).png) - -5. Select the required option for the following integrations in the **Switchboard Configuration** window: - 1. **Default Switchboard Integration**: Select the primary contact point for users in your Sunshine Conversations application. - 2. **Next Switchboard Integration to Kore.ai**: Select the next switchboard integration to which the control of an AI Agent conversation is passed from Kore.ai. - 3. **Next Switchboard Integration to Agent**: Select the next switchboard integration to which control is transferred after an agent conversation with a user. - - ![alt_text](/ai-for-service/channels/images/sunshine-(3).png) -The options listed include the default mapped integrations and others available in your Sunshine Developer account. - -6. After selecting the above fields, click **Done**. - -7. On the **Zendesk Sunshine Configurations** window, follow either step below to set **Session Closure Metadata**: - * Disable the toggle switch if you don’t want the Platform to pass the session metadata to Zendesk. - ![alt_text](/ai-for-service/channels/images/sunshine-(4).png) - * Enable **SessionClosure Metadata**, and do one of the following: - * Provide at least one **Key** and **Value** input (optional) to allow Kore.ai to capture the session metadata using the switchboard integration API and share it with Zendesk. Adding these parameters and saving the configuration will create a Zendesk ticket with the conversation details and close it. - ![alt_text](/ai-for-service/channels/images/sunshine-(2).png) - * Skip the **Key-Value** input and move to the next step. Not adding these parameters will create a Zendesk ticket with the conversation details but not close it. - -8. Select **Yes** for **Enable Channel**. - ![alt_text](/ai-for-service/channels/images/sunshine-(6).png) -9. Click **Save**. - -## Templates Support - -Sunshine Conversations templates are pre-defined structures you can use to send rich messages to users for consistent and engaging interactions on the Platform. Templates help create a set of “canned messages” or “agent saved replies,” which is especially useful for messages that are difficult to craft on the fly because they require external resources. - -To trigger various message templates, you must use a specific JavaScript format in the **Bot Responses** section of the **Message Node** in a Dialog Task. Below are the supported templates along with their sample code formats: - -* **Compound Message**: Combines multiple elements like text, images, buttons, and quick replies to create an engaging and informative message. [See example](https://docs.smooch.io/guide/template-messages/#compound-message). - - ```js - var message = { - "content":{ - type: 'image', - text: 'I strongly recommend our Family Basket. It's made just for people like you.' - "actions": [ - { - type: 'postback', - text: 'Subscribe', - payload: 'NOOP' - }, - { - type: 'postback', - text: 'Learn more', - payload: 'NOOP' - } - ], - mediaUrl: 'https://media.smooch.io/templates/template-family-basket.jpg' - } - } - print(JSON.stringify(message)) - - ``` - -* **Carousel Message**: Allows you to send a series of cards that users can swipe through. Each card can contain an image, title, subtitle, and buttons for further actions. [See example](https://docs.smooch.io/guide/template-messages/#carousel-message) . - - ```js - var message = { - "content": { - "type": "carousel", - "items": [ - { - "title": "Tacos", - "description": "Description", - "mediaUrl": "https://som.iitkgp.ac.in/images/71stFoundationDay.jpg", - "actions": [ - { - "text": "Select", - "type": "postback", - "payload": "TACOS" - }, - { - "text": "More info", - "type": "link", - "uri": "https://som.iitkgp.ac.in/images/71stFoundationDay.jpg" - } - ] - }, - { - "title": "Ramen", - "description": "Description", - "mediaUrl": "https://som.iitkgp.ac.in/images/71stFoundationDay.jpg", - "actions": [ - { - "text": "TemplateVisible", - "type": "postback", - "payload": "RAMEN" - }, - { - "text": "More info", - "type": "link", - "uri": "https://som.iitkgp.ac.in/images/71stFoundationDay.jpg" - } - ] - } - ] - } - }; - print(JSON.stringify(message)); - ``` - -* **File Message**: Allows you to send a file to the user. This can be useful for sharing documents, PDFs, images, or other types of files. [See example](https://docs.smooch.io/guide/template-messages/#file-message) . - - ```js - var message = - { - "content":{ - type: 'file', - role: 'appMaker', - mediaUrl: 'https://media.smooch.io/templates/template-warranty.pdf' - } - } - print(JSON.stringify(message)) - ``` - -* **Form Message**: Allows you to collect information from users through a structured form. This can include text fields, dropdown menus, radio buttons, and more. [See example](https://docs.smooch.io/guide/template-messages/#form-message) . - - ```js - var message = - { - "content":{ - type: 'file', - role: 'appMaker', - mediaUrl: 'https://media.smooch.io/templates/template-warranty.pdf' - } - } - print(JSON.stringify(message)) - ``` - -* **Quick Reply**: Provides users with predefined response options that they can select with a single tap. This can streamline interactions and guide users towards specific actions. [See example](https://docs.smooch.io/guide/template-messages/#quick-reply) . - - ```js - var message = - { - "content": { - type: 'text', - text: 'Which language do you prefer?', - actions: [ - { - type: 'reply', - text: 'English', - iconUrl: 'https://example.com/english.png', - payload: 'Hollywood' - }, - { - type: 'reply', - text: 'Hindi', - iconUrl: 'https://example.com/hindi.png', - payload: 'Bollywood' - } - ] - } - } - print(JSON.stringify(message)) - ``` - -* **Location Request**: Allows you to request the user’s location. This can be useful for services that require location information, such as finding the nearest store or providing location-based services. [See example](https://docs.smooch.io/guide/template-messages/#location-request) . - - ```js - var message = - { - "content":{ - type: 'text', - role: 'appMaker', - text: 'Let us know where you are.', - actions: [ - { - type: 'locationRequest', - text: 'Send location' - } - ] - } - } - print(JSON.stringify(message)) - - ``` - -### Create a Template - -To learn how to create a template, click [here](https://docs.smooch.io/guide/template-messages/#creating-a-template) . - -### Send a Template - -Once you create a template, you can send it to a user. [Learn more](https://docs.smooch.io/guide/template-messages/#sending-a-template-message) . \ No newline at end of file +8. Navigate to Admin Center > AI > AI Agents > AI Agents > Marketplace Bots. +9. Locate the integration you created, click the three-dot menu, and select Set as Default for All Channels. + + + + + + + +## Configurations On the Platform + +Follow the steps below to configure the Sunshine Conversations channel on the Platform. + + +1. In the Sunshine Conversations channel configuration, enter the App ID copied from Zendesk. +2. Enter your Zendesk subdomain. For example, if your Zendesk URL is `https://koreai-1234.zendesk.com`, enter `koreai-1234` as the subdomain. +3. Click Authorize. +4. Enter your Zendesk subdomain and click Sign In. + +5. When prompted, click Allow to grant the required permissions. + + + + + + +### Retrieve Conversations API Key and Secret + +follow the steps below to retrieve the Conversations API Key and Secret from Zendesk. + +1. Log in to Zendesk Admin Center. +2. Navigate to: Admin → Apps and Integrations → APIs → Conversations API Or access directly: `https://{{subdomain}}.zendesk.com/admin/apps-integrations/apis/conversations-api` +1. Generate or copy: + * API Key ID + * API Secret + + + + + +### Agent Handoff + +Enable Agent Handoff to allow conversations to be transferred to Zendesk agents through the Zendesk Switchboard using the Agent Transfer node. + + +### SessionClosure MetaData + +Enable Session Closure Metadata to send captured metadata to Zendesk as part of the pass control event triggered when a conversation session is closed. + +The Platform appends the key-value pairs configured in this section to the metadata sent to Zendesk. diff --git a/ai-for-service/integrations/agents/configuring-the-salesforce-agent.mdx b/ai-for-service/integrations/agents/configuring-the-salesforce-agent.mdx index 65858fe9c..38df48a5e 100644 --- a/ai-for-service/integrations/agents/configuring-the-salesforce-agent.mdx +++ b/ai-for-service/integrations/agents/configuring-the-salesforce-agent.mdx @@ -175,7 +175,7 @@ The platform supports two Salesforce integration methods: | Developer Name | Developer name (from Step 2) | | Unmask PII Data (optional)| Enable to allow PII data to be unmasked when the AI Agent connects to a Salesforce agent. Disabled by default. See [PII Data Masking](/ai-for-service/app-settings/advanced-settings/pii-data-masking). | - ![MIAW agent credentials](/ai-for-service/integrations/agents/images/miaw-metadata9.png) + ![MIAW agent credentials](/ai-for-service/integrations/agents/images/miaw-metadata9.jpg) 5. To make Salesforce the default agent, enable **Default Agent System for all bot channels**. @@ -265,7 +265,7 @@ To populate metadata on the Salesforce dashboard, complete these steps in order: - **Developer Name** - ![Salesforce configuration](/ai-for-service/integrations/agents/images/miaw-metadata9.png) + ![Salesforce configuration](/ai-for-service/integrations/agents/images/miaw-metadata9.jpg) 3. Click **Save**. 4. In Dialogflow, insert a **Script Node** before the Agent Transfer Node. diff --git a/ai-for-service/integrations/agents/configuring-the-zendesk-agent.mdx b/ai-for-service/integrations/agents/configuring-the-zendesk-agent.mdx new file mode 100644 index 000000000..9df9cd320 --- /dev/null +++ b/ai-for-service/integrations/agents/configuring-the-zendesk-agent.mdx @@ -0,0 +1,91 @@ +--- +title: Configuring the Zendesk Agent +sidebarTitle: Zendesk Agent +noindex: true +--- +[Back to Agent Transfer Integrations](/ai-for-service/integrations/overview#agent-transfer) + + +The Zendesk Agent integration allows you to hand off AI Agent conversations to live agents on Zendesk. The AI Agent acts as an intermediary between users and Zendesk agents. + + +## Configuration On Zendesk + +1. Sign in to your Zendesk account and navigate to Admin Center > Apps and integrations > Integrations > Conversations integrations. +2. Click Create an integration. +3. In the integration configuration, copy the Webhook URL from the Sunshine Conversations channel configuration page on the platform and paste it into the corresponding field in Zendesk. + +4. Under Subscriptions, select the following events: + 1. Switchboard pass control + 2. Switchboard release control + 3. Conversation message + + +5. Click Save to create the integration. +6. After the integration is created, click the three-dot menu next to the integration and select View details. +7. Copy the App ID displayed in the integration details. You will need to enter this ID in the Sunshine Conversations channel configuration in the platform. + + +8. Navigate to Admin Center > AI > AI Agents > AI Agents > Marketplace Bots. +9. Locate the integration you created, click the three-dot menu, and select Set as Default for All Channels. + +## Configurations On Platform + +1. Log in to the Platform. +2. Navigate to Channels & Flows > Channels > Digital > All > Sunshine Conversations Channel. +3. Enter the App ID copied from Zendesk. +4. Enter your Zendesk subdomain. For example, if your Zendesk URL is `https://koreai-1234.zendesk.com`, enter `koreai-1234` as the subdomain. +5. Navigate to: Admin > Apps and Integrations > APIs > Conversations API. +6. Generate or copy (if applicable) + 1. API Key ID + 2. API Secret + + +**Ignore Events From** + +Provide a list of BotKit authors whose messages should be excluded from being sent to the Zendesk agent. + +**Configure Ticket Field IDs (Agent View)** + +Ticket fields (labels visible to agents) must be configured on the Zendesk configuration page. These field IDs determine the label name to the agent during conversations. + + + +**Configure Third-Party Integration Events** + +1. If you are using a third-party integration URL, copy the URL where you want to listen to the events sent by Zendesk. +2. Navigate to the Zendesk Conversations Integrations page: `https://{{subdomain}}.zendesk.com/admin/apps-integrations/integrations/conversations-integrations/integrations`. +3. Select the events you want to subscribe to. +4. Copy the exact event names. +5. Provide these event names in the Platform configuration. + + + +**Authorize** + +1. Click Authorize. +2. Enter your Zendesk subdomain and click Sign In. + +3. When prompted, click Allow to grant the required permissions. + + +**Conversation Type** + +Choose Single Conversation if you want to maintain a one-to-one relationship between the user and a single persistent record. Select Multiple Conversations if you want each chat session to generate a unique Conversation ID for distinct tracking and reporting. + +## Additional Details + +### Configure Conversation Context Variables + +To pass specific user and conversation details during agent transfer, use the following context variables: + +* Zendesk Internal User ID: `context.session.BotUserSession.agentHandoffMeta.zendeskInternalUserId` + +* Zendesk Conversation ID: `context.session.BotUserSession.agentHandoffMeta.zendeskConversationId` + +### Zendesk Account Usage Limitation + +* A Zendesk account can be used with only one AI Agent at a time. +* If you want to reuse the same account: + * Remove the existing agent configuration first. + * Then configure it with the new AI Agent. \ No newline at end of file diff --git a/ai-for-service/integrations/agents/images/miaw-metadata9.png b/ai-for-service/integrations/agents/images/miaw-metadata9.png deleted file mode 100644 index c0f042d76..000000000 Binary files a/ai-for-service/integrations/agents/images/miaw-metadata9.png and /dev/null differ diff --git a/ai-for-service/manage-assistant/feedback-survey.mdx b/ai-for-service/manage-assistant/feedback-survey.mdx index 327706162..0c4c548e4 100644 --- a/ai-for-service/manage-assistant/feedback-survey.mdx +++ b/ai-for-service/manage-assistant/feedback-survey.mdx @@ -37,13 +37,13 @@ Go to **Automation AI > Virtual Assistant > Feedback Survey**. ### NPS (Net Promoter Score) -Measures customer loyalty with a single question rated on a **0-10 scale**. +Measures customer loyalty with a single question rated on a **0-10 scale**. Users can customize the score ranges for detractors, passives, and promoters to meet their requirements. -| Category | Score | Description | -|---|---|---| -| **Promoters** | 9-10 | Loyal, satisfied customers highly likely to return. | -| **Passives** | 6-8 | Satisfied customers who may or may not return. | -| **Detractors** | 0-5 | Unsatisfied customers unlikely to return; may share negative experiences. | +| Category | Description | +|---|---| +| **Promoters** | Loyal, satisfied customers highly likely to return. | +| **Passives** | Satisfied customers who may or may not return. | +| **Detractors** | Unsatisfied customers unlikely to return; may share negative experiences. | ### CSAT (Customer Satisfaction) diff --git a/ai-for-service/release-notes/platform-services.mdx b/ai-for-service/release-notes/platform-services.mdx index dcd704a6a..0224999b5 100644 --- a/ai-for-service/release-notes/platform-services.mdx +++ b/ai-for-service/release-notes/platform-services.mdx @@ -19,13 +19,13 @@ This update includes enhancements and bug fixes. The key enhancements included i

Granular Role Sub-permissions for Analytics and Settings

-Role management now supports granular sub-permissions for Analytics and Settings, letting administrators grant access to specific dashboards, menus, and configuration pages independently. This enables more precise access control, helping restrict sensitive operational and configuration data, while the existing permission structure for other sections stays unchanged. +Role management now supports granular sub-permissions for Analytics and Settings, letting administrators grant access to specific dashboards, menus, and configuration pages independently. This enables more precise access control, helping restrict sensitive operational and configuration data, while the existing permission structure for other sections stays unchanged. [Learn more→](/ai-for-service/user-management/users-and-role#automation)

Analytics

NPS Range Calculation

-You can now customize the Net Promoter Score (NPS) classification ranges for detractors, passives, and promoters, letting you tailor the scoring thresholds to your requirements. +You can now customize the Net Promoter Score (NPS) classification ranges for detractors, passives, and promoters, letting you tailor the scoring thresholds to your requirements. [Learn more→](/ai-for-service/manage-assistant/feedback-survey#nps-net-promoter-score)

Language Management

diff --git a/ai-for-service/user-management/users-and-role.mdx b/ai-for-service/user-management/users-and-role.mdx index e9d238eab..e3435f6a9 100644 --- a/ai-for-service/user-management/users-and-role.mdx +++ b/ai-for-service/user-management/users-and-role.mdx @@ -279,6 +279,59 @@ The tables below show the access level each default role and custom role has for | **Automations Dashboard** | Access automation metrics in Dashboard. | Yes | Yes | Yes | Yes | No | Yes / No | | **Automations Tab** | Access the Automations tab and Platform. | Yes | Yes | Yes | No | No | Yes / No | +**Bot Analytics** + +The table below shows the sub-permissions under Bot Analytics. Each menu or sub-menu permission can be granted independently to a role through Role Management. + + + + +| Permission | Description | Owner | Developer | Tester | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-----------|--------| +| **Summary** | Provides a consolidated snapshot of AI Agent conversation, user, and NLP/execution performance data aggregated from the Conversations, Users, and other overview sub-dashboards. | Yes | Yes | Yes | +| **Conversations Dashboard** | Shows self-service rates, agent transfers, incomplete sessions, channel distribution, and conversation path analysis to evaluate overall AI Agent effectiveness. | Yes | Yes | Yes | +| **Conversations History** | Lets users review and filter transcripts of past conversations, examine event-level chat details, and apply labels/tags for training and follow-up. | Yes | Yes | Yes | +| **Users Dashboard** | Tracks unique, new, and returning users, daily engagement trends, and cohort-based retention analysis. | Yes | Yes | Yes | +| **Feedback Dashboard** | Displays feedback score distribution and trends along with exportable NPS, CSAT, and Like/Dislike survey results. | Yes | Yes | Yes | + + + + + +| Permission | Description | Owner | Developer | Tester | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-----------|--------| +| **Overview** | Shows aggregated LLM token usage, request volume, success rates, and latency across models and GenAI features to guide cost and scaling decisions. | Yes | Yes | Yes | +| **Performance Analytics** | Provides a drill-down record of usage and performance trends for a specific LLM model or GenAI feature selected from the Overview dashboard. | Yes | Yes | Yes | +| **GenAI Logs** | Displays detailed request-response logs sent to LLMs, including payloads, token counts, and guardrail outcomes, for monitoring and prompt optimization. | Yes | Yes | Yes | + + + + + +| Permission | Description | Owner | Developer | Tester | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-----------|--------| +| **Performance Dashboard** | Tracks post-deployment intent identification, goal completion, API execution, and script execution rates, with drill-down into specific interactions. | Yes | Yes | Yes | +| **Conversation Insights** | Groups user utterances into semantic clusters so designers can classify them as true/false positives/negatives to spot misclassifications and guide retraining. | Yes | Yes | Yes | +| **NLP Insights** | Shows intent-found, intent-not-found, and unhandled-utterance metrics to help improve intent training and coverage. | Yes | Yes | Yes | +| **Task Execution Logs** | Provides detailed task, API, and script execution logs, including failed-task data and custom debug information, for troubleshooting. | Yes | Yes | Yes | +| **Conversation Flows** | Visualizes user journeys, showing commonly used intents, navigation paths, and drop-off points, in both aggregated and session-based views. | Yes | Yes | Yes | + + + + + +**Bot Settings** + +The table below shows the sub-permissions under Bot Settings. Each menu or sub-menu permission can be granted independently to a role through Role Management. + +| Permission | Description | Owner | Developer | Tester | +|---|---|---|---|---| +| **Advanced Settings** | Covers system-level configuration such as session behavior, data privacy, PII masking, and URL management. | Full | Full | No | +| **App Profile** | Allow general application configuration, including name, description, icon, target audience, default language, etc. | Full | View | No | +| **Language Management** | Controls configuration of supported languages, translation services, and language-specific NLU for the assistant. | Full | Full | No | +| **Dev Tools** | Contains developer resources including Bot Functions and authorization profiles. | Full | Full | No | +| **Variables** | Governs definition and management of reusable environment and content variables shared across tasks, nodes, and responses. | Full | Full | No | +| **Change Logs** | Maintains a filterable, exportable audit history of all modifications made across the app's modules. | Full | Full | No | ### Flows and Routing | Permission | Description | Owner | Developer | Tester | Supervisor | Agent | Custom |