Custom Contact Fields
Mobile Message allows you to add up to 5 custom data fields to your contacts. You can name these fields anything you like and use them to store additional information such as dates, membership IDs, departments, or any other data relevant to your contacts.
Setting up custom fields
To configure your custom fields:
- Go to Contacts > My Contacts
- Click the Manage Fields button
- Enter a name for each field you want to use (for example, "Date of Birth" or "Department")
- Click Save Changes
Fields with a name will appear as columns on your contacts table, in your add/edit contact forms, and as template variables when composing messages. Fields left blank are hidden.
Field name rules
Field names can contain letters, numbers, spaces, hyphens, and underscores. They cannot use the same name as a built-in field (such as "first_name" or "company").
Using custom fields in messages
When you name a custom field, a template variable is automatically created for it. The variable uses the field name in lowercase with spaces replaced by underscores.
For example:
| Field name | Template variable |
|---|---|
| Date of Birth | {date_of_birth} |
| Department | {department} |
| Member ID | {member_id} |
You can also use the generic format {field_1} through {field_5}, which always works regardless of the field name.
Inserting variables in messages
When composing a message on the Send Messages page:
- Click the Add Tags dropdown
- Your custom fields will appear alongside the built-in fields (First name, Last name, etc.)
- Click a field name to insert it into your message
The variable will be replaced with each contact's data when the message is sent.
Custom fields in imports and exports
Importing
When importing contacts from a CSV, Excel, or VCARD file, your custom fields appear as additional column mapping options. If your spreadsheet has a column header that matches a custom field name, it will be auto-detected.
Exporting
When exporting contacts, custom fields are included as additional columns in the CSV file. The column headers use your custom field names.
Custom fields also appear in message history exports, showing the contact data for each message recipient.
API support
Custom fields are supported in the API:
- POST /v1/contacts and PATCH /v1/contacts accept
field_1throughfield_5 - GET /v1/contacts returns
field_1throughfield_5in results and supports filtering - POST /v1/list-send supports custom field template variables in message content