One handle for whoever holds the pager

The name never rotates

Ask an engineering org how to reach on-call and you get a wiki page, a channel topic edited by hand, and a Slack group someone forgets to update. Meanwhile people mention the engineer they remember, who left the rotation two cycles ago and answers anyway.

@Oncall is a Slack app, so its name autocompletes in every channel and never goes stale. Mentions land in the on-call room, the person with the pager answers, and the asking team reads it in their own thread, from @Oncall.

A room the org can't read

Diagnosis is guesswork out loud: could be the cache, could be DNS, could be Friday. In the private room, responders guess with each other and send the org an answer once they trust it. Top-level messages in the room never relay, and a reply that starts with // stays inside the thread as a note.

Every escalation carries a link to the source message, so a responder can jump to the original conversation when context runs thin. Screenshots relay on their own, so the graph arrives with the question.

What this doesn't replace

BotFerry rings no phones. There are no escalation policies, no acknowledgment timers, no 3am wake-ups; a mention of @Oncall is a Slack message and stays one. Keep the pager for severity one. Point @Oncall at the questions that land in a random engineer's DMs today: "is this yours?", "safe to deploy?", "who owns this table?".

Handover is nothing

A rotation change updates the pager schedule and touches nothing else. The Slack handle, the room, and the open threads stay where they are, and Monday's responder inherits Friday's context by scrolling up.