THE SHORT ANSWER
Capture the minimum information needed to respond to the person's current intent, explain what will happen next and record source and permission accurately. Add information later as the relationship develops rather than front-loading friction and privacy risk.
Start with the action the person requested
| Interaction | Likely need | Possible minimum |
|---|---|---|
| Newsletter signup | Receive a defined publication | Email and recorded preference |
| Sales enquiry | Discuss a need | Contact route, need and useful context |
| Demo request | Evaluate a product | Work contact, use case and scheduling details |
| Event or offline conversation | Continue a specific discussion | Contact route, source, note and permission |
| Support chat | Resolve an issue | Account or order identifier and issue details |
The correct fields depend on the next action. Asking for company size on a newsletter form may add friction without helping delivery; omitting the problem from a complex service enquiry may create an unnecessary follow-up.
Treat every field as a cost
- Is this needed now, or merely interesting?
- Can the system infer it reliably from an existing transaction?
- Can it be requested later when its purpose is clear?
- Could a free-text field invite sensitive or unnecessary information?
- Will someone actually use and maintain it?
Evidence & context: UK Information Commissioner's Office
Make the exchange understandable
State what the person will receive, which channel will be used and what happens after submission. Keep marketing preferences distinct from a service request where appropriate. Requirements depend on the channel and jurisdiction, so use applicable legal and privacy guidance rather than assuming one checkbox works everywhere.
Record the source, timestamp and relevant preference. Do not convert an enquiry, receipt request or event scan into unlimited marketing permission.
Evidence & context: UK Information Commissioner's Office
Judge quality after the form
A higher completion rate is not enough. Review whether captured leads are reachable, relevant, properly routed and able to progress. A short form that creates unusable records is not successful.
Continue with CRM data, then use lead qualification to define what the next stage requires.
Sources & further reading
- Customer Relationship Management
OpenStax, Rice University. Open educational material on managing customer relationships and value over time. CRM software and lifecycle messaging do not themselves create retention.
- Direct marketing guidance
UK Information Commissioner's Office. UK regulatory guidance on planning, collecting information, transparency and respecting communication preferences, checked 28 September 2026. Requirements vary by jurisdiction and context; this is not individual legal advice.
Examples and exercises are illustrative unless attributed to a source. No independent expert review is claimed.
A correction, a counterexample or an experience worth sharing?
Join the conversation ↗