I have the enormous privilege to work in the Customer Support department at Webflow. I get to work on a fantastic product with even more amazing people, and I love it. As a part of that work, I help track issues that customers may be facing.
To improve our processes and make sure that we keep customers’ issues at the very core and forefront of what we’re doing, I built v3 of the Stabilizer App.
A lot of software companies have different methods and processes for tracking customer issues when building a product. I won’t get into the details and particulars of how that happens at Webflow, but I can provide a general outline of some of the difficulties and problems that arise.
In our situation, we keep our issues in Github. This presents a few challenges:
The solution to these issues was to build a bug tracking app in Webflow. This is a super complicated process, and I started by just sketching out the overall process and how to approach it.
I needed to start with sketching out the process since I needed to make sure that the no-code tools we were using would make this tool possible. As an overview, here’s the tools I would be using and the process and flow for the app:
This means when engineers, pm’s, or QA updates an issue in GitHub, it’s automatically updated in the Stabilizer App. Other apps allow us to have even more functionality.
This leaves us with a really clean site that allows us to easily track what’s impacting customers. The team can view by prioritization, by date, by what’s recently filed and updated, etc. With the ability to customize your views and to focus on only the customer-facing things, it helps the team be more efficient and better informed.
You can view some images of the Stabilizer above. For security and privacy reasons, this site can’t be shared publicly.
to work with you on your next project. Have something in mind? Just click on the button below and let me know all the details and I'll get back to you as soon as possible!