Knowledge templates
Fill-in-the-blanks markdown files to upload to your clone's Knowledge: brand voice, FAQ, product sheet, escalation policy and meeting notes style.
Team Studio · Studio Max
customer-facing-clone-requirements.mdEverything to decide before a clone talks to customers or the public: audience, integrations, persona, scope, escalation rules, approved knowledge, test plan and pilot.
# Customer-facing clone requirements: [COMPANY NAME] > How to use this template: fill in what you can before you build a clone that talks to customers, residents, patients or the public. Blank answers are fine; work through them with your team or your Clone onboarding contact. When it's done, upload it to that clone's Knowledge (Clone level) so the clone knows its own rules. ## 1. Purpose and audience - Who will talk to this clone? [customers, prospects, residents, visitors...] - Top 5 reasons they contact you today: 1. [ ] 2. [ ] 3. [ ] 4. [ ] 5. [ ] - What does success look like …
Download
v1
knowledge-plan-worksheet.mdPlan what each clone should know before you upload: knowledge levels, a document inventory, which clone gets what, document hygiene, a 15–20 question test set and owners. Fill it in; no Google account needed.
# Knowledge plan worksheet: [COMPANY NAME] > How to use this template: fill it in before you upload documents to Knowledge. It decides what each clone should know, where each document lives, and who can see it. Blank answers are fine; a rough plan beats none. Keep it as a working file; don't upload this worksheet itself. ## How knowledge levels work | Level | Who can use it | Best for | |---|---|---| | Clone | Only that clone | Role-specific documents (e.g. the support clone's FAQ) | | User | Any clone, but only when that user is the one using it | Personal notes, drafts, your own preferenc …
Download
v1
brand-voice.mdHow your company sounds. Upload it so every email, post and image your clones make stays on brand.
# Brand voice and style guide: [COMPANY NAME] > How to use this template: replace everything in [brackets], delete any section that doesn't apply, and keep real examples. Clones learn far more from examples than from adjectives. Upload it to Knowledge at the **Organization** level so every clone uses it, and turn on Runtime access. ## Who we are, in one paragraph [What the company does, for whom, and why it matters. Write it the way you'd say it to a customer.] ## Our voice We sound: [3 traits, e.g. warm, direct, quietly confident] We never sound: [3 opposites, e.g. salesy, stiff, jokey] | …
Download
v1
company-faq.mdThe questions customers ask most, with your approved answers. The single best upload for a support or sales clone.
# Customer FAQ: [COMPANY NAME] > How to use this template: one question per heading, phrased the way a customer would ask it. Keep answers short and factual, and link to the full article where one exists. Clones find "### question" headings very reliably. Review the file every quarter, and add the date you last checked each answer. Last reviewed: [DATE] by [NAME] ## Getting started ### What does [PRODUCT] do? [Two or three sentences, plain English.] ### How do I sign up / get started? [Steps, or a link.] ### Is there a free trial? [Answer.] ## Account and billing ### How do I change my …
Download
v1
product-sheet.mdWhat you sell, who it's for and how it compares, so your clones describe your products accurately.
# Product sheet: [PRODUCT OR SERVICE NAME] > How to use this template: make one file per product or service. Facts only, no hype; clones repeat what's here, so accuracy matters more than polish. Mark anything that must not be shared outside the company as INTERNAL. ## One-line description [What it is and who it's for, in one sentence.] ## The problem it solves [The pain, in the customer's words.] ## Who it's for - Ideal customer: [industry, size, role of the buyer] - Not a fit for: [who we should politely turn away] ## Key features and what they mean for the customer | Feature | What it d …
Download
v1
escalation-policy.mdExactly when your clones should stop and hand off to a person, and how.
# Escalation policy: when a clone hands off to a person > How to use this template: this file tells every clone where its authority ends. Be specific: name thresholds, topics and people. Upload it at the **Organization** level and turn on Runtime access. ## Always hand off to a person when... - The customer asks for a person, a manager or "someone real" - Money above [$ AMOUNT] is involved (refunds, credits, discounts) - Anything legal: contracts, disputes, threats, regulators - A security or privacy concern: a suspected breach, a data deletion request, account access problems - The customer …
Download
v1
meeting-notes-style.mdHow you want meeting recaps written, so every summary from every clone looks the same.
# Meeting notes and recap style > How to use this template: describe the recap you wish you always got. Your clones use this for meeting recaps, call summaries and follow-up emails. Edit the sections and order to match how your team works. ## Recap structure (in this order) 1. **One-line summary**: what the meeting was for, and the outcome 2. **Decisions**: bullet list; write "No decisions" if there were none 3. **Action items**: a table of Owner | Task | Due date 4. **Open questions**: what still needs an answer, and who will get it 5. **Key details**: numbers, dates, names and quotes worth …
Download
v1