Decide which CRM fields staff should have to complete
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
Consider this hypothetical situation: A salesperson cannot save a new record without an expected purchase date, so they choose the end of the month. A colleague enters a dash in the company field because the buyer is an individual. The completeness report looks healthy, but neither entry helps anyone do their work.
Which CRM fields should be mandatory? Require fields when a reliable answer is available and its absence would prevent a specific next action or create a material operational problem. Make fields conditional when they become necessary later or only for certain records. Keep fields optional when they are helpful context rather than prerequisites.
The distinction is not between valuable and unimportant information. It is between information needed now, information needed at a defined checkpoint, and information that would merely be useful to have. The worksheet below turns that distinction into a field-by-field decision.
1. Start with the person who uses the answer
Do not begin by asking managers which fields they would like completed. Begin with a task: assigning an enquiry, preparing a proposal, arranging a handoff, or deciding which open records need attention.
For each field, finish this sentence: When this value is present, this person can take this action. If the answer is only that someone can report on it, name the report, its user, and the decision it changes. A field used to allocate service capacity has a clearer purpose than one included in a dashboard that nobody acts on.
Then identify the consequence of a blank. Does work stop? Must someone contact the customer again? Is the record simply absent from an interesting breakdown? These are different costs and should not produce the same requirement.
Also test whether the field is the right way to support the task. A required free-text owner name is a weak substitute for a consistent assignment process. A required next-action sentence may duplicate an existing task record. Before making entry compulsory, remove unnecessary duplication.
2. Separate usefulness from answer availability
A purchase date can be useful for planning without being knowable during the first conversation. Making it mandatory does not bring the customer's decision forward; it changes what staff must type to continue.
Classify availability explicitly:
- Known at creation: Available from the interaction or the person creating the record.
- Known after a defined event: Established during a later conversation, review, or handoff.
- Sometimes unavailable: The customer may not know or may choose not to provide it.
- Not applicable: The field has no meaningful answer for this type of record.
Known-at-creation information may reasonably be required immediately. Later information belongs at a later checkpoint. Sometimes-unavailable information needs an honest uncertainty state. Inapplicable fields should not block work.
Be especially careful with estimates. A customer-stated target date, an employee's planning estimate, and a confirmed commitment are different things. If all occupy one field without a distinction, a filled value can appear more certain than the conversation warrants.
3. Use a filled field-requirement worksheet
Fictional worked example: A business sells equipment and provides installation. Staff create enquiry records, discuss needs, prepare proposals, and hand accepted work to a scheduling team. This hypothetical worksheet recommends an operating design; it does not describe an Alactic customer or establish available product controls.
Reuse the structure for your own fields: business use, answer availability, consequence of omission, treatment, and recovery. The recovery entry explains how to proceed without fabricating an answer.
Record owner or responsible queue
- Business use: Establish who must review and progress the enquiry.
- Known when: At creation, provided an intake responsibility exists.
- Consequence of omission: Nobody is clearly accountable for follow-up.
- Treatment: Required at creation. Use a designated intake queue when an individual owner is not yet known, if supported.
- Recovery: Review intake-held records and transfer responsibility explicitly. Do not select an arbitrary employee merely to save.
Customer or contact display name
- Business use: Help staff recognise and discuss the record.
- Known when: Usually at creation, although an enquiry may contain only a contact identifier.
- Consequence of omission: Recognition and duplicate review become harder, though work may remain possible.
- Treatment: Require a meaningful record identifier, not necessarily a full personal name. Keep a separate full-name field optional until genuinely needed.
- Recovery: Use a defined provisional naming convention that does not pretend to be verified customer information.
Usable contact route
- Business use: Allow the responsible person to respond.
- Known when: Usually at creation for an actionable enquiry.
- Consequence of omission: Follow-up cannot proceed through that route.
- Treatment: Conditionally require an appropriate contact route before active follow-up. Do not require both phone and email simply because both fields exist.
- Recovery: Separate records awaiting contact details from actionable enquiries. A saved address or number does not establish permission for every communication use.
Company name
- Business use: Associate business purchases with the correct organisation.
- Known when: During some initial business discussions; irrelevant for individual buyers.
- Consequence of omission: Business account matching may be delayed, but individual purchases are unaffected.
- Treatment: Conditional for business purchases before account-specific proposal work; optional for other records.
- Recovery: Allow an unresolved organisation state rather than entering a dash or inventing a company.
Expected purchase date
- Business use: Support follow-up timing and planning.
- Known when: After discussing timing; sometimes still uncertain.
- Consequence of omission: Planning is less precise, but initial contact and needs discussions can continue.
- Treatment: Optional at creation. At a planning review, require either a supported estimate or an explicit timing-unknown state with a review action.
- Recovery: Keep uncertainty visible. Do not default unknown dates to the end of a month.
Next action and due date
- Business use: Tell the owner what must happen next and when to revisit the record.
- Known when: After the first review or interaction.
- Consequence of omission: An active enquiry may remain open without an actionable plan.
- Treatment: Conditional before leaving an active record after review. Use a linked task instead of duplicate fields where supported.
- Recovery: If waiting on the customer, record the review action rather than inventing a customer commitment.
Installation address
- Business use: Let the scheduling team assess and arrange installation.
- Known when: Once the installation site is established.
- Consequence of omission: Scheduling cannot complete the handoff reliably.
- Treatment: Required before scheduling handoff for installation work, not for every enquiry or equipment-only purchase.
- Recovery: Hold the handoff for clarification while preserving the rest of the record.
Enquiry source
- Business use: Help a manager assess where enquiries originate.
- Known when: Sometimes at creation; staff may not be able to determine it retrospectively.
- Consequence of omission: Source analysis has a visible gap, but customer work can continue.
- Treatment: Optional unless a specific operational use justifies more. Include an honest unknown state if completeness is reviewed.
- Recovery: Improve capture at the source rather than requiring staff to guess from memory.
The worksheet produces a mixed result. Ownership is an early requirement; installation details are a handoff requirement; purchase timing preserves uncertainty. Making everything required would erase those distinctions.
4. Put the requirement at the point of dependency
For every conditional field, write down the trigger. Requiring information later is too vague. Requiring it before sending the installation handoff tells staff when the answer becomes necessary and what it enables.
Choose the narrowest checkpoint that protects the downstream task. Requiring an installation address at enquiry creation adds friction before the business knows whether installation is relevant. Requiring it after scheduling begins puts the check too late.
Distinguish saving information from committing to an action. Staff should, where practical, be able to preserve an incomplete conversation without pretending it is ready for handoff. A draft or incomplete state can serve that purpose, but its availability must be verified.
Check the workspace and current plan before designing around conditional requirements, stage checks, task links, defaults, or exception views. These are proposed workflow patterns, not assertions that particular controls exist. If a suitable control is unavailable, use a documented handoff checklist and a named reviewer rather than describing a manual process as system-enforced.
5. Make truthful completion easier than a workaround
A mandatory dropdown with no accurate option asks staff to choose the least-wrong answer. Review labels, answer choices, and error messages alongside the required setting.
Use labels that state the intended meaning. In this hypothetical workflow, a label such as Target installation date discussed with customer is more specific than Date. Explain whether an amount is confirmed or estimated. Accept sensible input formats where possible instead of rejecting a usable answer for superficial formatting differences.
The W3C guidance on input validation recommends understandable, accessible errors and accommodating varied input formats. In a configurable CRM, ask whether the person blocked by a field can understand what is missing and how to fix it.
Keep unknown, not yet discussed, and not applicable distinct where they lead to different actions. Unknown timing may need follow-up; an inapplicable company field does not. Do not offer uncertainty options merely to improve completion statistics: give each consequential uncertainty state an owner or review checkpoint.
6. Test awkward paths before enforcing the rule
Walk through representative work, not just the ideal record. Hypothetical test cases include an individual buyer, a returning customer with changed details, a partial enquiry, an equipment-only purchase, and a record created before individual assignment.
Ask a staff member to explain what they would enter and why. Watch for hesitation, copied placeholders, irrelevant selections, and requests to keep parallel notes. Those behaviours can reveal mismatches between the rule and available information.
Where relevant, check other entry paths, including imports or connected systems. A requirement may behave differently outside manual entry. Verify behaviour rather than assuming a screen-level setting protects every path.
For urgent exceptions, define who can review the gap, what work may proceed, and who must resolve it. An exception should preserve the visible omission, not replace it with plausible-looking fiction. If the same exception recurs, reconsider the requirement rather than making bypasses routine.
7. Recover carefully from fields containing guesses
Removing a requirement does not repair values entered under the old rule. Nor should you erase every suspicious value: a common date or repeated answer may still be correct.
Identify likely placeholders for review and prioritise records where an incorrect value could affect current work. Ask owners to confirm, correct, or mark uncertainty. Preserve genuine information and avoid replacing one unsupported assumption with another.
Explain what no longer needs to be entered, what is still needed later, and who uses it. If staff hear only that a field is now optional, they may assume nobody needs it. The intended message is more precise: capture it when it becomes reliable, before the task that depends on it.
8. Measure whether the requirement improves work
Completion rate alone cannot distinguish a verified answer from a workaround. Pair it with observations of downstream usefulness:
- How often does a handoff return because necessary information is missing?
- How often does a reviewer correct an apparently complete value?
- Which requirements block saving because the answer is not yet knowable?
- Do unknown states receive their planned review?
- Can the receiving colleague complete the task without clarification?
Hypothetical pilot: Review ten recently created records and ten recent handoffs. Select five disputed fields, fill out the worksheet for each, and trial one revised requirement for two weeks. Name the reviewer and record both missing-information incidents and corrections to misleading values. These sample sizes and duration illustrate a manageable trial, not a benchmark.
Keep the requirement if it protects the named task without encouraging unreliable entry. Move it later if the answer becomes known later. Narrow its scope if it applies only to some records. Remove it from the mandatory list if nobody can identify a consequential use. The goal is information colleagues can trust when they need to act.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications