PagerDuty
Your on-call team sees what customers said.
Fire a PagerDuty incident from a spec, and the customer quotes ride along in the payload.
Try Annsa- Category
- Code and operations
- Set up
- 3 steps
- Guide
- See Ship →
Improve retention Keep customers past month one3 to work on
1Add dark mode#12
2Fix mobile checkout#14
3Dark mode charts#13
Drive trials Trial to paid2 to work on
4Fix onboarding step 2#9
5Launch email for dark mode#16
spec → PagerDutyThe incident fires with the customer quotes in the payload on-call paged
One spec, one page, full context. A wave of “checkout broken” feedback becomes a spec, and the incident it fires carries those quotes.
On-call, with context.
- Quotes in the page.On-call sees what customers said, not just “something is broken.”
- The right severity.Annsa maps urgency to critical, warning or info.
- Wired on purpose.PagerDuty is never switched on for you. You add the hook when you're ready.
Key, hook, test.
A standard Events API v2 integration key.
- Add the integration key.Paste an Events API v2 key. Annsa encrypts it and reads it only when an incident fires.
- Add the hook.Settings → Hooks, then add PagerDuty. Fire it by hand from a spec, or when a spec is written.
- Check it worked.Test the connection. Annsa sends a dry-run event to confirm the key.
Questions people ask.
Does Annsa page anyone on its own?
No. An incident fires only from a hook you add, or when you fire it from a spec.
Why a separate hook for PagerDuty?
PagerDuty gets incidents that need someone now. Other automations go to Slack or a webhook.
The source of direction for agent teams.
Begin with one agent and the work that matters next.