> 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/capabilities/gateways.md).

# Gateways

Gateways put Aissist's AI agent to work inside your help desk or chat platform, on Auto-Pilot, handing over to your team when it should.

*Last updated: November 1, 2026*

A gateway is where your AI agent works: it connects a workspace to the help desk or chat platform your team already uses, so the AI receives conversations there and replies there. This page explains the platforms, the AI mode and the basics of routing and handover. Each platform has its own setup page under [Deploy](https://doc.aissist.io/tutorial/deploy.md).

### Platforms

You add gateways under **Deploy → Gateways**. Each one runs through your project's help desk [connector](https://doc.aissist.io/capabilities/connectors.md), so you sign in to the platform once and the gateway, actions and assets share that connection.

| Platform                                                                    | Setup                                                                      |
| --------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| Intercom                                                                    | [Intercom](https://doc.aissist.io/tutorial/deploy/intercom.md)             |
| Zendesk, tickets and messaging (web and mobile messaging, WhatsApp, social) | [Zendesk](https://doc.aissist.io/tutorial/deploy/zendesk.md)               |
| Front                                                                       | [Front](https://doc.aissist.io/tutorial/deploy/front.md)                   |
| Gorgias                                                                     | [Gorgias](https://doc.aissist.io/tutorial/deploy/gorgias.md)               |
| Freshdesk Omni                                                              | [Freshdesk Omni](https://doc.aissist.io/tutorial/deploy/freshdesk-omni.md) |
| Kustomer                                                                    | [Kustomer](https://doc.aissist.io/tutorial/deploy/kustomer.md)             |
| Salesforce (beta)                                                           | [Salesforce](https://doc.aissist.io/tutorial/deploy/salesforce.md)         |
| HubSpot (beta)                                                              | [HubSpot](https://doc.aissist.io/tutorial/deploy/hubspot.md)               |
| WATI (beta)                                                                 | [WATI](https://doc.aissist.io/tutorial/deploy/wati.md)                     |
| Chatwoot (beta, existing gateways only)                                     | [Chatwoot](https://doc.aissist.io/tutorial/deploy/chatwoot.md)             |

Freshchat is being retired: existing Freshchat gateways keep working, but new ones cannot be created.

### AI mode

Gateways run on **Auto-Pilot**: the AI responds to conversations without human intervention, and your team steps in on handover.

* **Auto-Draft** is deprecated: Draft Mode and auto-draft tags, where the AI wrote a draft for an agent to review and send. Existing Auto-Draft setups keep working and are shown read-only; new ones cannot be created. See [Why was Auto-Draft deprecated?](https://doc.aissist.io/faq.md) in the FAQ.

**Enable Co-Pilot** is a different setting, and it stays: it makes the gateway the default one for [in-note commands](https://doc.aissist.io/capabilities/in-note-command.md). It is only useful if you have deployed more than one gateway on the same help desk account. See [What does Enable Co-Pilot do?](https://doc.aissist.io/faq.md).

A gateway also lets you set an **Initial Delay** before the first reply, a **Delay per interaction**, and the **Output Format** messages are written in on the platform.

### Routing and handover

* **Managing Points** decide which conversations the AI handles: the inboxes, groups, teams, queues or tags of your platform. By default it manages all of them. Start with one.
* **Actor** is the agent account the AI works as on your platform.
* **Escalate & Handover** sets what happens when the AI hands a conversation to people. **Handover Rules** map [sub agents](https://doc.aissist.io/capabilities/sub-agents.md) to teams, so a billing conversation goes to billing and a return to the returns team.
* **Chat Only** holds settings for chat channels, such as a thinking message while the AI works and a message when no reply is generated.

When to hand over is set in the workspace and its sub agents; where the conversation goes is set in the gateway. See [Escalation and Handover](https://doc.aissist.io/capabilities/escalation-and-handover.md).

### With Ask Engine

Ask Engine can tell you what each gateway is doing and why a conversation was or was not answered:

```
Which gateways is this workspace on? Are they deployed, and is each connection still valid?
```

```
Why didn't the AI reply to conversation 48213?
```

Ask Engine reads the gateways' configuration and the conversation's records and answers with what it found. You change gateway settings yourself, on **Deploy → Gateways**.

### Best practice

* **Start on one managing point,** such as one inbox or one tag, then widen.
* **Set up handover rules before going live,** so escalated conversations land with a team, not in a general queue.
* **Watch the first days under Deploy → Sessions** and in [Weekly Reports and Alerts](https://doc.aissist.io/capabilities/weekly-reports.md).
* **Sign in again when the connector shows Re-authorize.** The gateway relies on that connection.

### Related

* [Deploy](https://doc.aissist.io/tutorial/deploy.md)
* [Connectors](https://doc.aissist.io/capabilities/connectors.md)
* [Escalation and Handover](https://doc.aissist.io/capabilities/escalation-and-handover.md)
