# Post-Meeting CRM Autopilot: Meeting Notes → CRM Updates

> **Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Intermediate · Setup time: 30–60 minutes**

After a customer or sales meeting, your clone reads the notes, works out what happened, and prepares the CRM updates for you: a logged meeting, a summary note, follow-up tasks, contact updates and suggested deal changes. You approve the list, then it writes.

---

## 1. Overview and value

Everyone agrees the CRM should be up to date. Nobody has time at 5:45 PM after a day of calls. So notes stay in a doc, next steps stay in someone's head, deal stages go stale and the forecast drifts.

Post-Meeting CRM Autopilot closes that gap. After a meeting, your clone:

- finds the notes from **whichever source exists** (its own transcript, AI meeting notes, or notes you paste),
- extracts the **summary, decisions, next steps (owner + due date), deal signals, new contacts and follow-up dates**,
- matches the meeting to the right **account, contacts and open deal**,
- shows you a **proposed change list** and waits for your approval,
- writes the approved items to **Salesforce or HubSpot**,
- optionally emails you a short recap of what was logged.

**What you get:**

| Benefit | What it looks like |
|---|---|
| A CRM that is actually current | Every external meeting is logged with a summary and next steps |
| No dropped follow-ups | Next steps become tasks with owners and due dates |
| Cleaner forecasts | Stage, amount and close date changes are suggested from what was said |
| Time back | 5–15 minutes of data entry saved per meeting |
| You stay in control | Nothing is written until you approve; deals never move backward or close without your explicit OK |

---

## 2. Who it's for

- **Sales reps and account executives** who want every call logged and every deal field kept honest.
- **Customer Success Managers** who need QBR, check-in and escalation calls recorded against the account with clear next steps.
- **RevOps** who want consistent activity data and fewer stale opportunities, with a human approval step built in.
- **Sales and CS managers** who want pipeline hygiene without nagging the team.

It is built for **external** meetings (customers, prospects, partners tracked in the CRM). Internal-only meetings are skipped.

## 3. How it works

```
   Trigger
   ├─ On demand: "Log my last meeting"
   └─ On a schedule (e.g. hourly): any new meetings since last run?
                         │
                         ▼
 ┌───────────────────────────────────────────────────────────────────┐
 │  "Post-Meeting CRM Log" skill                                     │
 │                                                                   │
 │  1. Find the meeting + the notes (first source that has them)     │
 │       a) meeting_archive  (clone attended)                        │
 │       b) AI notes in Drive / OneDrive, or emailed notes           │
 │       c) notes you paste in chat                                  │
 │  2. Skip internal-only meetings ({YOUR_COMPANY_DOMAINS})          │
 │     and anything matching {SKIP_RULES}                            │
 │  3. Extract: summary · decisions · next steps (owner, due date)   │
 │       · deal signals · new contacts · follow-up dates             │
 │  4. Match: attendee domain → account → contacts → open deal       │
 │       (several open deals? ask you)                               │
 │  5. Dedupe: "[Meeting Log] {Meeting title} – {YYYY-MM-DD}" exists?│
 │       → skip                                                      │
 │  6. Show the PROPOSED CHANGE LIST                                 │
 └───────────────────────────────┬───────────────────────────────────┘
                                 │
                  You reply "approve" (or edit the list)
                                 │
                                 ▼
 ┌───────────────────────────────────────────────────────────────────┐
 │  Write to Salesforce or HubSpot                                   │
 │   · logged meeting/activity + summary note                        │
 │   · follow-up tasks (owner, due date)                             │
 │   · contact updates · new contacts (with confirmation)            │
 │   · deal stage / amount / close date: SUGGESTIONS, applied only   │
 │     on your explicit approval                                     │
 │  Optional: short recap email to you                               │
 └───────────────────────────────────────────────────────────────────┘
```

### Where the notes come from

The clone uses the first source that has notes for the meeting, and tells you which one it used.

| Source | When it applies |
|---|---|
| `meeting_archive` | The clone attended the meeting and has its own transcript |
| AI meeting notes in Drive | For example Gemini notes saved in a Google Drive "Meet Recordings" folder (GoogleDriveCoreOperator, GoogleDocsCoreOperator), or the Microsoft 365 equivalent in OneDrive |
| AI meeting notes by email | Notes emailed to you (found with Gmail or Outlook). Common when you were not the meeting organizer |
| Pasted notes | You paste notes into chat: "Log this meeting: ..." |

### How the meeting is matched to the CRM

1. External attendee **email domain** → **account / company**.
2. Attendees → **contacts** on that account.
3. Account → **open opportunity / deal**. If there is more than one open deal, the clone **asks you which one**. It never guesses.

## 4. What the clone does (and never does)

**It does, after you approve:**

