Skip to content
AISARAISAR
All articles

Custom fields of a contact and a conversation

How to keep what matters to your business on the contact and conversation cards: city, order number, deadline, inquiry reason. Creating fields, types, filling them in chat, filters, scenarios, broadcasts, the AI employee and import.

What it is and why

Custom fields extend the standard contact data (name, phone, email, company). A contact field describes the person: lead source, city, a child's birthday. A conversation field describes one inquiry: the reason, order number, deadline. Values show on the card, and you can search and sort contacts by them, build segments and broadcasts, and use them in messages and scenario conditions.

Who can create fields

  • Administrators and managers can create, edit, reorder and archive fields.
  • Only an administrator can delete a field permanently.
  • Contact values can be filled in by people who may edit contacts, and by employees who have the separate right to fill in contact fields (the Agent role has it too). Conversation values are filled in by those who may edit conversations.

Step 1. Create a field

  1. Open "Settings", the "Custom fields" section. There are two tabs on top: "Contact" and "Conversation". Pick what the field belongs to.
  2. Click "Add field". If there are no fields yet, examples are offered ("Source", "City", "Inquiry reason", "Order number", "Deadline"): you can start with them.
  3. Enter a name and pick a type. For lists, add the options. The optional hint is shown to the operator under the field name.
  4. Save. The field appears on contact or conversation cards, and you can set the order of the fields by dragging in the table.

Every field has a key: Latin letters, digits and "_". AISAR suggests it from the name. The key is used in scenarios and the API and never changes after saving, just like the field type. If you need a specific key, set it on creation.

Field types

TypeWhat it stores
StringShort text up to 1000 characters.
Multi-line textLong text up to 10,000 characters. The contact list shows the beginning.
NumberA number, with decimals if needed (the field settings say how many digits to show).
DateA calendar date.
ListOne option out of predefined ones.
Multi-listSeveral options out of predefined ones.
CheckboxYes or no.
LinkAn address starting with http:// or https://.
PhoneA phone number, saved in international format.
EmailAn email address.

List options and the archive

A list option cannot be removed in a way that loses values: it goes to the archive. On contacts where it is already chosen the value stays (marked "archived"), but it cannot be chosen again. You can bring the option back from the archive in the field window.

The field itself is archived first as well. An archived field disappears from cards, filters and pickers, but the values on contacts stay and the field can be restored with "Restore from archive" (the "Show archived" switch above the table). If the field is used in scenarios, segments, AI employees or broadcasts, AISAR shows exactly where before archiving and, after you confirm, switches it off in those places. "Delete forever" is available only for an archived field that is used nowhere, and wipes all its values for good.

Filling in chat and on the card

  • In chat, open the right-hand panel: contact fields are in the "Fields" section, conversation fields in "Conversation fields". A value is saved when you leave the field or press Enter, and Esc cancels; in multi-line text you can save with Ctrl+Enter or by clicking outside the field.
  • Contact fields are also in the "Contacts" section: on the contact card and in the edit form.
  • To clear a value, click "Clear" in the field.
  • Under the value you can see who changed it last, when, and where the change came from: operator, scenario, AI, import, API, contact merge.
  • One card has a total limit on the volume of its custom field values. If you hit it, AISAR says the card holds too much text: shorten the longest values.

Filters and sorting in "Contacts"

In the contact list, add a "Custom field" filter: choose the field, the condition and the value. Conditions depend on the type: a string has "equals", "contains", "starts with", "is filled"; a number and a date have "greater than", "less than", "between"; a list has "equals" and "in list"; a multi-list has "includes"; a checkbox has "yes" and "no". You can apply up to five custom field filters at once, and they work together (a contact must match all of them). Custom field columns can be shown in the table and sorted: empty values always go last. Multi-line text and multi-lists cannot be sorted. The same filters apply to the contact export.

For lasting selections, create a segment with a "Custom field" condition: it comes in handy for broadcasts. If the field is archived later, such a condition stops selecting contacts instead of widening to the whole base; choose another field to save the segment.

