> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm-hermes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/preview-features-advanced-options/settings/external-chat-tool-integrations.md).

# External Chat tool Integrations

{% hint style="info" %}
Applicable to systems on GAIA (ASM Version 10.4 and later)
{% endhint %}

For example, you can configure ASM to use MS Teams Chat so that when a User initiates a Chat from the ASM Portal the Analyst can accept the chat in Core. At that point, an MS Teams Chat is created and the Chat can continue in MS Teams. The Analyst then has the option to import the Chat History from MS Teams into the associated ASM Call.

![Microsoft Teams integration screenshot](https://alemba.com/storage/app/media/Release%20notes/10-4/104-teams.jpg)

## Configure ASM for Teams Integration

{% hint style="warning" %}
Teams Chat functionality does not support the transfer of attachments uploaded in the Teams Chat to the ASM Call when the Teams Chat is ended. Currently it will bring through the Chat Transcript into the ASM Call History only.
{% endhint %}

1. Register the ASM app using the Azure Portal 

{% hint style="info" %}
ASM uses the authorization code flow to access the Microsoft Graph API on behalf of the logged in user. 

The Azure administrator should register an application in Azure AD and will require the redirect URL for ASM. 

e.g. https\://{asm-server-url}/{asm-system-name}/oauth2callback.htm 

The Azure administrator may need to pre-authorize the Chat.Read delegated permission 

&#x20;<https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow> &#x20;
{% endhint %}

2. Configure Chat: Change the Chat Type to Teams in **System Administration>Preview Settings >Settings**&#x20;

<figure><img src="/files/qLPUNQGrcDnUFDsyI4rS" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Teams Service Account: <teamsintergraiton@alemba.com>&#x20;

Client Secret: .d4OWaeT04eAJdevo86D.kttQ\~\_l4U0LKH&#x20;

Application ID: 992cee91-4fc3-4555-9651-c844683a3714&#x20;

Tenant ID: c3994514-768e-447c-9523-faf45b0c23f7
{% endhint %}

Beginning with ASM 10.6.8 (FEB 25 MR), call/meeting recordings along with messages created during the chat are attached to the related ticket in ASM. After ending the chat in ASM, the Call history will display the Teams chat history along with a link to the recording.

<figure><img src="/files/euz1BIePykhZiHZ0INOB" alt=""><figcaption><p>Example Meeting Recording</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/preview-features-advanced-options/settings/external-chat-tool-integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.