# Sales SOP: Call to reviewed CRM handoff Version: draft-1 / 2026-11-09. Department: Sales. Source: [Canonical SOP](https://dive.vladyslavpodoliako.com/sops/sales-call-to-crm/) > Untested general-purpose draft. All procedure steps, quality checks, and acceptance tests are not run. These are proposed templates, not actual Belkins SOPs or hands-on test reports. No external actions, sends, model calls, or schedules are performed or configured. No action is preapproved. Prepare a timestamped account note, proposed CRM changes, and an unsent follow-up from approved call evidence. ## Purpose Turn an approved call record into a source-linked account note and an unsent follow-up. A human must verify the account match and every proposed field change. This procedure does not change deal state or contact the customer. ## Ownership and trigger - Owner: Account owner. Named person: not assigned. - Approver: Designated sales reviewer. Named person: not assigned. - Proposed trigger: A call record is explicitly cleared for review. Use one unique call/run identifier; an ambiguous account match blocks preparation. ## Approved inputs - Approved call reference with call ID, date, time zone, and timestamps. Use a restricted reference, not a public transcript link. - Approved account identifier and read-only CRM snapshot with record IDs and snapshot date. - Required note fields, approved follow-up style, retention rules, and permitted processing environment. - Unique run identifier and named owner/reviewer. Describe sources instead of entering credentials or unrelated contact data. ## Proposed procedure (not run) 1. [ ] Not run: Verify processing permission and that the call maps to exactly one approved account. Record the matching evidence. Stop when permission or identity is ambiguous; never choose the closest-looking record. 2. [ ] Not run: Extract needs, objections, decisions, next actions, owners, and dates. Attach a timestamp or excerpt reference to each factual item. Leave missing owners, budget, and dates explicitly unknown. 3. [ ] Not run: Compare the extracted information with the approved CRM snapshot. Keep proposed information separate from existing values and flag contradictions for the account owner instead of overwriting them. 4. [ ] Not run: Draft the structured note and an unsent follow-up. Do not invent promises, decision authority, meeting dates, pricing, or product capabilities. Minimize personal information in both artifacts. 5. [ ] Not run: Present a field-level change list showing current value, proposed value, source, and unresolved question. Request reviewer disposition. Do not write to CRM or send the follow-up. 6. [ ] Not run: Record the draft version and review request in an empty handoff record. If a separate authorized process later performs a write, its owner must reconcile the actual receipt and duplicate-prevention key before any retry; this template does not execute that process. ## Proposed outputs - Account note draft with call/account IDs and source timestamps. - Action-item list and unresolved questions, with unknown values preserved. - Unsent follow-up and proposed field-level CRM diff. - Empty reviewer decision and separate-execution receipt fields; neither implies approval or delivery. ## Quality checks (not run) - [ ] Not run: Every factual item traces to an approved source, including commitments and action dates. - [ ] Not run: Exactly one account matches; dates and time zones agree with the source. - [ ] Not run: No credential, unrelated contact, or unnecessary personal detail appears in the export. - [ ] Not run: The artifacts are drafts; no CRM write or external message is represented as completed. ## Acceptance tests (not run) - [ ] Not run: Normal. Proposed fixture: Synthetic call with one account, two timestamped actions, and an approved CRM snapshot. Expected result: The note contains the expected fields and both supporting timestamps; the follow-up remains unsent. - [ ] Not run: Missing identity. Proposed fixture: Call without an approved account identifier, or with two possible matches. Expected result: Preparation stops and requests account-owner clarification; no match is guessed. - [ ] Not run: Contradiction. Proposed fixture: Two different next-meeting dates in the supplied evidence. Expected result: Both dates remain an unresolved conflict instead of becoming a fabricated commitment. - [ ] Not run: Duplicate trigger. Proposed fixture: The same synthetic call/run identifier submitted twice in the proposed trial. Expected result: The duplicate is flagged for reconciliation; no second write or follow-up is authorized. ## Stop and recovery - Stop on ambiguous identity, missing permission, conflicting commitments, or an uncertain external result. - Keep the draft private in the approved environment. Ask the account owner to resolve the blocker and record the resolution. - Resume only from the last reviewed draft after confirming current account state. A timeout is not proof that a separate write failed. ## Evidence record (empty) - Template version: draft-1 / 2026-11-09. Adapted version and run identifier: not recorded. - Run status: Not run. Fixture/source versions and approved environment: not recorded. - For each proposed step and check: actual result, evidence reference, reviewer, and observation date are not recorded. Expected results above are not observations. - Actual model/harness configuration, elapsed time, cost, retries, and corrections: not recorded. No model call is made here. - Human decision: pending. Approver identity, review date, and scope: not recorded. No response is not approval. - External execution: none performed by this template. Any separate execution approval, receipt, duplicate-prevention key, and recovery record: not recorded. - Keep any future evidence in its approved restricted location. Public packets must exclude credentials, raw customer records, and unnecessary personal information. ## Related planning reference [SOP library](https://dive.vladyslavpodoliako.com/sops/) | [Workflow planner preset](https://dive.vladyslavpodoliako.com/workflow-planner/?preset=call-to-crm-follow-up) The planner preset is an editable starting specification, not an execution of this procedure. Its fields are starting values: replace its owner, approver, trigger, and inputs with this SOP's, and reconcile the rest before use.