Read the current behavior
LACRM’s current help distinguishes intake forms that create records from update forms that match and change existing records. An older nonprofit example describes only the earlier new-record route; do not use that older wording to claim updates are impossible today. Check the current documentation and your actual configuration before publishing a form.
Test a fictional return visit
Use a permitted test record to examine a repeated submission, a changed contact detail and a cleared selection. In the documented update behavior, matching and replacement rules differ by field type. That makes blank or changed answers important. Do not assume that every new response is merged safely or that every checkbox preserves its previous choices.
Plan who reviews the change
A preference update may require a new conversation without changing an already confirmed commitment. Name an owner for that review. Keep the source and date of the change available in the approved record. If two people may share a contact route, do not merge their records on assumption alone; follow the product’s matching behavior and your own verification process.
Worked distinction
A fictional volunteer clears a location preference on an update form. The team checks whether this means no preference, no longer available or an incomplete response before acting. It does not cancel existing assignments automatically. The useful outcome is a reviewable change, not a silent rewrite of operational commitments.
Inspect the before-and-after record
For a fictional test, capture the existing non-sensitive field values, submit one intended change, then compare the resulting contact and any related pipeline item. Check a matching email, a changed phone number and an empty optional selection separately. The documented update behavior can differ by field type, and permission or matching conditions affect the outcome. Record whether a second contact or new pipeline item was created. Do not assume a form labelled update preserves every prior value, merges duplicates or updates an existing workflow item.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- LACRM intake and update forms — Merchant documentation · lessannoyingcrm.com · Merchant-controlled · checked 2026-10-01