Channels

​

Microsoft Teams

​

When to Use

​

Architecture

[AI for Work Platform] ↔ [Azure Bot Service] ↔ [Microsoft Teams]

​

Prerequisites

​

Configuration

1. Log in to the Admin Console.
2. Navigate to Channels > Microsoft Teams and Copilot.
3. Copy and save the Webhook URL, to use in Azure Bot configuration later.

1. Sign in to the Azure Portal.
2. Click + Create a resource → Search for Azure Bot.
3. Select Azure Bot and configure the following:
   • Bot Handle: Choose a unique name.
   • Subscription: Select your active subscription.
   • Resource Group: Create or reuse an existing group.
   • Pricing Tier: Select based on expected usage.
   • App Type: Select Multi-Tenant or Single-Tenant based on organizational needs.

1. After deployment completes, click Go to resource and navigate to Configuration in the left sidebar.
2. Paste the webhook URL copied from the AI for Work platform into the Messaging endpoint field and click Apply to save the configuration.

1. In Configuration, click Manage Password next to the Microsoft App ID.
2. Go to Certificates & secrets → + New client secret.
3. Enter description and expiry → Add.
4. Copy the Value of the client secret (App Password).
5. Record the Microsoft App ID and App Password for the Platform configuration.

1. Navigate to Channels in the bot resource menu and locate the Available Channels section.
2. Select the Microsoft Teams channel and M365 Extensions channel (required for Copilot integration), review channel information, and select Save.

1. In the Azure Portal, navigate to App registrations and select + New registration.
2. Register New Application:
   • Name: Provide a descriptive name (for example, Platform-Microsoft Teams-Notifications).
   • Supported account types: Choose based on organizational requirements.
   • Redirect URI: Leave blank for this use case.
3. Select Register.

1. In the app registration, navigate to API permissions and select Add a permission.
2. Select Microsoft Graph → Application permissions. Required Permissions: Add the following permissions for full functionality:
   • TeamsAppInstallation.ReadForUser.All
   • TeamsAppInstallation.ReadWriteSelfForUser.All
   • TeamsAppInstallation.ReadWriteForUser.All
   • User.Read.All
   • AppCatalog.Read.All
3. Grant Admin Consent.
4. Generate a Client Secret and note down App ID, Directory (Tenant) ID.
5. Configure these values in AI for Work under Microsoft Teams & Copilot Channel Settings.
6. Generate a JWT token for secure communication.

1. Navigate to the Admin Console.
2. Locate Channels on the left pane.
3. Select Microsoft Teams and Copilot.
4. Enter the following credentials under Configuration:
   • Microsoft App Tenant ID: (SingleTenant only) The tenant ID from the bot’s app registration.
   • Microsoft App ID: The App ID from your Azure Bot resource.
   • App Password: The client secret from the bot’s app registration.
   
   • App ID of the Microsoft Teams App: The additional app credentials for sending Proactive Notifications.
   • Application (Client) ID: From the notifications app registration.
   • Client Secret: From the notifications app registration.
   • Delivery (Tenant) ID: From the notifications app registration.
   

• App Name – Choose a custom display name for Microsoft Teams.
• Logo – Upload an organization-specific logo.
• Description – Provide a tailored description that reflects organizational context.

1. Sign in to Microsoft Teams Admin Center.
2. Navigate to Teams apps → Manage apps.
3. Click Upload new app and select the downloaded application package. Wait for upload and verify to complete.

• Add App for All Users (Recommended) — Automatically installs the custom app for all employees in the organization. All users receive a notification in Microsoft Teams and a welcome message when the app is added.

• Let Users Add the App Themselves — The custom app is available in the organization’s app catalog within Teams. Users need to search for the app in the Apps section in Teams and add it manually. No automatic notifications or installations occur.

• Add App for Selected Users or User Groups — Uses app setup policies to assign the app only to specific users or security groups. Selected users are automatically notified in Microsoft Teams and receive the welcome message. Other users can find and install the app from the organization’s app catalog if permitted by policy.

​

Troubleshooting

• Verify the webhook URL is correctly configured in Azure Bot.
• Check that the Microsoft Teams channel is enabled and saved.
• Validate client secrets haven’t expired.

• Confirm admin consent is granted for all required API permissions.
• Verify client secrets are copied correctly (Value, not Secret ID).
• Check tenant ID matches between configurations.

