For B2B SaaS support teams

Stop paying your team to answer the same question twice.

Paste your website URL and FAQ Hub builds a help centre and an in-app AI assistant from it. Answers come only from your content, with the source shown. Anything it can't answer goes to your team with the conversation attached.

New here? Your trial starts with account creation.Already have an account? Sign in instead.

Not ready to try it? Find the gaps in your help content →
  • 7-day free trial
  • No credit card
  • Imports your website, PDFs and Word files
your-product.com / welcome / billing / supportFAQ Hub
Help users without leaving your app.OrbitFlow AI is a made-up example product. Its search, AI chat and help centre run on FAQ Hub.The live version is further down this page.

From OrbitFlow docs

Invite team membersWorkspace → Team · Updated 2d ago
Roles and permissionsWorkspace → Access control

✓ Answer from your articles

Go to Settings → Team, select Invite member, enter their work email, and choose a role. They will receive a secure invite link valid for 24 hours.

WebsitePDFDOCXMarkdownCSVJSON

In production

Live on FAQ Hub today.

These help centres and in-app assistants run on FAQ Hub in production.Open one and ask it a question.

  • The Knowledge ElephantAI and Azure consultancy. Help centre and in-app assistant across its website.See it live →
  • FAQ HubOur own help centre and in-app assistant run on the product we sell.See it live →
  • Max & MiaAI phone and back-office assistants for UK tradespeople. Help centre and in-app assistant.See it live →

The problem

Every repeat question is a ticket your team didn't need to handle.

The answer usually exists already. Customers can't find it, so they ask your team, and harder tickets wait.

See what repeat questions cost your team →

The queue fills with questions you've already answered

Inviting a teammate, finding an invoice, resetting access. Your team types the same reply again.

With FAQ Hub the assistant answers them inside your product, from your published articles.

The answer is buried where customers can't find it

It sits in a PDF, a release note or one person's head, so customers email instead of searching.

With FAQ Hub those sources become one help centre that search and chat both answer from.

Generic AI chatbots guess

An invented answer sends the customer back to your team, now with less trust in self-service.

With FAQ Hub answers come only from your content, cite the article, and go to a person when the content runs out.

How it works

From your website to a working help centre.

Start with content you already have. You can read, edit and unpublish any answer at any time.

01

Paste your site or upload docs

Give FAQ Hub your website URL, or upload PDF, Word, Markdown, CSV or JSON files. It builds categories and help articles from them.

02

Check and edit the answers

Read what was built. Edit, correct or unpublish any article whenever you need to.

03

Put it live

Share the help centre link, or add the in-app assistant to your product with an embed snippet.

04

Hard questions go to your team

When your content doesn't cover a question, the assistant says so and offers a ticket or live chat, with the conversation attached.

Product demo

FAQ Hub in action: support inside the product

Watch more FAQ Hub videos →

FAQ Hub turns scattered support documents into a help centre and an in-app assistant

What your customers see

Answers from your own content, with the source shown.

Customers ask in plain words. The assistant answers from the articles you have published and links to them. Your team sees which questions the content could not answer.

  • Sources shownEach answer links to the articles it came from.
  • Says when it doesn't knowThe customer is offered a ticket or live chat instead of a guess.
  • You choose where it appearsA help centre page, a widget inside your product, or keyboard search.
Explore all features →
FAQ Hub portal with an embedded AI support conversation

For AI agents

Tell your agent torun your help centre.

Connect Claude, Cursor, GitHub Copilot, Codex or any MCP client. Your agent answers customers from your articles, logs the questions it could not answer and drafts the missing ones. See what agents can do →

ClaudeExample

Build a help centre for OrbitFlow AI from our website and turn on the chat assistant.

faqhub · client_product_createfaqhub · client_product_onboardfaqhub · client_onboarding_statusfaqhub · client_product_set_features

ClaudeDone. The OrbitFlow AI help centre is live in Private Preview, so search engines can't see it yet. Take a look, then make it public when you're ready.

ClientYour client key
ProductOrbitFlow AI
ArticlesFrom your website
PermissionsPer key scope
FAQ Hubapi.faqhub.io/mcp
PreviewPrivate, noindex
ImportRuns in background
ChatPer product setting
Portalorbitflow.app.faqhub.io
orbitflow.app.faqhub.ioPrivate Preview
OrbitFlow AI

How can we help?

  • Getting Started5 articles
  • Troubleshooting4 articles
  • Billing & Plans3 articles
  • Manage Your Team2 articles

Powered by FAQ Hub

Example with OrbitFlow AI, a made-up product. The tool names are FAQ Hub's own MCP tools. Client-level tools need a Growth or Enterprise client key.

Works with any AI

Setup takes about a minute once you have a key.

