Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve problem and incident management for the BC Wallet #2316

Open
knguyenBC opened this issue Dec 11, 2024 · 0 comments
Open

Improve problem and incident management for the BC Wallet #2316

knguyenBC opened this issue Dec 11, 2024 · 0 comments
Labels
epic needs/huddle story/design Work involving user experience, including design and research

Comments

@knguyenBC
Copy link

Background

When the app experiences issues, the team struggles to acquire information on the issue. The only information comes from support emails reported by users and agents. This makes it hard for the team to investigate, as:

  • support agents need to go back and forth with the user to gather more information
  • The information acquired by support agents are only surface level information users can discover themselves (i.e. not backend mechanics)
  • More detailed information acquired can only be done with one-on-one troubleshooting sessions with a support agent through remote troubleshooting
  • user reports may not be reliable
  • the team doesn't have visibility on reports made to other support centres

The team needs a better method to acquire more information when an issue occurs to help address incidents in real time and minimize impact, and finding the root cause to prevent them from happening in the future.

@knguyenBC knguyenBC added epic story/design Work involving user experience, including design and research needs/huddle labels Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic needs/huddle story/design Work involving user experience, including design and research
Projects
Status: No status
Development

No branches or pull requests

1 participant