- logs the meeting as an activity (Salesforce) or engagement meeting (HubSpot), linked to the account, contact and deal,
- adds a summary note,
- creates follow-up tasks with owners and due dates,
- updates contact title and phone when they were clearly stated,
- creates new contacts only after you confirm each one,
- suggests deal stage, amount and close date changes.

**It never:**

- writes anything before you approve the change list,
- moves a deal backward, changes an amount, or closes a deal (won or lost) without your explicit approval for that specific change,
- logs the same meeting twice (it checks for an existing "[Meeting Log] {Meeting title} – {YYYY-MM-DD}" activity first),
- logs internal-only meetings ({YOUR_COMPANY_DOMAINS}) or meetings matching your `{SKIP_RULES}`,
- emails customers or prospects,
- deletes records,
- 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. You need a CRM connection with write access, a place the notes come from, and the ability to create a scheduled task (if you want automation).

**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 operators and connections it has and which are missing.

**Step 4: Answer the placeholder questions (5 min).** See section 6.

**Step 5: Approve the plan (2 min).** Say "yes" only when it looks right.

**Step 6: Do your part (10–20 min).** Only you can:
- Connect **your own** Salesforce or HubSpot account. Some CRM connections must be finished manually in the integrations settings instead of in chat.
- Make sure the connection has **write** access to contacts, companies/accounts, deals/opportunities and activities (admin is not needed).
- Connect Gmail/Drive or Outlook/OneDrive so the clone can find AI notes (optional).
- Turn on AI meeting notes in your meeting tool if you want that source.

**Step 7: Save the Post-Meeting CRM Log skill (5 min).** The clone saves it, or gives you the full text to paste.

**Step 8: Run the test plan (10–15 min).** Log one test meeting against a test account and check the results.

**Step 9: Turn on the schedule (optional).** Hourly checks for new meetings, with approval by chat.

## 6. Placeholders to decide

| Placeholder | What it means | Example |
|---|---|---|
| `{CRM_CHOICE}` | Which CRM you use | Salesforce or HubSpot |
| `{YOUR_COMPANY_DOMAINS}` | Your company's email domains (internal = these) | yourcompany.com, yourcompany.io |
| `{NOTES_SOURCE}` | Where your meeting notes usually live | Gemini notes in Drive "Meet Recordings", emailed notes, clone transcript, pasted |
| `{NOTES_FOLDER}` | Drive or OneDrive folder with AI notes (if used) | "Meet Recordings" |
| `{SKIP_RULES}` | Optional extra meetings to skip | Titles containing "1:1" or "Interview"; calendar category "Personal" |
| `{RUN_SCHEDULE}` | How often the clone checks for new meetings (optional) | Hourly, 8 AM–6 PM Mon–Fri, my time zone |
| `{AUTO_LOG_MODE}` | Optional: auto-write activity + note only (never deal changes) | off (default) or on |
| `{RECAP_DELIVERY}` | How you receive proposals and recaps | Email, Slack, Teams, or chat only |
| `{DEFAULT_TASK_OWNER}` | Who owns a next step when no owner is stated | Me (the CRM user) |
| `{DEFAULT_TASK_DUE_DAYS}` | Due date when none is stated | 3 business days |

## 7. What to expect

- **On demand:** say "log my last meeting". Within a few minutes you get a proposed change list. Reply "approve" (or edit it) and the clone writes it and confirms.
- **On a schedule:** the clone checks for meetings that ended since its last run. If it finds one, it sends you the proposed change list by email or chat and **waits for you to reply "approve"** before writing anything. It tracks the time of its last run so nothing is processed twice.
- **Auto-log mode (optional):** if you turn on `{AUTO_LOG_MODE}`, the clone writes only the activity and summary note automatically. Deal changes, contact changes, new contacts and tasks always still need approval.
- **Review time:** about 1–2 minutes per meeting.

Example proposed change list:

```
Meeting: "Q4 Renewal Check-in" · 2026-10-21 · notes from: meeting_archive
Matched: Account "Example Corp" · Contacts: A. Lee, B. Kim · Deal: "Example Corp Renewal" (only open deal)

1. LOG meeting activity "[Meeting Log] Q4 Renewal Check-in – 2026-10-21"      (no duplicate found)
2. ADD summary note (6 bullets)
3. CREATE tasks
   a. Send revised proposal      · owner: me        · due 2026-10-24
   b. Share security whitepaper  · owner: A. Lee    · due 2026-10-28
4. UPDATE contact A. Lee: title → "VP Operations"  (stated in meeting)
5. NEW contact? "C. Ortiz, Procurement" (needs your confirmation)
6. SUGGESTED deal changes (not applied unless you say so):
   - Close date: 2026-11-30 → 2026-12-15  (customer asked for more time)
   - Risk noted: competitor mentioned
Reply "approve", "approve 1-4", or tell me what to change.
```

