Contacts & CRM
Creating custom fields for contacts
4 minutes read time Difficulty: intermediate
Creating custom fields for contacts
Custom fields let you store any additional data about your contacts beyond the default fields.
Default fields vs custom fields
Default fields (built-in):
- Name, Phone, Email
- Tags, Lifecycle Stage
- Assigned Agent, Source
Custom fields (you create):
- Company name, City, Order ID
- Subscription plan, Birthday
- Any data specific to your business
Creating a custom field
- Go to Settings → Custom Fields
- Click "New Field"
- Configure:
- Field Name — Display name (e.g., "Company Name")
- Field Key — System key, auto-generated (e.g.,
company_name) - Field Type — Choose the data type
- Required — Whether this field must be filled
- Options — For Select/Multi-select types, define the choices
- Click Save
Field types
| Type | Use for | Example |
|---|---|---|
| Text | Short text values | Company name, City |
| Number | Numeric values | Order count, Revenue |
| Date | Date values | Birthday, Subscription date |
| Boolean | Yes/No values | Is VIP, Has opted in |
| Select | Single choice from options | Plan (Free/Growth/Scale) |
| Multi-select | Multiple choices | Interests (Product A, B, C) |
Setting custom field values
On a contact
- Open the contact
- Scroll to the Custom Fields section
- Click on a field to edit its value
- Save
During CSV import
Include custom field keys as column headers in your CSV:
phone_number,name,company_name,city,plan
+919876543210,John Doe,Acme Corp,Mumbai,Growth
+919876543211,Jane Smith,Tech Inc,Delhi,Scale
Via API
PUT /api/contacts/{id}/custom-fields
{
"company_name": "Acme Corp",
"city": "Mumbai",
"plan": "Growth"
}
Using custom fields in segments
Custom fields can be used as filter conditions:
- "City equals Mumbai" → All Mumbai contacts
- "Plan equals Growth" → All Growth plan customers
- "Birthday is today" → Birthday greetings campaign
Using custom fields in templates
Reference custom field values in chatbot responses or campaign personalization using the field key.
Tips
- Plan ahead — Define fields before importing data
- Use Select types — For fields with limited options (prevents typos)
- Keep it minimal — Only create fields you'll actually use for filtering or personalization
- Consistent naming — Use snake_case for keys (auto-generated)
- Order matters — Set display order to show important fields first
Limits
- Maximum 50 custom fields per organization
- Text fields: max 500 characters
- Select options: max 50 per field
Related Articles
Was this guide helpful?
Your feedback helps us make these guides better for everyone.