Customer Briefing Deck

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:

• 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.

   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 present

#Where the context comes from

#Two deck variants

Your clone matches these to the exact skill names in your workspace. 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:

Context sources (use any that apply; more sources mean a better deck):

Optional:

• 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.