Contact Fields

A complete reference for every field you can store on a contact, which fields are required, and how to format your data.

Overview

Volume Reach supports a set of standard fields for common contact information, plus custom fields for any data unique to your business. Understanding what each field does — and how to format it correctly — helps you get the most out of personalization and filtering.

Standard Fields

Phone Number (Required)

The phone number Volume Reach uses to place calls and send text messages. This is the only field that must be present for a contact to be imported.

Accepted formats:

Format	Example
E.164 (international standard)	`+15558675309`
US with country code, no plus	`15558675309`
US with dashes	`555-867-5309`
US with parentheses	`(555) 867-5309`
US digits only	`5558675309`

Volume Reach automatically normalizes any of these formats to the E.164 standard (+1XXXXXXXXXX for US numbers) when the contact is saved. You do not need to pre-format your list as long as the numbers are valid 10-digit US numbers or properly formatted international numbers.

Contacts with phone numbers that cannot be parsed as valid numbers are skipped during import.

First Name

The contact's first name. The AI agent uses this to open the conversation naturally — for example, "Hi Sarah, my name is Alex..." — which improves engagement.

Not required, but strongly recommended. Contacts without a first name receive a generic greeting.

Last Name

The contact's last name. Optional, but useful for your own reference and for use cases where the full name is read aloud (such as formal scripts).

Email

The contact's email address. Volume Reach does not send email outreach — this field is for your reference only, useful when your team follows up outside the platform or when you want to filter and identify contacts.

Standard email format is expected: name@domain.com.

Address

The contact's street address. Optional. Useful for real estate, home services, and other industries where property or location is relevant to the conversation.

City

The city portion of the contact's address. Can be used for geographic filtering and segmentation.

State

The state or province. Use standard two-letter US state abbreviations (e.g., TX, CA, FL) for best results with filtering.

Zip

The postal or ZIP code. Useful for local market segmentation and can be referenced by the AI agent in location-specific scripts.

Custom Fields

Beyond the standard fields above, you can bring in any additional data from your own systems by mapping CSV columns to custom fields during upload.

Custom fields can hold any text value. Common examples include:

Lead source — where the contact came from (e.g., Facebook Ad, Website Form, Referral)
Property type — relevant for real estate campaigns (e.g., Single Family, Multi-Family)
Loan amount — for mortgage or finance campaigns
Last contact date — a date from your CRM to inform prioritization
Interest level — a score or label from a previous qualification step

Custom field values can be used for filtering in the Contacts page and are available to personalize AI agent scripts if your campaign is configured to reference them.

Field Length Limits

All text fields accept up to 500 characters. Phone numbers are stored in normalized E.164 format regardless of how they are entered. If a value exceeds the character limit, it is truncated at import — no error is raised, so verify that long field values are not being cut off by checking the preview before confirming an import.

Tips & Best Practices

Normalize state values before import. Entering Texas in some rows and TX in others means filters treating state as a category will not work cleanly. Pick one format and stick to it.
Use custom fields for data you actively need. Every column you map takes up space in your contact record. Map only what you will use for filtering, personalization, or follow-up — leave irrelevant columns unmapped.
Phone number is the deduplication key. When re-importing a list, Volume Reach matches on phone number. If a contact's phone number changes, a new record is created rather than updating the old one.
International numbers need the + prefix. If you are importing non-US numbers, include the country code with a leading + (e.g., +442071838750 for a UK number). Numbers without a country code are assumed to be US.