Custom fields for contacts

Custom fields are how you make Callaro match your business. They let you store the one thing your team always asks for (lead source, plan tier, property type, qualification score) and then use it in filters, segments, and agent variable mapping.

At a glance

• Custom fields define your contact schema beyond the standard fields.
• Custom fields can be used in:
  • import mapping
  • contacts filters
  • segments
  • campaign audience mapping
  • manual calling (agent variable mapping)

Field-by-field: what you can configure

Key

The key is the stable identifier used in mappings, segments, and APIs. Treat it like a database column name.

Label

The label is what operators see.

Field type

Custom fields can be typed (for example: text, number, date, boolean, enum). The UI renders different inputs based on type.

Required

Required fields should be used sparingly. If a field is required but not available in your source data, imports become painful.

Default value

Defaults are useful for fields with a common baseline.

Enum values (for enum fields)

Use enums when you want consistency (and predictable filtering).

How custom fields show up downstream

In Imports

You can map columns to custom fields (shown as cf:<key>).

In Contacts filters and segments

Custom fields appear as filterable attributes, and can become segment rules.

In campaigns and agent variables

There are two distinct patterns:

1. Store the value on the contact record (import/manual edit), then map contact fields into agent variables.
2. Map directly at campaign audience time (CSV mapping or segment mapping) into agent variables.

Use Contacts → Campaigns → Agent variables for the deep “how it passes” reference.

What good looks like

• Every custom field has an owner and a meaning.
• Operators can explain how the field affects script behavior.
• Segments use fields consistently across campaigns.