Customer Briefing Deck
Ask for a short briefing deck before a customer call and get a 6–9 slide PDF built from your knowledge base, past calls, CRM, Linear and email.
The problem
Preparing for a customer call means hunting through transcripts, tickets, the CRM and email, then building slides. Most people skip it and wing the call. Customer Briefing Deck does the gathering and the first version in a few minutes, and a person reviews and presents it.
Customer Briefing Deck
Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Beginner · Setup time: 20–40 minutes
Before a customer call, ask your clone for a short briefing deck. It gathers context from your knowledge base, past call transcripts, the CRM, Linear and email, then builds a 6–9 slide 16:9 deck and emails it to you as a PDF.
1. Overview and value
Customer calls go better when the deck is specific: what changed for them, what we fixed, what we need from them. But building that deck means hunting through transcripts, tickets, the CRM and email, then arranging slides. Most people skip it and wing it.
Customer Briefing Deck does the gathering and the first version. You say: "Make a short briefing deck for my {CUSTOMER} call on {DATE} about {TOPICS}." Your clone:
- searches the knowledge base (product docs, release notes, account notes),
- reads past call transcripts with that customer (
meeting_archive,call_archive, and transcripts in Google Drive or OneDrive from the last 30 days), - pulls the account, open opportunities and open cases from Salesforce or HubSpot,
- checks Linear issues for the account,
- skims recent email threads (Gmail or Outlook),
- builds a short deck (about 6–9 slides, 16:9) with Clone-Research-Report and emails it to you as a PDF (with a text version).
What you get:
| Benefit | What it looks like |
|---|---|
| A prepared call in minutes | A clean 6–9 slide deck in your inbox before the call |
| Specific, not generic | Slides use the customer's own history, open issues and goals |
| Two ready-made shapes | A standard update deck or a "Save the account" deck |
| Less hunting | Transcripts, tickets, CRM and email gathered in one pass |
| You stay in control | You review the deck for unreleased features and internal notes before anyone sees it |
2. Who it's for
- Customer Success Managers preparing check-ins, QBRs and escalation calls.
- Sales reps and account executives preparing update or renewal calls.
- Leadership joining a customer call and needing a quick, accurate brief.
You don't need to be technical. If you can ask a question in chat, you can use it.
3. How it works
You: "Make a short briefing deck for my {CUSTOMER} call
on {DATE} about {TOPICS}."
│
▼
┌───────────────────────────────────────────────────────────────────┐
│ "Customer Briefing Deck" skill │
│ │
│ 1. Confirm: customer, date, topics, variant │
│ (a) Standard update or (b) Save the account │
│ 2. Gather context (skip what isn't connected): │
│ · search_knowledge: docs, release notes, account notes │
│ · meeting_archive + call_archive: past calls │
│ · Drive / OneDrive transcripts (last 30 days, │
│ matched by customer name, {TRANSCRIPTS_FOLDER}) │
│ · CRM: account, open opportunities, open cases │
│ · Linear: issues for the account │
│ · Email: recent threads (Gmail or Outlook) │
│ 3. Write a user_query: context + topic order + slide outline │
│ 4. Call Clone-Research-Report: │
│ format = deck · deck_length = short · email = you │
└───────────────────────────────┬───────────────────────────────────┘
│ a few minutes
▼
┌───────────────────────────────────────────────────────────────────┐
│ Email to you: PDF deck (6–9 slides, 16:9) + text version │
└───────────────────────────────┬───────────────────────────────────┘
│
You review (unreleased features? internal notes?) and presentWhere the context comes from
| Source | What it adds |
|---|---|
search_knowledge | Product docs, release notes, account notes |
meeting_archive, call_archive | What was said on past calls: goals, concerns, commitments |
| Transcripts in Drive or OneDrive | Recent call notes from the last 30 days, matched by customer name |
| CRM (Salesforce or HubSpot) | Account facts, open opportunities or deals, open cases (HubSpot: notes and tasks) |
| Linear | Open and recently closed issues for the account |
| Email (Gmail or Outlook) | Recent threads, open questions, commitments |
Two deck variants
| Variant | Slides (about 6–9) | Use it when |
|---|---|---|
| (a) Standard update deck | Title · Agenda · What's new · How it applies to them · Next steps · Closing | Check-ins, product updates, renewals |
| (b) "Save the account" deck | Title · Situation · Issues and owners · What we've fixed · Success plan with dates · Asks · Next steps · Closing | Escalations, at-risk accounts |
4. What the clone does (and never does)
It does:
- gather context from every source that is connected,
- tell you what it found and what was missing (a one-line source status),
- build the deck through Clone-Research-Report and email it to you,
- offer a one-page 16:9 infographic through Image_Operator when you just need something to screen-share.
It never:
- sends the deck to the customer (it goes to you),
- presents or shares its screen (a person presents),
- invents features, dates, numbers or commitments that are not in your sources,
- includes known internal-only notes or unreleased items on purpose (and flags what it was unsure about),
- changes the CRM or Linear (read-only),
- asks for your password or tokens.
5. Setup walkthrough
The quickest path: download CLONE-INSTRUCTIONS.md and give it to your clone. It checks what is connected, asks for your settings, shows a plan, and sets up what it can after you approve.
Step 1: Check requirements (5 min). Open REQUIREMENTS.md and run the pre-flight checklist. The deck builder is built in. Everything else is optional: the more sources you connect, the better the deck.
Step 2: Hand the instructions to your clone (2 min). Paste or upload CLONE-INSTRUCTIONS.md into a chat with your clone and say: "Please set up this use case for me. Show me a plan before changing anything."
Step 3: Review the discovery table (5 min). The clone reports which sources it can reach and which are missing.
Step 4: Answer the placeholder questions (3 min). See section 6.
Step 5: Approve the plan (2 min). Say "yes" only when it looks right.
Step 6: Do your part (5–15 min). Only you can:
- Connect your own CRM (read access), email, and Drive or OneDrive, and Linear if you use it.
- Tell the clone which folder holds call transcripts.
- Add the deck sender address to your safe senders so the email isn't lost in spam.
Step 7: Save the Customer Briefing Deck skill (5 min). The clone saves it, or gives you the full text to paste.
Step 8: Run the test plan (10 min). Build one deck for a test or low-stakes customer.
Step 9: Optional schedule. Auto-build decks for tomorrow's customer meetings from your calendar.
6. Placeholders to decide
| Placeholder | What it means | Example |
|---|---|---|
{CUSTOMER} | The customer (asked each time) | The customer's name as it appears in the CRM |
{DATE} | Call date (asked each time) | 2026-11-03 |
{TOPICS} | What the call is about, in order (asked each time) | Release update, open issues, renewal plan |
{CRM_CHOICE} | Which CRM you use | Salesforce, HubSpot or none |
{TRANSCRIPTS_FOLDER} | Drive or OneDrive folder with call transcripts | "Meet Recordings" |
{DECK_RECIPIENT} | Where the deck is emailed | My own email address |
{DEFAULT_VARIANT} | Which variant if you don't say | Standard update (a) |
{INTERNAL_ONLY_RULES} | Things never to put on slides | Pricing floors, roadmap items not yet announced |
{SCHEDULE_OPTION} | Optional: auto-build decks for tomorrow's customer meetings | off (default) or on, daily at 4 PM |
7. What to expect
- On demand: you ask, the clone confirms customer, date, topics and variant (one short question if anything is missing), gathers context and requests the deck.
- A few minutes later: an email arrives with the PDF deck (and a text version). Request it ahead of the call, not five minutes before.
- Review time: about 5 minutes. Check names, numbers and anything that looks unreleased or internal.
- Length: short means about 6–9 slides at 16:9, always with a title and closing slide.
Example request and the clone's confirmation:
You: Make a short briefing deck for my {CUSTOMER} call on 2026-11-03
about the Q4 release, their open issues and renewal plans.
Clone: Got it. Variant: Standard update (say "save the account" for the other one).
Gathering context from: knowledge base ✅ · past calls ✅ · CRM ✅ · Linear ✅ · email ✅
Requested the deck. It will arrive at {DECK_RECIPIENT} in a few minutes as a PDF.
Heads up: 1 open case and 2 Linear issues are covered. Please verify the renewal date
on slide 6 (it came from a transcript).8. Customizing
- Variant. Choose (a) Standard update or (b) "Save the account", or ask for your own outline.
- Topic order. Say the order you want: "start with open issues, then what's new."
- Audience. Tell it who is on the call (executive sponsor, technical team) so it adjusts depth.
- Quick option. Ask for a one-page 16:9 infographic via Image_Operator when you just need a visual to screen-share.
- Internal-only rules. Set
{INTERNAL_ONLY_RULES}so certain topics never appear. - Scheduled variant. Turn on
{SCHEDULE_OPTION}to auto-build decks for tomorrow's customer meetings from your calendar. - Related cards. Pair with daily-meeting-briefing, account-health-autopilot or post-meeting-crm-autopilot.
9. Known gotchas
- The clone can't share its screen. A person presents the deck.
- Review before showing a customer. Check for unreleased features and internal-only notes (internal ticket comments, pricing, roadmap).
- Decks take a few minutes. Request ahead of the call.
- Check the sender address. The deck arrives by email. Look at the sender and add it to safe senders so it isn't missed in spam.
- The shortest deck still has a title and a closing slide. Count them in the 6–9 slides.
- Transcripts contain errors. Names, numbers and dates may be wrong. Verify before presenting.
- Transcripts only exist for calls that were recorded or attended. If the clone wasn't on the call and no notes were saved, that source will be empty.
- Customer name matching. Transcripts are matched by customer name. If the name is spelled differently in files or the CRM, tell the clone the alternate names.
- HubSpot has no ticket operator. Support issues come from notes and tasks in HubSpot, and from Linear.
- Each user connects their own accounts. The clone only sees what you can see.
- Read every instruction before saving the skill. You are responsible for what your clone does.
10. FAQ
How long does the deck take? A few minutes after the request. It is emailed to you as a PDF with a text version.
How long is a short deck? About 6–9 slides, 16:9, including a title and closing slide.
Can the clone present it on the call? No. It can't share its screen. You or a teammate presents.
Can it send the deck to the customer? No. It is emailed to you. You decide what to share.
What if I don't have a CRM or Linear? The deck still works from the other sources. The clone tells you what was missing.
What's the difference between the two variants? (a) is a normal update. (b) is for at-risk accounts and focuses on issues, fixes, a dated success plan and asks.
Can I get just one page? Yes, ask for the one-page infographic (Image_Operator).
Can it build decks automatically? Optionally, for tomorrow's customer meetings found on your calendar.
Is it safe to show as-is? Review first. Check for unreleased features and internal-only notes.
11. Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Deck email didn't arrive | Still building, or filtered as spam | Wait a few minutes, check spam, add the sender to safe senders |
| Deck is thin or generic | Few sources connected or customer name didn't match | Connect more sources; give alternate customer names |
| No transcripts found | Wrong folder, older than 30 days, or clone didn't attend | Set {TRANSCRIPTS_FOLDER}; paste notes into the request |
| Wrong customer in the deck | Similar names in CRM or files | Give the exact CRM account name or domain |
| Open case missing | HubSpot has no ticket operator, or case closed | Check notes/tasks in HubSpot or the case in Salesforce; tell the clone what to include |
| Unreleased feature on a slide | Source mentioned a roadmap item | Remove it before presenting; add it to {INTERNAL_ONLY_RULES} |
| Wrong number or name | Transcript error | Verify against the CRM or source; ask for a rebuild |
| Too many or too few slides | Variant or length mismatch | Ask for the other variant or a tighter outline |
| Scheduled decks not arriving | Task paused or calendar not connected | Ask the clone to list scheduled tasks and check the calendar connection |
Version: 1.0.0 · Last updated: 2026-10-22 · Part of the Clone Use Case Library.
Paste these instructions into clone chat
# Clone Instructions: Customer Briefing Deck
> **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 **Customer Briefing Deck** for your user.
When setup is done, you will run a skill called **Customer Briefing Deck**. When the user says "Make a short briefing deck for my {CUSTOMER} call on {DATE} about {TOPICS}", you will:
1. confirm the customer, date, topics and variant (standard update or "Save the account"),
2. gather context from the knowledge base (`search_knowledge`), `meeting_archive`, `call_archive`, call transcripts in Google Drive or OneDrive (last 30 days, matched by customer name), the CRM (Salesforce or HubSpot), Linear and recent email,
3. write a `user_query` containing the collected context, the topic order and a slide outline,
4. call **Clone-Research-Report** with format = deck, deck_length = short and the email recipient = the user,
5. tell the user the deck will arrive by email as a PDF (with a text version) in a few minutes, with source status and "verify" flags.
Optionally you also offer a one-page 16:9 infographic via **Image_Operator**, and (if the user wants) a scheduled task that builds decks for tomorrow's customer meetings.
Your job right now is **setup only**: discover what is available, collect settings, propose a plan, do what you can after approval, and hand over what only the user can do. Be honest about limits. If a tool is missing or a step fails, say so and give exact manual steps.
## 2. Safety rules (read before doing anything)
1. **Plan first, then act.** Before you attach, create, schedule or change anything, show a numbered plan and wait for an explicit "yes". No yes, no changes. If the plan changes, ask again.
2. **Never ask for, accept or handle passwords, API keys or tokens.** Connections are made by the user through the platform's sign-in (OAuth) screens. If the user pastes a secret, tell them not to and do not use it.
3. **Never email customers during setup or later.** Decks go to the user only. The only message you may send during setup is a test deck to the user, after they approve it.
4. **Read-only on all data sources.** Discovery and the running skill only read the CRM, Linear, email, calendar, Drive/OneDrive and knowledge base. No CRM, Linear, email-send or file writes.
5. **Don't guess names.** Use exact skill and operator names as they appear in the user's catalog.
6. **Each user connects their own accounts.** Never suggest a shared service account.
## 3. Discovery
Use the `platform` tool to list your attached skills, operators and connections. Use `describeOperator` on each relevant operator to confirm what it can do and whether its connection is active.
Look for:
| Need | Required? | What to look for |
|---|---|---|
| Deck builder | Required | Clone-Research-Report (format = deck, deck_length = short, email recipient) |
| Knowledge base | Recommended | `search_knowledge` |
| Past calls | Recommended | `meeting_archive`, `call_archive` |
| Transcripts: Google Drive/Docs | Optional | GoogleDriveCoreOperator, GoogleDocsCoreOperator |
| Transcripts: OneDrive | Optional | Microsoft_OneDrive |
| CRM: Salesforce | Optional | SalesforceAccountOperator, SalesforceOpportunityOperator, SalesforceCaseOperator, SalesforceContactOperator, SalesforceActivityOperator |
| CRM: HubSpot | Optional | HubspotCompanyOperator, HubspotDealOperator, HubspotContactOperator, HubspotEngagementOperator |
| Tracker | Optional | Linear_Operator |
| Email | Optional | GoogleGmailOperator or the Outlook email operator |
| Calendar | Optional (needed for the scheduled variant) | GoogleCalendarOperator or the Outlook calendar operator |
| One-page infographic | Optional | Image_Operator |
| Scheduled task | Optional | `platform` scheduled tasks |
Note for HubSpot: there is no ticket operator. Open support items are read from notes and tasks through HubspotEngagementOperator, and from Linear.
**Report the results in a table:**
| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Clone-Research-Report | ✅ Connected / ⚠️ Attached, not signed in / ❌ Missing / ❓ Couldn't check | … | … |
| search_knowledge | … | … | … |
| meeting_archive / call_archive | … | … | … |
| Drive/Docs or OneDrive | … | … | … |
| CRM operators | … | … | … |
| Linear_Operator | … | … | … |
| Email | … | … | … |
| Calendar | … | … | … |
| Image_Operator | … | … | … |
| Scheduled task | … | … | … |
If you can't check something, mark it "❓ Couldn't check" and say why.
## 4. Collect placeholder values
Ask **once**, in a single short list. Offer examples and defaults. (`{CUSTOMER}`, `{DATE}` and `{TOPICS}` are asked at request time, not now.)
> To set this up I need a few details:
>
> 1. **CRM** (`{CRM_CHOICE}`): Salesforce, HubSpot or none?
> 2. **Transcripts folder** (`{TRANSCRIPTS_FOLDER}`): which Google Drive or OneDrive folder holds call transcripts or AI notes? *(default: search by customer name across files from the last 30 days)*
> 3. **Deck recipient** (`{DECK_RECIPIENT}`): which email should receive decks? *(default: your own email)*
> 4. **Default variant** (`{DEFAULT_VARIANT}`): standard update or "Save the account"? *(default: standard update)*
> 5. **Internal-only rules** (`{INTERNAL_ONLY_RULES}`): anything that must never appear on slides (for example pricing floors, unannounced roadmap)? *(default: none, but I will still flag anything that looks internal)*
> 6. **Scheduled variant** (`{SCHEDULE_OPTION}`): should I auto-build decks each day for tomorrow's customer meetings from your calendar? If yes, when? *(default: off)*
Repeat the answers back in a table and ask the user to confirm.
## 5. What you can do yourself (after approval)
Present a plan filled in with real names from discovery:
> **Proposed plan (nothing changes until you say yes):**
> 1. Attach these missing operators from the catalog: *[exact names]*.
> 2. Create the **Customer Briefing Deck** skill from section 7, with your values filled in.
> 3. *(If you want it)* Create a scheduled task "Customer Briefing Deck: tomorrow's meetings" at `{SCHEDULE_OPTION}`.
> 4. Run the test in section 8: one deck for a test or low-stakes customer, emailed to you only.
>
> **You'll need to do:** *[list from section 6]*.
>
> Reply **yes** to proceed, or tell me what to change.
After a clear "yes":
1. **Attach operators.** Use the `platform` tool to search the catalog and attach each approved item. Confirm each with `describeOperator`. If one needs sign-in, add it to the user's list.
2. **Create the Customer Briefing Deck skill.** Fill in placeholders and save it.
- **If you can't create a custom skill directly**, give the complete skill markdown from section 7 in one copy-paste block, plus these steps:
1. Open your clone's settings → **Skills** (or **Custom skills**).
2. Click **New skill** / **Add skill**.
3. Name it exactly **Customer Briefing Deck**.
4. Paste the full block into the instructions field.
5. Read it through, then **Save**.
6. Tell me "saved" so I can verify it's attached.
(Menu names may differ in your workspace.)
3. **Create the scheduled task** (only if the user wants one). Name: "Customer Briefing Deck: tomorrow's meetings". Schedule: `{SCHEDULE_OPTION}`. Action: "Run the Customer Briefing Deck skill in scheduled mode: find tomorrow's external customer meetings on my calendar, build a short standard deck for each, and email the decks to me." If you can't create scheduled tasks, give the exact values and steps for the user to create it manually.
4. **Report back** what succeeded and what failed, honestly.
## 6. What the user must do
Give this list with the how-to steps and track what is done.
1. **Connect your own accounts (OAuth)** on the clone's **Connections** / **Integrations** page, with **read** access:
- CRM: Salesforce or HubSpot (accounts/companies, opportunities/deals, cases, contacts, activities/engagements).
- Email: Gmail or Outlook.
- Files: Google Drive/Docs or OneDrive (view the transcripts folder).
- Tracker: Linear (if used).
- Calendar (only for the scheduled variant).
- Some CRM connections must be finished manually. If the connection does not complete in chat, finish it in the integrations settings, then tell me "connected" so I can re-check.
2. **Tell me where call transcripts live** (`{TRANSCRIPTS_FOLDER}`) and share the folder with the connected account if needed.
3. **Check the deck email arrives.** After the first deck, look at the sender address. Add it to your safe senders and check spam if it's missing.
4. **Review every deck before showing a customer.** Look for unreleased features, internal-only notes, and wrong names or numbers.
5. **Present the deck yourself.** I can't share my screen.
## 7. The Customer Briefing Deck skill (save this in full)
Fill in the placeholders, then save as a skill named **Customer Briefing Deck**. Don't shorten it.
~~~~markdown
# Customer Briefing Deck
## Purpose
Before a customer call, gather context about the customer from every connected source and build a
short briefing deck (about 6-9 slides, 16:9) with Clone-Research-Report, emailed to the user as a
PDF. A person presents the deck; the clone cannot share its screen.
## Settings
- CRM: {CRM_CHOICE} (Salesforce, HubSpot or none)
- Transcripts folder (Drive or OneDrive): {TRANSCRIPTS_FOLDER}
- Deck recipient: {DECK_RECIPIENT} (default: the user)
- Default variant: {DEFAULT_VARIANT}
- Internal-only rules: {INTERNAL_ONLY_RULES}
- Scheduled variant: {SCHEDULE_OPTION} (off by default)
- Asked at request time: {CUSTOMER}, {DATE}, {TOPICS}
## Tools
Use the exact names from my skill catalog. Skip what isn't connected and say so.
| Purpose | Tool (exact catalog name) | Required | Access |
|---|---|---|---|
| Product docs, release notes, account notes | search_knowledge | Recommended | Read |
| Past calls with the customer | meeting_archive, call_archive | Recommended | Read |
| Transcripts in Google Drive | GoogleDriveCoreOperator, GoogleDocsCoreOperator | Optional | Read |
| Transcripts in OneDrive | Microsoft_OneDrive | Optional | Read |
| Account, opportunities, cases, contacts, activities (Salesforce) | SalesforceAccountOperator, SalesforceOpportunityOperator, SalesforceCaseOperator, SalesforceContactOperator, SalesforceActivityOperator | Salesforce | Read |
| Company, deals, contacts, notes/tasks (HubSpot) | HubspotCompanyOperator, HubspotDealOperator, HubspotContactOperator, HubspotEngagementOperator | HubSpot | Read |
| Issues for the account | Linear_Operator | Optional | Read |
| Recent email threads | GoogleGmailOperator or Outlook email operator | Optional | Read |
| Calendar (scheduled variant) | GoogleCalendarOperator or Outlook calendar operator | Optional | Read |
| Build the deck | Clone-Research-Report | Required | format = deck, deck_length = short, email recipient |
| One-page infographic | Image_Operator | Optional | Create image |
| Scheduled runs | platform (scheduled task) | Optional | Existing task |
## Guardrails
- All sources are READ-ONLY. Never write to the CRM, Linear, email, calendar or files.
- NEVER send the deck, or any message, to the customer. The deck goes only to the user ({DECK_RECIPIENT}).
- NEVER invent features, dates, numbers, prices, owners or commitments. Use only what the sources say. If a fact is uncertain, mark it "verify" in your reply and phrase it carefully on the slide.
- Do NOT include unreleased features, roadmap items not announced to customers, internal-only notes (internal ticket comments, internal pricing, margin, other customers' details) or anything matching {INTERNAL_ONLY_RULES}. If something looks internal or unreleased, leave it out and tell the user you did.
- Transcripts are unreliable for names, numbers and dates. Cross-check against the CRM or other sources and mark conflicts "verify".
- Keep the deck short: deck_length = short (about 6-9 slides, 16:9). Always include a title slide and a closing slide.
- You cannot share your screen or present. Say so if the user asks, and remind them a person presents.
- Match transcripts by customer name (and known alternate names or domain). Only use files from the last 30 days unless the user says otherwise.
- Scheduled mode: build only standard decks, only for external customer meetings, only for tomorrow, and email them to the user only.
- Retry rule: if a tool call fails, retry ONCE. If it fails again, mark that source "unavailable", continue without it, and report it. If Clone-Research-Report fails twice, tell the user and offer the infographic option or a text briefing in chat.
- HubSpot has no ticket operator: use notes and tasks (HubspotEngagementOperator) and Linear for support issues.
- Never ask for or handle passwords or tokens.
## Step 1: Confirm the request
From the user's message get: customer ({CUSTOMER}), call date ({DATE}), topics in order ({TOPICS}), variant. Variant (a) Standard update deck is the default ({DEFAULT_VARIANT}); use (b) "Save the account" deck when the user says the account is at risk, escalated or asks to "save the account". Ask ONE short question only if the customer is unclear. Also note the audience (who is on the call) if the user says it.
## Step 2: Gather context (skip unavailable sources)
1. Knowledge base: search_knowledge for the customer's account notes and for each topic in {TOPICS} (product docs, release notes).
2. Past calls: meeting_archive and call_archive for calls with {CUSTOMER}; note goals, concerns, commitments, dates.
3. Transcripts in files: search {TRANSCRIPTS_FOLDER} (GoogleDriveCoreOperator + GoogleDocsCoreOperator, or Microsoft_OneDrive) for files from the last 30 days matching the customer name.
4. CRM: account (owner, plan or products, key facts), open opportunities or deals (stage, amount, close date), open cases (priority, status, age) via the Salesforce operators or the HubSpot operators. For HubSpot, open support items come from notes and tasks.
5. Linear: search issues for the account (open, in progress, recently done; owner, status, target date).
6. Email: recent threads with the customer (Gmail or Outlook): open questions, commitments, tone.
Collect short, factual bullets per source with where each came from.
## Step 3: Filter and cross-check
- Remove internal-only and unreleased items (see Guardrails).
- Cross-check numbers, names and dates between sources; mark conflicts "verify".
- Select only what supports {TOPICS}. Less is better for a short deck.
## Step 4: Write the user_query
Build one user_query for Clone-Research-Report containing: the audience and call date, the topic order, the collected context (bullets with source labels), what to avoid (internal-only items), and the slide outline for the chosen variant.
Variant (a) template, Standard update deck:
```
Create a short customer briefing deck (about 6-9 slides, 16:9) for a call with {CUSTOMER} on {DATE}.
Audience: {AUDIENCE}. Tone: clear, professional, customer-facing.
Topics in this order: {TOPICS}.
Slide outline:
1. Title: "{CUSTOMER}: Update for {DATE}"
2. Agenda (the topics, in order)
3. What's new (released items relevant to them only)
4-5. How it applies to {CUSTOMER} (tie each item to their goals, setup and open issues)
6. Open items and status (their open cases and issues, owners, dates)
7. Next steps (owner and date for each)
8. Closing: summary and questions
Context to use (only this; do not invent anything):
- Account facts: {CRM_FACTS}
- Past calls and goals: {CALL_CONTEXT}
- Product and release information: {KNOWLEDGE_CONTEXT}
- Open issues: {CASES_AND_LINEAR_CONTEXT}
- Recent email: {EMAIL_CONTEXT}
Do not include unreleased features, internal notes, internal pricing or other customers' information.
Mark anything uncertain as "to confirm".
```
Variant (b) template, "Save the account" deck:
```
Create a short "save the account" briefing deck (about 6-9 slides, 16:9) for a call with {CUSTOMER} on {DATE}.
Audience: {AUDIENCE}. Tone: accountable, calm, specific, no blame.
Topics in this order: {TOPICS}.
Slide outline:
1. Title: "{CUSTOMER}: Our plan to get you back on track"
2. Situation (what the customer has experienced, in their words where possible)
3. Issues and owners (each issue, current status, named owner)
4. What we've fixed (completed items with dates)
5. Success plan with dates (milestones, owners, measurable outcomes)
6. Asks (what we need from {CUSTOMER}, with dates)
7. Next steps (owner and date for each, next check-in)
8. Closing: commitment and contact
Context to use (only this; do not invent anything):
- Account facts and renewal context: {CRM_FACTS}
- Escalation and call history: {CALL_CONTEXT}
- Issues from cases and Linear (status, owner, target date): {CASES_AND_LINEAR_CONTEXT}
- Fixes already shipped: {KNOWLEDGE_CONTEXT}
- Recent email: {EMAIL_CONTEXT}
Do not include unreleased features, internal commentary, internal pricing or other customers' information.
Do not promise dates that are not in the context. Mark anything uncertain as "to confirm".
```
## Step 5: Build the deck
Call Clone-Research-Report with: format = deck, deck_length = short, user_query = the query from Step 4, email recipient = {DECK_RECIPIENT} (the user). Only one deck request per customer call unless the user asks for a rebuild.
## Step 6: Reply to the user
Reply right away (do not wait for the deck) with:
1. "Your deck is being built. It will arrive at {DECK_RECIPIENT} as a PDF (with a text version) in a few minutes."
2. The variant used and the topic order.
3. Source status: each source worked / no data / unavailable.
4. "Verify" flags: uncertain names, numbers, dates.
5. What you left out because it looked internal or unreleased.
6. Reminders: check the sender address and spam folder; review before showing the customer; a person presents (I can't share my screen).
7. Offer: "Want a one-page 16:9 infographic for screen-sharing instead (or as well)?"
## Step 7: Optional one-page infographic
If the user asks, use Image_Operator to create a one-page 16:9 infographic with: customer name and date, 3-4 key points, status of open issues (or what's new), and next steps. Apply the same guardrails. Deliver it to the user only.
## Step 8: Scheduled mode (only if {SCHEDULE_OPTION} is on)
Read tomorrow's events on the user's calendar (GoogleCalendarOperator or Outlook calendar operator). Keep only external customer meetings (attendees outside the user's company domain who match a CRM account). For each, run Steps 2 to 6 with variant (a) and topics taken from the meeting title and description. Email each deck to the user. If a meeting has no matching account, skip it and list it.
## Output format
**Customer Briefing Deck: {CUSTOMER} · {DATE}**
- Variant and topic order: …
- Deck requested: yes, emailed to {DECK_RECIPIENT} (PDF + text version, a few minutes)
- Source status: each source worked / no data / unavailable
- Verify flags: …
- Left out (internal or unreleased): …
- Reminders: check sender and spam; review before showing; a person presents
~~~~
## 8. Test plan
Ask the user to approve the test first. Use a **test or low-stakes customer** and send the deck only to the user.
1. The user names a customer (a test account, or a customer whose data they're comfortable with), a date and two topics.
2. Run the skill: "Make a short briefing deck for my {CUSTOMER} call on {DATE} about {TOPICS}."
3. Wait a few minutes for the email. Open the PDF and the text version.
4. Run it again with "save the account" to test variant (b) (optional).
5. Ask for the one-page infographic (optional).
| Check | Pass? |
|---|---|
| Clone confirmed variant and topic order, and asked at most one question | ☐ |
| Source status was reported (worked / no data / unavailable) | ☐ |
| Deck email arrived within a few minutes at the right address | ☐ |
| Sender address noted and not in spam (or added to safe senders) | ☐ |
| Deck is 16:9 with about 6–9 slides, including a title and a closing slide | ☐ |
| Topics appear in the order requested | ☐ |
| Slides use real customer context (calls, CRM, Linear, email), nothing invented | ☐ |
| No unreleased features or internal-only notes appear | ☐ |
| "Verify" flags were raised for uncertain names or numbers | ☐ |
| Variant (b) (if tested) has situation, issues and owners, fixes, dated plan, asks, next steps | ☐ |
| Infographic (if tested) is one page, 16:9 and readable | ☐ |
| Nothing was sent to the customer; no CRM, Linear or file changes were made | ☐ |
| (If scheduled) the scheduled task exists and builds decks only for tomorrow's customer meetings | ☐ |
6. Fix anything that failed and re-run.
## 9. Final status checklist
When you finish, send the user a status summary in this format:
**✅ Done by me**
- [ ] Discovery table shared
- [ ] Placeholder values confirmed
- [ ] Missing operators attached: …
- [ ] Customer Briefing Deck skill created (or full text handed over for copy-paste)
- [ ] Scheduled task created (if wanted)
- [ ] Test deck requested; results: …
**⏳ Waiting on you**
- [ ] Connect your own CRM, email, Drive/OneDrive and Linear (read access)
- [ ] Tell me the transcripts folder
- [ ] Save the skill (if I handed it over)
- [ ] Check the sender address and spam folder for the deck email
- [ ] Review every deck before showing it to a customer
**💡 Optional next steps**
- [ ] Turn on the scheduled variant for tomorrow's customer meetings (`{SCHEDULE_OPTION}`)
- [ ] Add `{INTERNAL_ONLY_RULES}` after your first decks
- [ ] Try the "Save the account" variant on an at-risk customer
- [ ] Ask for a one-page infographic for screen-sharing
- [ ] Pair with **daily-meeting-briefing** or **account-health-autopilot**
Requirements
Requirements: Customer Briefing Deck
Version 1.0.0 · Last updated 2026-10-22 · Estimated setup time: 20–40 minutes
Use this checklist before you hand CLONE-INSTRUCTIONS.md to your clone. Your clone will also check most of this during discovery.
1. Required skills / operators
Use the exact names below. Confirm them in your skill catalog before saving the skill. Your clone will report the exact names it finds.
Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.
Required:
| # | Skill / operator (exact name) | What it's used for | Notes |
|---|---|---|---|
| 1 | Clone-Research-Report | Builds the deck (format = deck, deck_length = short) and emails it to you as a PDF | Built-in platform tool |
| 2 | Customer Briefing Deck (custom skill) | The workflow itself | Saved from CLONE-INSTRUCTIONS.md section 7 |
Context sources (use any that apply; more sources mean a better deck):
| # | Skill / operator (exact name) | What it's used for | Notes |
|---|---|---|---|
| 3 | search_knowledge | Product docs, release notes, account notes | Needs a knowledge base with content |
| 4 | meeting_archive, call_archive | Past call transcripts with the customer | Only calls the clone attended or that were archived |
| 5 | GoogleDriveCoreOperator, GoogleDocsCoreOperator | Transcripts in Google Drive (last 30 days, matched by customer name) | Google users |
| 6 | Microsoft_OneDrive | Transcripts in OneDrive | Microsoft 365 users |
| 7 | SalesforceAccountOperator, SalesforceOpportunityOperator, SalesforceCaseOperator, SalesforceContactOperator, SalesforceActivityOperator | Account, open opportunities, open cases, contacts, activity history | Salesforce users |
| 8 | HubspotCompanyOperator, HubspotDealOperator, HubspotContactOperator, HubspotEngagementOperator | Company, open deals, contacts, notes and tasks (support items) | HubSpot users (no ticket operator exists) |
| 9 | Linear_Operator | Issues for the account | Linear users |
| 10 | GoogleGmailOperator or the Outlook email operator | Recent email threads with the customer | Read only |
Optional:
| # | Skill / operator (exact name) | What it's used for | Notes |
|---|---|---|---|
| 11 | Image_Operator | One-page 16:9 infographic for screen-sharing | Quick alternative to a deck |
| 12 | GoogleCalendarOperator or the Outlook calendar operator | Find tomorrow's customer meetings (scheduled variant) | |
| 13 | Scheduled task (via the platform tool) | Auto-build decks for tomorrow's meetings | Only if you want the scheduled variant |
2. Connections and minimum permissions
| Connection | Minimum permission | Why |
|---|---|---|
| Salesforce or HubSpot (optional) | Read access to accounts/companies, opportunities/deals, cases (or notes/tasks), contacts and activities | Account facts, open deals and issues |
| Linear (optional) | Read access to the team(s) with the customer's issues | Issues and owners |
| Gmail or Outlook (optional) | Read | Recent threads |
| Google Drive/Docs or OneDrive (optional) | View the transcripts folder | Recent call transcripts |
| Google Calendar or Outlook calendar (optional) | Read | Scheduled variant only |
| Knowledge base | Content added to the clone's knowledge base | Docs, release notes, account notes |
Important points:
- Everything is read-only. The clone does not write to your CRM, Linear, email or files for this use case.
- Each user connects their own accounts. No shared service accounts. The clone only sees what you can see.
- Some CRM connections must be finished manually in the clone's Connections / Integrations settings instead of in chat.
- All connections are made by you through the platform's sign-in (OAuth). Your clone never needs your password.
- The deck arrives by email. Check the sender address and add it to your safe senders.
3. Optional add-ons
| Add-on | Adds | Operators |
|---|---|---|
| One-page infographic | A quick 16:9 visual to screen-share | Image_Operator |
| Scheduled variant | Auto-built decks for tomorrow's customer meetings | Calendar operator + scheduled task |
| Related cards | Daily briefings and account health | daily-meeting-briefing, account-health-autopilot, post-meeting-crm-autopilot |
Salesforce ⇄ HubSpot mapping
| Generic concept | Salesforce | HubSpot |
|---|---|---|
| Account / company | Account (SalesforceAccountOperator) | Company (HubspotCompanyOperator) |
| Contact | Contact (SalesforceContactOperator) | Contact (HubspotContactOperator) |
| Opportunity / deal | Opportunity (SalesforceOpportunityOperator) | Deal (HubspotDealOperator) |
| Open support item | Case (SalesforceCaseOperator) | Notes or tasks (HubspotEngagementOperator); no ticket operator |
| Recent activity | Task/Event history (SalesforceActivityOperator) | Engagements (HubspotEngagementOperator) |
| Owner | Owner (User) | Company / deal owner |
Google ⇄ Microsoft 365 mapping
| Concept | Google Workspace | Microsoft 365 |
|---|---|---|
| Gmail (GoogleGmailOperator) | Outlook email operator | |
| Calendar | Google Calendar (GoogleCalendarOperator) | Outlook calendar operator |
| Transcript files | Google Drive (GoogleDriveCoreOperator) + Docs (GoogleDocsCoreOperator) | OneDrive (Microsoft_OneDrive) |
4. Data prerequisites
- Customer names are consistent between the CRM, transcript file names and email, or you can tell the clone the alternate names.
- Knowledge base has content (product docs, release notes, account notes), if you want those on the slides.
- Call transcripts exist (clone transcripts, or files in a known folder from the last 30 days), or you're willing to paste notes.
- You know what is internal-only (pricing floors, unannounced roadmap) so you can list it in
{INTERNAL_ONLY_RULES}. - Your email can receive the deck. You can check spam and safe senders.
- A test or low-stakes customer is available for the first deck.
5. Roles and permissions
| Who | Needs to |
|---|---|
| Clone admin (owner of the clone) | Attach operators, approve the plan, save the Customer Briefing Deck skill, create or approve the optional scheduled task |
| Account owner / presenter (each person) | Connect their own accounts (read), request decks, review and present them |
| Admin of CRM, Linear or files (only if your org restricts permissions) | Grant read access to the objects and folders above |
| Leadership / sponsor (optional) | Agree on what must never appear on customer slides |
6. Estimated setup time
| Step | Time |
|---|---|
| Pre-flight check (this doc) | 5 min |
| Clone discovery + placeholders + plan | 10 min |
| Your connections (read access) | 5–15 min |
| Save skill + optional scheduled task | 5 min |
| Test deck | 10 min |
| Total | 20–40 min |
7. Pre-flight checklist
- I'm the clone admin (or have one available)
- I know which sources I have: knowledge base, call transcripts, CRM, Linear, email
- I can sign in with my own account to each source I want to use
- I know the folder where call transcripts live (
{TRANSCRIPTS_FOLDER}) - I've chosen
{DECK_RECIPIENT}and{DEFAULT_VARIANT} - I've listed
{INTERNAL_ONLY_RULES}(or none) - I've decided whether to use the scheduled variant (
{SCHEDULE_OPTION}) - I know who will present the deck (the clone can't share its screen)
- I have a test or low-stakes customer for the first deck
8. You're ready when…
- ✅ Clone-Research-Report is available and at least one context source works.
- ✅ You have answers for the placeholders in README section 6.
- ✅ You know where to look for the deck email (sender address, spam folder).
- ✅ You have a test or low-stakes customer.
- ✅ You are comfortable reviewing every deck before showing it to a customer.
Then download CLONE-INSTRUCTIONS.md and give it to your clone.
Was this use case helpful?
Thanks!