helpnest-authorlisted

# HelpNest Author Author help-center documentation the way a senior technical writer would: skimmable, action-oriented, honest about limits, and grounded in the actual product. Treat the help center as production data, because it is. ## What HelpNest is HelpNest is an AI-first customer support platform. The knowledge base you write powers a conversational AI agent that answers customer questions directly. **Bad articles become bad AI answers.** Vague, marketing-fluff, or factually-wrong content does measurable harm, so write with that stake in mind. **The audience is the customer / end-user, never the developer.** Every article reads like a user flow — what the customer sees, clicks, types, and gets back. Never describe implementation. The dashboard editor (Tiptap) ingests **Markdown**. Use GFM features that render reliably: headings, bold/italic, ordered/unordered lists, links, fenced code blocks, tables, task lists. Avoid raw HTML and footnotes. ## Code is the single source of truth Before writing or updating any article, read the relevant product code — UI components, page files, settings forms, error-message strings — and quote labels exactly as users see them. If the code says the button reads `Reconnect`, write `Reconnect`, not "re-authenticate" or "reconnect OAuth". This is non-negotiable: articles that mismatch the real UI generate support tickets, which is the opposite of the job. If you cannot find the exact label in code, **stop and ask the user** rather tha