Capability · Channels
Routing as a first class object.
A channel is not a single recipient. It is a contract: a kind subscription, a timezone, a set of active days, and a set of quiet hours. Save once, forget. Engager does the rest.
Three kinds
Telegram, Email, Slack. The transports your team already uses.
Telegram: bot token plus chat ID. Email: Resend integration plus a recipient list. Slack: incoming webhook URL.
The same routing model applies across all three. The same Send test button. The same audit trail.
engager.rookhq.com / @realm / channels
Channels
4
Enabled
3
Failed test
1
Ops bot
AllBot ending …Df1Q · chat -1001234567
On call only
Alerts onlyBot ending …Hf2X · chat -1009876543
ops@team.rookhq.com
Reports onlyResend → ops@…, legal@…
GitHub admin chat
GitHub onlyBot ending …Kp9R · chat -1005556677
The editor
Six fields. That is the whole config.
Subscribed kinds (a checkbox grid grouped by intent). Timezone. Active days. Quiet hours. Mute window. Enable toggle. Six fields, evaluated in a fixed order, every time a notification is dispatched.
No tag soup. No regex. No "label this notification with seven attributes and pray".
Edit channel
Ops bot · Telegram
Subscribed kinds
Timezone
Asia/Kolkata
Active days
Mon–Sun
Quiet hours
22:00–07:00 · critical only
What lives on a channel row
Six controls in the dashboard.
Subscribed kinds
Compact summary in the row. Click Edit for the full grid.
Active window
Timezone, days, quiet hours rendered as a single human readable string.
Send test
Live send to the channel with a fresh test payload. Result lands inline within seconds.
Enable toggle
Flip on or off without losing config. The history travels with the channel.
Last test pill
Pass or fail with the last error message on hover. The forensics live next to the row.
Edit and delete
Both gated by a confirmation. Every change is audited.
Secrets are encrypted
Every channel secret is wrapped with the workspace data encryption key, which is wrapped with a Key Vault master key.
Decrypted just in time
When a notification needs to fire, the dispatcher decrypts the secret, hits the API, and drops it. No long lived plaintext in memory.
Test before saving secrets
During edit, leave the secret field blank to keep the existing value. Engager never asks you to retype a token you already saved.