Contacts

Contacts represent the people your agents will call. Each contact can have associated metadata that gets injected into conversations.

What is a Contact?

A contact stores:

Basic Info - Name, phone number, email
Metadata - Custom fields relevant to your use case
History - Previous conversations with this contact

Contact Properties

Property	Description
`id`	Unique identifier (UUID)
`workspaceId`	The workspace this contact belongs to
`firstName`	Contact’s first name
`lastName`	Contact’s last name
`phone`	Phone number in E.164 format
`email`	Email address
`metadata`	Custom JSON object with additional data
`createdAt`	When the contact was created
`updatedAt`	When the contact was last modified

Importing contacts

Click Import on the Contacts page to add contacts in bulk.

File types: CSV or Excel (.xlsx), up to 5MB.
Excel files: Nedzo reads the first sheet only. If it’s empty, you see “No rows found. Put the contacts on the first sheet.”
Up to 10,000 contacts per import.

After you upload, match each File Column to a contact field.

Contact timezone

Each contact has a Timezone field on the contact panel in Contacts. Workflow voice calls use it to keep calls inside your calling hours where the contact is. Nedzo fills it in when the contact is created, from their phone number. When the phone number does not show where the contact is, Nedzo fills in your workspace’s timezone instead. That zone is a placeholder, not a fact about the contact, so the field shows a warning:

Not confirmed. We copied this zone from your workspace. Workflow calls use the phone number’s zone, and skip this contact if the number has none. Campaigns use your workspace’s zone. Choose a zone, even this one, to confirm it.

To confirm it, search for and choose the contact’s timezone in the field. Choosing the same zone that is already there also confirms it. The warning goes away, and Nedzo trusts that zone from then on. You can also clear the field.

What the field shows	What happens on a workflow voice call
A timezone, no warning	Calls follow that zone
A timezone with the Not confirmed warning	Nedzo checks the phone number. If the number gives a zone, it uses it. If not, the call is skipped
No timezone set	Nedzo uses the phone number. If the number gives no zone, the call is skipped

Campaigns use their own rules. See Which timezone is used.

Phone Number Format

All phone numbers must be in E.164 format:

+[country code][subscriber number]

+14155551234

+447911123456

+525512345678

Using Metadata

Metadata lets you store custom data that can be used in agent conversations:

{
  "firstName": "John",
  "lastName": "Doe",
  "phone": "+14155551234",
  "metadata": {
    "accountNumber": "AC-12345",
    "preferredLanguage": "Spanish",
    "lastPurchaseDate": "2024-01-15",
    "vipStatus": true
  }
}

These values can be referenced in your agent’s system prompt using {{contact.customFields.<fieldName>}} syntax.

Custom fields

Custom fields are workspace-level fields that show up on every contact. Define them once in Settings > Workspace > Custom fields & Tags and they appear on the Contacts page and in workflow conditions.

Field types

Each custom field has a type that controls how it’s stored, validated, and rendered in the dashboard.

Type	Stored as	Contacts page input	Use for
Text	string	Single-line text input	Account numbers, notes, identifiers
Number	number	Numeric input (digits, decimals, negatives)	Budget, quantity, score
Date	ISO 8601 date string (`YYYY-MM-DD`)	Date picker	Renewal date, last contact, birthday
Boolean	true/false	Toggle / checkbox	VIP, opted-in, qualified

The type is set when the field is created and can’t be changed afterwards. Delete and re-create the field if you need a different type. Before you delete a field, Nedzo shows how many contacts have a value in it.

Where field types apply

Contacts page — the cell renders the right input for the type. Number cells reject non-numeric input, date cells open a calendar picker, boolean cells show a toggle.
Filters — date fields support Before, After, Equals, and In Between operators (see Condition action → Operators). Number fields support numeric comparisons. Text fields support Does not equal, Does not contain and Is empty, and these work on any number of contacts. Booleans support Is / Is not with Yes or No. Is No also matches contacts with no value in the field.
Workflow conditions — the same operators are available when a custom field is referenced inside a workflow.
API and integrations — custom field values are returned in their typed form on agent webhooks and the contact APIs.

In agent prompts

Reference any custom field in a prompt or opening line:

Hi {{contact.firstName}}, I see your renewal is on {{contact.customFields.renewalDate}}.

Filtering by tag

The Tag filter has two modes. Has all of shows contacts that have every tag you pick. Has none of shows contacts that have none of them, so you can leave out a tag.

Starting a workflow for contacts

Select contacts on the Contacts page, then click Add to workflow in the bulk bar. Only workflows that use the Manual trigger are listed, and each must be published and turned on.

Saved views

Save the filters and sort you use most often as a named view. Each view is a preset of filters, sort order, and visible columns on the Contacts page — pick one from the view switcher and the page reconfigures instantly. Built-in views:

All Contacts — every contact in the workspace, no filters, default sort. Always available, can’t be deleted.

Creating a view:

On the Contacts page, set the filters, sort, and columns you want.
Click the view switcher and choose Save as view.
Give the view a name and save.

Saved views are workspace-scoped — anyone in the workspace can use them. Update or delete a view from the same dropdown. Views you create persist across sessions and devices. Common patterns:

New leads this week — filter by tag lead + created within the last 7 days
Renewals due — filter by custom date field renewalDate between today and end of month
Opted-out contacts — filter by SMS opt-out status to audit compliance

Get Started

Unibox

Agents

Telephony

Workflows

Campaigns

Billing

Settings

Integrations

Contacts

Contacts

What is a Contact?

Contact Properties

Importing contacts

Contact timezone

Phone Number Format

Using Metadata

Custom fields

Field types

Where field types apply

In agent prompts

Filtering by tag

Starting a workflow for contacts

Saved views

API Operations

​Contacts

​What is a Contact?

​Contact Properties

​Importing contacts

​Contact timezone

​Phone Number Format

​Using Metadata

​Custom fields

​Field types

​Where field types apply

​In agent prompts

​Filtering by tag

​Starting a workflow for contacts

​Saved views

​API Operations

Contacts

What is a Contact?

Contact Properties

Importing contacts

Contact timezone

Phone Number Format

Using Metadata

Custom fields

Field types

Where field types apply

In agent prompts

Filtering by tag

Starting a workflow for contacts

Saved views

API Operations