Just an incoming webhook. Create one on the destination channel under Integrations, copy the URL into the SleekAI chatbot settings, and choose the escalation trigger. No Mattermost plugin, no bot account, and no extra dependency on a paid Mattermost tier as long as your edition allows incoming webhooks.

The webhook receives the chat transcript, the user-supplied email if you collected one, the page URL, the chatbot name, the model name, and the user role. The format is plain Mattermost markdown, so agents see the transcript laid out with role labels and you can adjust the template in the chatbot settings.

Yes. The on-page widget stays live. Agent replies posted into the Mattermost channel can be relayed back through an outgoing webhook, or the agent can email the visitor directly from the captured address. Many teams prefer the email path because it doubles as a paper trail in their CRM.

Each chatbot has its own escalation trigger. You can require an explicit visitor request like talk to a human, a low-confidence signal from the model, or a button click. Display conditions also let you disable handoff entirely on pages where it does not make sense, like the marketing homepage.

Two places. The SleekAI conversation log writes every exchange to a WordPress custom table with the model name, token usage, and origin page. Mattermost keeps the escalation thread under whatever retention policy your channel has. You decide if you want to purge the WP log on a schedule.

It can be. Both WordPress and Mattermost are deployable inside your own infrastructure, and the model provider is whichever vendor you sign a DPA with. SleekAI passes only the chat context to the model and only the escalation payload to Mattermost, so the surface area is small enough to audit per route.

Yes. Multibot gives each chatbot its own webhook URL and escalation rules, so a billing bot can post to a finance channel, a docs bot to support, and an internal HR bot to a private staff channel. The transcripts include the source bot name so it is clear where the request originated.

The WordPress server needs outbound network access to the Mattermost webhook URL. If Mattermost is only reachable on a private network, you can deploy WordPress on the same network, or expose the webhook endpoint behind a reverse proxy that authenticates the request. The webhook itself is HTTP POST, so any standard tunnel works.