• Ensure you have proper admin permissions in the Teams Admin Center.
• Verify the application package is not corrupted during download.
• Check organizational policies allow custom app uploads.

• Verify that admin consent is granted for all required Microsoft Graph permissions.
• Verify that the notification app registration client secret is valid.
• Ensure JWT token generation is working correctly.

​

Slack

​

When to Use

​

Architecture

[AI for Work Platform] ↔ [Slack App Configuration] ↔ [Slack Workspace]

​

Prerequisites

​

Integration Lifecycle

​

Configuration

1. Log in to the Admin Console.
2. Navigate to Channels → Slack.
3. Open the Configuration page and set the following:

   Setting	Description
   App Name	Name users see when interacting with the app in Slack
   App Description	Explains the app’s capabilities; appears in the About section in Slack

   

1. On the Configuration page, click Get Manifest.
2. Copy the entire manifest code.

1. Go to the Slack Developer Portal.
2. Sign in with your workspace credentials.
3. Click Your Apps.

1. Click Create New App (or Create an App for first-time users).
2. Select From a manifest.
3. Select the target workspace from the Slack Workspace dropdown.

1. Paste the manifest code copied from the Platform.
2. Click Next, review the configuration and permissions, then click Create.

1. In the Slack Developer Portal, navigate to Basic Information in the left sidebar.
2. Scroll to App Credentials and copy:
   • Client ID
   • Client Secret
   • Signing Secret
   

1. Return to the Admin Console > App Credentials page.
2. Paste the copied values into the corresponding fields.
3. Click Authorize.

1. Review the permission request that Slack displays.
2. Click Allow.

1. In the Admin Console, navigate to the Welcome Experience page.
2. Configure the following:

   Setting	Description
   Welcome Message	Introductory message users see when they first open the app
   Sample Prompts	Up to four clickable prompts to help users start a conversation

3. For each sample prompt, set:
   • Display Message — Text shown to users as the prompt button.
   • Actual Query — The complete query sent to the Platform when the user clicks the prompt.
4. Click Save and Update. Changes take effect immediately for all users.

1. In the Slack Developer Portal, go to Basic Information → Display Information.
2. Click Upload next to App Icon and select an image file.
3. Optionally, set a Background Color.
4. Click Save Changes.

​

User Access Management

1. Invite all intended users to the Platform.
2. Onboard users with the appropriate access permissions.
3. Confirm users exist in both the Platform and the target Slack workspace.

​

Current Limitations

​

Web/Mobile SDK

​

When to Use

​

Architecture

[Host Web/Mobile App] ↔ [Web/Mobile SDK] ↔ [AI for Work Platform]

​

Prerequisites

​

Configuration

1. Log in to the Admin Console.
2. Navigate to Channels → Web/Mobile SDK.
3. On the SDK Apps page, click + Create New.

1. Open the App Credentials section.
2. Configure or copy the following values:

   Field	Description
   App Name	Display name for the SDK app. Used to identify the app in the SDK Apps list.
   Client ID	System-generated identifier for the SDK app. Use the copy icon to copy the value.
   Client Secret	System-generated secret used to sign JWTs. Use the copy icon to copy the value, or the refresh icon to regenerate it.
   JWT Generation	Sample JWT payload structure showing the mandatory and optional claims required by the SDK.

3. Click Continue.

