This article covers how the WPResidence real estate CRM organizes the fields you see on Contact and Lead forms — what types exist, how they are grouped, and how to customize the values behind dropdown pickers.

What “Custom Fields” Means in This CRM

In the current release, fields are predefined in code rather than user-configurable. The CRM ships with 31+ contact fields and 6 lead fields, each with a specific type, label, and storage column. What is customizable:

• The values inside dropdowns (picklists) — lead source list, deal stages, task types, etc.
• Whether a field appears as read-only or editable based on context.

Administrators edit the picklist values in CRM Settings.

Supported Field Types

Type	Used for
Input	Short text (names, email, phone, address)
Textarea	Long text (notes, messages)
Picklist	Dropdown selection from a settings-driven list
Date	Date values (formatted per site settings)
Number	Numeric values (prices, bedrooms)
Taxonomy	Reference to a WordPress taxonomy term
Post type	Reference to another post (e.g., an agent or a listing)
Content	Read-only display of HTML content (used for legacy messages)

Field Sections on the Contact Form

Contact fields are grouped into seven logical sections:

1. Personal Info — prefix, first name, last name, date of birth.
2. Contact Info — email, mobile, phone, home phone.
3. Address — street, city, county, state, zip, country.
4. Social Profiles — Twitter, LinkedIn, Facebook.
5. Lead Info — lifecycle stage, lead source, lead type, status, assigned agent, tags.
6. Buyer Preferences — price range, bed range, bath range, area range, preferred locations and property type/status.
7. Notes — private note field.

Read-Only vs Editable

The field renderer has two modes:

• Edit mode — shown on Add/Edit forms, renders an actual input for each field.
• Read-only mode — shown on detail pages, renders a formatted display value.

This is why the contact detail page looks different from the edit form even though both show the same data.

Formatting Behavior

The read-only renderer applies type-specific formatting:

• Numbers are locale-formatted (thousand separators per your site’s locale).
• Dates use your site’s date format.
• Empty values show the Empty Value Text setting — default dash (—) — so the page never looks broken.
• Taxonomy fields show the term name (not the slug).
• Post-type fields show the post title and link to the post.

Customizing Picklist Values

Picklist values are edited in CRM Settings by an administrator. Comma-separated lists make it easy to add, rename, or remove values. Any field anywhere in the CRM that pulls from that picklist updates instantly.

Adding Truly Custom Fields

Adding a brand-new field (a new column in the database) is currently a developer task. See the developer version of this article for how to add columns and extend the field-renderer mapping.

Best Practices

• Use the existing fields before thinking about new ones.
• Use tags for ad-hoc classification — that’s what they are for.
• Keep picklist values short and stable. Renaming a picklist value after production use breaks old records that reference the old value.