Product Knowledge Q&A Assistant
Your clone answers product questions from your own documents, names the source, and says so when the answer isn't there.
Build an org-level knowledge base from your product docs, spec sheets, FAQs, installation guides and policies. Your clone searches it first for every question, answers briefly and accurately, names the source document, quotes specs exactly, never guesses, and routes unanswered questions to a person. It works in web chat, Slack or Teams, email, phone and live meetings.
At a glance
- Difficulty
- Beginner
- Setup time
- 30–60 min (plus time to gather documents)
- Built for
- Sales, Support, Customer Success, Marketing
Version 1.0.0 · updated 2026-10-22
Overview
Sales reps, support agents and partners lose time hunting through spec sheets and old PDFs, and answers drift between people. A clone grounded in your own documents gives fast, consistent, sourced answers and knows when to hand off.
Product knowledge lives in spec sheets, PDFs, FAQs and the heads of a few experts. Reps and agents interrupt those experts, answers differ from person to person, and customers wait.
With this use case you build one org-level knowledge base (so every clone in your organization can use it) and give your clone a small skill, Product Q&A. From then on, anyone can ask the clone a product question in web chat, Slack or Teams, email, by phone, or live in a meeting (via Join Meeting).
| Benefit | What it looks like |
|---|---|
| Fast answers | Specs, compatibility, install steps and policy answers in seconds |
| Consistent answers | Everyone gets the same answer from the same documents |
| Sourced answers | Every answer names the document it came from |
| Honest gaps | Missing information is flagged, never invented |
| Safe by default | Internal-only pricing and margins stay away from external audiences |
| Fewer interruptions | Experts only see the questions the documents can't answer |
Who it’s for
- Sales: reps who need accurate specs and compatibility answers during calls and quotes.
- Support: agents answering installation, warranty and troubleshooting questions.
- Customer Success: CSMs answering "does it support...?" questions without waiting.
- Marketing: teams who want consistent product facts in copy and partner enablement.
- Partners and customers: if you choose to expose the clone to them (see audience rules).
How it works
┌───────────────────────────────────────────────────────────────┐
│ Your documents: specs, FAQs, guides, warranty, pricing │
│ (Google Drive / OneDrive / uploads) │
└───────────────────────────────┬───────────────────────────────┘
│ upload by folder
▼
┌───────────────────────────────────────────────────────────────┐
│ ORG-LEVEL KNOWLEDGE BASE (folders per product line) │
└───────────────────────────────┬───────────────────────────────┘
│ search_knowledge
Question (chat, Slack/Teams, ▼
email, phone, meeting) ──► "Product Q&A" skill
│
┌──────────────────┼───────────────────┐
▼ ▼ ▼
Found in docs Partly found Not in docs
short answer + answer what is say so, don't guess,
source name sourced, flag gap offer {ESCALATION_CONTACT}Setup, step by step
- Gather documents (the long part)Product docs, spec sheets, FAQs, installation guides, warranty and policy docs, and internal pricing sheets. Look early for documents from legacy systems or acquired product lines.
- Scrub and nameRemove confidential material that shouldn't be shared. Use clear file names and group files by product line or category. Get text versions of scanned PDFs.
- Hand the instructions to your cloneIt checks what is connected and asks for the placeholders.
- Create the org-level knowledge baseThe clone can do this with the platform tool, or you can use the Knowledge page. Make folders per product line or category. Keep internal-only material in its own clearly named folder (for example "INTERNAL ONLY - Pricing").
- UploadUpload files in the Knowledge page, or ask the clone to pull files from Google Drive (Google Drive Core Operator) or OneDrive (Microsoft OneDrive) after you connect them.
- Save the Product Q&A skillThe clone saves it, or gives you a copy-paste block.
- Run the test planAsk 10 questions from your own documents and score them (see CLONE-INSTRUCTIONS.md section 8).
- Roll out and schedule the monthly refresh
The full walkthrough is in the README. The Clone Instructions file tells your clone exactly what to do.
What you’ll need
Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.
| # | Skill / operator (exact name) | What it's used for | Notes |
|---|---|---|---|
| 1 | Search Knowledge | Search the org-level knowledge base for every question | Required |
| 2 | platform | Create the knowledge base and folders, attach skills, create the scheduled task | Required (or use the Knowledge page) |
| 3 | Product Q&A (custom skill, in CLONE-INSTRUCTIONS.md) | The answering rules | Saved by the clone or pasted by you |
Known gotchas
- Load enough documents first. With too few documents, the clone leans on general platform knowledge and talks about the platform instead of your products. Upload the full set before you test.
- Find legacy and acquired-product documents early. Documents from legacy systems or acquired product lines are often the blocker. Ask for them in week one.
- Scrub confidential material before using with customers. Remove margins, internal notes and unreleased roadmap, or keep them in an internal-only folder with
{AUDIENCE_RULES}. - Use clear file names and folders. "ModelX-Spec-Sheet-2026.pdf" beats "final_v3.pdf".
- Scanned PDFs may need text versions. If a PDF is an image, the clone may not read it. Provide a text or OCR version.
- Keep documents current. Old documents give old answers. Use the monthly refresh and remove superseded files.
- For best accuracy, say "check your knowledge first." It is slower but more accurate.
Questions
Can customers use it directly?
Yes, if you set {AUDIENCERULES} and scrub the documents. Test with the external audience rules before opening it up.
Does it learn from conversations?
No. It answers from the documents. Add or update documents to change answers.
Why is internal pricing in the knowledge base at all?
So internal staff get fast answers. The clone is told not to share it externally, but the safest approach for sensitive data is a separate internal-only clone or folder access.
Do I need a CRM?
No.
Can it answer by phone?
Yes, wherever the clone can talk or write, it uses the same skill.