1. Open the Allowed Domains section.
2. Enter a domain in the Enter domain field (for example, https://example.com).
3. Click + Add Domain.
4. Repeat to add additional domains.
5. To modify the list, edit any existing domain inline, or delete a domain to remove it.
6. Click Continue.

1. Open the SDK Details section.
2. Use the following resources to set up the SDK in your host application:
   • Web SDK — Click Download SDK to access the prebuilt Web SDK library and embed it in your web application.
   • Mobile SDK — Click Download SDK to access the prebuilt Mobile SDK library and embed it in your mobile application.
3. Click Save.

​

Managing SDK Apps

• View all SDK apps, including the creation date and the user who created them.
• Edit an existing app to update credentials, allowed domains, or SDK setup.
• Delete an app that’s no longer needed using the actions menu.

​

Web SDK Integration through CDN

1. Load the Web SDK through CDN.
2. Authenticate the user (through SSO).
3. Generate a JWT token.
4. Exchange the JWT for an access token.
5. Initialize the chatbot widget.

<!-- SDK CSS -->
<link rel="stylesheet" href="https://staticqa-workassist.kore.ai/eva_sdk/1.0/dist/sdk-styles.css" />

<!-- SDK external library dependencies -->
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@shoelace-style/shoelace@2.0.0/dist/themes/light.css">
<script type="module" src="https://cdn.jsdelivr.net/npm/@shoelace-style/shoelace@2.0.0/dist/shoelace.js"></script>
<link href="https://cdn.jsdelivr.net/npm/tom-select@2.4.3/dist/css/tom-select.css" rel="stylesheet">
<script src="https://cdn.jsdelivr.net/npm/tom-select@2.4.3/dist/js/tom-select.complete.min.js"></script>

<!-- React (peer dependency) -->
<script src="https://unpkg.com/react@18/umd/react.production.min.js"></script>
<script src="https://unpkg.com/react-dom@18/umd/react-dom.production.min.js"></script>

const CLIENT_ID = "YOUR_CLIENT_ID";
const CLIENT_SECRET = "YOUR_CLIENT_SECRET";
const USER_PROFILE_URL = "https://yoursite.example.com/api/users/me";
const SSO_LOGIN_URL = `https://work.kore.ai/api/1.1/sdk/${CLIENT_ID}/sso/login/`;
const API_URL = `https://work.kore.ai/api/1.1/sdk/${CLIENT_ID}/`;
const PRESENCE_URL = `https://work.kore.ai/`;
const JWT_EXPIRY = "5m";

const fetchJson = async (url, options = {}) => {
  const response = await fetch(url, options);
  if (!response.ok) {
    throw new Error(`Request failed: ${response.status}`);
  }
  return response.json();
};

const me = await fetchJson(USER_PROFILE_URL);

{
  "Email": "john@example.com",
  "FirstName": "John",
  "LastName": "Doe"
}

<body>
  <!-- Your page content -->
  <script src="https://staticqa-workassist.kore.ai/eva_sdk/1.0/dist/eva-web-sdk.umd.js"></script>
  <script>
    // Step 4 to Step 6 code goes here in a single script block
  </script>
</body>

const { SignJWT } = await import("https://cdn.jsdelivr.net/npm/jose@5/+esm");
const secret = new TextEncoder().encode(CLIENT_SECRET);

const id_token = await new SignJWT({
  sub: me.Email,
  firstName: me.FirstName,
  lastName: me.LastName,
  clientId: CLIENT_ID
})
  .setProtectedHeader({ alg: "HS256", typ: "JWT" })
  .setIssuedAt()
  .setExpirationTime("5m")
  .sign(secret);

const ssoResponse = await fetchJson(SSO_LOGIN_URL, {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ id_token })
});

const accessToken = ssoResponse.authorization.accessToken;
const userId = ssoResponse.userInfo.id;

EvaSDK.chatBot.init({
  accessToken,
  api_url: API_URL,
  presence_url: PRESENCE_URL,
  userId,
  title: "ChatBot",
  showHistory: true
});

EvaSDK.chatInterface.configure({
  disableAppAvatar: true
});

const bootstrapSdk = async () => {
  try {
    const me = await fetchJson(USER_PROFILE_URL);

    const { SignJWT } = await import("https://cdn.jsdelivr.net/npm/jose@5/+esm");
    const secret = new TextEncoder().encode(CLIENT_SECRET);

    const id_token = await new SignJWT({
      sub: me.Email,
      firstName: me.FirstName,
      lastName: me.LastName,
      clientId: CLIENT_ID
    })
      .setProtectedHeader({ alg: "HS256", typ: "JWT" })
      .setIssuedAt()
      .setExpirationTime("5m")
      .sign(secret);

    const ssoResponse = await fetchJson(SSO_LOGIN_URL, {
      method: "POST",
      headers: { "Content-Type": "application/json" },
      body: JSON.stringify({ id_token })
    });

    const accessToken = ssoResponse.authorization.accessToken;
    const userId = ssoResponse.userInfo.id;

    EvaSDK.chatBot.init({
      accessToken,
      api_url: API_URL,
      presence_url: PRESENCE_URL,
      userId,
      title: "ChatBot",
      showHistory: true
    });
  } catch (error) {
    console.error("SDK bootstrap failed:", error);
  }
};

bootstrapSdk();

​

Testing Checklist

• The user profile API returns the expected data.
• The JWT is generated correctly.
• The SSO endpoint returns an access token.
• The chatbot loads without console errors.
• Conversation history is preserved across sessions.
• The presence connection is successful.