Copilot prompt for a knowledge base

Draft a customer-facing knowledge-base article that resolves [CUSTOMER PROBLEM] in [PRODUCT OR SERVICE]. Use only these verified sources and product facts: [SOURCE MATERIAL]. The intended reader is [AUDIENCE AND SKILL LEVEL], using [PLATFORM, PLAN, OR ENVIRONMENT]. The support team’s approved escalation route is [ESCALATION PATH].

Start with a plain-language title phrased as the customer’s goal or problem. Then write: a 40-60 word answer or outcome summary; “Before you start” with only necessary access, plan, permission, device, or backup requirements; numbered resolution steps; expected result; common errors or edge cases; and “Contact support” criteria.

Each action must name the exact screen, setting, menu, or command where the source material provides it. Put a verification point after consequential steps so customers can tell whether it worked. Explain unfamiliar terms once, at the point they appear. If the issue could affect data, billing, access, privacy, security, or irreversible changes, state the precaution and stop at the approved handoff boundary.

Do not claim a feature exists, invent navigation labels, create troubleshooting paths without source support, promise response times, or blame the customer. Use empathetic but compact language: acknowledge the interruption once, then move directly to the solution.

Return the article in publish-ready Markdown, followed by an internal “source gaps and review notes” list that will not be published. Before answering, check that every instruction is supported by the supplied material and that escalation triggers cover failed steps and account-specific cases. Ask up to 3 clarifying questions only if a required input is missing.

Write a troubleshooting article for [ISSUE] in [PRODUCT] using these verified diagnostics: [DIAGNOSTIC SOURCE]. The reader is [AUDIENCE], using [ENVIRONMENT]. Begin with symptoms and prerequisites, then provide a decision table: symptom, likely supported cause, diagnostic step, resolution, and escalation trigger. Follow with numbered instructions for each resolution and an expected result. Clearly separate customer-safe actions from actions requiring support. Do not infer causes, invent logs or settings, or ask customers to expose passwords, tokens, or sensitive personal data. Check that every branch has a supported next step and a safe exit to [ESCALATION PATH].

Create a getting-started article for [FEATURE OR PRODUCT] for [NEW USER TYPE]. Use these verified setup requirements and steps: [SETUP DOCUMENTATION]. Return a title, what the reader will accomplish, prerequisites, a numbered setup sequence, a first-success check, and three next actions after setup. State ownership or permission requirements before the customer reaches a blocked step. Include only approved links and terminology from the source. Do not describe optional features as required or invent default settings. Before answering, check that the steps are in dependency order and flag any onboarding gap that needs product-team confirmation.

Draft a knowledge-base article explaining [POLICY TOPIC] for [CUSTOMER AUDIENCE]. Use this approved policy text and operational guidance: [APPROVED POLICY]. Explain what the policy covers, who it applies to, the customer actions required, relevant dates or exceptions, and how to get account-specific help through [ESCALATION PATH]. Use plain language, but preserve defined terms when their meaning matters. Do not reinterpret legal terms, promise exceptions, or add enforcement consequences not in the policy. Return publish-ready Markdown plus a list of unclear statements for policy-owner review. Check every claim against the supplied policy.