Let your clone run the first minute of every customer call

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:

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.

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

 ┌───────────────────────────────────────────────────────────────────┐
 │  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").

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.

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.

The skill itself: 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.

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