Skip to content
⌘K
InboxAsk a human

Step 8: Setting up your Help Center and Customer Inbox — migrating your docs and turning on self-serve

Updated by Dustin

The final step in setting up your workspace is giving customers a place to find answers on their own and check the status of their existing conversations. Most teams arriving at this step already have documentation living somewhere else so the goal here isn't necessarily to write a knowledge base from scratch (though you can do this if you want!).

Provided your existing docs are public, you can stay on that system and simply connect it as a knowledge source for the Customer Agent and Sidekick Agent you set up in the previous step.

However, if you want Plain's hosted Ask AI (self-serve search that hands off to your queue when a customer still needs help) and the Customer Inbox (a portal where customers can see and reply to their threads across email, Slack, and other channels), you'll want to migrate or mirror those articles into a Plain Help Center.

This page walks you through deciding whether to index or mirror, bringing your existing articles over via an LLM/agent or the API, and turning on the Customer Inbox.

What good looks like

What we define as "good" for this step is having knowledge living somewhere that can be indexed by your agents. Sometimes, this can be your existing docs tool. For others, creating a free Plain Help Center is the right choice.

In this guide, we’ll be going with the latter — by the end, you’ll have been able to:

  • Search or ask Ask AI one of your top support questions and get a cited answer from a migrated, published article

  • Log into Your requests (the Customer Inbox) with a 6-digit email code and see their open and past threads

  • Submit a New request from the inbox and have it land in your Plain queue and run through your Step 6 routing workflow

The outcome is a working self-serve surface that deflects your most repetitive questions and acts as a "brain" for your agent to gather context from.

What to consider

  • Staying on your existing docs vs. mirroring/migrating into a Plain Help Center. This comes down to which surfaces you want to give your customers:

    • Stay on your existing docs if your documentation is already public and you only want the Customer Agent and Sidekick Agent to read from it when answering threads. Plain indexes your sitemap or URLs directly, so there's nothing to migrate.

    • Mirror or migrate your articles into a Plain Help Center if you're shutting down an old help desk's KB, or if you want to give customers Plain's hosted Ask AI search and the Customer Inbox. Ask AI and the Customer Inbox both live inside a Plain Help Center, so even if you keep your developer docs in a separate repo, mirroring your support articles into Plain can give your customers that unified self-serve + ticket portal experience.

  • One-time migration vs. continuous mirror. Because Plain's Help Center has a GraphQL API (upsertHelpCenterArticle, createHelpCenterArticleGroup, updateHelpCenterIndex), you don't have to author in Plain's UI if your team prefers docs-as-code. If you're leaving an old help desk behind, run a one-time import script and edit in Plain going forward; if your team writes in a Git repo or CMS, run that same script in CI (for example, on merge to main) so your Plain Help Center stays mirrored automatically.

  • Email must be enabled before turning on the Customer Inbox. The Customer Inbox signs customers in with a 6-digit code sent to their email address, so Email needs to be live first.

  • Don't block on DNS. Every Help Center gets a free yourcompany.support.site subdomain — if you want a custom domain like help.yourcompany.com, hand the CNAME record to whoever manages your DNS and run on the subdomain in the meantime.

  • Who should have access? Most small teams set access to Everyone (public, indexed by search engines); if you need a gated portal later, you can restrict access to authenticated customers by tier or account.

How to implement

Step 1: Create the Help Center and set your domain

You create the Help Center shell in the Plain UI first (even if you plan to populate its articles via an agent or the API in Step 2):

  1. Click Help Center in the left navigation. With no Help Center yet, Plain opens the Create a help center form, prefilled from your workspace name (name, description and support.site subdomain) with Visibility set to Everyone and Plain AI set to Allow. Then, click Create.

    Create your help center
  2. Under Help Center → Appearance, pick your primary brand color and upload your logo and favicon

    Set your help center's brand color
  1. Under Help Center → Domains, check the yourcompany.support.site subdomain you set when creating the Help Center (change it here if needed); the site is already live on it (to use a custom domain such as help.yourcompany.com, add the CNAME record shown on that page to your DNS provider settings — SSL is provisioned automatically once the record propagates)

Step 2: Migrate or mirror your existing articles into Plain

Once the Help Center exists, you have three ways to bring your content over depending on where it lives today and how many articles you have.

