Data type directory

      Data Type Directory

      Data types are used to let the system know what sort of data to expect in the specific field. Some data types will be validated as well. The data type “E-mail”, for example, will be checked to have the format “[name]@[domain].[top domain]” (i.e. info@herobase.com).

      Data types are added as the need arises in the Hero Applications. Sometimes a new data type replaces an old one and, in these cases, we maintain the old data type for legacy reasons and don't remove it until we are absolutely sure that there are no customers using it in any context.

      Some data types can be expected to hold “sensitive data” and should be treated according to the rules of GDPR. These fields are either named “Sensitive” or marked with an asterisk. Help articles concerning “Automatic deletion of lead data” can be found in this Help portal by searching for “GDPR”, for example.

      Data types currently supported in the Hero Outbound Campaign Templates:

      • Text (Small field): Simple box that can hold 1 line of text.
      • Text (Large field): Larger box covering 10 lines of text. If you enter more than 10 lines of text, a scrollbar will appear
      • Time (hh:mm): A box where time can be entered. The format is validated to be “hh:mm”
      • Date (dd/mm/yyyy): A box that can hold a date in the default format indicated in the parenthesis. Note that there is an option to change the expected format to something that fits your needs/culture. This change can be done for all data types where a date is expected
      • Date/Time (dd/mm/yyyy hh:mm): A box that can hold a date and time in the format indicated. Note that there is an option to change the expected format to something that fits your needs/culture
      • Number: A box where a number without decimals are accepted. The technical data type is “Integer which means that accepts values between -2147483647 and 2147483648
      • Decimal number: A box that can hold numbers with decimals. The technical data type is “Float” which means that it accepts values between 1.175494351 E –38 and 3.402823466 E +38
      • Checkbox: A small box that can be ticked or unticked (corresponding to “True” or “False”)
      • Phone number: This field is one of the mandatory fields for any lead upload. Fields with this data type are used to dial the lead. At least one field of this data type is necessary in order to save your campaign template. The field is validated depending on the country you are going to call to. If you want to be absolutely sure that you are not calling invalid numbers for your country, you should upload the phone numbers in international format (including the country code)
      • E-mail: A box that accepts and validates correct e-mail addresses
      • Picklist: This type of field is also known as a “DropDown menu”. In the configuration of this data type, you can enter a number of options that the agent can choose from by clicking the menu.
      • Priority: Obsolete. The data type is still maintained for legacy reasons but is replaced by the setting “Lead pool priority” for the campaign template
      • Number (4 digits): A box that validates numbers to be exactly 4 digits
      • Original Lead Owner: A box that shows the Name of the user/team assigned as Lead Owner when the lead was created/uploaded
      • Notes: A box that accepts 1 line for text. It looks the same as “Text (Small field)” but it is treated as notes on, for example, exports of Lead- and Result data
      • National ID number: This field holds the personal ID-number. It is not just any number as it is expected to hold sensitive data. 
      • Bank code (4 digits): Most banks have a country unique “clearing number” which is used before the account number to identify the bank. Similar to the personal ID, this data type is expected to hold sensitive data and should, therefore, be treated separately
      • Is not empty: validates that a field is not empty and returns True or False
      • Bank number (6. 7. 10): A box that is meant to hold the account number to the lead’s bank account. This is, of course, sensitive data and should, therefore, be considered sensitive
      • Date (yyyy-mm-dd): Same as Date (dd/mm/yyyy) but with a different default order of the day, month and year
      • CPR/CVR number: A box that holds either the personal ID number or the company’s registration number. Validates according to Danish standards
      • Revenue: This data type generates a number field that is used for reports or Score Boards where the revenue of a success is calculated
      • Profit: This data type generates a number field that is used for reports or Score Boards where the Profit of a success is calculated
      • Commission: This data type generates a number field that is used for reports or Score Boards where the Commission of a success is calculated
      • Points: This data type can be used to calculate points scored by agents on various actions (like gathering more data on a lead, for example)
      • Main Outcome: This is the other Mandatory field in any campaign template. It is formed as a Picklist where the administrator enters the different possible closures of any contact with a lead. As this is a mandatory field, the Campaign template cannot be saved unless there is at least 1 field with this data type.
      • Outcome details: This data type is also known as “Sub-closure”. Data entered here can be used for defining the details of the Main Outcome, for example
      • URL: This data type becomes a clickable link to a webpage, for example. Note that the field must be saved as ‘not editable’ in the template for the user to be able to click it. It validates that the entry is a valid URL
      • Label: Simply adds a text to the contact page. Ideal if you want to divide the contact page into head-lined sections
      • Unit Price: Obsolete field. It was used together with the data type “Number of units” to make automatic calculations and the total order value. It has since been replaced by formulas in the campaign template. It is kept only for legacy reasons.
      • Number of units: See “Unit price”
      • Booking entry ID: Adding this data type to a field creates a button on the contact page. If there is a calendar connected to the project of the Campaign, the booking calendar will slide in and the Agent can book appointments
      • Booking calendar code: Each calendar connected to a project has a code. When a project has several calendars connected it can be very useful to get this code automatically entered in the field for later exports of booked appointments.
      • Booking time: This data type adds a box where the date and time of the booked appointment are entered automatically. This is only used together with Booking Entry ID and connected calendars. The default format of this type is DD/MM/YYYY, hh:mm but, like the other date types, this can be changed to fit your culture.
      • Birthday: This data type is a date and is expected to hold sensitive information. Like all date data types, you can change the format to fit your culture
      • Full name: This data type will present a text box in which both first name and the family name is expected. Fields with of this data type are expected to hold sensitive information
      • First name: This data type will present a text box in which the first name of the lead is expected. Fields with of this data type are expected to hold sensitive information
      • Last name: This data type will present a text box in which the family name of the lead is expected. Fields with of this data type are expected to hold sensitive information
      • Address: This data type will present a text box in which the address of the lead is expected. Fields with of this data type are expected to hold sensitive information
      • Country: This data type will present a text box in which the country of residence of the lead is expected. Fields with of this data type are expected to hold sensitive information
      • City: This data type will present a text box in which the city of residence of the lead is expected. Fields with of this data type are expected to hold sensitive information
      • City 2: In some cultures, the City has 2 lines in a Lead address
      • Street: This data type will present a text box in which the Street address of the lead is expected. Fields with of this data type are expected to hold sensitive information
      • Building number: This data type will present a text box in which the building number of the lead is expected. Fields with of this data type are expected to hold sensitive information
      • Apartment number: This data type will present a text box in which the apartment number of the lead is expected. Fields with of this data type are expected to hold sensitive information
      • Apartment door: This data type will present a text box in which the apartment door of the lead is expected. Fields with of this data type are expected to hold sensitive information
      • Sensitive integer: This data type will present a box where a number is expected. The difference between this data type and the other Number-fields is that this one should be used when a number that may be regarded as sensitive is expected (Annual income of the Lead, for example)
      • Sensitive text: This data type will present exactly like the “Text (Small field)”. The difference is that this data type is expected to hold information that is sensitive to the lead
      • Mobile phone: This is a data type of the phone number type. When a number is entered here, the dialer knows that it should try to call that number. It presents exactly like any phone number on the contact page
      • Sensitive phone number: In some cases, the Lead may consider a phone number to be sensitive and that it should be treated in compliance with GDPR. In such cases, you can use this data type. The Dialer will still know that it is a phone number and try to call it
      • Sensitive Mobile phone. See “Sensitive Phone Number”
      • Sensitive E-mail: The difference between this data type and the standard E-mail data type is that this one can be treated by the functions that apply to the GDPR compliance.
      • Subscription Start Date: Separate date type that can be used for indicating when a subscription starts. This can be useful if, for example, there is a starting period where the subscription is free of charge but the paid subscription starts at the date indicated in the field with this data type.

Still need help? Contact Us Contact Us