Support Escalation Triage
When support escalates a ticket to engineering, replays the customer's session, errors and logs, and matches them to a known issue by stack trace and release. Drafts the reply, or files a reproducible bug when the failure is new.
How it works
- Runs when: support escalates a Pylon ticket to engineering.
- Starts from the customer: replays their FullStory session around the failure, then filters logs and errors by their account and the release they hit.
- Matches last: a known issue matches only when its exception, top stack frame and release range are this customer's. The same error message is never enough.
- Files or links: links the known issue, or files a new bug to the team that owns the top frame, with the session, reproduction steps, the error event, the release and the suspected commit.
- You get: a hand-off for engineering and a reply drafted for support. It never contacts the customer itself.
What it needs
- Pylon: read the ticket
- FullStory: replay the session
- Datadog and Sentry: read logs and errors
- Jira: link or file bugs
- Slack: post the hand-off