From 8af4a53099756b35638a77f9fd022b3da4c10fd3 Mon Sep 17 00:00:00 2001 From: vishnubkore Date: Wed, 15 Jul 2026 16:31:20 +0530 Subject: [PATCH 1/5] Update agent-behavior-settings.mdx --- .../administration/agent-behavior-settings.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/agent-platform/administration/agent-behavior-settings.mdx b/agent-platform/administration/agent-behavior-settings.mdx index ddcfbe4fc..c70077eac 100644 --- a/agent-platform/administration/agent-behavior-settings.mdx +++ b/agent-platform/administration/agent-behavior-settings.mdx @@ -132,12 +132,12 @@ Session Lifecycle controls how long transfer sessions stay open on each channel Default Routing sets the fallback connection, queue, priority, and post-transfer behavior that the platform uses when an agent initiates a transfer. Individual agents or workflows can override these values at runtime. -| Setting | Description | Default | -|----------------------|------------------------------------------------------------------------------------------------------------------|--------------------------------| -| **Connection** | Agent desktop connection for transfers. Select a configured connection or leave as **None (use agent-level config)** to defer to the agent's own setting. Click **+** to add a new connection inline. | None (use agent-level config) | -| **Queue** | Default queue ID for routing. The platform routes transferred conversations to this queue unless the agent specifies a different one. | `default` | -| **Priority** | Default priority level for transferred conversations. Scale: 0 (lowest) to 10 (highest). | 5 | -| **Post-Agent Action** | What happens after the human agent ends the conversation. **Return to bot** hands control back to the AI agent. **End session** terminates the session entirely. | Return to bot | +| Setting | Description | Default | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| **Connection** | Agent desktop connection for transfers. Select a configured connection or leave as **None (use agent‑level config)** to defer to the agent's own setting. To add a new connection, select **+**, which opens a dialog window listing supported providers: **Kore SmartAssist, Genesys Cloud, Salesforce, ServiceNow, and Five9**. | None (use agent‑level config) | +| **Queue** | Default queue ID for routing. The platform routes transferred conversations to this queue unless the agent specifies a different one. | `default` | +| **Priority** | Default priority level for transferred conversations. Scale: 0 (lowest) to 10 (highest). | 5 | +| **Post-Agent Action**| What happens after the human agent ends the conversation. **Return to bot** hands control back to the AI agent. **End session** terminates the session entirely. | Return to bot | ### Voice Gateway From 72bef4240c69bffc2599c29cead1a8c2cf4d2c45 Mon Sep 17 00:00:00 2001 From: vishnubkore Date: Wed, 15 Jul 2026 19:07:12 +0530 Subject: [PATCH 2/5] Microsoft Teams section added in Digital.mdx --- agent-platform/channels.mdx | 28 ++++----- agent-platform/channels/digital.mdx | 97 +++++++++++++++++++++++++++++ agent-platform/channels/voice.mdx | 2 +- agent-platform/drafts/digital.mdx | 6 -- 4 files changed, 112 insertions(+), 21 deletions(-) create mode 100644 agent-platform/channels/digital.mdx delete mode 100644 agent-platform/drafts/digital.mdx diff --git a/agent-platform/channels.mdx b/agent-platform/channels.mdx index fefebbf60..2a63c1745 100644 --- a/agent-platform/channels.mdx +++ b/agent-platform/channels.mdx @@ -31,20 +31,20 @@ All five route to the same agent definition. The adapter normalizes inbound and The Platform supports the following messaging or digital channels: -| Channel | Description | Setup | -|-----------------|------------------------------------------------------------------------------------------|------------------------| -| **Slack** | Deploy agents as Slack bots for team collaboration | Set up Slack | -| **LINE** | Connect agents to LINE Official Accounts for chat and media messaging | Set up LINE | -| **Microsoft Teams** | Integrate agents into Teams channels and chats | Set up Microsoft Teams | -| **WhatsApp** | Connect agents to WhatsApp Business for customer messaging | Set up WhatsApp | -| **Messenger** | Connect agents to Facebook Messenger for customer support | Set up Messenger | -| **Twilio SMS** | Send and receive SMS messages via Twilio for customer engagement | Set up Twilio SMS | -| **Telegram** | Connect agents to Telegram bots for messaging and group conversations | Set up Telegram | -| **Zendesk** | Connect agents to Zendesk Sunshine Conversations for customer support | Set up Zendesk | -| **Instagram** | Connect agents to Instagram Messaging for direct customer conversations | Set up Instagram | -| **Genesys** | Connect agents to Genesys Cloud as a Bot Connector for contact center automation | Set up Genesys | -| **Email** | Process inbound emails and send agent responses via email | Set up Email | -| **AIforWork** | Kore.ai's Employee Experience (EX) platform -- bidirectional agent messaging integration | Set up AI for Work | +| Channel | Description | Setup | +|--------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------| +| **Slack** | Deploy agents as Slack bots for team collaboration | Set up Slack | +| **LINE** | Connect agents to LINE Official Accounts for chat and media messaging | Set up LINE | +| **Microsoft Teams**| Integrate agents into Teams channels and chats | [Set up Microsoft Teams](/agent-platform/channels/digital#set-up-microsoft-teams) | +| **WhatsApp** | Connect agents to WhatsApp Business for customer messaging | Set up WhatsApp | +| **Messenger** | Connect agents to Facebook Messenger for customer support | Set up Messenger | +| **Twilio SMS** | Send and receive SMS messages via Twilio for customer engagement | Set up Twilio SMS | +| **Telegram** | Connect agents to Telegram bots for messaging and group conversations | Set up Telegram | +| **Zendesk** | Connect agents to Zendesk Sunshine Conversations for customer support | Set up Zendesk | +| **Instagram** | Connect agents to Instagram Messaging for direct customer conversations | Set up Instagram | +| **Genesys** | Connect agents to Genesys Cloud as a Bot Connector for contact center automation | Set up Genesys | +| **Email** | Process inbound emails and send agent responses via email | Set up Email | +| **AI for Work** | Kore.ai's Employee Experience (EX) platform — bidirectional agent messaging integration | Set up AI for Work | Each setup page covers credential registration, webhook configuration, channel-specific features (such as Slack threading and slash commands, or WhatsApp interactive messages), and troubleshooting. diff --git a/agent-platform/channels/digital.mdx b/agent-platform/channels/digital.mdx new file mode 100644 index 000000000..b6ad84eee --- /dev/null +++ b/agent-platform/channels/digital.mdx @@ -0,0 +1,97 @@ +--- +title: Digital Channels +--- + +[Back to Messaging or Digital](/agent-platform/channels#messaging-or-digital) + +## Set up Microsoft Teams + +Integrate your agent into Microsoft Teams channels and chats through an Azure Bot registration. + +Complete the Azure Bot setup before you begin — it produces the App ID, client secret, and tenant ID this connection needs. + +To configure a Microsoft Teams channel, go to **Deployments** > **Channels** > **MESSAGING** > **Microsoft Teams** > **+ New** and complete the following steps in order. + + + + 1. Go to [Azure Portal](https://portal.azure.com/) and navigate to **Azure Bot** > **Create**. + 2. In **Bot settings**, set **Messaging endpoint** to the webhook URL shown on the **New Microsoft Teams Connection** page. + 3. Under **Configuration**, copy the **Microsoft App ID**. + 4. Go to **App Registrations** > find your bot > **Certificates & secrets** > create a **New client secret** and copy the value. + 5. Copy the **Directory (tenant) ID** from the **Overview** page. + 6. Go to **Channels** > add the **Microsoft Teams** channel. + 7. In the Teams app manifest, set `bots[0].supportsFiles` to `true`. + + Attachment ingestion currently supports personal chat scope only. + + + + On the **New Microsoft Teams Connection** page, provide the following fields. + + | Field | Description | + | ----- | ----------- | + | **Display Name** | A label for the connection, e.g. `Microsoft Teams Production`. Up to 255 characters. | + | **Bot App ID** | The Microsoft App ID of your bot registration, e.g. your Microsoft App ID. Up to 255 characters. | + | **App ID** | Your Microsoft App ID. | + | **Client Secret** | The client secret value from your Azure bot registration. | + | **Azure Tenant ID** | The Directory (tenant) ID from the Azure Overview page. | + | **Environment** | Select an environment to follow its active deployment, or leave the default to use the working copy. | + | **Provider Verification Strength** | Controls how strictly the platform trusts the provider's identity assertions for session continuity and linking. **Weak** is the default. Choose **Strong** only for channels or providers whose identity assertions you trust for stronger continuity and linking decisions. | + | **Initial Status** | **Active** connections are usable immediately. **Inactive** connections stay saved but disabled until you activate them. | + + Select **Create**. + + + +### Manage an Existing Microsoft Teams Channel + +Open a channel from **Deployments** > **Channels** > **MESSAGING** > **Microsoft Teams** shows four tabs: **Overview**, **Credentials**, **Configuration**, and **Deployment**. + + + + The **Connection Summary** shows these fields. + + | Field | Description | + | ----- | ----------- | + | **Status** | for example: *Active* | + | **Created** | Timestamp the channel was created | + | **Updated** | Timestamp of the last change | + | **Environment** | for example: `staging` | + | **Source Type** | `Channel Connection` | + | **Source ID** | Unique channel identifier (UUID) | + + Under **Setup Instructions**, the tab also shows the **Webhook URL** to set as the bot's messaging endpoint in Azure, and the **Bot App ID** for reference. + + + + Credentials are saved and encrypted after creation; the fields show placeholder text and accept new values only if you want to update them. + + | Field | Description | + | ----- | ----------- | + | **Use Auth Profile** | Toggle on to authenticate through a saved Auth Profile instead of entering credentials manually. When enabled, select the profile from the dropdown in place of the fields below. | + | **App ID** | Your Microsoft App ID. Shown as *(saved — enter to update)*; leave blank to keep the current value. | + | **Client Secret** | The client secret from your Azure bot registration. Shown as *(saved — enter to update)*; leave blank to keep the current value. | + | **Azure Tenant ID** | The Directory (tenant) ID from the Azure Overview page. Shown as *(saved — enter to update)*; leave blank to keep the current value. | + + Select **Save Credentials** to apply any changes. + + + + Under **General**, update the **Display Name** and **Provider Verification Strength** described in [Set up Microsoft Teams](#set-up-microsoft-teams) above. + + Under **Microsoft Teams Settings**, the **Bot App ID** is shown for reference and cannot be changed after creation. + + Select **Save Changes** to apply any changes. + + + + The tab collects these fields. + + | Field | Description | + | ----- | ----------- | + | **Agent Version** | An **Environment** dropdown (for example: `Staging`) that selects which deployed version handles incoming messages. | + | **Active Deployment** | Shows the bound deployment version and when it was deployed, for example `v4.0` deployed `May 11, 2026, 06:17 PM`. | + + Select **Save Changes** after switching the environment/version. + + diff --git a/agent-platform/channels/voice.mdx b/agent-platform/channels/voice.mdx index b98a0bac8..e4d99d963 100644 --- a/agent-platform/channels/voice.mdx +++ b/agent-platform/channels/voice.mdx @@ -67,7 +67,7 @@ To configure a Realtime LLM Voice channel, go to **Deployments** > **Channels** ### Manage an Existing Realtime LLM Voice Channel -Opening a channel from **Deployments** > **Channels** > **VOICE** > **Realtime LLM Voice** shows three tabs: **Overview**, **Configuration**, and **Deployment**. +Open a channel from **Deployments** > **Channels** > **VOICE** > **Realtime LLM Voice** shows three tabs: **Overview**, **Configuration**, and **Deployment**. diff --git a/agent-platform/drafts/digital.mdx b/agent-platform/drafts/digital.mdx deleted file mode 100644 index e81f9e149..000000000 --- a/agent-platform/drafts/digital.mdx +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Digital Channels -sidebarTitle: Digital Channels ---- - -Add badge From 36a8824cef975cde34ac76b34e282ebdd9849c43 Mon Sep 17 00:00:00 2001 From: vishnubkore Date: Wed, 15 Jul 2026 19:22:17 +0530 Subject: [PATCH 3/5] Update digital.mdx --- agent-platform/channels/digital.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/agent-platform/channels/digital.mdx b/agent-platform/channels/digital.mdx index b6ad84eee..106678936 100644 --- a/agent-platform/channels/digital.mdx +++ b/agent-platform/channels/digital.mdx @@ -10,12 +10,10 @@ Integrate your agent into Microsoft Teams channels and chats through an Azure Bo Complete the Azure Bot setup before you begin — it produces the App ID, client secret, and tenant ID this connection needs. -To configure a Microsoft Teams channel, go to **Deployments** > **Channels** > **MESSAGING** > **Microsoft Teams** > **+ New** and complete the following steps in order. - 1. Go to [Azure Portal](https://portal.azure.com/) and navigate to **Azure Bot** > **Create**. - 2. In **Bot settings**, set **Messaging endpoint** to the webhook URL shown on the **New Microsoft Teams Connection** page. + 2. In **Bot settings**, set **Messaging endpoint** to the webhook URL shown on the **Microsoft Teams Overview** page. 3. Under **Configuration**, copy the **Microsoft App ID**. 4. Go to **App Registrations** > find your bot > **Certificates & secrets** > create a **New client secret** and copy the value. 5. Copy the **Directory (tenant) ID** from the **Overview** page. @@ -25,7 +23,9 @@ To configure a Microsoft Teams channel, go to **Deployments** > **Channels** > * Attachment ingestion currently supports personal chat scope only. - + + To configure a Microsoft Teams channel, go to **Deployments** > **Channels** > **MESSAGING** > **Microsoft Teams** > **+ New** and complete the following steps in order. + On the **New Microsoft Teams Connection** page, provide the following fields. | Field | Description | @@ -90,7 +90,7 @@ Open a channel from **Deployments** > **Channels** > **MESSAGING** > **Microsoft | Field | Description | | ----- | ----------- | | **Agent Version** | An **Environment** dropdown (for example: `Staging`) that selects which deployed version handles incoming messages. | - | **Active Deployment** | Shows the bound deployment version and when it was deployed, for example `v4.0` deployed `May 11, 2026, 06:17 PM`. | + | **Active Deployment** | Shows the bound deployment version and when it was deployed. | Select **Save Changes** after switching the environment/version. From bcb8d7f2a774e16aa416b245f0e33fa7b02bb204 Mon Sep 17 00:00:00 2001 From: Ashish Gupta Date: Wed, 15 Jul 2026 20:16:13 +0530 Subject: [PATCH 4/5] Channel doc updates --- agent-platform/channels.mdx | 32 ++++++++++++------------- agent-platform/channels/digital.mdx | 36 ++++++++++++++--------------- 2 files changed, 34 insertions(+), 34 deletions(-) diff --git a/agent-platform/channels.mdx b/agent-platform/channels.mdx index 2a63c1745..5d1de3c57 100644 --- a/agent-platform/channels.mdx +++ b/agent-platform/channels.mdx @@ -1,6 +1,6 @@ --- -title: "Channels" -sidebarTitle: "Channels" +title: Channels +sidebarTitle: Channels --- Channels connect your deployed agents to the surfaces where users interact: your own apps, voice calls, messaging apps, webhooks, and other agent frameworks. Artemis provides channel adapters that handle the protocol-specific details, so a single agent definition works across every channel without modification. @@ -31,20 +31,20 @@ All five route to the same agent definition. The adapter normalizes inbound and The Platform supports the following messaging or digital channels: -| Channel | Description | Setup | -|--------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------| -| **Slack** | Deploy agents as Slack bots for team collaboration | Set up Slack | -| **LINE** | Connect agents to LINE Official Accounts for chat and media messaging | Set up LINE | -| **Microsoft Teams**| Integrate agents into Teams channels and chats | [Set up Microsoft Teams](/agent-platform/channels/digital#set-up-microsoft-teams) | -| **WhatsApp** | Connect agents to WhatsApp Business for customer messaging | Set up WhatsApp | -| **Messenger** | Connect agents to Facebook Messenger for customer support | Set up Messenger | -| **Twilio SMS** | Send and receive SMS messages via Twilio for customer engagement | Set up Twilio SMS | -| **Telegram** | Connect agents to Telegram bots for messaging and group conversations | Set up Telegram | -| **Zendesk** | Connect agents to Zendesk Sunshine Conversations for customer support | Set up Zendesk | -| **Instagram** | Connect agents to Instagram Messaging for direct customer conversations | Set up Instagram | -| **Genesys** | Connect agents to Genesys Cloud as a Bot Connector for contact center automation | Set up Genesys | -| **Email** | Process inbound emails and send agent responses via email | Set up Email | -| **AI for Work** | Kore.ai's Employee Experience (EX) platform — bidirectional agent messaging integration | Set up AI for Work | +| Channel | Description | Setup | +|---------------------|-----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| **Slack** | Deploy agents as Slack bots for team collaboration | Set up Slack | +| **LINE** | Connect agents to LINE Official Accounts for chat and media messaging | Set up LINE | +| **Microsoft Teams** | Integrate agents into Teams channels and chats | [Set up Microsoft Teams](/agent-platform/channels/digital#set-up-microsoft-teams) | +| **WhatsApp** | Connect agents to WhatsApp Business for customer messaging | Set up WhatsApp | +| **Messenger** | Connect agents to Facebook Messenger for customer support | Set up Messenger | +| **Twilio SMS** | Send and receive SMS messages via Twilio for customer engagement | Set up Twilio SMS | +| **Telegram** | Connect agents to Telegram bots for messaging and group conversations | Set up Telegram | +| **Zendesk** | Connect agents to Zendesk Sunshine Conversations for customer support | Set up Zendesk | +| **Instagram** | Connect agents to Instagram Messaging for direct customer conversations | Set up Instagram | +| **Genesys** | Connect agents to Genesys Cloud as a Bot Connector for contact center automation | Set up Genesys | +| **Email** | Process inbound emails and send agent responses via email | Set up Email | +| **AI for Work** | Kore.ai's Employee Experience (EX) platform — bidirectional agent messaging integration | Set up AI for Work | Each setup page covers credential registration, webhook configuration, channel-specific features (such as Slack threading and slash commands, or WhatsApp interactive messages), and troubleshooting. diff --git a/agent-platform/channels/digital.mdx b/agent-platform/channels/digital.mdx index 106678936..042d15318 100644 --- a/agent-platform/channels/digital.mdx +++ b/agent-platform/channels/digital.mdx @@ -2,7 +2,7 @@ title: Digital Channels --- -[Back to Messaging or Digital](/agent-platform/channels#messaging-or-digital) +[Back to messaging or digital channels](/agent-platform/channels#messaging-or-digital) ## Set up Microsoft Teams @@ -51,14 +51,14 @@ Open a channel from **Deployments** > **Channels** > **MESSAGING** > **Microsoft The **Connection Summary** shows these fields. - | Field | Description | - | ----- | ----------- | - | **Status** | for example: *Active* | - | **Created** | Timestamp the channel was created | - | **Updated** | Timestamp of the last change | - | **Environment** | for example: `staging` | - | **Source Type** | `Channel Connection` | - | **Source ID** | Unique channel identifier (UUID) | + | Field | Description | + |-----------------|-----------------------------------| + | **Status** | for example: *Active* | + | **Created** | Timestamp the channel was created | + | **Updated** | Timestamp of the last change | + | **Environment** | for example: `staging` | + | **Source Type** | `Channel Connection` | + | **Source ID** | Unique channel identifier (UUID) | Under **Setup Instructions**, the tab also shows the **Webhook URL** to set as the bot's messaging endpoint in Azure, and the **Bot App ID** for reference. @@ -66,12 +66,12 @@ Open a channel from **Deployments** > **Channels** > **MESSAGING** > **Microsoft Credentials are saved and encrypted after creation; the fields show placeholder text and accept new values only if you want to update them. - | Field | Description | - | ----- | ----------- | + | Field | Description | + |----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Use Auth Profile** | Toggle on to authenticate through a saved Auth Profile instead of entering credentials manually. When enabled, select the profile from the dropdown in place of the fields below. | - | **App ID** | Your Microsoft App ID. Shown as *(saved — enter to update)*; leave blank to keep the current value. | - | **Client Secret** | The client secret from your Azure bot registration. Shown as *(saved — enter to update)*; leave blank to keep the current value. | - | **Azure Tenant ID** | The Directory (tenant) ID from the Azure Overview page. Shown as *(saved — enter to update)*; leave blank to keep the current value. | + | **App ID** | Your Microsoft App ID. Shown as *(saved — enter to update)*; leave blank to keep the current value. | + | **Client Secret** | The client secret from your Azure bot registration. Shown as *(saved — enter to update)*; leave blank to keep the current value. | + | **Azure Tenant ID** | The Directory (tenant) ID from the Azure Overview page. Shown as *(saved — enter to update)*; leave blank to keep the current value. | Select **Save Credentials** to apply any changes. @@ -87,10 +87,10 @@ Open a channel from **Deployments** > **Channels** > **MESSAGING** > **Microsoft The tab collects these fields. - | Field | Description | - | ----- | ----------- | - | **Agent Version** | An **Environment** dropdown (for example: `Staging`) that selects which deployed version handles incoming messages. | - | **Active Deployment** | Shows the bound deployment version and when it was deployed. | + | Field | Description | + |-----------------------|---------------------------------------------------------------------------------------------------------------------| + | **Agent Version** | An **Environment** dropdown (for example: `Staging`) that selects which deployed version handles incoming messages. | + | **Active Deployment** | Shows the bound deployment version and when it was deployed. | Select **Save Changes** after switching the environment/version. From d208d6e7c38ef4d7bccb4a3a7d542cb1713a344d Mon Sep 17 00:00:00 2001 From: Ashish Gupta Date: Wed, 15 Jul 2026 20:16:50 +0530 Subject: [PATCH 5/5] MCP doc updates --- agent-platform/mcp-server.mdx | 2 +- agent-platform/tools/mcp.mdx | 2 -- docs.json | 1 + 3 files changed, 2 insertions(+), 3 deletions(-) diff --git a/agent-platform/mcp-server.mdx b/agent-platform/mcp-server.mdx index ee4aadd94..5b3f5a0ca 100644 --- a/agent-platform/mcp-server.mdx +++ b/agent-platform/mcp-server.mdx @@ -1,6 +1,6 @@ --- title: Use Agent Platform's MCP Server -sidebarTitle: Platform MCP Server +sidebarTitle: MCP Server --- Agent Platform exposes its features through a Model Context Protocol (MCP) server. Your AI assistant can connect to the platform and perform platform operations to let you build, evaluate, optimize, debug, and analyze agents. diff --git a/agent-platform/tools/mcp.mdx b/agent-platform/tools/mcp.mdx index bf823a0a3..cbac7f7ad 100644 --- a/agent-platform/tools/mcp.mdx +++ b/agent-platform/tools/mcp.mdx @@ -13,8 +13,6 @@ MCP (Model Context Protocol) is an open standard that lets AI agents interact wi **With MCP:** The agent communicates with all services through a single interface, dramatically reducing development complexity. -You can connect to the platform's MCP server from within your editor or terminal—perform platform operations without leaving your context. For details, see [How to use platform MCP server](/agent-platform/mcp-server) - ## When to Use MCP is particularly suited for tools hosted on external servers, shared toolsets across teams, and cases where you want clear separation between tool logic and agent logic. diff --git a/docs.json b/docs.json index b65308a14..94e488921 100644 --- a/docs.json +++ b/docs.json @@ -137,6 +137,7 @@ "group": "References", "pages": [ + "/agent-platform/mcp-server", "/agent-platform/sdks", "/agent-platform/faq", "/agent-platform/glossary"