The numeric phone number of the record.

The length of the phone number will vary by the CountryCode used. Please do not include CountryCode within the Phone field.
Size Range: 9,10

The postal code or regional code for the record.

Size Range: 5,6
This allows us to target the record by time zone.

The abbreviation for the state or region depending on country code.
The full state name is accepted as well.

The record's first name.

It is important to include the records first name as it can be included in SMS message templates.

The records last name.

The record's associated email address.

Your internal ID associated with the current record.

A phone number to send this record to upon transfer.

While all projects have default settings for call transfers, you can specify a specific DID for individual records. If you provide a DID at the record level, it will always override the project's default settings.

Size Range: 9,10

A phone number to send this record to upon transfer from an inbound action.

Like DID, you can also specify a new InboundDID specifically for if they call inbound vs us placing an outbound call.

Size Range: 9,10

Drive to Site Projects Only
This is the URL specific to the endpoint you would like us to drive users back to. The Long URL must be posted within a record on insert.

Allowed Values: 1000 character limit.

This will show the full results of the operation requested.

In order to utilize async call responses (Webhooks), you need to store the token returned in the original response.

You can categorize records into different groups for more granular reporting. To maintain data integrity and simplify analysis, limit the number of unique subgroups.

Avoid using values in subgroups that are specific to individual records, like unique campaign IDs. Excessive variation in these fields can hinder reporting accuracy. We recommend limiting subgroups to no more than 10 distinct values. If you need more options, refer to our documentation on custom fields.

A value used for categorizing records for detailed reporting.

Avoid using values in subgroups that are specific to individual records, like unique campaign IDs. Excessive variation in these fields can hinder reporting accuracy. We recommend limiting subgroups to no more than 10 distinct values. If you need more options, refer to our documentation on custom fields.

A value used for categorizing records for detailed reporting.

Avoid using values in subgroups that are specific to individual records, like unique campaign IDs. Excessive variation in these fields can hinder reporting accuracy. We recommend limiting subgroups to no more than 10 distinct values. If you need more options, refer to our documentation on custom fields.

A value used for categorizing records for detailed reporting.

Avoid using values in subgroups that are specific to individual records, like unique campaign IDs. Excessive variation in these fields can hinder reporting accuracy. We recommend limiting subgroups to no more than 10 distinct values. If you need more options, refer to our documentation on custom fields.