Chat channels
tenant = …
What you're looking at. This page is the operator console for the CodeB chat-channel
bridges. Each channel plugin is a small transport module that reads and writes the same on-disk
per-tenant JSON store. The Simulator channel below is a walking-skeleton that exercises the
full pipeline (config, inbound handler, dry-run sender, thread meta, metering, license gate) without
any external API key — use it to prove the plumbing before your real WhatsApp / Booking / Airbnb
numbers are wired in.
Configured channels
Simulator
Walking-skeleton channel. Exercises the pipeline end-to-end without external APIs. Useful for smoke tests, integration tests, and operator training.
Live · today
WhatsApp Business
Meta Cloud API, per-tenant app credentials, HMAC X-Hub-Signature verification.
Coming soon
Booking.com
Partner API messaging with the reservation guest.
Coming soon
Airbnb
Host API messaging with the reservation guest.
Coming soon
Email
SMTP + IMAP bridge that treats an email thread as one channel thread.
Coming next
SMPP / SMS
Direct SMSC connection or aggregator; treats one MSISDN as one thread.
Coming next
Signal
Open protocol; ToS review pending before we ship a plugin.
Deferred
Telegram
Bot API; per-tenant bot token.
Coming next
Matrix
Federated XMPP-cousin over Matrix homeserver bridging.
Q4 2026
IRC
Ships on request; the pipeline treats an IRC channel as one thread.
On demand
Simulator channel
Configuration
When on, outbound sends are persisted with status
dry-run and never leave the box.
Config lives at
App_Data/<tenant>/xmpp-channels/simulator/config.json. The webhook-verify token is auto-generated on first load and remains stable across restarts.Simulate inbound message
Send outbound (dry-run by default)
Threads & messages
No threads yet. Simulate an inbound above to seed one.