Standard Contact Fields

27 built-in fields that define every contact record

Every contact in Zyntro has 27 standard fields. These are built-in — they cannot be removed, but any can be left empty. In addition to these, you can create unlimited custom fields for data specific to your business.

Some fields are purely informational (name, address). Others directly control platform behavior — timezone determines when SI sends, auto_engage controls whether SI processes the contact at all, and email_verified determines whether email is available as a channel.

Identity Fields

Field	Type	Description
salutation	String	Title prefix (Mr, Ms, Dr, etc.)
name	String	Full display name. Auto-generated from first_name + last_name if not provided.
first_name	String	Contact first name. Required for contact creation.
last_name	String	Contact last name.
primary_email	Email	Primary email address. Used as the default lookup key in upsert operations and the primary channel for email communication.
secondary_email	Email	Alternative email address.
primary_phone	Phone	Primary phone number. Required for SMS and call channels.
secondary_phone	Phone	Alternative phone number.

Location Fields

Field	Type	Description
address	String	Street address line 1.
address_line_2	String	Street address line 2.
city	String	City name.
state	String	State or province.
zip	String	Postal or ZIP code.
country	String	Country name.
country_code	String	Two-letter country code (e.g., US, MY, GB). Used for phone number formatting and regional compliance.
timezone	IANA Timezone	Critical for SI. Determines when SI sends messages (business hours enforcement), when Phona schedules calls, and how event times are displayed. Format: America/New_York, Asia/Kuala_Lumpur, etc. The contact detail view shows the current local time next to the timezone.

Relationship Fields

Field	Type	Description
acquisition_source	String	How the contact was acquired: Website Form, API Import, Card Scanner, Referral, etc. Used for source attribution reporting.
acquisition_date	DateTime	When the contact entered the system. Auto-set on creation.
status	Enum	Contact lifecycle status. Configurable via CRM settings (e.g., Active, Inactive, Prospect, Customer). Drives Contact Status mandates.
role_label	String	The contact’s role (e.g., Decision Maker, Influencer, End User). Helps SI tailor messaging to the contact’s authority level.

SI & Channel Control Fields

Field	Type	Description	SI Impact
auto_engage	Boolean	Enrolls the contact into Segmentation Intelligence.	When off, SI ignores this contact entirely. No scanning, no scoring, no outreach.
dnc	Boolean	Do Not Call flag. Prevents all outbound phone calls.	Removes phone/call as an available channel for SI.
email_optout	Boolean	Email opt-out. Contact has requested no email.	Removes email as an available channel for SI.
sms_optout	Boolean	SMS opt-out. Contact has requested no text messages.	Removes SMS as an available channel for SI.
email_verified	Boolean	Whether something claimed the email address was good when the contact was created. A provider's actual answer is stored separately — see Contact Verification.	This flag is set by imports and forms, so it is weak evidence. It does gate one real behaviour: when it is not set, the address is checked before every send.
phone_verified	Boolean	Whether something claimed the phone number was good when the contact was created. A provider's actual answer, including whether the number is a mobile or a landline, is stored separately.	Set on presence by most importers, so a contact can carry it while holding no number at all. SI may deprioritize phone channels.
verification_notes	String	Notes about verification status or issues.	Context for why verification may have failed.

Important: The five most impactful fields for SI effectiveness: timezone (when to send), auto_engage (whether to process), email_verified (email channel reliability), primary_phone (SMS/call channel availability), and status (drives Contact Status mandates that can pause or restrict all outreach).

5 min read Updated Oct 13, 2026