Contacts
Manage customer contacts, accounts, attributes, events, and lead records in Nexvio.
Contacts
Contacts are team-scoped records for the people and accounts that interact with agents in a team.
Contact records
Nexvio contact services support contact CRUD, account relationships, custom attributes, search, contact events, and email-domain helpers.
Custom attributes
Every contact carries a set of built-in fields — name, email, phone, company, tags, timezone,
source, and assigned owner. Beyond these defaults, each team can define its own custom
attributes to track information specific to their business (for example, plan_tier or
renewal_date).
Custom attributes support the following types:
| Type | Description |
|---|---|
text | Free-form text. |
email | Email address. |
phone | Phone number. |
number | Numeric value. |
date | Date value. |
boolean | True/false toggle. |
select | A single value chosen from a fixed list of options. |
Each attribute has an id, name, type, and display label, and can optionally be marked
required, given a placeholder, and (for select attributes) a list of options. Values you
save for a custom attribute are stored in custom_fields on the contact and returned alongside
the built-in fields whenever the contact is read. The Public API stores these values without
enforcing the attribute's type, required flag, or select options, so integrations should validate
them before saving.
Default attributes (name, email, phone, company, address, timezone, tags) can each be toggled on or off per team without deleting the underlying data.
Custom attributes are created, updated, and listed through the Public API — see the Contacts API guide for the full request/response reference and curl examples.
Lead collection
When built-in lead tools are enabled on your deployment, lead collection actions can create or update contacts from widget conversations. Use this when an anonymous visitor provides contact information during a conversation.
Identity linking
For logged-in users, use identity verification to associate conversations with stable user IDs and known contact data.