Write for Ask

Members ask in chat the way they talk. NotionFlare answers only from pages you synced — so write pages that match operational questions you are tired of answering by hand.

This guide is for your Knowledge Base: training shops, brand support, community / membership ops, and small internal teams. Official product docs do not answer inside your groups.

Loading diagram…

What members usually ask

Cover these explicitly (titles can be the question):

• What’s the refund policy?
• When is the next class / session / kickoff?
• What are the group rules?
• How do I get help / who do I contact for billing?
• Do you ship to …? / What’s the return window?
• What’s the homework / checklist for this week?

Prefer operating facts over generic “knowledge essays” — the former is why small teams pay for Ask; the latter is easy for AI to replace elsewhere.

Writing rules

1. One page, one job — Do not bury three policies in one wall of text.
2. Title / H2 as the question — Prefer “When is the next cohort?” over “Schedule notes”.
3. Fact in the first sentence — Date, price, link, or yes/no first; detail after.
4. Body over cover images — Ask prefers body text; image text is optional and noisier.
5. Short lists over wide tables — Steps ordered; parallel points unordered; FAQs as toggles or short bullets.
6. Stable Slug — After first sync the public URL slug freezes; plan names before publishing.

Status and which group sees what

• Inquiry / lead chats — Status public + group corpus Public (works on Free).
• Paid members / staff — Status private or draft + corpus Private or Private + Public (Pro+).
• Never expect private pages in Free IM groups — corpus is hard-locked to Public.

Details: Private vs public.

After you edit

1. Wait for sync (or Sync now).
2. Self-test in Try /ask — confirm Sources cite the page you meant.
3. If answers stay stale, Rebuild under Ask → Knowledge.

Related

• How /ask cites sources
• Knowledge Base
• Use cases
• Getting started