> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/team-plus.md).

# Connect a Conversation Platform: Team+

Connect the Team+ enterprise messaging platform: enable the API in the Team+ admin console to obtain credentials, create a conversation platform in MaiAgent, and enter the Webhook URL. Only one-on-one

Team+ is an enterprise messaging platform. Once connected, employees can chat with an Agent directly in Team+ without opening another system.

{% hint style="warning" %}
The Team+ integration currently **supports only one-on-one conversations**. Adding an Agent to a group chat will not trigger replies or create conversation records in MaiAgent. If you need group conversations, use another conversation platform.
{% endhint %}

## Before You Connect <a href="#pre-integration-checklist" id="pre-integration-checklist"></a>

* You have created an AI Assistant on the [MaiAgent platform](https://admin.maiagent.ai/)
* You have administrative access to the Team+ service channel (you can access its Feature Settings)
* You have confirmed with your Team+ vendor contact whether your organization uses a test or production environment

{% hint style="warning" %}
**Credentials cannot be changed after the channel is created.** Obtain all three credentials before proceeding to Step 2.
{% endhint %}

***

## Step 1: Enable the API and Obtain Credentials in the Team+ Admin Console <a href="#step-enable-api-in-teamplus" id="step-enable-api-in-teamplus"></a>

Log in to the Team+ admin console, then go to <mark style="color:blue;">Service Channels</mark> → select the channel you manage → <mark style="color:blue;">Feature Settings</mark> → <mark style="color:blue;">API Settings</mark>, and **enable the API**.

On the same page, obtain these three items after enabling the API:

| Credential               | Description                                                          |
| ------------------------ | -------------------------------------------------------------------- |
| **Channel ID**           | The identifier of this service channel                               |
| **Channel Secret**       | Verifies that messages sent by Team+ actually come from your channel |
| **Channel Access Token** | Used by MaiAgent to call the Team+ API to send replies               |

{% hint style="info" %}
Skip the Webhook field for now. It requires the Webhook URL generated by MaiAgent. You will return to fill it in during **Step 3**.
{% endhint %}

***

## Step 2: Create a Team+ Conversation Platform in MaiAgent <a href="#step-create-channel-in-maiagent" id="step-create-channel-in-maiagent"></a>

### 1. Open Connect Conversation Platform <a href="#step-go-to-channel-integration" id="step-go-to-channel-integration"></a>

In the MaiAgent left menu, click <mark style="color:blue;">Conversation Platforms</mark>, click <mark style="color:blue;">Connect Conversation Platform</mark> in the upper-right corner, and select <mark style="color:blue;">Team+</mark>.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-9557e30aa762671728de3ff2fa7aa9c167365a68%2Fteamplus-choose-channel.png?alt=media" alt="Team+ on the platform selection page"><figcaption><p>Select Team+ from the platform list</p></figcaption></figure>

### 2. Fill In the Basic Settings <a href="#step-fill-basic-settings" id="step-fill-basic-settings"></a>

| Field                            | Description                                                                    |
| -------------------------------- | ------------------------------------------------------------------------------ |
| **Name**                         | Give this integration a name (required). This is only a label within MaiAgent. |
| **AI Assistant**                 | Select the Agent to connect                                                    |
| **Channel ID**                   | Obtained in Step 1 (required)                                                  |
| **Channel Secret**               | Obtained in Step 1 (required)                                                  |
| **Channel Access Token**         | Obtained in Step 1 (required)                                                  |
| **Team+ Service URL (optional)** | See the explanation below                                                      |

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-1e29c7657eb7312df002c39f446d3f50672a2e45%2Fteamplus-create-form.png?alt=media" alt="MaiAgent Team+ creation form with three credentials, a service URL, and the Skip Certificate Security Check option"><figcaption><p>Team+ creation form (example values shown)</p></figcaption></figure>

### 3. When to Enter a Team+ Service URL <a href="#when-to-set-api-base-url" id="when-to-set-api-base-url"></a>

* **Leave blank** — Uses the test environment. Leave it blank for typical testing scenarios.
* **Enter a URL** — Your organization uses a production environment, or Team+ is deployed on your own server. Obtain the URL from your Team+ vendor contact. It must be a complete URL starting with `http://` or `https://`.

### 4. Skip Certificate Security Check <a href="#trust-insecure-tls" id="trust-insecure-tls"></a>

The <mark style="color:blue;">Skip Certificate Security Check</mark> option appears in the form **only after you enter a Team+ Service URL**.

Some organizations have incomplete TLS certificate configurations on their servers (for example, a missing intermediate certificate). This causes standard connection verification to fail, preventing MaiAgent from connecting to Team+. Enabling this option skips verification so the integration can work.

{% hint style="danger" %}
Enabling this option **reduces the security of the connection** to the Team+ server, as MaiAgent cannot confirm that it is connecting to your server. Enable it only after the server administrator has confirmed that the certificate issue cannot be fixed, and disable it once the certificate is repaired.
{% endhint %}

### 5. Enable Reset Commands <a href="#enable-reset-command" id="enable-reset-command"></a>

Once enabled, you can add one or more command phrases (for example, “Start over”). When a user's message in Team+ exactly matches one of these phrases, a new conversation is started for that user. The command itself receives no reply. The AI responds in the new conversation when the user sends their next message.

### 6. Feature Settings Tab <a href="#feature-settings-tab" id="feature-settings-tab"></a>

Switch to the <mark style="color:blue;">Feature Settings</mark> tab to adjust the Agent's behavior on this conversation platform:

The toggles on this tab (<mark style="color:blue;">Enable OCR</mark>, <mark style="color:blue;">Use System Time in Responses</mark>, and <mark style="color:blue;">Use Sender Name in Responses</mark>) are shared with other conversation platforms. For explanations of each toggle and the time zone rules, see [Feature Settings](https://docs.maiagent.ai/maiagent-user-guide/en/build/conversation-settings/platform-settings/function-settings.md).

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-7c97c0209ae6644fd58d46bbe7d4e1ffe192c706%2Fteamplus-feature-settings.png?alt=media" alt="Team+ Feature Settings tab with Enable OCR and AI awareness settings"><figcaption><p>Feature Settings tab</p></figcaption></figure>

### 7. Test the Integration <a href="#step-validate-credentials" id="step-validate-credentials"></a>

Click <mark style="color:blue;">Test Integration</mark>. MaiAgent makes a Team+ API call to verify the credentials.

If <mark style="color:red;">Credential verification failed</mark> appears, check the following in order:

* The Channel ID and Channel Secret come from the same service channel
* The API is enabled in the Team+ admin console
* If you entered a service URL, it is accessible from outside your network; for certificate issues, see “Skip Certificate Security Check” above

### 8. Create the Platform and Copy the Webhook URL <a href="#step-save-and-get-webhook-url" id="step-save-and-get-webhook-url"></a>

Click <mark style="color:blue;">Connect Conversation Platform</mark> to finish creating it. The system generates a **Webhook URL**. Copy it for later use.

You can also return to the channel's settings page at any time to copy this URL.

***

## Step 3: Enter the Webhook URL in the Team+ Admin Console <a href="#step-configure-webhook" id="step-configure-webhook"></a>

Return to the <mark style="color:blue;">API Settings</mark> page from Step 1, enter the **Webhook URL** generated by MaiAgent in the <mark style="color:blue;">Webhook</mark> field, and save.

Employees can now send messages to this service channel in Team+, and the Agent will reply automatically.

***

## Getting Started <a href="#getting-started" id="getting-started"></a>

### Supported Message Types <a href="#supported-message-types" id="supported-message-types"></a>

| User Sends                    | How the Agent Handles It                          |
| ----------------------------- | ------------------------------------------------- |
| Text                          | Answers directly                                  |
| Image                         | Can recognize the image content                   |
| File (PDF, Excel, Word, etc.) | Reads the content and answers related questions   |
| Voice message                 | Converts to text for processing                   |
| Video                         | Saves as an attachment in the conversation record |
| Location                      | Records it in the conversation                    |

Agent replies support text and attachments. If a single text message exceeds the Team+ limit of 4,000 characters, the system automatically splits it into multiple messages without truncation.

***

## FAQ <a href="#faq" id="faq"></a>

### Why Does the Agent Not Respond in Group Chats? <a href="#no-group-support" id="no-group-support"></a>

The Team+ integration currently handles only one-on-one conversations. Group chat messages do not trigger replies or appear in MaiAgent's All Conversations.

This differs from platforms such as LINE WORKS, Slack, and Microsoft Teams, which support groups and can be configured to reply only when @mentioned.

### Why Can't Credentials Be Changed? <a href="#why-credentials-are-immutable" id="why-credentials-are-immutable"></a>

Credentials are sensitive data. After storing them, MaiAgent does not return them to the frontend or accept changes on the settings page, to avoid exposing them repeatedly during transmission or on screen. The Channel ID is displayed as read-only so you can verify which service channel is connected.

To replace any credential, delete this channel and create it again.

### The Agent Suddenly Stopped Replying <a href="#troubleshoot-no-reply" id="troubleshoot-no-reply"></a>

Check the following in order:

* The API is still enabled in the Team+ admin console
* The URL is still present in the Webhook field (it may be cleared when settings are changed in the admin console)
* The Channel Access Token has not been regenerated in the Team+ admin console—if it has, the old token is invalid, and you must delete this channel and recreate it with the new credentials
* If you use your own server, it is still accessible from outside your network

### Can Test and Production Environments Coexist? <a href="#test-and-production" id="test-and-production"></a>

Yes. Create two Team+ conversation platforms, each with its own credentials and service URL. Each has an independent Webhook URL, so they do not affect each other.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/team-plus.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
