# Custom Fields (/docs/guides/reference/custom-fields)



Custom fields extend the customer record with whatever your agency tracks
that careCycle does not have a column for. Define them once at **Settings >
CRM Settings > Custom Fields** and they behave like native fields across the
platform. You'll find each customer's values on their profile under **Notes &
Docs > Custom Data**.

Defining a Field [#defining-a-field]

| Setting               | Notes                                                                                                                            |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Field Label**       | Unique name, up to 255 characters                                                                                                |
| **Field Description** | Required. The AI uses it to populate the field automatically from customer conversations, so describe exactly what belongs in it |
| **Field Type**        | Text (with max length), Number (min/max), Boolean, Date, Select (with options), or Multi-Select (options plus max selections)    |
| **Required Field**    | Marks the field required where it is collected                                                                                   |

Where Custom Fields Show Up [#where-custom-fields-show-up]

* **Customers list**: as optional columns via Manage columns.
* **Calls list**: as columns alongside call data.
* **Scripts**: insert them like any field so agents capture them
  mid-conversation ([Scripts](/docs/guides/campaign-toolkit/scripts)).
* **Automation filters**: filter enrollment on custom field values, with
  operators matched to the field's type
  ([reference](/docs/guides/reference/automation-triggers-and-filters)).
* **Scripts and texts**: every field has a key (shown in the **Key**
  column) that you can drop into an SMS or an AI script as a variable, like
  `{planChanges2027}`. Use **Insert variable** in the SMS editor to pick one.
* **Pulse routing**: a Routing step can branch on a custom field's value.
* **API**: full CRUD on definitions and per-customer values
  ([API reference](/docs/api-reference)).

The AI-description detail is the part teams miss: a well-described custom
field fills itself from calls, which turns "we should really track that" into
a column that populates on its own.

<Callout type="warn">
  The key is generated from the label. If you rename a field, its key changes
  too, and any text or script using the old key stops filling in. Rename with
  care.
</Callout>

Some features create fields for you. The [Plan
Crosswalk](/docs/guides/aep-2027/plan-crosswalk) adds **Plan Changes
2027** and **Plan Changes 2027 Details**, which the AEP campaign's AI reads on
every call.

<Cards>
  <Card title="Scripts" href="/docs/guides/campaign-toolkit/scripts">
    Capture custom fields during live calls.
  </Card>

  <Card title="Automation Triggers and Filters" href="/docs/guides/reference/automation-triggers-and-filters">
    Enroll customers based on custom field values.
  </Card>
</Cards>