🏫
Obvious University
Website
  • 👋Welcome to Obvious University!
  • Strategy
    • Sprints
      • 1️⃣Map
      • 2️⃣Sketch
      • 3️⃣Decide
      • 4️⃣Prototype
      • 5️⃣Test
    • Benchmarking
    • Research
      • 1️⃣Research guide
      • 2️⃣How to recruit users
      • 3️⃣How to conduct an interview well
      • 4️⃣How to take notes
      • 5️⃣How to prep for remote research
      • 6️⃣How to throw a watch party
      • 7️⃣How to create artefacts
  • Working with Features
    • Building with AI
      • 1️⃣Understand the tech
      • 2️⃣Map your product
      • 3️⃣Build a proof of concept
      • 4️⃣LLM Inputs
      • 5️⃣LLM Responses
    • Building Help and Support
      • 1️⃣How to scope a support experience
      • 2️⃣How to design discovery for support
      • 3️⃣How to design a support centre
      • 4️⃣How to write good support articles
  • Product Design
    • Microcopy
      • 1️⃣How to write well
      • 2️⃣How to write phrases
      • 3️⃣How to write messages
      • 4️⃣How to create a voice
    • Typography
      • 1️⃣How to compose type
      • 2️⃣How to create a type scale
      • 3️⃣How to pick typefaces
      • 4️⃣How to pair typefaces
    • Design System
      • 1️⃣Introduction to design systems
      • 2️⃣How to audit a design system
      • 3️⃣How to run a design system pilot
      • 4️⃣How to set up a design foundation
      • 5️⃣How to build components
      • 6️⃣How to document a design system
      • 7️⃣How to enable adoption and govern a design system
    • Mobile Engineering
      • 1️⃣Trunk based development
      • 2️⃣Agile development terminology
      • 3️⃣Git commit messages
      • 4️⃣Code review and pull requests
      • 5️⃣Readings
  • Delivery
    • Project Management
    • Collaboration
  • Hiring and Growth
    • Growth
      • 1️⃣Design growth framework
      • 2️⃣How to give ongoing feedback
      • 3️⃣How to check-in every quarter
      • 4️⃣How to address underperformance
      • 5️⃣FAQs
    • Hiring and careers
      • 1️⃣The Hiring Process
      • 2️⃣Diverse and Inclusive Hiring
  • PEOPLE EXPERIENCE
    • Benefits and Perks
      • 1️⃣Paid time off
      • 2️⃣Insurance and healthcare
      • 3️⃣Continuing education
      • 4️⃣Speaking at conferences
    • Starting at Obvious
      • 1️⃣Introducing Obvious
      • 2️⃣Set up your workspace
      • 3️⃣Onboarding
      • 4️⃣Finances
      • 5️⃣Code of Conduct
    • Employment policies
      • 1️⃣Equal opportunity employment
      • 2️⃣At-will employment
      • 3️⃣Employee records and privacy
      • 4️⃣Prevention of sexual harassment
      • 5️⃣Drugs and alcohol
      • 6️⃣Fraternisation
      • 7️⃣Non-compete and non-solicitation
      • 8️⃣Non-disclosure
Powered by GitBook
On this page
  • 👋 Introduction
  • 1️⃣ Search
  • Use a placeholder to demonstrate breadth
  • Highlight keyword matches in the results
  • 2️⃣ Recent actions
  • 3️⃣ Categories
  1. Working with Features
  2. Building Help and Support

How to design a support centre

PreviousHow to design discovery for supportNextHow to write good support articles

Last updated 1 year ago

👋 Introduction

Support experiences should be designed to help users find their solution as quickly as possible. Finding the most relevant content should be straightforward and intuitive.

This article is about different ways to help users discover solutions swiftly.

1️⃣ Search

A good Search allows users to narrow down to their issue quickly. This is important because users that end up raising tickets have specific queries in mind. Tickets are high-touch so you should deflect them as much as possible.

Use a placeholder to demonstrate breadth

Mention topics that the users can search across.

Highlight keyword matches in the results

Display the context in which the keyword is matched. This will help users can decide if a result is relevant to them.

✨ Try a semantic search

Most Support searches use a keyword search. Semantic search is a better way to match by looking at “meanings” within the context in which the keywords are used. This improves search result relevance and ranking.

✨ Generate LLM summaries

It’s possible that the user’s query can be answered by 3 lines in a ~600 word article.| A good LLM summary helps them get to their solution as soon as they hit enter—without sifting through article titles to find the right one, and then scanning it to find the solution.

2️⃣ Recent actions

Certain actions are more likely to require Support. These could be:

  1. Time-sensitive actions (Eg: UPI payment)

  2. Actions that trigger background operations (Eg: food delivery)

3️⃣ Categories

Support is for specific questions, and Search, while straightforward, has higher interaction cost. Users need to formulate their queries, type them out, scan the results, and hope they find something relevant.

Conversely, grouping articles and FAQs into categories and sub-categories can help users drill down to the solution quickly.

Use terms that users are familiar with

Listen in to customer support calls to learn what words users use. You can also test with users.

Articles can repeat across topics

Prioritise ensuring articles are easy to find.

☝ Guiding principle: Redundancy is fine as long as it improves discovery of the content, which brings faster resolution to the user.

Nesting is fine as long as it is intuitive

The interaction cost will be low if the categories are intuitive. That means that the user doesn’t have to go back and forth through multiple categories, or scan through a long list of articles in a single category. Again, prioritise making articles easy to find.

There will also be a Support entry point in the feature from where the actions are taken (refer ). Use the same flow for both entry points.

3️⃣
About semantic search and how it works
here