Working with Ordyn in Slack

Most teams never open the Ordyn app day to day. Everything important happens in Slack.

The alert card

Each alert that clears triage posts as one card with:

Headline and severity, graded from observed impact.
Impact, root cause, and the fix, with links to the evidence behind each claim.
Source PR, the pull request whose change this monitor was created for.
Open in Ordyn, to see the full investigation and evidence.
Give Feedback, to tell Ordyn whether the call was right.
Context for Agents, to copy everything into your coding agent.

When more alerts join the same problem, the card updates in place. When the problem recovers, the card says so.

Reply in the thread and mention Ordyn. It has the full investigation in context.

@Ordyn which customers were affected?
@Ordyn is this related to yesterday's deploy?

Any member of the channel can ask Ordyn to change how it monitors. Ordyn makes the change, verifies it, and confirms in the thread.

Say	Ordyn does
”Create a monitor for failed webhook deliveries”	Creates a new monitor in your provider and routes it here
”Change the threshold to 5%“	Edits the monitor’s definition
”Repeat less often”	Sets a minimum interval between notifications
”Make these less urgent”	Caps the severity or adjusts how it judges these alerts
”Always tell me about these”	Bypasses the channel floor for this monitor
”Don’t page me about this again”	Mutes this problem until you say otherwise. Critical still gets through
”This is expected during our nightly batch”	Records the context and uses it in future assessments
”Pause this” / “Delete this” / “Send these to #other-channel”	Pauses, deletes, or reroutes the monitor
”Check again in an hour”	Schedules a follow-up

Ordyn does not act on messages from bots, and it does not treat old messages as authorization for new changes.