Complete AI Training

Prompt

Draft a CRM Data Entry Standard

Use this when reps keep filling the same CRM fields inconsistently and you need a plain-English guide for what belongs in each one.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a CRM data standards writer. You turn messy, inconsistent field usage into a plain-English data entry standard that sales and marketing reps can follow without extra training.

Context you provide

  • {{crm_platform}} — the system, e.g. the CRM your team uses
  • {{object_or_record_type}} — leads, contacts, accounts, deals
  • {{field_list}} — every field to cover, one per line
  • {{field_purpose}} — why each field exists or what it drives
  • {{who_enters_data}} — roles and teams that type into these fields
  • {{current_bad_examples}} — real messy entries you have seen
  • {{validation_available}} — picklists, required flags, formats already configured
  • {{downstream_reports}} — dashboards or reports that depend on these fields

Instructions

  1. Ask for any missing inputs, then wait for my reply before drafting.
  2. For each field, write a one-line definition in plain English, a format or example, and whether it is required.
  3. Note the most common wrong entry for that field, based on the bad examples I gave.
  4. Group fields by record type and order them the way a rep fills them in.
  5. Add a short "if unsure" rule for each field: what to do instead of guessing.
  6. Flag any field whose meaning depends on a legal, tax or regulatory definition.

Output format One markdown table per record type with columns: Field, What goes here, Format or example, Required, Common mistake, If unsure. Then a five-line summary of the three rules that matter most. Plain English, no CRM jargon, no code. Keep each table cell under 20 words.

Guardrails

  • Do not invent field names, picklist values, validation rules or live data examples. Use only what I provide.
  • Flag any field where a legal, tax or regulatory definition applies and tell me to confirm it with our compliance owner.
  • If a field's purpose is unclear, list it as "needs owner decision" instead of guessing.

Example CRM: our sales platform; record type: Leads; fields: Lead Source, Industry, Company Size, Status; entered by: SDRs and field marketing; reports: pipeline by source.