Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Example: You want to collect phone numbers/email

    • Name: The internal name of the field. Used for analytics and integration purposes. Shouldn’t be changed after the queue is created. Should be the same within the tenant so later we will provide the analytics on the tenant level. Example: “phone-number” / “email”

    • Label: Customer visible name. Example: “Please provide your phone number” / “Please provide your email”

    • Placeholder: Customer visible placeholder if no value is specified by customer “+46999999999” / “test@email.com“

    • Value: Value that is used before customers specify any information. If customers do not change the value, the value will be used. For example, if value is omitted, there is no predefined value for all customers. Usually, you do not want to provide it

    • Validation rules: Applied for checking if the information is valid. Example: Regular expression (Regexp) pattern is specified (please reach technical team to support here). Default validations always will be applied to check that provided value is the phone/email address

      • Required field: The customer has to provide information before the ticket is created

      • Will be used for user notification: The Queue system will automatically use collected phone/email for sending notifications if SMS / email notifications are enabled

...

Category:

  • Note: please specify Categories first. add link to categories

  • Example: You want the customer to select under which Category ticket should be created, for example which type of questions the customer has

    • Name: The internal name of the field. Already fixed. Used for analytics and integration purposes. Shouldn’t be changed after the queue is created

    • Label: Customer visible name. Example: “Please choose service the service”

    • Placeholder: Not applied

    • Options: Will be taken from the Categories section (add link to categories).

    • Validation rules: Applied for checking if the information is valid. Example: Regular expression (Regexp) pattern is specified (please reach technical team to support here). Default validations always will be applied to check that provided value is the phone/email address

      • Required field: The customer has to provide information before the ticket is created

...