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

# Front

Deploy Aissist in Front - sign in, choose the inboxes it manages, set the actor, escalation and handover rules.

*Last updated: November 1, 2026*

Deploy Aissist in Front so it answers conversations in the inboxes you choose, tags them, and hands over to your team. Read [Deploy](/tutorial/deploy.md) first for the steps every gateway shares.

### Prepare Front

* Pick or create the teammate Aissist will answer as. A dedicated teammate works best.
* Route the conversations Aissist should handle into one shared inbox.

### Connect Front

1. Go to **Deploy → Gateways**, click **Add Gateway** and choose **Front**.
2. On **Connect**, choose a Front connector, or create one and click **Save and sign in with Front**.
3. Approve Aissist in Front with an admin account.

The connector keeps the sign-in fresh.

### Set up the agent

* **Managing Points**: the inboxes Aissist manages. Aissist only processes conversations in these inboxes, unless a conversation is already assigned to another teammate.
* **Stop at the following tag(s)**: tags that make Aissist skip a conversation. Use it rarely.
* **Actor**: the teammate Aissist answers as (required).
* **Escalation**: the inbox that gets a conversation when Aissist escalates. If empty, Aissist only unassigns itself.
* **Handover Rules**: map sub-agents to inboxes, so each workflow hands over to the right team.
* **Chat Only**: the thinking message and handover message.

No additional steps are needed in Front.

### How Aissist works in Front

Aissist replies in the conversation using your instructions, assets and actions.

It applies tags, which your Front rules can act on.

When a human should take over, Aissist summarizes the conversation and hands it to the escalation inbox or the inbox of the matching handover rule.

<figure><img src="https://301624521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKHM836KGDAfAWvw6XL6%2Fuploads%2FfmzPRmb14eAIGqLiHyxQ%2FFrontapp-human.png?alt=media&amp;token=07dd7046-b8ce-4e97-a1ff-2fdd25d13a9d" alt=""><figcaption></figcaption></figure>

<figure><img src="https://301624521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKHM836KGDAfAWvw6XL6%2Fuploads%2FagVxKkcFqjmaeX0VF8Hr%2FFrontapp-summary.png?alt=media&amp;token=1d3de9a4-b6c0-4d74-8800-5759c0be43f4" alt=""><figcaption></figcaption></figure>

### Co-Pilot in Front

The Aissist plugin gives your teammates Co-Pilot inside Front: translate what the customer said, summarize the conversation, translate or rephrase a reply and send it, create a draft, and teach Aissist how to handle similar cases.

If you do not see the plugin, open any conversation in Front, click **Manage** in the right panel, and pin the **Aissist** plugin.

Your teammates can also use [in-note commands](/capabilities/in-note-command.md) in Front comments. If you have deployed more than one gateway on this Front account, turn on **Enable Co-Pilot** on the gateway's **Settings** for the one that should answer the plugin and the commands.

### Do it with Ask Engine

> Which inboxes does our Front gateway manage, and is it on Auto-Pilot?

Ask Engine answers from the gateway's settings, including whether its connection is still valid.

### Best practice

* Start with one shared inbox and a dedicated teammate as the actor.
* Pin the Aissist plugin for the team that works the escalation inbox.
* Use handover rules so each workflow lands in the right inbox.

### Related

* [Deploy](/tutorial/deploy.md)
* [In-note Commands](/capabilities/in-note-command.md)