Channels
Channels are communications applications that your virtual assistant can integrate with and open from within. For instance, if you're already using an application like MS Teams or Slack, you can integrate your virtual assistant as a feature within those applications.
Webchat, Copilot, Webex, MS Teams and Slack Channels Support Markdown
Markdown support is enabled by default for the Webchat, Webex, MS Teams, and Slack Channels. You can disable the Markdown default using you bot Details settings.
Therefore, LLM Responses are formatted as HTML for all channels where the Markdown format is not supported.
To disable the Markdown Support: NOTE: Ensure the channel is not open when editing the configuration.
Navigate to Settings > AiseraGPT.
Open an existing application or bot.
Choose the pencil icon to see the Details page for that bot.
Scroll down to the Channel section.
Double-click on the line of the Channel that you want to modify.
Uncheck the Enable Markdown Syntax field (while the channel is not open).
Two Special Channels
Two of the supported channels require extra description.
The AiseraGPT application (bot) comes with a default channel called Aisera Webchat that serves as the bot UI. You can use this channel (and the JavaScript snippet that gets automatically generated for it) to embed your bot in your portal or web site.

Use the API Channel if you are creating your own UI or customizing another UI using the Aisera APIs.

Third Party Channels
The rest of the topics in this section contain step-by-step instructions that describe how to integrate channels with your Aisera platform.

Channel ID
When you are viewing your Bot/Application Details page, you can see the ID for your Bot/Application in the top left corner of the window.

When you choose one of your Channels on the Bot/Application Details page, you will see the Channel Details page.

This page now contains a Channel ID.
Application Messaging
For channels where the streaming is enabled, you can see the processing steps that the application performs during a request. The new messages provide details on the number of sources searched, the number of documents validated, and other relevant metrics.
You can see the the processing is performed in four steps:
The first step acknowledges the search of the user's query.
The second step presents the search results found from various sources.
The third step displays the results after validation of the search results.
The fourth step summarizes the validated information to produce the final answer.
The messages you see within the application resemble the following screenshot:

See also: Workflows - Use Message Node for Markdown Variables with Copilot
Last updated