A practical way to review lead source fields for a local service business: an incident review
When a local service business has an open tracking incident, change one thing at a time. First write down the symptom, the affected record, and the time it appeared.
Read the symptom
The form can send a value that the CRM overwrites, ignores, or maps to the wrong field. The problem is easier to find when the original payload and final record sit next to each other.
Inspect the path
- Capture the exact form payload for one test submission.
- Compare each source field with the CRM field that should receive it.
- Check for hidden field names that differ between forms.
- Look for workflow steps that overwrite the first source value.
During the incident
Keep one mapping table that names the source field, destination field, and owner. Keep the test result with the record it describes so the next review starts with evidence, not a guess.
If the next step is a shared source and outcome record, see LeadSheet.