If you have an export from your old tool (a folder of Markdown or HTML files, a CSV/JSON export, or an API key for Zendesk, Intercom, Help Scout, Notion, or GitBook), our recommendation is to let a coding agent (like Cursor or Claude Code) write and run the migration script for you — or connect it directly to Plain's MCP server so it can create the groups and articles for you in a single session. And no worries — if that sounds involved, it normally takes about fifteen minutes!

  1. Go to Settings → Machine users & Agents, create a machine user (or use an existing one), and grant its API key the helpCenter:edit, helpCenter:read, helpCenterArticle:read, and helpCenterArticleGroup:read permissions

  2. Grab your helpCenterId (either from the URL in the Plain app under Help Center, or by having your agent query helpCenters)

  3. Point your agent at your exported Markdown/HTML folder (or your old tool's API), hand it your Plain API key, helpCenterId, and our Help Center API docs (https://www.plain.com/docs/graphql/help-center.md, https://www.plain.com/docs/graphql/help-center/manage-article-groups.md, and https://www.plain.com/docs/graphql/help-center/manage-articles.md), and ask it to:

    • Convert any Markdown body content into clean HTML (contentHtml is rendered directly in the Help Center)

    • Create your category folders with createHelpCenterArticleGroup (passing parentHelpCenterArticleGroupId if you have nested subcategories)

    • Create or update each article with upsertHelpCenterArticle and status: PUBLISHED, starting with a dry run or a batch of 3-5 articles so you can check the formatting on your support.site URL before running the rest

Option B: Migrate or mirror directly via the GraphQL API

If you're building a script yourself — or wiring up a GitHub Action so a docs repo continuously mirrors into your Plain Help Center — the Help Center GraphQL API comes down to three mutations:

  1. Create your folders (createHelpCenterArticleGroup): Creates a top-level group (or a nested group when you pass parentHelpCenterArticleGroupId) and returns the helpCenterArticleGroup.id.

  2. Upsert each article (upsertHelpCenterArticle): Omit helpCenterArticleId to create a new article, or pass an existing helpCenterArticleId (looked up via helpCenterArticleBySlug) to update it in place when mirroring from Git.

  3. Optionally set the sidebar order (updateHelpCenterIndex): If you want a specific navigation order or inline section headings, query helpCenterIndex to get the current hash and pass the full ordered tree to updateHelpCenterIndex.

The abbreviated shape of creating a group and upserting an article looks like this:

mutation { createHelpCenterArticleGroup(input: { helpCenterId: "hc_01J..." name: "Getting started" }) { helpCenterArticleGroup { id slug } error { message } } } mutation { upsertHelpCenterArticle(input: { helpCenterId: "hc_01J..." helpCenterArticleGroupId: "hcg_01J..." title: "How do I reset my API key?" slug: "reset-api-key" description: "Rotate or revoke an existing key from Settings." contentHtml: "<p>Head to <strong>Settings → API keys</strong> and click <strong>Rotate</strong>.</p>" status: PUBLISHED }) { helpCenterArticle { id slug status } error { message } } }

Option C: Move a small handful of articles in the UI (or generate them from threads)

If you only have a few articles to bring over — or you want to fill gaps after migrating — you can paste or generate them directly in Plain:

  1. In the Help Center sidebar, click the + beside Articles, choose New article, and paste your content into the editor (or open a support thread where a teammate already wrote a great answer and generate a draft article directly from the thread using AI)

  2. Title the article as the question the customer actually types — e.g. "How do I reset my API key?" rather than "API key management" — and keep it to one topic per article so Ask AI can retrieve and cite it cleanly

  3. Change the article's status from Draft to Published and click Save and publish

Create and publish an article

Once published (via any of the three options), both Ask AI and the Customer Agent from Step 7 can use your Help Center articles immediately — no extra knowledge-source setup required.

Step 3: Enable the Customer Inbox

The Customer Inbox adds a Your requests section to your Help Center sidebar where customers log in with a 6-digit email code (no password) to view and reply to their threads, or submit new ones. Customers see simplified status labels: your internal Needs first response, Investigating, and Snoozed statuses all appear to them as In progress, Waiting for customer appears as Waiting for you, and Done appears as Done.

  1. Go to Help Center → Customer Inbox

  2. Toggle on Customer Inbox and click Save (the status line reads Customer Inbox is currently enabled once it saves)

  3. Under Default thread visibility, choose whose threads a logged-in customer can see:

    • Their own threads is always on

    • Check Threads from anyone with the same account if you want colleagues at the same company to see each other's requests (recommended for B2B; note that this option uses the explicit accounts from Step 3 — CRM-synced, API-created, or Slack-linked — and ignores domain-based accounts)

    • Check Threads from anyone with the same email domain if you rely on domain-based accounts and want everyone @customer.com to share visibility

  4. Click Save

Let customers see their company's threads

If you want structured intake instead of a single open text box when customers click New request, you can add fields under Custom forms.

Some gotchas to be aware of:

  • upsertHelpCenterArticle defaults status to DRAFT if you omit it, and Draft articles are invisible to customers, Ask AI, and the Customer Agent alike. Pass status: PUBLISHED in your migration script when you're ready for articles to go live (or flip them to Published in the UI after reviewing).

  • contentHtml expects HTML, not raw Markdown, and article slug values are normalized to lowercase and must be unique within the Help Center. If your source files are .md or .mdx, have your LLM/script convert them to HTML and strip any framework-specific components before calling upsertHelpCenterArticle.

  • Internal image links from your old help desk will break once you turn that tool off. When migrating from Zendesk, Intercom, Help Scout, or Notion, make sure your images are hosted on a public CDN/bucket (or re-uploaded) rather than pointing at private or expiring URLs on the old platform.

  • If you ever set a Help Center's human access to Your team (internal only), toggle on AI access under Help Center → General if you still want the Customer Agent and Sidekick to reference those articles.

  • Threads submitted through the Customer Inbox's New request form arrive on the API support channel. If any of your Step 6 workflows filter by channel (e.g. Support channel equals Email), add API to that condition so portal requests get routed too.

  • The Threads from anyone with the same email domain option only appears when Show domain-based accounts is enabled in Settings → Accounts.

How to verify if this step is working/complete

  1. If you're migrating via an LLM or script, run it against a batch of 3-5 articles first (or with status: DRAFT), then open the articles on your support.site URL to confirm headings, code blocks, and images render cleanly before running the full batch as PUBLISHED.

  2. Open your Help Center URL in an incognito window, search for one of your migrated articles, and ask the same question in Ask AI — confirm it answers and cites the article.

  3. Click Your requests, sign in using the personal test email you used in Step 1, and confirm your earlier test thread appears with its simplified status.

  4. Submit a New request from the Customer Inbox and confirm the thread appears in Plain's All threads view and is picked up by your Step 6 routing workflow.

Troubleshooting/FAQ

My migrated articles are in Plain, but they don't show up on the Help Center or in Ask AI.

upsertHelpCenterArticle defaults status to DRAFT when status isn't passed, and Ask AI, the Customer Agent, and your customers only read Published articles.

Try this: Re-run your upsert with status: PUBLISHED (or open the article in the UI and confirm its status reads Published). If the Help Center's human access is set to Your team, also toggle on AI access under Help Center → General.

Updating an existing article from my sync script failed with a duplicate slug error (or created a second copy).

upsertHelpCenterArticle only updates in place when you pass helpCenterArticleId — without it, Plain treats the call as a brand-new article and rejects duplicate slugs within the same Help Center.

Try this: Have your script query helpCenterArticleBySlug first using your helpCenterId and slug. If an article comes back, pass its id as helpCenterArticleId in upsertHelpCenterArticle; if it returns null, omit helpCenterArticleId to create it.

The Customer Inbox toggle is disabled / won't turn on.

The Customer Inbox signs customers in with a code sent to their email, so the toggle stays disabled until email is enabled as a channel and Plain can send that code.

Try this: Finish the email setup in Step 1 (receiving is enough to get started), then come back to Help Center → Customer Inbox.

A logged-in customer can't see a thread they opened earlier.

The inbox matches threads to the email address the customer signed in with, so a thread they opened from Slack under a different email, or from an alias, won't show up.

Try this: Open the thread in Plain, check the customer's email in the sidebar, and have them sign in with that address.

Colleagues at the same company can't see each other's threads.

Shared visibility is opt-in, and the same account option only looks at explicit accounts. Here are the two reasons it stays hidden:

Threads from anyone with the same account is unchecked

  • Out of the box, a customer only sees their own threads.

  • Try this: Head to Help Center → Customer Inbox and check Threads from anyone with the same account under Default thread visibility.

You're relying on domain-based accounts, which that option ignores

  • Everyone @customer.com is grouped by domain, not by an explicit account.

  • Try this: Either check Threads from anyone with the same email domain instead (it only appears when Show domain-based accounts is on in Settings → Accounts), or group those customers into an explicit account following Step 3.

Threads submitted via "New request" aren't triggering our workflows.

Portal requests arrive on the API support channel, not Email, so a Step 6 workflow filtered to Support channel equals Email never sees them.

Try this: Open the workflow, find the Support channel equals condition, add API to it, then submit a fresh request from the inbox and check the run log.