Support Flows


Developed user flows and a comprehensive user support guide for Loblaw Technology.



Product Analysis:

Note: Specifics are not included as they are company property of Loblaw Technologies.

Problem Identified: New blood pressure machines (PC health stations) being developed but no clear structure on customer support.

KPI: 100 views of the support guide. Issue tickets are assigned to the correct team.

Goals:
Role: Product Analyst.

Technologies Utilized: Jira, Confluence, Gliffy.

Example User Journey:
  1. A customer identifies an issue with the blood pressure machine.
  2. The customer finds the builders information online and calls them.
  3. The support team documents the issue and collects customer information.
  4. The support team creates an issue ticket on Jira and assigns it to the correct team based on the issue - IT, the builder, etc.
  5. The team assigned fixes the issue and closes the ticket, along with letting the support team know it is closed.
  6. The support team may reach out to the customer if they requested to acknowledge the issue has been corrected.
  7. The team assigned documents how to solve the issue for future use if it is reoccuring.
Development Journey: July, 2022:Problem identified. Started developing over 20 user flows, edited and improved them. Support guide document in progress.
August, 2022: Support guide and Confluence page updated and completed. Presentation to the team.


Learnings:With additional time and resources I would have liked to understand metrics on the following:
Challenges:
Over the course of the project, some challenges I encountered were: