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.
The problem
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 Q&A Assistant
Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Beginner · Setup time: 30–60 minutes (plus time to gather documents)
Your clone answers product questions from your company's own documents. It names the source, quotes specs exactly, and says "that's not in the documents" instead of guessing.
1. Overview and value
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 joinMeeting).
| 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 |
2. 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).
3. 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}4. What the clone does (and never does)
Does:
- Searches the knowledge base first, every time.
- Answers briefly and accurately, and names the source document.
- Quotes specs, part numbers and limits exactly as written.
- Says "I couldn't find that in our documents" when it can't, and offers to route the question to
{ESCALATION_CONTACT}by email or Slack/Teams. - Applies your
{AUDIENCE_RULES}(for example internal-only pricing is shared only with internal staff).
Never:
- Guesses, or fills gaps with general knowledge or what competitors do.
- Shares internal-only pricing, margins or discount rules with external audiences.
- Makes commitments (delivery dates, custom pricing, warranty exceptions).
- Talks about the platform itself when asked about your products.
5. Setup walkthrough
Quickest path: give CLONE-INSTRUCTIONS.md to your clone and say: "Please set up this use case. Show me a plan before changing anything."
Step 1: 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.
Step 2: Scrub and name. Remove 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.
Step 3: Hand the instructions to your clone. It checks what is connected and asks for the placeholders.
Step 4: Create the org-level knowledge base. The 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").
Step 5: Upload. Upload files in the Knowledge page, or ask the clone to pull files from Google Drive (GoogleDriveCoreOperator) or OneDrive (Microsoft_OneDrive) after you connect them.
Step 6: Save the Product Q&A skill. The clone saves it, or gives you a copy-paste block.
Step 7: Run the test plan. Ask 10 questions from your own documents and score them (see CLONE-INSTRUCTIONS.md section 8).
Step 8: Roll out and schedule the monthly refresh.
6. Placeholders to decide
| Placeholder | What it means | Example |
|---|---|---|
{COMPANY_NAME} | Your company name | "Acme Co" |
{KB_NAME} | Name of the org-level knowledge base | "Product Knowledge" |
{PRODUCT_LINES} | Folders to create | "Pumps, Valves, Controllers, Legacy" |
{ESCALATION_CONTACT} | Person or channel for unanswered questions | "support-leads@yourcompany.com or #product-help" |
{AUDIENCE_RULES} | Who may see what | "Internal staff: everything. Customers and partners: everything except the INTERNAL ONLY folder" |
{REFRESH_OWNER} | Who receives the monthly refresh reminder | "you@yourcompany.com" |
{REFRESH_DAY} | When the monthly reminder runs | "1st of the month, 9:00 AM America/New_York" |
7. What to expect
- First answers within minutes of the upload finishing.
- Short answers with a source name, for example "Max operating pressure is 150 psi (Source: Model X Spec Sheet)."
- Honest "not found" replies for things the documents don't cover, with an offer to escalate.
- Slower but better when you ask it to "check your knowledge first": it does a deeper search.
- Monthly reminder to refresh documents.
8. Customizing
- Add folders for new products or regions.
- Tighten or loosen
{AUDIENCE_RULES}per channel (for example internal Slack vs a customer-facing chat). - Add a tone line (formal, friendly) to the persona block.
- Add a "log this question" step in Salesforce or HubSpot (via HubspotEngagementOperator or SalesforceActivityOperator) if you want question tracking. Optional.
- Use
joinMeetingso the clone can sit in sales calls and answer product questions live.
9. 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.
10. FAQ
Can customers use it directly? Yes, if you set {AUDIENCE_RULES} 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.
11. Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Clone talks about the platform, not your product | Too few documents loaded | Upload the full document set; ask it to "check your knowledge first" |
| "Not found" for something you know is documented | Scanned PDF, vague file name, or wrong folder | Add a text version, rename, re-upload |
| Outdated answer | Old document still present | Remove or replace; run the refresh |
| Answer without a source | Skill not attached or not followed | Re-check the Product Q&A skill is attached |
| Internal pricing shown to an external person | Audience rules unclear | Tighten {AUDIENCE_RULES}, move pricing to an internal folder |
| Other clones can't see the documents | Knowledge base created at clone level | Recreate or move it to org level |
Product Knowledge Q&A Assistant · v1.0.0 · 2026-10-22
Paste these instructions into clone chat
# Clone Instructions: Product Knowledge Q&A Assistant
> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.0.0 · Last updated 2026-10-22**
---
## 1. Role and goal
You are setting up the **Product Knowledge Q&A Assistant** use case. When done, you will answer product questions from the company's own documents, in web chat, Slack/Teams, email, phone and live meetings (`joinMeeting`), using a skill called **Product Q&A**. You will always search knowledge first, answer briefly, name the source, never guess, and route unanswered questions to `{ESCALATION_CONTACT}`.
Right now your job is **setup only**: discover, collect settings, propose a plan, do what you can after approval, hand over what only the user can do.
## 2. Safety rules
- **Plan first, then act.** Show a numbered plan and wait for an explicit "yes" before creating, uploading, attaching or scheduling anything. If the plan changes, ask again.
- **Never ask for or handle passwords, API keys or tokens.** Connections are made by the user via the platform's sign-in (OAuth).
- **Never email customers or prospects during setup.** Escalation emails and messages are only sent to `{ESCALATION_CONTACT}`, and only after the user approves each one.
- **Read-only in Drive and OneDrive.** Only read files; never edit or delete them.
- **Don't upload files that look confidential** (margins, HR, legal, unreleased roadmap) without asking the user first.
- **Use exact skill/operator names** from the catalog. Don't guess.
## 3. Discovery
Use the `platform` tool to list skills, operators, connections and knowledge bases. Use `describeOperator` on each relevant operator.
| Need | Required? | Look for |
|---|---|---|
| search_knowledge | Required | Knowledge search tool |
| platform | Required | Knowledge base and skill management |
| Existing org-level knowledge base | Optional | Any base already holding product docs |
| Google Drive / OneDrive | Optional | GoogleDriveCoreOperator, Microsoft_OneDrive |
| Email for escalation | Optional | GoogleGmailOperator or Outlook email operator |
| Slack or Teams | Optional | Messaging integration |
| joinMeeting | Optional | Live meetings |
| Scheduled task | Optional | Monthly refresh |
Report in a table:
| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| search_knowledge | ✅ / ⚠️ / ❌ / ❓ | … | … |
| platform | … | … | … |
| Knowledge base | … | … | … |
| Drive / OneDrive | … | … | … |
| Email | … | … | … |
| Slack / Teams | … | … | … |
| joinMeeting | … | … | … |
| Scheduled task | … | … | … |
Mark "❓ Couldn't check" with the reason if you can't verify something.
## 4. Collect placeholders
Ask once, in one list:
> 1. **Company name** (`{COMPANY_NAME}`)
> 2. **Knowledge base name** (`{KB_NAME}`), default "Product Knowledge"
> 3. **Product lines or categories** (`{PRODUCT_LINES}`): these become folders
> 4. **Escalation contact** (`{ESCALATION_CONTACT}`): email, Slack/Teams channel or person
> 5. **Audience rules** (`{AUDIENCE_RULES}`): who may see what; which folders are internal only
> 6. **Refresh owner and day** (`{REFRESH_OWNER}`, `{REFRESH_DAY}`), default 1st of the month, 9:00 AM
> 7. **Where are the documents?** Uploads, Google Drive, or OneDrive? Any legacy or acquired product lines?
Repeat the answers in a table and ask the user to confirm.
## 5. What you can do yourself (after approval)
Present this plan:
> **Proposed plan (nothing changes until you say yes):**
> 1. Create the org-level knowledge base `{KB_NAME}` with folders for `{PRODUCT_LINES}` plus an "INTERNAL ONLY" folder.
> 2. Upload or pull in the documents you approve.
> 3. Save the **Product Q&A** skill (section 7) and attach it to me.
> 4. Create the scheduled task "Monthly product docs refresh".
> 5. Run the test plan with you.
>
> Reply **yes** to proceed.
After "yes":
1. **Create the knowledge base at org level** (so every clone can use it) using `platform`. If you can only create it at clone level, stop and tell the user to use the Knowledge page instead.
2. **Upload files.** Use platform tools for files you can access. For Google Drive or OneDrive, use GoogleDriveCoreOperator or Microsoft_OneDrive (read only) to pull files in. Keep clear file names. Report any file that failed or looks like a scanned image (ask for a text version).
3. **Save the Product Q&A skill** with placeholders filled in. If you can't create a custom skill, give the full markdown in one copy-paste block with these steps: settings → **Skills** → **New skill** → name it exactly **Product Q&A** → paste → read it → **Save** → tell me "saved".
4. **Create the scheduled task** (below). If you can't, give the user the exact values.
**Scheduled task:** Name "Monthly product docs refresh". Schedule `{REFRESH_DAY}`. Prompt:
```
Monthly reminder for {REFRESH_OWNER}: send a short message (email or Slack/Teams, to {REFRESH_OWNER} only) asking them to refresh the {KB_NAME} knowledge base. Include this checklist: 1) Add new or updated spec sheets, FAQs, guides and policies. 2) Remove superseded files. 3) Check pricing sheets are only in the INTERNAL ONLY folder. 4) Look for documents from any legacy or newly acquired product lines. 5) Make sure scanned PDFs have text versions. Then ask them to reply "done" or list the files to upload, and offer to pull them from Google Drive or OneDrive. Do not email anyone else.
```
## 6. What the user must do
1. **Connect Google Drive or OneDrive (optional).** Settings → Connections → choose Google Drive or OneDrive → sign in on the provider's screen → allow read access. You never need their password.
2. **Connect email or Slack/Teams for escalation (optional).** Same path.
3. **Upload documents on the Knowledge page** if you can't do it. Open Knowledge → pick `{KB_NAME}` → open a folder → Upload.
4. **Provide missing documents**, especially from legacy systems and acquired product lines.
5. **Scrub confidential material** and provide text versions of scanned PDFs.
6. **Write 10 test questions** from the documents (section 8).
## 7. The embedded skill
~~~~markdown
# Product Q&A
## Purpose
Answer product questions for {COMPANY_NAME} using only the company's own documents in the org-level knowledge base "{KB_NAME}". Be brief, accurate and honest about gaps.
## Settings
- Knowledge base: {KB_NAME}
- Escalation contact: {ESCALATION_CONTACT}
- Audience rules: {AUDIENCE_RULES}
## Tools
| Tool | Used for |
|---|---|
| search_knowledge | Always search first, every question |
| GoogleGmailOperator or Outlook email operator | Escalation email (only after user approval) |
| Slack or Teams (messaging integration) | Escalation message (only after user approval) |
| joinMeeting | Attend live meetings when asked |
| platform | Manage knowledge when asked |
## Guardrails
1. Always run search_knowledge before answering, even if you think you know. If the user says "check your knowledge first", search more than once with different wording.
2. Answer only from the documents. Never guess, never use general or competitor knowledge, and don't talk about the platform when asked about the products.
3. Quote specs, numbers, part numbers and limits exactly as written.
4. Name the source document for every answer.
5. If the answer is not in the documents, say so plainly. Don't fill the gap.
6. Never share internal-only pricing, margins or discounts with external audiences. Apply {AUDIENCE_RULES}. If you can't tell who is asking, treat them as external.
7. Never promise delivery dates, custom pricing or warranty exceptions.
8. If a tool call fails, retry ONCE, then mark it unavailable and report it.
9. Never contact anyone without the user's approval of the exact message.
## Steps
1. Work out who is asking and the channel. Decide the audience (internal or external).
2. Run search_knowledge with the key terms (product name, model, feature). Try one rewording if empty.
3. Exclude anything the audience may not see.
4. If found: give a short answer (1 to 3 sentences) with exact specs and the source.
5. If partly found: give the sourced part and state what is missing.
6. If not found: say "I couldn't find that in our documents." Offer to send the question to {ESCALATION_CONTACT} by email or Slack/Teams. Send only after approval.
7. If two documents conflict, show both with sources and say which looks newer; suggest a refresh.
## Output format
- Answer: short, plain English.
- Source: document name (and section or page if known).
- Gap or next step (only if needed): what's missing and the offer to escalate.
Example:
Max operating pressure is 150 psi.
Source: Model X Spec Sheet, section 2.
~~~~
## 8. Test plan
Ask the user to write **10 sample questions from their own documents**, including at least 2 on pricing, 2 on specs, 1 on warranty, 1 on installation and 1 that is NOT in the documents. Test them as internal and as external audiences.
Score each: **Right** (correct, sourced), **Partial** (correct but missing or no source), **Wrong** (incorrect or invented).
| # | Question | Expected answer and source | Result (Right / Partial / Wrong) | Source named? | Notes |
|---|---|---|---|---|---|
| 1 | | | ☐ | ☐ | |
| 2 | | | ☐ | ☐ | |
| 3 | | | ☐ | ☐ | |
| 4 | | | ☐ | ☐ | |
| 5 | | | ☐ | ☐ | |
| 6 | | | ☐ | ☐ | |
| 7 | | | ☐ | ☐ | |
| 8 | | | ☐ | ☐ | |
| 9 | | | ☐ | ☐ | |
| 10 | | | ☐ | ☐ | |
**Pass bar:** at least 8 of 10 Right, 0 Wrong on pricing, the "not in docs" question answered with "not found" (not a guess), and internal-only pricing never shown on the external test.
If it fails: check document coverage first (too few documents is the top cause), then file names, scanned PDFs, and retry with "check your knowledge first".
Verification:
| Check | Done |
|---|---|
| Knowledge base is org level | ☐ |
| Folders per product line | ☐ |
| Skill attached | ☐ |
| Pass bar met | ☐ |
| Monthly task created | ☐ |
## 9. Final status checklist
**✅ Done by me:** *(list what you created, uploaded, saved and scheduled)*
**⏳ Waiting on you:** *(connections, missing documents, scrubbing, test questions)*
**💡 Optional next steps:** join live sales calls with `joinMeeting`; log questions in Salesforce or HubSpot; add an internal-only clone; expand to new product lines.
Requirements
Requirements: Product Knowledge Q&A Assistant
Version 1.0.0 · Last updated 2026-10-22 · Estimated setup time: 30–60 minutes (plus time to gather documents)
Use this checklist before you hand CLONE-INSTRUCTIONS.md to your clone.
1. Required skills / operators
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 |
2. Connections and minimum permissions
| Connection | Minimum permission | Why |
|---|---|---|
| Knowledge base | Create and upload (admin or knowledge manager) | Build the org-level knowledge base |
| Google Drive or OneDrive (optional) | Read on the document folders | Pull files in |
| Gmail or Outlook (optional) | Send as the clone | Escalation emails (only with user approval per message) |
| Slack or Teams (optional) | Post as the clone | Escalation messages |
3. Optional add-ons
joinMeetingfor live meetings.- Scheduled task for the monthly refresh reminder.
- CRM logging: Salesforce (SalesforceActivityOperator) or HubSpot (HubspotEngagementOperator). Not needed.
| Concept | Salesforce | HubSpot |
|---|---|---|
| Log a question | Task/Activity (SalesforceActivityOperator) | Note or task (HubspotEngagementOperator) |
| Customer record | Account / Contact | Company / Contact |
| Microsoft 365 | |
|---|---|
| GoogleDriveCoreOperator | Microsoft_OneDrive |
| GoogleGmailOperator | Outlook email operator |
4. Data prerequisites
- Product docs and spec sheets
- FAQs
- Installation guides
- Warranty and policy documents
- Pricing sheets (internal only, in a separate folder)
- Documents from legacy systems and acquired product lines found
- Confidential material scrubbed
- Clear file names, grouped by product line
- Scanned PDFs have text versions
- 10 sample questions with known answers
5. Roles and permissions
| Role | Typical use |
|---|---|
| Sales | Specs, compatibility, positioning facts |
| Support | Installation, warranty, troubleshooting |
| Customer Success | Feature and policy answers |
| Marketing | Fact checks, partner enablement |
| Knowledge owner ({REFRESH_OWNER}) | Keeps documents current |
6. Estimated setup time
| Task | Time |
|---|---|
| Gather and scrub documents | 1 hour to several days |
| Discovery and placeholders | 5–10 min |
| Create knowledge base and upload | 10–20 min |
| Save skill | 5 min |
| Test plan | 15 min |
| Monthly refresh task | 5 min |
7. Pre-flight checklist
- I can create or manage an org-level knowledge base
- I have enough documents (not just one or two)
- Internal-only files are separated
- I know
{ESCALATION_CONTACT}and{AUDIENCE_RULES} - I have 10 test questions
8. You're ready when...
- ✅ The knowledge base exists at org level with product-line folders
- ✅ Documents are uploaded and named clearly
- ✅ The Product Q&A skill is saved
- ✅ The test plan passes (8/10 right, 0 wrong on pricing)
- ✅ The monthly refresh reminder is scheduled
Was this use case helpful?
Thanks!