Create a help center

Build a self-service help center on Mintlify that helps customers find answers, reduces support ticket volume, and scales with your team.

A help center helps customers troubleshoot and find information about your product. When customers can find answers themselves, they get help faster and your support team can focus on complex issues that require their expertise.

Mintlify provides infrastructure for help centers that scale with your customer base.

• AI-powered search: The assistant answers customer questions using your support content, so people can get answers quickly without knowing exactly where to look or specific terms to search for.
• Feedback collection: Built-in feedback widgets let customers rate articles and report issues so you can improve content.
• Analytics: Track which articles get views, what questions customers ask, and where they struggle in the analytics dashboard.
• Authentication: Use SSO or OAuth to show personalized content based on customer plans or account types.

The fastest way to create a new help center is with the mint new --template command. Run the command and select the help center starter template.

mint new your-help-center-name --template help-center-starter

This creates a new project pre-configured for a help center, including navigation structure, sample pages, and directory listings. See the live example or browse the template source.

If you prefer to configure a help center in an existing project, continue with the steps below.

If you haven't created a Mintlify project yet, see the Quickstart to deploy your site.

• Content for your most common support topics
• Admin access to your Mintlify organization
• Domain for hosting your help center: a custom domain or your default .mintlify.site URL

If you're creating a help center from scratch, skip to Plan your help center structure.

Review your current support resources to understand what to migrate.

• Help articles: What topics do you address? Which articles get the most views?
• FAQs: Do you have frequently asked questions that should become articles?
• Support tickets: What questions do customers ask repeatedly? These should become self-service content.
• Product documentation: Is there overlap between support content and product docs?

• Export to Markdown for the simplest migration to Mintlify.
• Export to HTML if Markdown isn't available, then convert to Markdown.
• Export ticket data to identify common questions that need documentation.

Organize your help center around customer problems, not product features. Customers arrive with questions and goals, so structure content that aligns with how they think about your product and common tasks.

Use the directory property to create index pages for each group in your navigation. When you use the directory property, every root page displays a directory listing for the other pages in the same navigation group. This gives customers an overview of the content in each section that they can click through to the specific pages they need.

Set directory to "card" for a horizontal card layout or "accordion" for a list. The value passes down through the navigation tree unless you specifically override it on a later level.

{
  "navigation": {
    "directory": "card",
    "groups": [
      {
        "group": "Get Started",
        "root": "getting-started/index",
        "pages": [
          "getting-started/quick-setup",
          "getting-started/first-steps"
        ]
      },
      {
        "group": "Account",
        "root": "account/index",
        "pages": [
          "account/billing",
          "account/plans",
          "account/team-management",
          "account/security"
        ]
      },
      {
        "group": "Using the Product",
        "root": "product/index",
        "pages": [
          "product/feature-one",
          "product/feature-two",
          "product/integrations"
        ]
      },
      {
        "group": "Troubleshooting",
        "root": "troubleshooting/index",
        "pages": [
          "troubleshooting/common-errors",
          "troubleshooting/connectivity",
          "troubleshooting/performance"
        ]
      }
    ]
  }
}

See Navigation and Directory listings for more configuration options.

Support content should help customers solve problems quickly. Every article should answer one specific question or solve one specific problem. Organize related content into groups instead of creating overly long pages that have too much information.

Customers scan support pages looking for their specific issue. Use clear headings and short paragraphs.

---
title: "Fix login issues"
description: "Troubleshoot common problems signing in to your account"
---

## Reset your password

If you forgot your password, request a reset link from the login page.

1. Go to the login page.
2. Click **Forgot password**.
3. Enter your email address.
4. Check your inbox for the reset link.

## Clear browser cache

Old cached data can cause login problems. Clear your browser cache and try again.

## Check account status

If your account is suspended or deactivated, you'll see an error when logging in.
Contact support if you believe this is a mistake.

When explaining how to do something, use numbered steps.

Screenshots and diagrams help customers confirm they're in the right place.

![Settings page with billing section highlighted](/images/billing-settings.png)

The assistant answers customer questions using your support content. Configure it from your dashboard.

Feedback helps you understand which pages are helpful and which need improvement. Review feedback to see which pages customers find helpful and which need improvement. Read all comments and update pages based on valid feedback.

Monitor the analytics in your dashboard to see how customers use your help center and improve content over time.

• Popular articles: Which articles get the most views? Keep these accurate and well-maintained.
• Search queries: What do customers search for? Create content for common searches that return no results.
• Assistant conversations: What questions does the assistant receive? Use this to identify content gaps.

If you have different customer tiers or product plans, show relevant content to each segment using group-based access control.

Support content becomes outdated as your product changes. Establish processes to keep content accurate.

Your help center is ready to launch. After deploying:

1. Link to your help center from your product and website.
2. Monitor assistant conversations and search queries to find content gaps.
3. Review feedback ratings weekly and improve low-rated articles.
4. Track ticket volume to measure self-service effectiveness.

A good help center reduces support costs while improving customer satisfaction. Invest in content that answers common questions effectively.

• Guides
• Pages
• Can I rename my project or organization?