FAQ Hub runs an MCP server, so any assistant that supports remote MCP servers can connect. Start the trial, create a key, and copy the setup for your AI. See the full guide.

  1. 01

    Start your free trial

    Create your account and paste your website URL. FAQ Hub builds the help centre your AI will work with. The 7-day trial needs no card.

    Start free trial
  2. 02

    Create an API key

    In FAQ Hub open Product Info, switch on MCP access and create a named key. A Content Writer key lets your agent save drafts. A key only reaches the product it belongs to.

    Read the key guide →
  3. 03

    Connect and ask

    Copy the setup for your AI below and swap in your key. Then ask it to list your articles or draft a new one.

  • Claude Code

    One command in your terminal.

    Show what you copy

    Run in your terminal

    claude mcp add --transport http faqhub https://api.faqhub.io/mcp --header "Authorization: Bearer YOUR_FAQHUB_API_KEY"
  • Claude Desktop

    Add it to your desktop config.

    Show what you copy

    Add to claude_desktop_config.json (needs Node.js for npx)

    {
      "mcpServers": {
        "faqhub": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://api.faqhub.io/mcp",
            "--header",
            "Authorization:${FAQHUB_AUTH}"
          ],
          "env": {
            "FAQHUB_AUTH": "Bearer YOUR_FAQHUB_API_KEY"
          }
        }
      }
    }
  • Cursor

    Paste into your MCP settings.

    Show what you copy

    Add to ~/.cursor/mcp.json

    {
      "mcpServers": {
        "faqhub": {
          "url": "https://api.faqhub.io/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_FAQHUB_API_KEY"
          }
        }
      }
    }
  • GitHub Copilot

    Agent mode in Visual Studio Code.

    Show what you copy

    Add to .vscode/mcp.json. VS Code asks for the key and keeps it out of the file.

    {
      "servers": {
        "faqhub": {
          "type": "http",
          "url": "https://api.faqhub.io/mcp",
          "headers": {
            "Authorization": "Bearer ${input:faqhub-api-key}"
          }
        }
      },
      "inputs": [
        {
          "type": "promptString",
          "id": "faqhub-api-key",
          "description": "FAQ Hub product API key",
          "password": true
        }
      ]
    }
  • Codex

    Reads the key from an environment variable.

    Show what you copy

    Add to ~/.codex/config.toml, then set FAQHUB_API_KEY in your shell

    [mcp_servers.faqhub]
    url = "https://api.faqhub.io/mcp"
    bearer_token_env_var = "FAQHUB_API_KEY"
  • Any agent

    Let the agent set itself up.

    Show what you copy

    Paste into your agent chat and give it your key

    Add an MCP server named "faqhub" using Streamable HTTP at https://api.faqhub.io/mcp.
    Send the header "Authorization: Bearer YOUR_FAQHUB_API_KEY" with every request, replacing YOUR_FAQHUB_API_KEY with the FAQ Hub product API key I give you.
    Then call product_get to confirm the connection and tell me which product it is scoped to.
  • Any MCP client

    Streamable HTTP with a bearer key.

    Show what you copy

    Server URL, plus the header Authorization: Bearer YOUR_FAQHUB_API_KEY

    https://api.faqhub.io/mcp

Replace YOUR_FAQHUB_API_KEY with your own key and keep it out of shared files. Client-level tools, such as creating products and importing from a website, need a Growth or Enterprise client key. A product key covers one product's content. Browser chat apps such as claude.ai and ChatGPT add servers through their own connector settings, and what they accept for sign-in varies. If yours does not take a bearer API key, use one of the clients above.

1 sourceof answers behind your help centre, in-app assistant and AI agents
Multi-producthelp centres on your own domains, from one account
24/7self-service, with every answer linked to its source

Live example

This help centre runs on FAQ Hub. Ask it anything.

This is FAQ Hub's own help centre, loaded live on this page. It is the same product you would use for yours.

Loading help centre...

Built for support teams

Run self-service across every product and team.

FAQ Hub scales from one help centre to a portfolio of products, with the controls support, product and docs teams need to share one source of answers.

Plan an enterprise rollout →
01

Multi-product, multi-domain

Run a separate help centre and assistant for each product, each on its own custom domain, from one account.

02

Seats for the whole team

Give support, product and docs teams their own seats, so the people who know the answer can fix the article.

03

Escalation into your tools

Questions the content can't answer go to your team in Slack, Microsoft Teams, Zapier or n8n, with the conversation attached.

04

Scoped access for AI agents

Connect agents with keys limited to a role, such as answering customers, drafting articles or reviewing changes.

Onboarding

Onboarding with your team, from import to launch.

We import your site and docs, review the first answers with your team, set up escalation routes and plan the launch. Questions go straight to the people who build FAQ Hub, not a ticket queue.

Book a demo

Try it on your own site

See a help centre built from your own website.

Start the free trial and see your own help centre today.Or book a demo and we will walk your team through it.

Enterprise

Plan a larger rollout with us.

Tell us about your products, support volume and rollout goals. We will help you plan what to import, which integrations you need and when to launch.

  • Up to 10 products and custom domains
  • Higher article and AI conversation limits, with seats for up to 110 people
  • Hosted on Microsoft Azure in the EU (West Europe region)
  • Guided onboarding, rollout planning and answers for your security review
We reply by email.