Store docs & FAQs: a help center that writes itself (with approval)

Store docs and FAQs are your help center: structured articles under **Docs**, quick question-and-answer pairs under **FAQs**, and one AI agent whose entire job is keeping both current. Docs publish to a searchable help center at `/<storeSlug>/docs`; FAQs render on the storefront FAQ page and feed the chatbot's answers. Together they deflect the same fifty tickets you are tired of answering. ## Build the help center with docs 1. Open **Docs** in the dashboard. Start with **categories** — Shipping, Returns, Orders, Products — because categories are how shoppers navigate a help center. 2. Click **New doc**, pick a category, and write the article with a clear title ("Where is my order?") and a direct answer in the first paragraph. 3. Save, and the article is live in your help center at `/<storeSlug>/docs`, searchable by customers. 4. Keep articles short and one-topic. A reader in a hurry scans; they do not read. Link between related docs instead of cramming everything into one page. ## Add FAQ entries 1. Open **FAQs** → **New FAQ**. Write the question exactly as customers ask it and the answer in two or three sentences. 2. Order the list by what customers actually ask — put the top five first. 3. Save. The entries render on the storefront **FAQ page** automatically, and they do something quieter and more important: they feed the **chatbot**. When a shopper asks the chatbot "do you ship on weekends?", the answers come from your FAQs, docs, and products — so a saved FAQ is also a chatbot answer. ## Let the Docs & FAQ Manager draft for you The **Docs & FAQ Manager** agent (part of the AI Agent Workforce) reads real customer questions — chat conversations, support tickets, repeated chatbot questions — and drafts new FAQ entries or doc updates where it spots a gap: a question asked three times with no published answer becomes a draft FAQ the next shift. The rule is strict and worth repeating: **drafts never auto-publish.** Everything the agent writes arrives as a proposal with the drafted text, and it goes live only when you approve it. Review the drafts, fix the tone if needed, approve — and the help center grows from actual customer behavior instead of guesswork. ## What happens next - Watch the docs **feedback** signal: each help center article can collect "was this helpful?" feedback from readers, which flags the pages that need rewriting. - Reuse real language. If customers say "track my parcel," title the doc "Track my parcel," not "Order Fulfillment Status Inquiry." - When a support conversation ends with a good explanation, copy it into a FAQ before you forget. That is the cheapest content you will ever produce. ## Tips - Ten honest FAQs beat forty generic ones. Start with the questions you answered by hand this week. - Docs are also SEO surface area: "returns policy" pages rank, and the SEO Suite's on-page optimizer lets you set titles and meta descriptions for help content like any other page. - If an FAQ keeps being answered wrong by the chatbot, the fix is usually a clearer FAQ entry — the chatbot's answers are only as good as the content behind them. ## FAQ **Do doc and FAQ changes go live instantly?** Yes. Saving a doc or FAQ updates the storefront help center and the chatbot's answer pool immediately — no publish step, no cache to clear. **Where do customers find the help center?** At `/<storeSlug>/docs`, and themes place a help link in the footer; the help-center widget can also surface it from the storefront chat experience. **Can the agent edit existing articles, or only draft new ones?** It proposes edits too — outdated shipping times, changed return windows — always as before/after proposals you approve or reject. Nothing changes on the storefront without your click.