Finish the call. Your clone updates the CRM.

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:

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

   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.

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

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.

Pick one CRM (required):

Also required:

Notes sources (use any that apply):

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