Eight channels out.
Every one alertable.
The old paradigm is out. The new paradigm is AI. AI automation is InTouch AI — and "who to notify" is the last clause of the contract. You tell a job what to do, when, what to do when it works, what to do when it doesn't, and who to hear about it. These eight channels are how it tells you. A success report, a failure page, a "file arrived" heads-up — InTouch AI picks the channel and sends.
Five ship on every edition (Email, Slack, Discord, Telegram, SMS — the ones an individual or small team can stand up without an org-tier business account). Three business-account channels activate on Department and Enterprise (WhatsApp, Microsoft Teams, LINE — each requires Meta Business, a Microsoft 365 tenant, or a LINE Official Account). All audit-logged, all credential-vaulted — the tokens live in the AES-256 vault, referenced by name, never pasted into a job, never exposed even to the AI itself. All throttled and retried on failure.
What Actually Sends
Email (SMTP)
Any SMTP server — O365, Gmail, SendGrid, Postmark, your internal MTA. TLS support, per-recipient templating, HTML and plain-text bodies, attachments. The most boring channel and the most reliable.
Slack
Bot token sends to channels and DMs. Block Kit formatting. Per-channel thread support.
Discord
Bot sends to channels and DMs. Embed formatting. Rate-limit-aware.
Telegram
Bot send API. Markdown formatting. Per-chat delivery.
SMS — Twilio / Telnyx / Plivo
Provider of choice. Per-recipient throttling. Error handling for non-deliverable numbers. A paid Twilio/Telnyx/Plivo account is required, but it's a third-party provider tier — no InTouch AI edition gate.
WhatsApp (Meta Cloud API)
Template message support, session message support, media attachments. Requires a Meta Business account and an approved phone number.
Microsoft Teams (Bot Framework)
Channel and 1:1 delivery. Adaptive cards. Essential where Teams is the corporate chat surface.
LINE (Messaging API)
Channel access token delivery. Rich messages, stickers, flex messages. Critical for APAC deployments.
One Alert Object, Any Channel
Alerts aren't hard-coded to a channel. Each subscriber lists the transports they accept. An alert fires, InTouch AI looks up the subscriber, picks the right transport, sends. The same alert body lands in Slack for one user, SMS for another, email for a third. No per-channel alert duplication.
And what fires isn't a dumb log dump. The old config-era tools could only retry N times and email you a stack trace. InTouch AI reads the failure first — it knows why the job broke, smart-retries the transient stuff, refreshes the token that expired — and the message that reaches you is the one sentence that matters: it broke, here's why, here's what I did. Messaging isn't bolted onto the engine. The AI is the center; these channels sit behind it, carrying out its assessment. No legacy notifier can say that.
Alerts Your Team Actually Sees
An intelligent contract needs an intelligent last clause. Start with the five out-of-the-box channels on the free Personal edition (Email, Slack, Discord, Telegram, SMS) — and let the AI tell you what happened, not just that something did.