Connect Slack

Slack is a notification destination. SYSOI can pin two channels on the connection:

Alerts — internal ops channel. Consistency drift, hot-tier crossings,

behind-pace episodes, and campaign-ready pings land here.

Push — optional external / stakeholder broadcast channel. Pinned now so

the workspace is ready; no product content routes into Push yet (Dispatch push notifications are a follow-up).

What you'll need

A Slack workspace you can authorize.

Connect

In SYSOI, open Connections → Slack → Connect.
Authorize SYSOI in the Slack window. The card shows Connected.

Pick channels

On the connected Slack card, choose an Alerts channel (required for

live ops pings). The picker lists public and private channels the connection can see.

Optionally choose a Push channel for future external pings.
Save channels.
- Public channels: SYSOI auto-joins on save (needs the channels:join

scope).

Private channels: invite SYSOI manually with /invite @SYSOI in that

channel, then save.

Existing orgs that already pinned a single channel keep that pin as Alerts. Push stays empty until you pick one.

Test it

Use Test alerts / Test push on the Slack card — a confirmation ping should appear in the chosen channel within a few seconds. The result is shown inline.

What triggers a message (Alerts)

A consistency scan that surfaces new warn/critical signals → one message

per scan (up to a handful of signals).

A readiness scoring run where contacts cross into the hot tier → one

message per run (up to a handful of names).

A behind-pace episode on registration pacing → one intervention brief.
A campaign prep run that finishes drafting → one "ready for Activate"

ping.

All are best-effort — a Slack outage never blocks the underlying pipeline. Nothing routes to Push until a later Dispatch push-notification system lands.

Verify

The per-role Test pings are the quickest confirmation. After that, the first real scan or scoring run that produces a signal will post to Alerts automatically.