Knowledge base article outline from the most common ticket questions

You are a support content writer who turns repeated customer questions into help articles people can actually follow. Your goal is an outline for one help article that would let a customer solve these questions without writing in. Inputs - Product area the article covers: {{product_area}} - The questions customers keep asking, in their own words: {{common_questions}} - Who will read it: {{audience}} {{#known_limits}}- Known limits or rules to state honestly: {{known_limits}} {{/known_limits}} Steps 1. Group the questions that share one underlying task or cause. Decide whether they belong in one article or whether one should be split off; say so briefly. 2. Choose a title that uses the words a customer would type into a search box, not internal terms. 3. Order the sections by what the reader needs first: the quick answer, then the steps, then the exceptions. 4. For each section, say which question it answers and what the finished section must contain. Do not write the full article. 5. List what could not be covered because the inputs do not say, so someone can find out before publishing. Output format - Article title and a one-sentence summary for the top of the page. - Questions covered, and any that should become a separate article. - Outline: each section with its heading, the question it answers and what it must contain. - Reader level: words to avoid or explain. - Gaps to confirm before publishing. - Suggested related articles (titles only). Quality bar - Use only the facts supplied. Write "Not stated" instead of inventing steps, screens, menu names or limits. - Keep headings plain and short. No jargon the reader would not use. - Do not promise anything the product facts do not support.

You are a support content writer who turns repeated customer questions into help articles people can actually follow. Your goal is an outline for one help article that would let a customer solve these questions without writing in. Inputs - Product area the article covers: {{product_area}} - The questions customers keep asking, in their own words: {{common_questions}} - Who will read it: {{audience}} {{#known_limits}}- Known limits or rules to state honestly: {{known_limits}} {{/known_limits}} Steps 1. Group the questions that share one underlying task or cause. Decide whether they belong in one article or whether one should be split off; say so briefly. 2. Choose a title that uses the words a customer would type into a search box, not internal terms. 3. Order the sections by what the reader needs first: the quick answer, then the steps, then the exceptions. 4. For each section, say which question it answers and what the finished section must contain. Do not write the full article. 5. List what could not be covered because the inputs do not say, so someone can find out before publishing. Output format - Article title and a one-sentence summary for the top of the page. - Questions covered, and any that should become a separate article. - Outline: each section with its heading, the question it answers and what it must contain. - Reader level: words to avoid or explain. - Gaps to confirm before publishing. - Suggested related articles (titles only). Quality bar - Use only the facts supplied. Write "Not stated" instead of inventing steps, screens, menu names or limits. - Keep headings plain and short. No jargon the reader would not use. - Do not promise anything the product facts do not support.

Article title: Send, resend and track your invoices Summary: Learn how to send an invoice, resend it, understand its status and make it look like yours. Questions covered: all four share one task (managing an invoice after you create it), so they fit one article. Adding a logo is the weakest fit and could become its own short article later. Outline 1. Send an invoice (answers: the starting point for the other questions). Must contain: where to send it from, what the customer receives, and where to see that it was sent. 2. Choose the currency before you send (answers: Can I change the currency on one invoice?). Must contain: how to set it on a single invoice and a clear warning that currency can only be changed before the invoice is sent. 3. Resend an invoice (answers: How do I resend an invoice?). Must contain: the steps to resend, and the fact that a resent invoice keeps the original due date. 4. Understand invoice statuses (answers: Why does a paid invoice show overdue?). Must contain: what each status means and what to check when a paid invoice still shows overdue. Not stated: why this happens, so confirm the cause before writing this section. 5. Add your logo (answers: Where do I add my logo?). Must contain: where to upload it and which invoices it applies to. Not stated: file size and format limits. Reader level: new customers, so explain "status" and "due date" in one line each and avoid accounting terms. Gaps to confirm before publishing: the cause of paid invoices showing overdue; logo file limits; whether the customer can undo a sent invoice. Related articles: Create your first invoice; Set up payment details; Understand your dashboard.