A client FAQ should answer real questions with information the team has approved. The difficult part is finding that information across briefs, service notes, and later decisions without introducing new promises.
OGAD (Off Grid AI Desktop) can help you search a local project collection and draft questions and answers from its sources. Review each answer against the document behind it, mark gaps, and publish only the version your team approves. The analysis can stay on your computer after setup.
Download OGAD | Desktop releases
What would you like to do with Off Grid AI?
Have a feature or use case you would like us to support? Tell us what you want to do and which device you use.
Write to support@offgridmobileai.co, join our Slack community, or talk to us on Reddit.
For a small agency or service team, the useful result is a clear FAQ that reduces repeated explanation while keeping the offer accurate. It should not become a place where plausible answers fill gaps in the client's documentation.
Which documents should be approved sources?
Use current material that establishes the offer, process, conditions, and limits. Keep draft ideas, old prices, and unapproved sales copy out of the main source collection or label them clearly as unsuitable for factual answers.
Suppose a training company needs an FAQ for a workshop. The approved documents describe the intended audience, prerequisites, format, materials, and how participants prepare.
A useful source map is:
| FAQ topic | Source to verify |
|---|---|
| Who it is for | Approved audience description |
| What participants do | Workshop outline |
| What is included | Current offer document |
| What to prepare | Participant instructions |
| Exceptions or limits | Approved policy or clarification |
If a question concerns something the sources do not establish, leave it for the client to answer. A common question is still an open question until there is a supported response.
What do you need to set up?
Install OGAD, download a local text model, and complete local document indexing setup. The free core Projects workflow supports Mac and Windows, with Linux beta packages in 0.0.54-beta.108.
Use readable TXT, Markdown, DOCX, or text PDFs. Scanned documents need checked text first. Keep dates and approval status visible in filenames and inside the sources.
Start with a small collection that covers one offer. Mixing several products or client services can produce an answer that combines conditions from different offers.
Keep the selected model local for the processing described here. Initial downloads and later publishing need their own connection.
How do you build the source collection?
Create a project for the FAQ's offer and add the approved documents. Wait for indexing before asking the model to find questions or answers.
- Select a downloaded model in Models > Text.
- Open Projects > New project, enter a clear name, and press Enter.
- Open Knowledge & settings > Knowledge base > Add files.
- Add current approved files and leave their retrieval switches enabled.
- Open Chats > New chat inside the project.
The project interface provides the document controls. If you use Pro and want a selected-file collection, leave Include captured memory off and save the setting.
A short project instruction can say that only approved sources establish client facts and that missing answers must remain unresolved.
How do you choose the questions?
Use questions people actually ask when you have them. Supplement them with candidate questions based on the offer, clearly labelled for review. Do not present model-generated questions as measured customer demand.
Ask:
Propose an FAQ question list for someone considering this workshop. Use the supplied customer questions where present and label additional questions as suggestions. For each, identify the source likely to support an answer or mark it as a gap.
Review the list for relevance. A broad question such as “Why is training important?” may add little if the reader is trying to decide whether this particular workshop fits them.
For the example, “Do I need prior facilitation experience?” is useful if the approved audience and prerequisite notes answer it.
How do you draft the answers?
Ask for a direct answer followed by only the detail needed to act. Keep conditions close to the claim and retain source references in the working draft.
Draft answers to these approved questions using the project sources. Start with a direct response. Include relevant conditions and limits. Give the supporting source for each answer. If the sources do not establish an answer, write a question for the client instead of guessing.
Check each source before accepting the answer. A passage about a typical workshop may not apply to a customised client session. The wording should reflect the exact offer the FAQ covers.
Avoid fixed answer lengths. A simple preparation question may need two sentences, while an exception may need a short list.
How do you handle contradictions and gaps?
Keep both sources when they disagree, with their dates and status. Ask the client which instruction is current. Do not automatically choose the newest file if it is still a draft.
Use:
Identify FAQ answers where the sources disagree or leave an important condition unstated. Quote the conflicting passages and draft one clarification question for each. Do not choose an authoritative answer without evidence.
Maintain a separate open-question list. Once the client supplies an approved answer, save it as a dated source and update the FAQ.
Project search retrieves selected passages. A missing result does not prove the entire archive lacks the answer, so inspect likely source documents directly for important questions.
How do you review the FAQ for unsupported promises?
Look for words that imply guarantees, universal suitability, fixed availability, or included services. Compare those statements with the approved offer.
For example, a workshop that provides practice exercises should not become a promise that every participant will achieve a specific business result. A draft answer about scheduling should not invent available dates.
Ask the model for a claim review:
Flag statements that promise an outcome, availability, inclusion, or exception. Name the source supporting each. Mark any statement that is broader than the source.
Then perform the final check yourself. A second model pass can help identify risky wording but does not replace approval.
How should you publish and maintain it?
Copy the reviewed FAQ into your normal website or document editor. Check links, formatting, and the exact offer version. This workflow does not change site metadata, add schema, or publish the answers automatically.
Keep a source map privately so you can update an answer when the offer changes. Review the FAQ when new questions arrive rather than expanding it with generic filler.
| Check | What to confirm |
|---|---|
| Relevance | The question helps the reader make or complete a decision |
| Accuracy | The answer matches an approved source |
| Conditions | Limits are visible near the claim |
| Consistency | Other offer pages do not contradict it |
| Maintenance | Someone knows which source changes affect the answer |
Answer the next repeated client question
Download OGAD and add the current approved documents for one offer. Draft a small FAQ, check every answer, and resolve the gaps before publishing.
The useful result is a reference the client can stand behind, built from facts rather than plausible filler.
Top comments (0)