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

# Salesforce

Deploy Aissist in Salesforce (beta) - sign in to your org, let Aissist deploy its case triggers, choose the queues it manages, set the actor, escalation and handover rules.

*Last updated: October 25, 2026*

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

{% hint style="info" %}
The Salesforce gateway is in beta.
{% endhint %}

### Prepare Salesforce

* Use a Salesforce **admin** of the org to sign in. Aissist deploys triggers to the org, which needs admin rights.
* Pick or create the user Aissist will answer as. A dedicated user works best.
* Route the cases Aissist should handle to one queue.
* Turn on Topics for cases: Aissist tags cases with Salesforce Topics. In Setup, go to **Topics for Objects**, select **Case** and enable **Topics**.

### Connect Salesforce

1. Go to **Deploy → Gateways**, click **Add Gateway** and choose **Salesforce**.
2. On **Connect**, choose a Salesforce connector, or create one: choose the **Environment** (**Production** or **Sandbox**) and click **Save and sign in with Salesforce**.
3. Sign in to your org and allow access.

The connector keeps the sign-in fresh. The **Salesforce Connection** card shows the instance URL it is connected to.

### Set up the agent

* **Managing Points (Queues)**: the queues Aissist manages. By default, it manages all.
* **Actor**: the user Aissist answers as (required).
* **Escalation**: the queue that gets a case when Aissist escalates. If empty, Aissist only unassigns itself.
* **Handover Rules**: map sub-agents to queues, so each workflow hands over to the right team.

On the **Advanced** tab:

* **Organization-Wide Email**: the address Aissist's email replies are sent from. Without one, emails are sent as the signed-in user.
* **Apex Trigger Deployment**: Aissist deploys the Apex triggers and classes that send case events (new cases, assignments, messages and notes) to it. This happens automatically once the connection is ready; the card lists what is deployed. If it failed, click **Deploy Apex Triggers**, and use **Test Connectivity** to check the link.

The Salesforce gateway has no chat-only settings.

### How Aissist works in Salesforce

Aissist replies on the case, adds Topics as tags, and when a human should take over, summarizes the case and moves it to the escalation queue or the queue of the matching handover rule.

### Do it with Ask Engine

> Is our Salesforce gateway deployed, and which queues does it manage?

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

### Best practice

* Try the gateway in a **Sandbox** org first, then connect production.
* Enable Topics for cases before going live, or tagging will not work.
* Start with one queue, and check the **Advanced** tab shows the Apex components as deployed.

### Related

* [Deploy](/tutorial/deploy.md)
* [Escalation and Handover](/capabilities/escalation-and-handover.md)