...
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
...
Categories
Note: please specify Categories first. add link to categorieshttps://ombori.atlassian.net/wiki/spaces/OAKB/pages/919896065/Console+Settingss#Categories first
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): https://ombori.atlassian.net/wiki/spaces/OAKB/pages/919896065/Console+Settingss#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
...
Enable integration to have Digital Call with our Partner Bambuser.
Please reach the Ombori team for support here.
...
Enable or disable digital call
Agent base URL - received from Bambuser (a page to open a call for agents)
API token - token received from Bambuser to make API calls
Customer URL template - Url which redirects the customer to the call page
Routing timeout - optional parameter, which determines interval time for searching next available agents
Digital call queue type - Default or Global - for single queue/store it should be Default. When we have a queue responsible for calling multiple queues/stores, we should select Global
Global queue ID - when it’s the Default digital call queue type, and you want to have your queue connected to the global digital call queue, then you should type the id of the global queue here.
...