When the first person sleeps through it.
Priority 2 repeats until somebody acknowledges it. When nobody does, the escalation policy wakes the next person on the rota, then the one after that. It is the same send you were already making, with two more fields.
One request, a whole rota
Name a policy on the send and the alert walks down it. Each step waits, then wakes the next people on its own. The first person to acknowledge stops the whole thing, on every device it reached.
A step can point at a rotation instead of a person, and the rotation is read when the step fires. Somebody on holiday hands over by adding a cover, and the ladder follows it without the policy being touched.
curl https://acciti.com/v1/messages \ -H "Authorization: Bearer $ACCITI_TOKEN" \ -d '{ "user": "your-user-key", "title": "api.acme.com is down", "message": "No response for 90 seconds", "escalation": "weeknights", "priority": 2 }'api.acme.com is down
nowNo response for 90 seconds
Uptime · alarm
- 0 min
production rota
Maya, this week
- 5 min
Tom
Secondary
- 10 min
Whole team
Everyone with a device
Tom acknowledges at 6 minutes. Nobody else is woken.
Shared senders, private phones
A team owns what colleagues need in common and nothing more. Your devices and the key people reach you by are yours, and no teammate can list them, rename them or retire them.
The team owns
- Sending tokens, one per script or service
- The sound library
- On-call policies
- The plan and the bill
You own
- Your devices
- Your user key
- Your passkeys and sessions
- The messages sent to you
A teammate who could retire your devices could silence your alerts, and a silenced alert looks exactly like a quiet night.
Two roles, and that is all
Enough to keep billing and credentials away from everybody who only needs to be paged. Not so many that somebody has to read a manual to add a colleague.
| Can | Member | Admin |
|---|---|---|
| Send, and read what the team sent | ||
| Be on an on-call rota | ||
| Create and revoke sending tokens | — | |
| Edit on-call policies | — | |
| Invite and remove people | — | |
| Change the plan and the card | — |
A team always keeps one admin. Removing the last one is refused, because a team nobody can manage cannot appoint somebody who can.
What a team costs
$15 a month for the whole team, with 1,000,000 messages and 365 days of history. One bill and one allowance, however many people are on the rota, so a sixth person on the roster costs nothing and adding them is not a procurement conversation.