Gorgias Help Center Explained (Knowledge Base for Ecommerce)

What the Gorgias Help Center actually is

The Help Center is a hosted knowledge-base website that lives on its own subdomain and sits alongside your Gorgias helpdesk. It's built from three nested pieces: articles (the individual answers), categories (the shelves those articles sit on, like "Shipping" or "Returns & Exchanges"), and optional subcategories for deeper structure. Customers land on it, search, and self-serve — and, importantly, the same articles can feed your on-site chat and AI answers rather than living in a silo.

Per Gorgias's Help Center 101 documentation, the Help Center is available on all Helpdesk plans, with one catch worth flagging up front: you cannot create a Help Center during the 7-day free trial — you have to wait until the trial window ends. Management is also permission-gated: only the account Owner, Admins, and Leads can create and configure a Help Center; everyone else can view published articles but not touch the setup.

If you're still getting your bearings on the wider platform, our what is Gorgias overview sets the Help Center in context alongside the inbox, rules, and automation.

Creating a Help Center, articles, and categories

You build the Help Center through a short setup wizard. Per the Create a Help Center, Article, or Category docs, the path is:

1. Go to the Settings icon (bottom-left) → Channels → Help Center → Manage tab → Create help center.
2. In Step 1 (the basics), name it, pick a subdomain, and choose a default language (you can add more languages now or later).
3. Connect an email address (so replies from the Help Center flow into tickets) and, if you run one, a connected ecommerce store.
4. Populate it. You have four ways in: manual entry, AI-generated suggestions built from your past ticket data, templates (Gorgias ships six general ones, including product-FAQ, shipping-and-returns, and brand-FAQ starters), or imports.

For imports specifically, you can upload a formatted CSV or pull directly from Zendesk, HelpDocs, Re:amaze, or Intercom — handy if you're migrating an existing knowledge base rather than starting cold.

Articles carry a visibility setting that matters for SEO. A Public article is searchable inside the Help Center and may surface in Google results; an Unlisted article is reachable only by its direct URL and is excluded from search — useful for policy pages you want to link but not advertise. Each article is also assigned a language and, optionally, a category.

Categories and subcategories give the site its shape. You create a category with a title, a URL slug, a description, and an optional grid image; a subcategory is just a category with a parent selected from a dropdown. Gorgias added multi-level subcategory support so brands with deep catalogs can nest "Returns → International Returns," for instance, rather than flattening everything onto one shelf.

The screenshot above is the admin surface on a fresh trial before any Help Center exists — the About/Manage entry point and a storefront preview, rather than a populated site. Once you complete the wizard, this is where your articles, categories, and appearance settings live.

Theming: make it look like your store, not like Gorgias

A knowledge base that looks bolted-on erodes trust, so the Appearance controls are worth spending time on. Per the Customize Help Center appearance docs, you can set:

• Branding — a brand name, a standard logo, a white logo (for dark backgrounds), and a favicon; the recommended logo size is roughly 180×32px, JPG or PNG.
• Theme — a light or dark mode.
• Typography — a customizable primary font; note that swapping in a custom font changes the pages' overall design.
• Accent color — an adjustable icon and hover color to match your brand palette.
• Banner — a title, an optional background image, and a toggle to show or hide the search bar.
• Category images — grid thumbnails at an optimal 318×160px (4:2).

The one structural choice that shapes the whole experience is layout. The One-page layout renders articles as inline accordions — titles that expand in place without navigating away (capped at a 16px font, and disabled once you use multiple category levels). The Card layout shows each article as a titled box with an excerpt that opens on its own page. Card layout tends to suit larger knowledge bases; one-page suits a tight FAQ.

One honest nuance: the visual appearance editor stays no-code, but deeper styling lives in the Help Center’s Extra HTML section, where you can inject custom CSS and HTML directly (Gorgias docs) — a code-level step rather than point-and-click.

Multilingual: how far the native system goes

If you sell across borders, the Help Center supports multiple languages — with an important nuance about how it translates. Gorgias natively covers roughly 15 languages (English, French, Spanish, German, Italian, Dutch, and other major markets). Detection is automatic: the Help Center reads a visitor's browser language and, if you've published a version in that language, serves it; if there's no match, it falls back to the default language you set in Step 1.

