Create Custom Data Definition Page

Required security profile permissions: Calling List Edit

To enable multi-number support or add complexity to your calling lists, you can create custom data definitions to your system. From there, you can map calling lists to the custom fields so the system can recognize and track the fields for you.

The page provides additional options when you select Phone or SMS Phone from the Type drop-down. These options are shown in the second of the following images.

Field Name
The unique name of the custom data definition.
Type
The type of field you want to create. Valid options include the following:
  • Boolean — The only valid values for the field are True and False. They are not case-sensitive. This is a good option for a field that specifies compliance.
  • Date — The only valid values for the field are dates.
  • Decimal — The only valid values for the field are numbers. The numbers may, but do not have to, include decimals.
  • Integer — The only valid values for the field are numbers, but they cannot be decimals.
  • Value String — The field can contain any value. This is a good option for a field that asks for a description.
  • Email — The only valid values for the field are email addresses. This option does not appear unless Proactive Email is enabled for your business unitHigh-level organizational grouping used to manage technical support, billing, and global settings for your NICE inContact environment.
  • Phone — The only valid values for the field are telephone numbers.
  • Phone — The only valid values for the field are telephone numbers. This option does not appear unless Proactive SMS is enabled for your business unit.
Caller ID
Available for fields with Type set to Phone or Phone.

Sets another custom field as the caller ID, or number that contacts see as the company phone number when they receive a call or text. To create a caller ID field with custom data definitions, you must create a Value String field and set the value to a phone number.

Value Required
Available for fields with Type set to Boolean, Date, Decimal, Integer, or Value String.

Specifies that, if you map this field to a calling list, every contact in the calling list must have a value for this field. Selecting Value Required disables the Default field, so any contacts with null values in the corresponding column fail the list processing step of the calling list upload process.

Default

Available for fields with Type set to Boolean, Date, Decimal, Integer, or Value String.

Sets a default value for the field. When a calling list does not specify a value for the field, Personal Connection (PC) automatically applies the value provided here.

Attempts

Available for fields with Type set to Phone.

Associates the value with a column in the dialing list that contains a number value representing a maximum number of times the dialer should attempt to dial the number before retiring it.

Compliance

Available for fields with Type set to Phone.

Links the phone number to a compliance field. You can select Compliance Required to require compliance, or you can create a custom field with a Type of Boolean which you link to the phone number. For example, if you are creating a custom field called WorkPhone, you might also want to create a field called WorkPhoneCompliance that handles the compliance for work numbers on a per-record basis.

Description

Available for fields with Type set to Phone or Email.

Associates a column in the dialing list with a text description of the phone number or email address field. For example, in that record in your contact list, you might want to provide text to note that a phone belongs to the contact's spouse.

Start Time
Available for fields with Type set to Phone, SMSPhone, or Email.

Sets another custom field for the start time in the allowable contact time range for the phone number or email address. To create a start time field with custom data definitions, you must create an Integer field and set the value to the number of minutes after midnight that you want PC to start attempting to reach the phone number or email address. For example, to set the start time to 8:00 AM in each record's respective time zone, you would create a new Integer Type custom field definition and set the value to the number of minutes past midnight that 8:00 AM is, or the value of 8*60: 480.

End Time
Available for fields with Type set to Phone, SMSPhone, or Email.

Sets another custom field for the end time in the allowable contact time range for the phone number or email address. To create an end time field with custom data definitions, you must create an Integer field and set the value to the number of minutes after midnight that you want the dialer to stop attempting to call, text, or email the phone number or email address. For example, to set the end time to 12:00 PM in each record's respective time zone, you would create a new Integer Type custom field definition and set the value to the number of minutes past midnight that 12:00 PM is, or the value of 12*60: 720.

Constraints
Available for fields with Type set to Phone and Phone.

Sets the default allowable calling or texting contacts. You can create different windows for weekdays and weekends, and each one can have multiple time ranges. Because these constraints set the default calling time ranges, the system does not honor defaults set for fields you might have selected for the Start Time and End Time.

Related Tasks