## 8. Customizing

- **Skip rules.** Set `{SKIP_RULES}` for meetings you never want logged (by title keyword, calendar, or attendee).
- **Note format.** Ask for a shorter summary, a template (for example MEDDIC-style fields or a QBR layout), or a different subject prefix.
- **Task defaults.** Change `{DEFAULT_TASK_OWNER}` and `{DEFAULT_TASK_DUE_DAYS}`.
- **Schedule.** Change how often it checks, or run it only on demand.
- **Delivery.** Receive proposals and recaps by email, Slack or Teams.
- **Auto-log mode.** Turn on activity + note auto-logging after a few weeks of clean approvals. Deal changes always stay manual.

## 9. Known gotchas

- **Write access is required, admin is not.** Your CRM connection needs WRITE access to contacts, companies/accounts, deals/opportunities and activities. It does not need admin rights. People often mix these up and ask for an admin account, or connect with a read-only user and see "permission denied" on the first write.
- **Each user connects their own CRM account.** No shared service accounts. Activities and tasks are then attributed to the right person, and the clone only sees what that user can see.
- **Some CRM connections must be finished manually.** If the connection does not complete in chat, finish it in the clone's integrations settings (Connections page) and then tell the clone to re-check.
- **Several deals at one company.** The clone must ask which deal the meeting belongs to. Pick the right one, or say "none".
- **Transcripts have errors.** Names, numbers, prices and dates can be wrong. The clone flags uncertain values, and you should verify amounts, dates and names in the change list before approving.
- **Don't log the same meeting twice.** The clone checks for an existing activity titled "[Meeting Log] {Meeting title} – {YYYY-MM-DD}". If you logged it by hand with a different subject, tell it to skip.
- **Notes from meetings you did not organize may arrive by email instead of Drive.** AI notes usually land in the organizer's Drive. If you were only an attendee, look in your inbox (the clone checks both).
- **The clone's own transcript only exists if it attended.** Otherwise it relies on AI notes or what you paste.
- **Read every instruction before saving the skill.** You are responsible for what your clone does.

## 10. FAQ

**Which CRMs work?** Salesforce and HubSpot. See the mapping table in REQUIREMENTS.md.

**Does it write to the CRM automatically?** No. It shows a proposed change list and waits for your approval. The only optional exception is auto-log mode for the activity and summary note, never deal changes.

**Can it change my deal stage or amount?** It can suggest changes. It only applies them after your explicit approval of that specific change. It never moves a deal backward and never closes a deal without your explicit OK.

**What if there are two open deals at the account?** It asks you which one.

**What if it logs the same meeting twice?** It won't. It checks for an existing "[Meeting Log] {Meeting title} – {YYYY-MM-DD}" activity first and skips if found.

**Does the clone need to attend my meetings?** No. It can use AI meeting notes from Drive or email, or notes you paste. If it does attend (via joinMeeting), it can use its own transcript.

**Will it email my customers?** No.

**Can I use it for internal meetings?** No, internal-only meetings are skipped on purpose.

**Does it need CRM admin?** No. It needs write access to the records it touches, not admin.

**Can the whole team use it?** Yes, but each person connects their own CRM account and sets up their own clone or runs their own schedule.

## 11. Troubleshooting

| Symptom | Likely cause | Fix |
|---|---|---|
| "Permission denied" when writing | Connection is read-only or missing write access to one object | Reconnect with write access to contacts, companies/accounts, deals/opportunities and activities (admin not needed) |
| CRM connection won't finish in chat | Some connections must be completed in settings | Finish it on the clone's Connections / Integrations page, then ask the clone to re-check |
| No notes found | Notes in a different folder or sent by email; clone did not attend | Tell the clone where to look, check your inbox, or paste the notes |
| Wrong account matched | Personal email domain, shared domain or missing domain on the account | Correct the match in the change list; add the domain to the account |
| Clone asks which deal | More than one open deal at the account | Pick the right one |
| Meeting skipped | Internal-only, matched `{SKIP_RULES}`, or already logged | Check the skip reason the clone reports |
| Duplicate activity | Meeting was logged earlier by hand with another subject | Delete one manually; tell the clone to skip that meeting |
| Wrong name or number in a note | Transcript error | Fix it in the change list before approving |
| Scheduled run did nothing | Task paused, no new meetings, or time zone mismatch | Ask the clone to list its scheduled tasks and its last-run time |
| Proposal sent but nothing written | Waiting for your approval | Reply "approve" in chat |

---

**Version:** 1.0.0 · **Last updated:** 2026-10-22 · Part of the Clone Use Case Library.