The catch is that translation is manual and per-article. As the eesel multilingual guide documents, there's no built-in machine translation — after you enable a language in settings, you (or your team) add the translated text for each article, chat campaign, and flow yourself. For beyond-15-language coverage or automated translation, brands typically bolt on a third-party app (Lingpad and similar), which is an added subscription. So multilingual is genuinely supported, but it's localization work you own, not a one-click toggle.

Feeding self-service and AI grounding

This is where the Help Center earns its keep for ecommerce. Two things read from it:

1. On-site self-service and chat. Embedded in your store, the Help Center lets shoppers search answers before they ever message you, and it powers article recommendations inside Gorgias Chat.
2. AI grounding. In the setup wizard's Step 4 (turn on AI Agent features), you can connect the Help Center to the AI Agent's knowledge base, so its answers are grounded in your published articles rather than guessed. That grounding is what turns a static FAQ into an automated first line of support, often wired together with Gorgias Flows for structured resolutions.

Embedding and AI depth are platform-dependent, and this is where the honesty matters. On Shopify, you get the full set — flows, article recommendations, and order management (letting the agent look up and act on orders). On BigCommerce or Magento 2, you get flows only. On any other website, embedding is manual and the richer commerce actions aren't available. Order management specifically also requires an AI Agent subscription, so it's an add-on, not part of the base helpdesk.

The honest limits — and where an AI layer picks up

The Gorgias Help Center is a solid, well-integrated knowledge base: it's on every plan, it themes cleanly, it imports from the major platforms, and it can feed AI grounding out of the box. Credit where due. But a knowledge base is fundamentally a library — it stores answers; it doesn't deliver the resolution. A shopper still has to search, read, and correctly self-diagnose. If they don't find it, or the article is close-but-not-exact, they open a ticket anyway.

It's also honest to name the gated bits: you can't create one during the trial, multilingual is manual translation work, deeper CSS styling is a code-level Extra-HTML step rather than point-and-click, and the highest-value AI actions — order management, the richer flows — are Shopify-first and require the AI Agent add-on. The Help Center is the substrate; the reasoning that turns it into resolutions is a separate, often paid, capability.

This is the seam where an AI agent layer fits. The category of AI agents for customer service exists precisely to read a knowledge base and act on it — understanding the shopper's actual question, retrieving the right article, and resolving rather than linking. Macha is one such layer, with a live Gorgias connector: it runs on top of the Gorgias you already use — it does not replace your helpdesk or its Help Center. Point Macha at your published articles and it grounds AI answers in that same content, so instead of returning a search result it returns the resolved answer, and where a question needs live data — "where's order #4471?" — a custom tool lets the agent call your store's API directly rather than sending the shopper to hunt. Because Macha's connector is platform-agnostic on the Gorgias side, that grounding works whether your store is Shopify, BigCommerce, or something bespoke. See the Macha–Gorgias integration for how the connection is wired, and note that credits are consumed per AI action, not per resolution — the pricing page has the breakdown.

The clean division of labour: keep the Gorgias Help Center as your canonical, branded knowledge base, and layer an agent on top for the part a static site can't do — actually reading the question and resolving it.

FAQ

Where do I set up the Gorgias Help Center? Go to Settings → Channels → Help Center → Manage tab → Create help center. The wizard walks you through naming it, choosing a subdomain and default language, connecting an email and (optionally) a store, and populating it via manual entry, AI suggestions, templates, or imports.

Is the Help Center free / on every plan? It's available on all Helpdesk plans. The one restriction: you cannot create a Help Center during the 7-day free trial — you have to wait until the trial ends. AI Agent features and order management require an AI Agent subscription.

How does multilingual work? Gorgias natively supports about 15 languages with automatic browser-language detection and a default-language fallback. Translation is manual and per-article — there's no built-in machine translation, so you add translated text yourself, or use a third-party app for automation and broader language coverage.

Can I customize how it looks? Yes — brand name, logos, favicon, light/dark theme, a custom primary font, an accent color, a banner, and a choice between one-page (accordion) and card layouts. The visual editor is intentionally no-code, but you can inject custom CSS and HTML via the Extra HTML section for deeper brand matching — a code-level step.

Can I add AI to my Gorgias Help Center without replacing Gorgias? Yes. An AI agent layer like Macha connects to Gorgias as a live connector and grounds its answers in your published Help Center articles, running on top of your existing helpdesk rather than replacing it — while Gorgias stays the system of record for your knowledge base and tickets.

Ready to turn your Help Center from a library into resolutions? Start a free trial of Macha and connect it to your Gorgias in minutes.