I redesigned Tamara's help center to serve both customers and merchants, two audiences with fundamentally different support needs, while reducing the friction that was pushing users to contact support instead of self-serving.
When customers visited the help center, they were overwhelmed by excessive content and unclear navigation. Merchants had it worse — the entire help center was built around customers, leaving merchants without a proper support path. Both issues were directly contributing to high contact rates.
Given Tamara's role in managing customers' finances, ensuring their security and support is paramount. The goal was to streamline access to support for both customers and merchants, eliminating barriers to help and lowering contact rates.
I restructured the help center with a templated content system and dedicated merchant vs. customer pathways, making it easier for both audiences to find what they need and reducing the need to contact support.
During the ideation phase I focused on revamping the Help Center to better match our new Tamara branding and cutting unnecessary information so users can quickly find what they need to resolve.
Key learnings in this phase:
In this phase, I focused on designing templates that can be used in the article pages of the help center. The design needed to be adaptable to both merchant and customer articles.
After iterating on wireframes, high-fidelity designs were created after implementing stakeholders' feedback. Some of the UI components were custom-designed for Tamara's help center.