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
Go to Deploy → Gateways.
Click Add Gateway.
Choose your platform.
Follow the setup steps to authorize the connection.
Set the managing point, escalation target, and any handover rules you need.
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.
Managing points and escalation targets
Use managing points to control scope.
Use escalation targets to control where escalated conversations should go by default.
Platform
Managing Point
Escalation Target
Avoid multiple gateways on the same managing point.
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 for workflow setup and Streamline with Human Team 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
Supported Agent Platforms
See the full platform list in Gateways.
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.
Last updated