Scenarios

  • The triggers "Contact field updated" and "Conversation field updated" start a scenario when a value changes. A condition lets you narrow it to a specific field.
  • The action "Update contact field" writes a value into a custom field of the contact or the conversation. If the field is archived or the value does not fit the type, the step is skipped and the scenario goes on.
  • Variables in messages and conditions: {{contact.custom.<key>}} for a contact field and {{conversation.custom.<key>}} for a conversation field. The value is substituted in readable form: the option name for a list, the date for a date, "Yes" or "No" for a checkbox. An empty field gives an empty string. The editor lists the variables, pick them from the hint.
The "field updated" trigger fires whatever the source of the change, including when the AI employee wrote the value from the client's words. Do not tie automatic discounts, payouts or other irreversible steps to such a field without a human check: a client can tell the AI anything.

More on variables and buttons: scenario variables; scenario basics: scenarios in plain words.

Broadcasts

In a broadcast text and in template variable bindings, contact fields are available as {{custom.<key>}}: they appear in the variable list marked "Custom field". The test message substitutes a sample value, and a real send takes the value from each recipient's card. Conversation fields are not used in broadcasts. Recipients can be selected by custom fields with a segment.

More on broadcasts: how broadcasts work.

AI employee

The AI employee has two independent kinds of access to custom fields, both off until you switch them on.

  • Reading. The field window has a "Visible to the AI employee" switch, off by default. When on, the AI sees the value in the contact or conversation summary and can rely on it in replies. Fields without the mark are invisible to the AI.
  • Writing. In the settings of the "Save name and contacts" tool the AI employee has a list "Custom fields it may fill in". The AI writes only the fields ticked there. The "Only empty fields" option forbids overwriting values that are already filled.

We recommend enabling reading and writing only for fields the AI really needs. If a field is used by an AI employee, AISAR warns about it when you archive the field.

Voice agent

The voice agent that answers calls also works with contact custom fields, and its access is configured separately from the text AI employee.

  • Reading. If your company has fields marked "Visible to the AI employee", the voice agent receives their values on its own: they go into the customer data block of its instructions. There is no need to type them in by hand. Hidden fields are not passed to the agent. For agents that are already set up, the block appears after the next save of the agent or after you change a field marked "Visible to the AI employee".
  • Writing. In the voice agent settings, on the "Voice" tab, there is a card for choosing the contact custom fields the agent may fill in. If the list is empty, the list from the "Save name and contacts" tool of the linked AI employee applies.

The voice agent fills only empty fields. The caller is recognised by phone number, and a number can be spoofed, so the voice agent never overwrites a value that is already filled.

CSV import

On the column mapping step choose "Custom field" for a column and pick which contact field to write to. One field can be tied to only one column. Dates can be written as DD.MM.YYYY or YYYY-MM-DD, a checkbox as "yes", "no", 1 or 0, and several multi-list values are separated by ";" or a comma. Values that are not in the list are skipped: the import never creates new options, so add the options to the field first. An unreadable value is skipped with a warning and the rest of the row is imported. If a column header matches the name of your field, AISAR suggests the mapping itself.

More on import: importing contacts from CSV.

Sensitive data

Do not keep in custom fields what you can do without: personal tax IDs, passport and document numbers, payment details, medical information. Which customer data you collect and how you protect it is up to your company, and the responsibility is yours. Field values are visible to everyone with access to the card, end up in exports, webhooks and your integrations, and, with "Visible to the AI employee" on, are passed to the AI. If you cannot do without such data, create the field without that mark and limit the circle of employees.

Limits

  • Up to 100 active fields separately for contacts and for conversations; archived ones do not count.
  • Up to 200 options per list; field and option names up to 100 characters, the hint up to 500.
  • For working with fields from other systems there is an API: the Custom fields group.

If something does not work

What you seeWhat to do
No "Add field" button, a note on top says only administrators and managers can change fieldsAsk a company administrator to give you a suitable role or to create the field.
"The limit of 100 active fields is reached"Move fields you no longer need to the archive.
"This key is already taken"The key is unique among all fields of this type, archived ones included. Pick another.
A value does not save: "Check the value format"A date must be real, a link must start with http:// or https://, a phone and an email must be valid.
"This field no longer exists"The field was archived or deleted while you were editing the card. Refresh the page.
The "Update field" action is skipped in a scenarioCheck that the field is not archived and the value fits the type (for example, a date in a clear format).