Skip to main content

Chat Integrations

Chat tools enable direct user interaction, automated notifications, and contextual assistance within team communication channels.

The following AI Incident Assistant chat integrations are available:

Microsoft Teams

The Biggy Microsoft Teams integration is used for collaboration and communication.

Integration categories

The Microsoft Teams integration is part of both the Chat and Conferencing integration categories.

Enable Online Meeting Creation for MS Teams

To allow Biggy to create meetings as part of the Managed Incident Channel action plan, you need to grant the necessary permissions by authorizing a designated user. 

Before you start, you will need:

  • A PowerShell instance with the MicrosoftTeams module

    • Install using this command: Install-Module -Name MicrosoftTeams -Force -AllowClobber

  • Your Biggy app ID. This is available in the web app MS Teams Integration page.

  • Your Microsoft tenant ID. This is available in the Azure AD or Microsoft Entra admin center.

  • The GUID of a user in your tenant that you'd like to use for meeting creation.

To enable online meeting creation:

  1. In a PowerShell window, run the following command:

    Connect-MicrosoftTeams

    This will allow your PowerShell instance to run these management commands.

  2. Run the following command to create the new application access policy. Replace <Your App ID> with your Biggy app ID:

    New-CsApplicationAccessPolicy -Identity Biggy-Teams-Meeting-Policy -AppIds "<Your App ID>" -Description "Used for Biggy to create meetings"

    You can customize the Identity and Description.

  3. Run the following command to grant a user the permission. Replace the <user GUID> with the GUID of the user you'd like to use for meeting creation:

    Grant-CsApplicationAccessPolicy -PolicyName Biggy-Teams-Meeting-Policy -Identity "<user GUID>"

  4. Within the AI Incident Assistant Web App, go to Configuration > Integrations and navigate to Microsoft Teams. Click Configure.

  5. Enter your Tenant ID and the Default User ID (GUID) of the user added to the policy.

  6. Click Save.

Slack

The Biggy Slack integration is used for collaboration and communication.

Integration categories

The Slack integration is part of both the Chat and Conferencing integration categories.

Due to rate limitations of the Slack API, retrieving all channels is done through a channel sync mechanism. Once synced, all channels are then available for selection in relevant settings and action plan configuration screens of the web app.

Click the Sync Channels button to sync or resync your Slack channels. We recommend syncing periodically to ensure your channel selection stays up to date.

Private channels

If you'd like to sync private Slack channels, be sure to add Biggy to those channels first.

Rate limitations

Syncing may take some time given the throttling required to stay within the Slack rate limitations.

Webex

Chat

The Webex integration is part of both the Chat and Conferencing integration categories.

The Biggy Webex integration enables Biggy to create bridge calls for Managed Incident Channels.

Prerequisites

The following is required to enable Webex meeting creation:

  • Webex Pro or Enterprise - a Webex Meetings subscription with Common Identity (CI).

  • Control Hub full admin - admin account required to authorize the Service App in your organization.

  • Licensed host email - a Webex user email with the meeting:admin_schedule_write permission to serve as the meeting host.

Enable Webex Meeting Creation

To enable Biggy to create Webex bridge calls for managed incident channels, you will need to create a Webex Service App and authorize it in your organization so that it can function as a designated host user.

To configure meeting creation:

  1. Go to the Webex Developer Portal and log in.

  2. Click your avatar, select My Webex Apps, and then create a new Service App.

  3. When configuring scopes, select meeting:admin_schedule_write. This allows the app to create meetings on behalf of users in your organization.

  4. With a full admin account, log in to the Webex Control Hub.

  5. Go to Apps > Service Apps and approve the new service app created in step 2.

  6. After the app is authorized, return to the service app in the Developer Portal.

  7. Under the Org Authorizations section, select your organization from the dropdown menu.

  8. Enter your Client Secret, and click Generate tokens. Copy the Refresh Token from the result. Biggy uses this to generate short-lived access tokens on demand.

    Do not update refresh tokens and client secrets

    Biggy automatically rotates the refresh token. Do not update it manually after saving.

    The client secret also should not be regenerated as it will invalidate the authorization. If it is regenerated, you'll need to re-authorize it in the Control Hub.

  9. In the AI Incident Assistant web app on the Webex integration configuration page, enter the following information:

    Field

    Description

    Client ID 

    Webex service app client ID.

    Client Secret

    Webex service app client secret.

    Refresh Token

    Refresh token from the Webex developer portal.

    Host Email

    Email address of the designated meeting host.

    The address must belong to a licensed Webex user. All meetings will be scheduled by this user account, since the meeting:admin_schedule_write scope operates on behalf of a real user, not a service identity.

    Webex System/Schema Nuances

    List any special field mappings, naming conventions, custom tables/fields, or other knowledge that helps Biggy more effectively interact with your tool. 

    We highly recommend configuring this field, as it allows you to enter organization-specific information that enables Biggy to provide more accurate and consistent results. 

    For example, you can include explanations of any custom fields and when or how they should be used to handle certain types of user queries.

  10. Click Save.

In this section: