Mobile banking app with multi-fiat currencies and Bitcoin integration.
Xapo is a fintech startup, created in Palo Alto, California, in 2014, offering multi-currency accounts, a Mastercard debit card, fee-free currency exchange, and a Bitcoin wallet.
They had an existing FAQ, hosted on the Intercom platform and later migrated to Salesforce, consisting of approximately 50 articles divided into three language support sites (English, Spanish, and Brazilian Portuguese).
The articles contained in the FAQ were drafted with the intention to answer and provide quick solutions in a self-serve manner to some of the most common questions submitted by end-users. However, the existing Knowledge-Base was struggling to deflect the volume of created tickets which was overloading the support team.
The main challenge Xapo was facing with its existing support site was that users needed help finding the answers they were looking for.
To address the challenge of an overloaded support team and a struggling knowledge base, Xapo recognized the importance of having a dedicated content manager to develop new content, organize, manage it, and optimize the Self-Support platform experience along with the Customer Support focus.
In 2017, on joining Xapo, my responsibilities included managing the existing FAQ site. This involved creating new content in English that provides clear and concise answers to users' questions, translating it into Spanish and Portuguese, and evaluating its performance based on key metrics ensuring the existing articles are easy for users to find.
To begin the project, I conducted a thorough audit of the entire Help Center. During this process, I discovered that the FAQ content had been produced by different individuals from various language sources. As a result, there were inconsistencies across the different language sites, with some original articles missing their corresponding translations.
This lack of consistency had a significant impact on the performance of the chatbot hosted on Facebook Messenger. Since it extracted answers from the Knowledge-Base articles, outdated or incomplete information resulted in incorrect responses.
Upon analyzing the analytics of the Support Site, it was discovered that most users were contacting support by searching for "contact us" instead of using the available library of help articles. The "Contact Us" article also included an email contact instead of a contact form, which allowed users to repeatedly use the email without returning to the Support Site.
Additionally, the search function performed poorly, with many queries producing no results or irrelevant articles that did not receive any clicks, indicating a lack of accuracy in suggesting relevant articles.
The auditing of the existing content of the Help Center revealed a number of critical maintenance issues, such as untranslated and outdated content, content with incorrect information, unclear/incomplete articles, lack of articles addressing the most common issues, country/regional incompatible content, misplaced content in navigational architecture, unclear indexation, low search performance due to lack of vocabulary learning (bitcoin, bit coin, BTC), and unresponsive/underperforming chatbot assistance via Facebook messenger.
Overall, these issues created a poor user experience and resulted in support agents receiving repetitive inquiries that could have been quickly resolved through self-service options.
From our initial discoveries, we determined the main areas of improvement and set our goals.
The key areas for improvement included enhancing the navigational experience and searchability for the end-users, updating and creating new content, and improving the visual appeal of the support site.
We set a list of self-service goals:
We ultimately developed a new Xapo-branded look for the support articles.
I teamed up with the Product and DevOps team to comprehensively review the existing content, while also identifying incorrect or missing information, including gaps in the translated articles throughout the FAQ. Subsequently, I arranged the updated and corrected content into distinct categories and established a clear content hierarchy. Finally, I created a system that monitored the structure of the new Help Center, along with the status and progress of all article translations.
After conducting a thorough audit, we identified three main types of articles:
We also discovered the need to distinguish the article types and map them to devices such as iOS, Android, and web app.
To simplify the instructional articles, we separated the instructions by device type (mobile and web) instead of having separate articles for each operating system (Android, iOS, and web app). We integrated a Xapo brand-illustrated mobile device to enhance brand extension and visibility, as the steps were similar between Android and iOS with only a few specific cases.
To save time, we used a template for repeat articles rather than coding each one from scratch.
We then developed a clear information architecture, and content indexation while designing customer journey maps and customer experience design until the point of contact (Contact Us redesign).
Despite the presence of relevant articles in the knowledge base, some end-users would still submit requests to the support team without checking the self-service resources. To encourage self-service, we removed the "contact us" button from the footer of the support page and instead provided contacting steps in each support article. This approach helped drive end-users to consult the knowledge base before reaching out to our support team.
Additionally, we aimed to proactively resolve frequently asked questions during the contact process, thus minimizing the number of tickets submitted to our support team.
After mapping the customer journey, we prepared a flow sitemap to put everything in order.
The support team's contact form was designed with four steps. The first two steps required the end-user to select from multiple-choice options, which would then generate specific content for the following step based on their selections. Depending on the options chosen, the third step would provide a list of relevant articles that could potentially solve the user's issue.
At this point, the end-user could review the suggested responses and try to resolve their issue by consulting the recommended articles. If none of the suggested responses were helpful, the end-user would be provided with a contact link to reach out to the support team directly for personalized assistance.
By incorporating pre-selected articles for specific topics within the contact navigation, we were able to provide self-help content from the knowledge base and potentially reduce resolution time, and avoid creating unnecessary support tickets.
Due to the nature of our business, certain users may face restrictions when accessing and utilizing our products and services. Similarly, it's important to restrict access to articles that don't apply to certain users based on their language or jurisdiction. To address this issue, we allocated selected articles under specific user segmentations, ensuring that users outside their jurisdiction were unable to access articles that did not apply to their profile type.
To achieve this, we utilized geolocation capabilities in our Salesforce content management tool, setting permission views and access restrictions for selected articles for certain user segments. This allowed us to hide certain articles from certain users and create various formats of content based on user segmentation by region or country of residence. This ensures that users access only the content that's relevant to their profile, depending on the type of service they use.
For instance, we created articles specific to the country-level available debit cards, such as those in Brazil, Argentina, Europe, the UK, and the USA.
Furthermore, we implemented restrictions on certain content at both the country and state levels based on user jurisdiction. For instance, while users in certain US states could receive Bitcoin payments and store them in their account, they were not able to buy Bitcoin from their account or use a Bitcoin Debit Card.
To improve the user experience and ensure that end-users can easily find the information they need, several steps were taken. Firstly, we created a translation glossary of key terms, such as transfer, transaction, and sending money.
Additionally, we worked closely with the Product and Development team to develop content in anticipation of future app feature releases. We also collaborated with the legal team to review and validate the newly created articles to ensure compliance with regulations.
Our goal was to develop content in line with future app feature releases and to provide our customers with the necessary resources to resolve their issues independently.
In addition to developing new content and optimizing the Self-Support platform, I was also responsible for monitoring user feedback and identifying areas for improvement. This feedback would be used to identify gaps in our knowledge base and unanswered queries, and continuously improve the overall support experience for Xapo's users.
The performance of Knowledge-Base articles was continuously tracked using analytics feedback. By analyzing user search and navigation patterns, we were able to identify and correct areas of poor site usability. For instance, we discovered that some Spanish-speaking users used a combination of English and Spanish words in their searches. By exploring this data, we instructed the knowledge base software to analyze cross-language semantic words, resulting in an improved content discoverability score for these users.
New articles would be created for two main reasons:
We recognized the significance of upholding brand consistency during the Xapo brand makeover. To achieve this, we revamped the support site entirely, ensuring it was in line with the brand's identity and image.
We incorporated several UI elements such as colors, fonts, images, and characters throughout the site to achieve this objective.
Button with descriptive text to call the user's attention to subsequent steps, or more information. Ex: "What next?", "See more".
These links are found inside articles and redirecting users to an alternative solution
These links are found inside articles and redirecting users to an alternative solution based on their mobile device (Android, iOS)
These links are found inside articles and redirecting users to their selected solution:
- Mobile vs Web
- ID or Proof of Address
The selection section will show a small GIF animation illustrating the visited device section.
- Mobile
- Web
Competition study
Establishing the design for the video
Design elements for animation
Youtube thumbnail design
We overhauled the articles indexation and listings and redesigned the site's structure and grouped the main sections within their category, giving each section a unique icon and a comprehensive description of their respective content offerings. This approach allowed end-users to have a more informed and intuitive navigational experience, making it easier and faster for users to access all articles of a particular section on the same page.
The website redesign led to a substantial improvement in site structure and an enhanced user experience for the support platform. These advancements successfully reduced the volume of ticket requests submitted via the contact form and increased the self-service score among end-users visiting the Help Center. Consequently, users were able to resolve their issues and access the information they needed more efficiently. Furthermore, the development of self-service articles supplied valuable resources for our support agents to create effective macros.
The project's success depended on taking a holistic approach to developing and maintaining the knowledge base, requiring collaboration across multiple departments within the fast-paced start-up. We established connections between various divisions and established chains of influence among the product planning, UX team, DevOps, and legal teams to ensure that the Help Center content was up-to-date with the latest technical and product developments.