Error states for embedded Zoom calls
Problem to solve
Embedding zoom calls on issues was done to streamline workflows for users in fire-fights, eliminating the need to switch to another tool to get a conference bridge up and running. In situations where this is not successful, we want to show users as much information about what went wrong to help them trouble-shoot the problem.
Places where we want to include informative error states:
- Request from Zoom quick action can't start a call via the API
- User can't access zoom call from button
Intended users
Sasha the Software Developer
Devon the DevOps Engineer
Sidney the Systems Administrator
Further details
This work contributes to the Incident Management Vision
Proposal
Identify all the places a user could run into an error. Prioritize based on the most likely error states and design for the main ones.
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
Users don't submit support tickets because we provided them informative error states that allowed them to troubleshoot on their own.