ISSUE INTAKE & FOLLOW-UP · Workflow idea
Capture each submitted issue in a shared record, then use its reported severity to guide team follow-up. Make urgent reports visible in a team channel and send other reports to the responsible inbox.
01 / The starting point
A submitted form with the reporter’s details, issue, and stated severity
“Record the submitted issue and route its notification according to the severity chosen on the form.”
02 / The work
Organizes incoming issue reports, records their details, and sends a notification to the appropriate internal destination based on the selected severity.
Collect the reporter’s name, contact details, issue description, and stated severity.
Add the submitted details to the team’s shared issue tracker so the report can be reviewed and tracked.
Use the team’s agreed severity categories to distinguish reports that need prompt visibility.
Send higher-severity reports to the designated team channel and other reports to the responsible inbox.
Have a team member verify the report, decide its priority, and record who owns the next step.
03 / The result
A shared issue record and a severity-based notification for the team, with higher-severity reports highlighted for prompt attention.
Reports & insights · Example outcome
A shared issue record and a severity-based notification for the team, with higher-severity reports highlighted for prompt attention.
Severity is the reporter’s stated assessment, not a verified diagnosis. Have a person review urgent reports and confirm the response needed.
04 / Make it yours
A few choices shape the work around your team.
Ask for the reporter’s name, email, issue description, and a clearly explained severity rating.
Choose fields for the submitted details, severity, review status, owner, and follow-up.
Agree which reports should be highlighted and select the internal destinations for each category.
Submit example reports at each severity and confirm that each is recorded and reaches the intended internal team.