Team Inbox

Custom Profile Fields

Your data on the contact, wherever it came from.

A phone number and a name is not a customer record. Custom profile fields let you hold what your business actually needs to know — plan, renewal date, last order, city, licence number — on the contact, visible in the conversation and usable everywhere else in the platform.

Contact profile
Search conversations

James Carter

1

Any offer on the annual plan?

Customer

Riverside Clinic

Can we move the call to Thu?

New Lead

Nova Retail

Sharing the proposal now.

Contacted

Emma Doyle

Thanks, received it.

Customer

James Carter

WhatsApp · Northbridge Ltd

CustomerRenewalDubai
Any offer on the annual plan?
You are due to renew on 12 Oct — let me check.
Great, thanks.
Type a message
ContactZoho CRMSheet CRM
DetailsActivityFiles
PlanSelectGrowth
Renewal dateDate12 Oct 2026
Lifetime valueCurrencyAED 18,400
Last orderDate04 Jun 2026
OrdersNumber14
CityTextDubai
InterestsMultiOuterwear, Bags
Opted inBoolYes
Margin bandSelectB2

Field permissions

Plan · staff can edit
Renewal date · staff can edit
Lifetime value · view only
Margin band · admin only
Save contact

The detail that decides the reply lives somewhere else

An agent knows the answer depends on which plan the customer is on, when they last ordered, or which branch they belong to — and none of it is in front of them. So they ask the customer questions the business already knows the answer to, or they guess. Meanwhile marketing sends the same broadcast to everyone because there is nothing to segment on.

What you get

Every field type you need

Text, number, date, currency, dropdown, multi-select, checkbox, phone and URL. Define them once in settings and they appear on every contact.

Permissions per field

Decide field by field who may see it and who may change it — admin only, read-only for staff, or fully editable. Commercially sensitive values do not have to be visible to everyone in the inbox.

Filled from anywhere

Save answers straight from a chatbot flow, write them from your own systems over the API, or bulk import them from an Excel or CSV file through contacts.

Segmentation that means something

Build broadcast audiences on the values themselves — combining recency, spend, location or plan — instead of sending the same message to your whole list.

Settings · Custom fields

Custom fields

New field
FieldTypePermission
PlanSelectStaff edit
Renewal dateDateStaff edit
Lifetime valueCurrencyView only
Last orderDateView only
InterestsMultiStaff edit
Opted inCheckboxStaff edit
Margin bandSelectAdmin only

Permission is enforced in the inbox and over the API.

Define once in settings, applied to every contact

Fields are created centrally, with a data type that decides how they behave — a date field gets a date picker, a dropdown restricts the options, a currency field sorts and filters as a number. Each one also carries a permission, so you can expose what agents need and keep the rest to admins.

  • Text, number, date, currency, dropdown, multi-select, checkbox, phone, URL
  • Admin-only, view-only or editable, decided per field
  • The same definitions apply in the inbox, the API and imports
Where values come from

Chatbot block

Ask → save to field

REST API

PATCH /contacts/:id

Excel / CSV import

contacts-2026-06.xlsx

James Carter

PlanGrowth
Last order04 Jun 2026
Lifetime valueAED 18,400
CityDubai

One record, whichever source wrote the value.

Filled by the bot, your systems, or a spreadsheet

In a structured chatbot flow, a field is a block: ask the question, save the answer, move on. Your own systems can write to the same fields over the REST API — an online store pushing last order date and total spend, for instance. And anything you already hold can be imported in bulk from Excel or CSV through contacts.

  • A save-to-field block inside the chatbot builder
  • Third-party systems write over the REST API
  • Bulk import existing data from Excel or CSV
Audience builder

Win-back · high value, gone quiet

Last orderbefore90 days ago
and
Lifetime valueoverAED 5,000
and
Opted inisYes
and
CityisDubai
Contacts in this audience
1,284
Send broadcast

Same fields drive personalisation inside the message.

Audiences built on what you actually know

Because the values live on the contact, the audience builder can combine them. Win back shoppers who have not ordered in ninety days but have spent well. Catch renewals fourteen days out before they lapse. Send a Dubai-only promotion to people who opted in and have never bought outerwear. The segment is the query, not a list somebody exported.

  • Stack conditions across any custom field
  • Recency, spend, location, plan and consent in one audience
  • The segment recalculates as the underlying data changes

How it works

  1. 1

    Define the fields

    Create the fields you need in settings, pick each one's type and set who can view or edit it.

  2. 2

    Fill them automatically

    Capture answers in a chatbot flow, sync them over the API, or import a spreadsheet.

  3. 3

    Use them everywhere

    Read them in the inbox, personalise messages with them and build broadcast audiences from them.

Frequently asked questions

Put your data where the conversation is

Define the fields that matter to your business, fill them automatically, and stop sending one message to everybody.