Naming Guidelines
- Be descriptive: “Last Service Date” not “Date1”
- Stay consistent: Use similar naming patterns across fields
- Avoid confusion: Don’t use “Customer Type” and “Client Category” for similar data
- Keep it simple: Avoid special characters in field names
Organization Tips
- Group related fields: Put all service-related fields together
- Logical order: Most important fields first
- Limit required fields: Only require truly essential information
- Regular cleanup: Remove unused dropdown options periodically
Data Quality
- Use dropdowns for consistency: Prevents typos and standardizes data
- Provide help text: Guide users on what to enter
- Set up validation: Use appropriate field types (dates for dates, numbers for quantities)
- Train your team: Ensure everyone understands how to use custom fields
Performance Considerations
- Reasonable limits: 10-15 custom fields per contact is optimal
- Choose field types wisely: Use dropdowns instead of text when possible
- Regular maintenance: Deactivate unused fields rather than accumulating them