# CRM field mapping

A reusable skill the "Walk in prepped, leave the CRM current" recipe pulls in. Add it once and every agent on the team can use it.

Know which CRM fields to update after each meeting type, so logging is consistent rather than guessed.

## Method
1. For every meeting that completed since the last run, check the CRM for an existing logged update.
2. If none exists, identify the meeting type (discovery, demo, negotiation, etc.) from the calendar event.
3. Look up which fields that meeting type requires: stage, next step, notes, or others per the stored mapping.
4. Draft the field update using only information from the calendar event and any linked notes — never invent detail.
5. Queue the drafted update for one-tap approval rather than writing it directly.

## Rules
- Which CRM fields to update per meeting type is set on first run, then stored in memory.
- Never draft a CRM update for a meeting with no notes or calendar detail to draw from.
- Every CRM update queues for approval; the skill never writes to the CRM directly.

## Output
A queued CRM field-update draft per completed meeting: stage, next step, notes — listed for one-tap approval.