Reducing Daily ACtivity Tickets
Lead Design | Research
Overview
Daily Activity was the heartbeat of our data. It's where PMS and POS data is ingested and mapped to our system. It was also the feature with the highest support ticket count. I was able to redesign this feature to help drop support tickets by 20% in the first 4 weeks.
Unmapped Codes
A majority of support tickets were a result of unmapped codes. This was primarily due to poor content design and scattered information. By implementing a more streamlined process for assigning and creating codes within Daily Activity, and redesigning the error messaging, we were able to empower the user to resolve issues independently.
Conclusion
The result is a hub for integrated data that feeds the entire system while allowing the user to easily collobrate, identify issues, and confidently solve them.

If you'd like to learn more about how I designed our import system status or why we included comments then please contact me.
Contact MeNext Case Study