# AI Meeting Co-Pilot: Customer Meeting Prep & Kickoff > **Version 1.1.0 · Last updated 2026-10-22 · Difficulty: Advanced · Setup time: 45–90 minutes** Your clone preps every customer meeting on your calendar, opens it with a 60-second kickoff, and stays in the call to answer questions. You get one briefing email each morning with everything it prepared. --- ## 1. Overview and value Most customer meetings start cold. The host spends the first ten minutes (or the ten minutes before) digging through the CRM, Linear, old email threads and last month's notes. Promises made in the last meeting get forgotten. Product updates the customer would care about never get mentioned. The AI Meeting Co-Pilot fixes that. Every weekday morning your clone: - finds today's **current-customer** meetings on its own calendar, - gathers context from every source you've connected, - writes a **60-second kickoff script** and **Q&A notes**, - creates a **one-page infographic** for the host to share, - **joins the meeting**, delivers the kickoff when asked, and answers questions, - sends you **one daily briefing email** with all of it. **What you get:** | Benefit | What it looks like | |---|---| | No more cold starts | Every meeting opens with a crisp recap of where things stand | | Fewer dropped commitments | Recent promises and open issues are surfaced before the call | | Better customer engagement | 1–2 relevant updates per customer, not already sent to them | | Time back | 15–30 minutes of prep saved per meeting | | A safety net | The clone is in the room with verified answers if a question comes up | > **Prebuilt option:** Google Workspace users can attach the prebuilt skill **Meeting-Command-Google** instead of saving the custom skill. The custom skill in CLONE-INSTRUCTIONS.md works for both Google and Microsoft 365. --- ## 2. Who it's for - **Customer Success Managers / Account Managers** running recurring check-ins, QBRs and onboarding calls. - **Support leads** running escalation or status calls. - **Sales / solutions teams** handling expansion conversations with existing customers. - **Team leads** who want consistent, well-prepared customer meetings across a team ({TEAM_HOSTS}). It is built for **current customers**. Prospect, vendor and internal meetings are skipped on purpose. ## 3. How it works ``` ┌───────────────────────────────────────────────────────────────────┐ │ You add {CLONE_NAME} to customer meeting invites (like any guest)│ └───────────────────────────────┬───────────────────────────────────┘ │ Every weekday at {RUN_TIME} (scheduled task) │ ▼ ┌───────────────────────────────────────────────────────────────────┐ │ "Meeting Command" skill │ │ │ │ 1. Read the clone's calendar ──► today's meetings │ │ 2. Filter ──► current customers only │ │ (skip internal / prospect / vendor / no-video, │ │ flag unclear ones "Needs review") │ │ 3. Gather context ──► CRM · Linear · inbox · │ │ calendar · meeting archive · │ │ knowledge base │ │ 4. This week's updates ──► 1–2 "Recommended for you" │ │ 5. Write kickoff + Q&A notes │ │ 6. Create infographic (Image_Operator) │ │ 7. Schedule itself into each meeting (joinMeeting) │ │ 8. Send ONE briefing email ──► {BRIEFING_RECIPIENTS} │ └───────────────────────────────┬───────────────────────────────────┘ │ ▼ ┌───────────────────────────────────────────────────────────────────┐ │ In the meeting: waits quietly → kickoff when the host asks → │ │ answers questions → recap goes to the owner only │ └───────────────────────────────────────────────────────────────────┘ ``` ### How it decides what is a "customer meeting" A meeting is kept only when **an external attendee's email domain matches an account in Salesforce or HubSpot that is a current customer**, according to the rule you define as `{CUSTOMER_DEFINITION}` (for example "Account Type = Customer" in Salesforce, "Lifecycle stage = Customer" in HubSpot, or "has an active contract"). | Meeting type | What happens | |---|---| | External attendee from a current customer, has a video link | **Kept** and prepped | | Only people from `{YOUR_COMPANY_DOMAINS}` | Skipped: internal | | External attendee is a prospect / open sales deal only | Skipped: prospect | | External attendee is a vendor / partner | Skipped: vendor | | No video link (phone or in-person) | Skipped: no video | | Domain not found, or conflicting data | Marked **Needs review** and listed in the briefing | If you don't connect Salesforce or HubSpot, the clone can't confirm who is a customer. It will then mark external meetings "Needs review" unless you give it a fallback list of customer domains. ## 4. What the clone does in meetings 1. **Joins quietly** with a short greeting in the chat (e.g. "Hi all, {CLONE_NAME} here. I'll be on standby with notes."). 2. **Waits** until the host asks for the kickoff ("{CLONE_NAME}, can you kick us off?"). 3. **Delivers the 60-second kickoff:** welcome → where things stand → today's focus → 2–3 updates → hands back to the host. 4. **Stays on as an active resource:** answers questions using the verified Q&A notes and connected sources. 5. **Never commits** to pricing, contracts, discounts, timelines, roadmap dates or unreleased features. It says something like: "That's a great question for {host first name}. I'll make sure it's captured." 6. **Recap goes to the owner only** (see Known gotchas). Customers are never emailed automatically. > The clone can't share its screen. The host shares the infographic (it's linked in the briefing email). ## 5. Setup walkthrough The quickest path: download **CLONE-INSTRUCTIONS.md** and give it to your clone. It will check what's already connected, ask you for the placeholder values, show you a plan, and set up what it can after you approve. The steps below are what happens, so you know what to expect. **Step 1: Check requirements (5 min)** Open **REQUIREMENTS.md** and run through the pre-flight checklist. You need at least a calendar connection, an email connection, joinMeeting, Image_Operator and the ability to create a scheduled task. **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 skills/operators and connections it already has and which are missing. **Step 4: Answer the placeholder questions (5–10 min)** See the table in section 6. Have your answers ready to save time. **Step 5: Approve the plan (2 min)** The clone lists exactly what it will attach, create and schedule. Say "yes" only when it looks right. **Step 6: Do your part (15–30 min)** Things only you can do: - Complete sign-in (OAuth) for calendar, email, Salesforce or HubSpot, and Linear connections. - Share your knowledge base with the clone. - Turn on auto-admit for invited guests in your meeting platform (or plan to admit the clone). - Set meeting follow-up recaps to **owner-only**. - Confirm how Salesforce or HubSpot marks a current customer. **Step 7: Save the Meeting Command skill (5–10 min)** Google Workspace users can skip this by attaching the prebuilt skill **Meeting-Command-Google** (the clone can attach it for you). Otherwise the clone saves the custom skill. If it can't create custom skills directly, it gives you the full skill text in a copy-paste block with exact steps. **Read it before you save it.** **Step 8: Run the test plan (15 min)** Create a test meeting with a test contact (not a real customer), run the skill manually and check the results against the checklist in CLONE-INSTRUCTIONS.md. **Step 9: Start adding the clone to real invites** From now on, add `{CLONE_INBOX}` to every customer meeting invite. The schedule takes care of the rest. ## 6. Placeholders to decide | Placeholder | What it means | Example | |---|---|---| | `{CLONE_NAME}` | Your clone's display name | "Ava" | | `{CLONE_INBOX}` | The clone's own email address (the one you invite) | ava@yourcompany.com | | `{YOUR_COMPANY_DOMAINS}` | Your company's email domains (internal = these) | yourcompany.com, yourcompany.io | | `{CUSTOMER_DEFINITION}` | How Salesforce or HubSpot marks a current customer | "Account Type = Customer AND Status = Active" | | `{TEAM_HOSTS}` | The people who run customer meetings | Your CSM team | | `{BRIEFING_RECIPIENTS}` | Who receives the daily briefing email | you@yourcompany.com, cs-leads@yourcompany.com | | `{RUN_TIME}` | When the daily run happens (with time zone) | 7:00 AM America/New_York, Mon–Fri | Tip: set `{RUN_TIME}` at least 30 minutes before your earliest typical customer meeting. ## 7. What to expect day to day - **Every weekday at {RUN_TIME}:** the run starts. It typically takes a few minutes per meeting. - **Shortly after:** the briefing email lands in `{BRIEFING_RECIPIENTS}`' inboxes with, per meeting: the kickoff script, the infographic link, Q&A highlights, plus a list of skipped meetings (with reasons) and which sources worked or failed. - **Before each meeting:** skim the briefing (2 minutes). Open the infographic so you're ready to share it. - **In the meeting:** admit the clone if you don't use auto-admit. Ask for the kickoff when you're ready. - **After the meeting:** the recap goes to the meeting owner only. Forward anything useful to the customer yourself. - **Meetings added after {RUN_TIME}** are not prepped that day unless you ask the clone to "run Meeting Command for my 3 PM meeting". ## 8. Customizing **Kickoff script tone.** Ask the clone to edit the skill, e.g. "Make the kickoff warmer and more casual", "Keep it under 45 seconds", or "Always thank them for being a customer". You can also set a fixed opening line. **Infographic content.** The default sections are *Where we are*, *Today's focus* and *New from us* (with a *Recommended for you* badge). You can rename sections, add your brand colors, or remove the infographic step entirely. **Filters.** Change which meetings are kept: e.g. include prospect meetings in late-stage deals, only prep meetings hosted by `{TEAM_HOSTS}`, or skip meetings shorter than 15 minutes. **Sources.** Add or remove sources at any time. The skill uses whatever is connected and reports what worked or failed. **Briefing format.** Change recipients, send one email per host instead of one combined email, or add a "top 3 risks" section. ## 9. Known gotchas - **Set follow-up recaps to owner-only for customer meetings.** Otherwise the clone may send its post-meeting recap to every attendee, including the customer. The skill sets `followup = owner` when it schedules itself, but also check the default in your clone's meeting settings. - **The waiting room / lobby.** A host must admit the clone, or you need to turn on auto-admit for invited guests (Zoom: let invited users bypass the waiting room; Google Meet: Host controls → let people join without asking (by invite); Teams: "Who can bypass the lobby" → "People I invite"). - **Possible double-join.** Being on the invite *and* being scheduled with joinMeeting can create two bots. The skill passes the **event UID** so both count as one meeting. If two clones show up anyway, remove the one without context (it won't respond to "kick us off" with the prepared script). - **The clone must actually be on the invite**, using `{CLONE_INBOX}`. If it's not on the invite, it won't see the meeting. Also make sure your knowledge base is **shared with the clone**, or it can't use it. - **The clone can't share its screen.** A human shares the infographic. - **Use exact skill/operator names** as they appear in your skill catalog (e.g. "Image_Operator", not "image generator"). Names can differ slightly between orgs; the clone checks them during discovery. - **Read every instruction before saving it into a skill.** You're responsible for what your clone does. Make sure the guardrails match your company's policies. ## 10. FAQ **Which CRMs work?** Salesforce and HubSpot. See the Salesforce to HubSpot concept mapping in REQUIREMENTS.md. For HubSpot there is no ticket operator, so "support cases" context comes from notes and tasks via HubspotEngagementOperator. **Do I have to write the skill myself? Is there a prebuilt one?** Google Workspace users can attach the prebuilt skill **Meeting-Command-Google** instead of saving the custom skill. The custom skill in CLONE-INSTRUCTIONS.md works for both Google and Microsoft 365. **Do I need a CRM at all?** No, but it helps a lot. Without one, the clone can't confirm who is a current customer or pull account context. You can give it a list of customer domains as a fallback. **Will the clone email my customers?** Not during setup and not in the daily run. The only email it sends is the briefing to `{BRIEFING_RECIPIENTS}`. Meeting recaps go to the owner only. **Will it change anything in my CRM?** No. The Meeting Command skill is read-only for the CRM, Linear and the knowledge base. **What if the clone gets a question wrong?** It only answers from verified sources and says when it doesn't know. It never commits to pricing, contracts, timelines, roadmap or unreleased features. The host stays in charge. **Which meeting platforms work?** Google Meet, Zoom and Microsoft Teams (links that joinMeeting can join). **Can several hosts share one clone?** Yes. Every host adds the same `{CLONE_INBOX}` to their invites, and you list them in `{TEAM_HOSTS}` and `{BRIEFING_RECIPIENTS}`. **What does it cost in time once it's running?** About 2 minutes per meeting to skim the briefing. ## 11. Troubleshooting | Symptom | Likely cause | Fix | |---|---|---| | No briefing email arrived | Scheduled task not created, paused, or wrong time zone | Ask the clone to list its scheduled tasks; check `{RUN_TIME}` time zone | | A customer meeting was skipped | Clone not on the invite, domain not in the CRM, or account not flagged per `{CUSTOMER_DEFINITION}` | Check the "Skipped" section of the briefing for the reason; fix the invite or CRM data | | Internal meeting was prepped | A personal-email or partner domain matched an account | Add the domain to `{YOUR_COMPANY_DOMAINS}` or an exclusion list | | "CRM: unavailable" in briefing | Connection expired or permissions missing | Re-run sign-in for the Salesforce or HubSpot connection; confirm read access | | Infographic missing | Image_Operator not attached or failed twice | Check the briefing's source status; re-attach Image_Operator | | Clone stuck in the lobby | Auto-admit off | Admit manually, or turn on auto-admit for invited guests | | Two clones joined | Invite + scheduled join not de-duplicated | Remove the one without context; confirm the skill passes the event UID | | Kickoff too long / wrong tone | Default script settings | Ask the clone to adjust the kickoff section of the skill | | Clone answered something it shouldn't | Guardrail wording too loose | Tighten the do-not-say list in the skill | --- **Version:** 1.1.0 · **Last updated:** 2026-10-22 · Part of the Clone Use Case Library.