Automate help centre articles

Overview

Support teams need a fast way to turn product docs into polished Help Centre articles that match their existing style. Perplexity Spaces can be configured with your Help Centre and product specs so you can generate, refine, and ship support content in a few prompts.

Your Search

Set up a Space that’s trained on your Help Centre and fed with your latest product docs:

• Connect your Help Centre as a source so Perplexity learns your tone, structure, and formatting patterns.
• Upload or connect your PRD (product requirements doc) via Connectors (e.g. Google Drive, Notion, Confluence) or file upload.

Set up your space with custom instructions, like:

You are a technical content writer creating help centre articles based on internal product documentation, specs, and company knowledge. Always refer to the links for references to match the tone and style of your company’s existing help centre articles. When given product materials, your job is to: 1. Extract the most important, user-facing information. 2. Organise it into a structured article with clear headings, bullet points, and simple language. 3. Anticipate common user questions and provide helpful context. 4. Write for clarity—assume the reader is not technical unless told otherwise. 5. Use examples, visuals (if suggested), or step-by-step instructions when helpful. Output should be clean, polished, and ready to publish in a help centre platform like Zendesk, Intercom, or Help Scout.

You can then start using the Space to automate your docs:

Write a help centre article about our new product, SlicedBread, based on the attached PRD.

Perplexity's Answer

Perplexity generates a full Help Centre article that:

• Matches your existing voice and structure, because it’s grounded in your current Help Centre content.
• Accurately reflects the PRD, pulling in feature behaviour, edge cases, and limitations from your source docs.
• Comes pre-formatted for publishing, with sections like overview, “How to use,” screenshots placeholders, and FAQs.

You see an answer panel with:

• A draft article ready to copy into your Help Centre or CMS.
• Inline references back to the PRD and relevant existing Help Centre pages, so your team can quickly verify details.
• Suggestions for related articles (e.g., “See also: Workspace permissions,” “Troubleshooting login issues”) to help you expand coverage.

You can keep refining the same draft in the Space: ask for a shorter version for in-app tooltips, or a more technical variant for admins, all grounded in the same underlying docs.

Your Space

https://www.perplexity.ai/collections/help-centre-article-generator-bRY45M7dRXOYr8blqgfHrA

Tip

In your first prompt, be explicit about audience (end users vs admins) and format (FAQ, step-by-step guide, release-note-style).

Use follow-ups to generate variants:

• Short version for in-product help.
• Longer, SEO-friendly version for public docs.