Platform builders
Bridge many messaging channels
Reach users where they already are — 12+ messaging channels bridged into one AI gateway, per-tenant.
The problem
- Your users live on different messaging apps, and integrating each one — WhatsApp, Telegram, Slack, Discord, Signal, iMessage, Teams, Matrix — is a project in itself.
- In a multi-tenant product, each customer needs their own channel pairings and credentials, kept separate from everyone else's.
- You want the same agent to answer regardless of which channel a message arrives on.
With OpenClawMU
- OpenClawMU bridges WhatsApp, Telegram, Slack, Discord, Signal, iMessage, Microsoft Teams, Matrix, LINE, Lark, Google Chat and an embeddable WebChat widget into one gateway.
- Channel credentials are part of a tenant's isolated directory — each tenant pairs its own channels, and no tenant sees another's pairing.
- The dispatcher normalizes inbound messages from every channel to the same agent runtime, so behaviour is consistent across surfaces.
How it works
Getting there, step by step.
- 1
Pick your channels
Decide which of the 12+ supported channels your product needs to reach users on.
- 2
Pair channels per tenant
Each tenant pairs its own channels (e.g. its own Telegram bot token or WhatsApp session) via the channels.* methods.
- 3
Route inbound to the agent
Point the channel webhooks at the gateway; the dispatcher resolves the tenant and hands the message to the agent runtime.
# one gateway, many tenants
npm install -g openclaw@latest
openclaw onboard --install-daemon
# a tenant per customer / team
openclaw tenants create acmeFrequently asked
FAQ — bridge many messaging channels
Every question here is also emitted as FAQPage JSON-LD — so Google AI Overviews, Perplexity, and ChatGPT browsing extract the answers cleanly. Crawler-friendly fallback below for screen readers and bots that don't run JS.
OpenClawMU bridges 12+ channels including WhatsApp, Telegram, Slack, Discord, Signal, iMessage, Microsoft Teams, Matrix, LINE, Lark, Google Chat and an embeddable WebChat widget.
Yes. A tenant's channel pairings and credentials live in its own directory alongside sessions and memory — no tenant can see another's pairings.
Related use cases
-
Ship a multi-tenant bot platform
The agent platform you're building needs isolation between customers without inventing it from scratch.
Read → -
Graduate a prototype to a product
You built a single-user assistant that works — now customers want their own, isolated and billed.
Read → -
How isolation works
The load-bearing change vs. upstream — tokens, per-tenant directories, path-traversal hardening.
Read the deep dive →
EXFOLIATE!
Run your own gateway today.
Apache-2.0, self-hosted, no SaaS layer between you and your users. Install the CLI, create your first tenant, mint a token — you're routing traffic in 60 seconds.