What are Contact Fields?

Contact fields define the additional data you can store on every contact's profile. Besides the built-in fields (name, phone number, email, Instagram, Messenger, tags), you can create custom fields to capture any information your team needs — company name, subscription plan, customer ID, and more.

Built-in Fields

Every contact automatically has these built-in fields that cannot be removed:

• Name — The contact's display name
• Phone Number — Primary phone number (required)
• Email — Email address
• Instagram — Instagram username
• Messenger — Facebook Messenger ID
• Tags — Labels for segmentation

Adding Custom Fields

Navigate to Workspace Settings → Contact Fields. Click "Add field" or use "Use defaults" to create common fields automatically.

When creating a field, you define:

• Label — Display name shown on the contact profile (e.g., "Company Name")
• Key — Machine-readable identifier, auto-generated from the label (e.g., "company_name")
• Field type — Determines the input type: Text, Number, Date, Yes/No, Dropdown list, URL, Email, or Phone
• Description — Optional tooltip explaining the field
• Placeholder — Hint text shown in the empty input
• Required — Whether this field must be filled when creating a contact
• Sort order — Controls display position (lower = higher)

Dropdown List Fields

When you select "Dropdown list" as the field type, you can define a set of allowed values. Type an option and press Enter or click + to add it. Users will select from these options when filling in the field.

Managing Fields

For each field you can:

• Edit (pencil icon) — Update label, description, type, or settings
• Hide (eye icon) — Remove from contact profiles without deleting. Data is preserved.
• Delete (trash icon) — Permanently remove the field definition. Existing data on contacts is NOT deleted.

System fields (created via "Use defaults") cannot be deleted, only hidden.

Default Fields

Click "Use defaults" to automatically create 10 commonly used fields:

• Company, Job title, City, Country, Date of birth, Gender, Language, Website, Notes, Customer ID

Fields that already exist (same key) will be skipped.

Tips

• Use clear, descriptive labels so your team knows what to fill in
• Keys must be unique — two fields cannot have the same key
• Hidden fields retain their data and can be re-activated at any time
• Use dropdown lists for fields with a fixed set of values (e.g., subscription plans)