🏷️ Custom Fields

When to use one

A few real examples:

• A restaurant tracking booking_date and party_size.
• A SaaS tracking plan_tier and renewal_date.
• A store tracking last_order_id and preferred_size.
• Anyone tracking birthday, city, or language.

Creating a custom field

1. Go to Settings → Custom Fields and click Add Field.
2. Give it a name (e.g. Booking Date) — we'll auto-create a key like booking_date you'll use in templates.
3. Pick a type:
   • Text — anything (a note, a code).
   • Number — for amounts, counts, sizes.
   • Date — for birthdays, expiry, appointments.
   • Dropdown — when you want to limit to a fixed list (e.g. plan: free / pro / enterprise).
4. Optionally mark it required if every contact must have it.
5. Save.

Filling in custom fields

Three places this happens:

• On a contact page — edit the contact and fill in the field directly.
• During CSV import — map a CSV column to your custom field on the mapping step.
• In a chatbot flow— a question or user-input node can save the customer's answer to a custom field.

Using custom fields in messages

In a template, you write variables like {{1}}. When you build a campaign, you map each variable to a value. Custom fields show up in that dropdown as custom:booking_date.

Template body:
"Hi {{1}}, your table for {{2}} is confirmed for {{3}}."

Mapping:
{{1}} → fullname
{{2}} → custom:party_size
{{3}} → custom:booking_date

Using custom fields in segments

Segments can also filter by custom field. For example: "plan_tier = enterprise AND renewal_date < 30 days" gives you a list of enterprise customers up for renewal.

Tips

• Keep keys short and lowercase. order_id beats OrderID-2.
• Add fields gradually. Start with what you need today; you can always add more.
• Renaming is easy. The key stays the same so templates keep working.

What's next

• Use them in messages → Templates
• Collect them automatically → Chatbots & Flows