> For the complete documentation index, see [llms.txt](https://doc.aissist.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.aissist.io/tutorial/deploy-gateway.md).

# Deploy Gateway

*Last updated: May 13, 2026*

Gateways connect Aissist to your support and messaging platforms.

A gateway defines:

* where Aissist should work
* how it should respond
* which conversations it should handle

### Create a gateway

1. Go to **Deploy → Gateways**.
2. Click **Add Gateway**.
3. Choose your platform.
4. Follow the setup steps to authorize the connection.
5. Set the managing point, escalation target, and any handover rules you need.

<figure><img src="/files/83MRlY8dm1P5A6U5yjVZ" alt=""><figcaption></figcaption></figure>

### Choose the managing point and escalation target

The managing point decides which conversations the gateway handles.

Once configured, Aissist only manages conversations in those points.

The escalation target is the default human destination when Aissist escalates a conversation.

Depending on the platform, the managing point and escalation target can be an inbox, team, group, or queue.

To limit Aissist to specific traffic, use routing rules in the agent platform first.

For example, add a tag, route messages into one inbox, or assign conversations to one queue.

Then use that target as the gateway managing point.

<details>

<summary>Managing points and escalation targets</summary>

Use managing points to control scope.

Use escalation targets to control where escalated conversations should go by default.

| **Platform**                                  | **Managing Point** | **Escalation Target** |
| --------------------------------------------- | ------------------ | --------------------- |
| [Front](/gateways/front.md)                   | Inbox              | Inbox                 |
| [Gorgias](/gateways/gorgias.md)               | Team               | Team                  |
| [Intercom](/gateways/intercom.md)             | Team inbox         | Team inbox            |
| [Zendesk](/gateways/zendesk.md)               | Group              | Group                 |
| [HubSpot](/gateways/hubspot.md)               | Inbox              | Inbox                 |
| [Freshdesk Omni](/gateways/freshdesk-omni.md) | Group              | Group                 |
| [Kustomer](/gateways/kustomer.md)             | Queue              | Queue                 |
| [Salesforce](/gateways/salesforce.md)         | Queue              | Queue                 |

{% hint style="info" %}
Avoid multiple gateways on the same managing point.
{% endhint %}

</details>

### Add handover rules

Use handover rules when different sub agents should route conversations to different human targets.

In the gateway setup, add a handover rule for each workflow that needs a different destination.

In each rule, choose:

* the sub agent that should trigger handoff
* the target that should receive the conversation

The target can be a team, group, inbox, or queue, depending on the platform.

This works well when billing, returns, and technical support should go to different destinations.

Use sub agents to decide **when** handoff should happen.

Use the escalation target for the default destination.

Use handover rules for fine-grained routing by workflow.

This lets Aissist assign different conversations to different targets based on the matched sub agent.

See [Create Sub Agents](/tutorial/create-sub-agents.md) for workflow setup and [Streamline with Human Team](/tutorial/streamline-with-human-team.md) for routing patterns.

### Configure thinking and handover messages

Use these messages to keep the customer informed during slower workflows and human handoff.

#### Thinking message

The thinking message is sent when Aissist takes longer than usual to respond.

Use it to reassure the customer that the request is still being processed.

This helps keep the customer engaged while Aissist is working.

#### Handover message

The handover message is sent when Aissist hands the conversation to a human team.

Use it to tell the customer that a human agent will continue the conversation.

#### Language handling

Both messages are rephrased in the user's language before they are sent.

This helps the message feel natural in the conversation, even if you configure it once in the gateway.

### Supported platforms

<details>

<summary>Supported Agent Platforms</summary>

See the full platform list in [Gateways](/gateways.md).

</details>

### Best practice

Start with one platform and one managing point.

Run **Auto-Pilot** for a short period of time, review live outputs, optimize Aissist, then gradually increase the **Auto-Pilot** time.


---

# 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://doc.aissist.io/tutorial/deploy-gateway.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.