Draft CRM Note

Purpose

Create a traceable interaction-note draft. Preserve the source meaning, separate observation from interpretation, and leave unsupported CRM fields unknown.

Required inputs

• Contact and account identifiers from supplied records
• Original interaction text, date, channel, and source location
• Relevant eligibility, consent, and opt-out status
• Requested note schema, owner, and proposed follow-up context

Mark absent or conflicting inputs Missing or Conflicting; never infer a CRM value.

Workflow

1. Quote or faithfully preserve the original interaction and record its date, channel, and supplied source.
2. List only directly observed facts. Keep account facts separate from contact statements.
3. Put model or rep interpretations in a distinct section, each labeled Inference with its supporting fact.
4. List every requested but unsupported field under Unknowns; do not invent stage, value, owner, probability, authority, budget, timeline, or next-contact permission.
5. Gate the next step. Missing current eligibility or contact-specific opt-out status permits only verification. Failed eligibility, an opt-out, or a clear negative permits no outreach. Otherwise propose one reviewable step consistent with the interaction.
6. Return a draft for human review. Never claim that a CRM, task, owner, field, or status was created or updated.

Output format

# CRM note draft
- Contact / account: [supplied identifiers]
- Interaction date / channel: [values or Missing]
- Source: [citation or supplied location]
- Original meaning: [quote or faithful summary]
## Observed facts
- [fact — source]
## Interpretation
- Inference: [interpretation — supporting fact]
## Unknowns or conflicts
- [field — Missing or Conflicting]
## Proposed next step
- [unexecuted, reviewable proposal or STOP]
## Record status
- DRAFT ONLY — CRM NOT UPDATED

Guardrails

• Do not fabricate or silently normalize fields, identities, dates, stages, values, outcomes, intent, consent, or qualification.
• Do not convert relevance, an information request, or an introduction offer into meeting consent or a qualified opportunity.
• Preserve opt-outs, hard disqualifiers, uncertainty, and the original reply's strength.
• Reject targeting or decisions based on protected traits (such as race, religion, disability, sex, or age) and collection or use of unnecessary sensitive personal data.
• Do not browse, send, schedule, assign, create tasks, use credentials, or read from or write to a CRM or other external system.

Quality check

Confirm source and date are visible; facts and inference are separate; safety gates control the next step; missing and conflicting fields remain unresolved; and the output says CRM NOT UPDATED.

Example invocation

Use draft-crm-note to turn Avery Lin's supplied 2026-07-02 reply into a sourced note draft with facts, inference, unknowns, and an unexecuted next step.