A BETTER WAY TO SHARE THE WORK
Give customers a clear answer before they need to ask again
A useful FAQ answers the question your customer has—not the question your company wishes they had.
New to creating with an agent? The request will guide it through the task. Bring your notes; you don’t need to write HTML.
How do I create a customer FAQ with my agent?
Give your agent the questions customers actually ask and the current approved policies that answer them. Ask for a short answer first, followed by exceptions and the next step. Keep unanswered questions visible in your review draft. Verify every policy and help link before sharing a readable HTML reference.
01 / SEE THE DIFFERENCE
Three answers from three approved policies
Fictional Cedar Workshops reference. The source bundle includes three policies and an unanswered refund question.
R1: one date change, requested at least 48 hours ahead, subject to space and confirmation. R2: recording available for 14 days after the session through the existing attendee portal. R3: invoice corrections go to the billing help route; do not send payment details to this page. Refund policy not supplied; the support policy owner must resolve it before publication.
- Change my date
- Request one change at least 48 hours before the session. A place on the new date still needs confirmation.
- Find my recording
- Use the existing attendee portal within 14 days after the session.
- Correct an invoice
- Use the billing help route. Do not send payment details to this page.
- Refund question
- No approved answer is available in this draft. The support policy owner must resolve it before publication.
Open a complete fictional HTML example, with its source notes →
Create my customer FAQ guide02 / MAKE IT YOURSELF
Start with the evidence. Shape the page around the reader.
Group by the customer's situation
Use the words customers use: changing a booking, finding a recording, correcting an invoice. A small set of practical groups is more useful than reproducing the company organization chart. Remove duplicate questions only after confirming they really have the same answer.
Put the answer before the explanation
Ask for one direct opening sentence, then the condition that changes it and the action to take. Keep a material exception alongside the answer. Do not make a customer expand several sections to discover that a policy does not apply to their booking.
Keep policy gaps out of confident prose
A missing refund rule is not permission to invent a generous policy or deny a refund. Mark the question as requiring an approved answer in the draft. Resolve it with the policy owner before publishing, or direct readers to the established support channel without pretending the answer is known.
Test the page against real questions
Have a reviewer try to locate each answer without knowing the internal policy names. Verify eligibility, dates, exceptions and the help path. Keep the full knowledge base as the maintained policy source; this page is a scoped reading guide, not a ticket system or automatic answer service.
03 / TRY THIS PROMPT
Copy this into your agent. Add your source material.
Use the conversation where you already did the work, or start one with your notes. Replace the placeholders and supply any missing context; only attach information you are allowed to share with your agent.
Get the ready-to-copy creation request for guided questions, this task, and a draft review before anything is published.
Create a customer FAQ as static HTML using my authorized customer questions and approved policies. Organize by customer situation. Give each question a direct answer, relevant conditions, and an approved next step. Preserve policy dates, exceptions, and scope. Do not invent entitlements, guarantees, prices, support response times, or missing policies. Ask only for missing essentials and flag conflicting or absent answers. Use existing authorized context and my saved artifact style if available. Include only audience-safe source links; no personal ticket details. No scripts, forms, live answers, or ticket submission. Show me the draft and unresolved policy questions. Do not publish or change access without separate explicit approval.
04 / BEFORE YOU SEND
A polished page still needs your judgment.
- Does every answer match a current approved policy and its exceptions?
- Can a customer find answers using their own situation rather than internal terminology?
- Are unanswered questions resolved or accurately routed without invented promises?
- Do help links work for the intended audience, with private ticket data excluded?
When HTML fits
A focused reference for a defined product, service or change where customers need a few verified answers.
When another format fits better
Keep large searchable knowledge bases, ticket routing and policy management in their established systems. This static page does not collect requests or learn from new tickets.
FROM DRAFT TO A LINK
Make it clear. Make it yours. Then share it.
Keep creating and revising in the agent you already use. With a compatible connection, share/artifacts publishes the reviewed HTML so you do not have to rebuild it in another editor. Ask your agent to use your saved artifact style for headings, color, and tone; review the result before sending it.
Choose who should be able to open the page and verify the returned link. For corrections to the same deliverable, update the existing artifact without changing its link. Publish a separate artifact when the old edition needs to remain available.
These are static pages, not live apps: no scripts, forms, or automatic data refresh. Source collection and scheduling depend on your agent and its available tools, not on share/artifacts.
Make this with my agentQuestions before you start
Should the FAQ include every question?
No. Start with recurring questions for this audience and scope. Link to maintained documentation for deeper topics. A long miscellaneous list can make the frequent answers harder to find.
Can the agent write an answer when the policy is missing?
It can identify what is missing and draft a question for the policy owner. It should not fill that gap with a plausible policy. Review unresolved answers before sharing.
How do I keep the FAQ current?
Name an owner and a review date. Recheck it when policies change, then approve a revised version. Updating the source policy does not automatically update this page.