+

The ping that matters.

Most alerts are noise. These are not: when a conversation needs a human, the right channel hears about it in seconds, with the reason attached.

# support-urgent
RB

ReplyBay APP 02:47

P0 escalation

Chargeback threat from a high-value customer · order #4711 · full thread and order history attached.

✅ 1   acknowledged by Dion · 41s later

# support-urgent
RB

ReplyBay BOT Today at 02:47

P0 escalation

Chargeback threat from a high-value customer · order #4711 · full thread attached.

The right ping, the right person, in seconds.

How it works with Slack & Discord alerts

1

One webhook per priority

P0 to the on-call channel, P1 to the manager, P2 to the team, and a fourth feed for errors. Slack and Discord both, or either.

2

Alerts carry context

Priority, reason, customer, order: enough to act from the notification without opening three tabs.

3

Silence stays silent

Auto-sent replies never ping anyone. If your phone buzzes, it actually mattered.

Severity-shaped channels

A refund dispute pings the manager channel; a failed send pings engineering. Nobody drowns in everything.

Sub-5-second delivery

Median time from angry message to alert: under five seconds.

Works with your on-call

Point P0 at the channel your escalation policy already watches.

Discord for small crews

No Slack? Discord webhooks get the identical treatment.