Create and verify a customer custom field
Create a Pixie CRM customer custom field with live clicks. Set its record type, name, input type, display order and administrator-only visibility, then reopen the field to verify the saved definition.
Give each field a reason to exist
Start with the decision or action the information supports. Choose a clear label and the most suitable field type, then explain what a good answer looks like. Controlled options can make reporting more consistent, while free text is useful when the detail genuinely varies. Decide which fields are required at each stage rather than demanding information before a person can reasonably know it.
Keep the data model manageable
Assign an owner to review field definitions and remove unnecessary duplication. A sales team and a support team may use different words for the same information; resolve that before creating two fields. Consider imports, exports, templates and integrations when changing a field, because other workflows may depend on it. Sensitive information needs an appropriate purpose and access boundary. Test a new field with real examples and check how it appears in the reports people use.