CoreComms · governed omnichannel routing spine
Every reply finds its way back to the conversation.
CoreComms is the routing spine underneath QuoxCORE: incidents and approvals reach you on Telegram, Slack, Discord or the web, and when you reply, it routes straight back to the conversation that raised it. No dead-end alerts.
Telegram & Slack bridges live · Discord rolling out · Matrix rooms shipping on the platform, not this add-on
In plain words
What it is, where it lives, when to reach for it
- What is it
- A plugin for the QuoxCORE dashboard that sends platform alerts to Telegram, Slack, Discord or email.
- Where do I use it
- On the dashboard's Comms page; the alerts themselves arrive in apps you already use.
- When would I use it
- When an agent action is waiting for your approval and nobody is watching the dashboard.
- How do I use it
- Add it from the store, open Comms, connect a channel, and choose which alerts it receives.
QuoxCORE is the free, self-hosted platform underneath this. What is QuoxCORE
Your agents pause and wait for a human. If that human is in another tab, another room or another timezone, the work waits too. And when the reply finally comes, it has to land back where the question was asked, not in a form somewhere else.
CoreComms gets the interruption to you fast, on the channel you already have open, and routes your answer straight back to the originating conversation. Every escalation lands in the HITL inbox first, so nothing gets approved outside the governed path.
Bidirectional and governed
It's a conversation, not a one-way alert.
Agents and humans share witnessed Matrix rooms on the same substrate, with a real team of agents answering as themselves, a working !halt kill switch, and approve-with-a-reaction in place of a form.
Older notification plugins fire an alert and stop. CoreComms keeps the thread open in both directions, and puts governance in the middle of it.
- A human reply from Telegram, Slack, Discord or the web routes back to the exact conversation that raised the request, not a generic inbox
- Every escalation lands in the HITL inbox first, so approvals happen through the governed path, never around it
- Agents and humans share witnessed Matrix rooms, with a real team of agents in the room, each answering as itself
- A working
!haltkill switch silences every agent in a room instantly, enforced in the platform, not requested of the model - Approve a risky action with a single reaction from your phone; the reaction is the governed approval, not a shortcut around one
Live demonstration
The routing desk.
This is the outbound side of CoreComms' routing model, recreated on the page. Tick which priorities each channel should receive, then fire a test alert and watch the delivery log route it. Replies you send back on any of these channels route the other way, straight to the conversation that raised the alert.
| Channel | Critical | High | Medium | Low |
|---|---|---|---|---|
| Telegram | ||||
| Slack | ||||
| Discord | ||||
What's in the routing spine
Four channels, one governed inbox.
Everything below reflects the current release and what's actively rolling out next. Nothing here is a metric, it's a description of the mechanism.
Telegram, live and bidirectional
Bot integration via @BotFather for notifications, plus double-puppeted replies into governed Matrix rooms so a reply from Telegram appears as you, in the room.
Slack, live and bidirectional
Incoming webhooks for alerts, with the same bridged reply path back into the originating room or conversation.
Discord, rolling out
The same bridge model as Telegram and Slack, being connected to the routing spine now. Honest status, not a shipped claim.
Agents and humans, one room
Escalations and replies land in the same witnessed Matrix rooms the web app uses, with a real team of agents in the room, each answering as itself.
Governed HITL escalation
Every escalation lands in the HITL inbox first and is priority-filtered before it reaches a channel. That is the matrix you just used above.
!halt and approve-with-a-reaction
!halt in a room and every agent in it goes silent, enforced in the platform. Approve a risky action with a single reaction from your phone.Built for the 3am page
A comms spine that fails well, not silently.
A routing spine is only useful if it behaves when a channel goes down. CoreComms retries failed deliveries with exponential backoff, and if a channel keeps failing it disables itself rather than flooding your queue, on both the alert and the reply path.
- Automatic retry with exponential backoff on every channel
- Channels auto-disable after repeated failures to prevent spam
- One-click test sends before you go live
- In-app notifications and the Matrix room continue regardless of external channel health
Pricing
One ticket, three live channels, one governed inbox.
| Capability | Free | CoreComms |
|---|---|---|
| Telegram | – | Included |
| Slack | – | Included |
| Discord | – | Rolling out |
| – | Included | |
| Notifications | In-app only | Telegram, Slack, Email + in-app; Discord when it lands |
Licence key activation. No subscription, no per-message fees; you bring your own bot token, webhook or SMTP account. Witnessed Matrix rooms and multi-agent teams ship as part of the QuoxCORE platform, not this add-on; see Matrix Rooms for that layer.
inbox:read · settings:write · network:external