Home, the base for your Orders & Bots. Home is where it all begins as far as using the Dialox Platform goes after the ordering stages. Within Home you have several options and tiles which are drag & dropable. We will go through them in the next steps.

Orders

Once you have made an order in Operator, it will be visable in your Home screen due to automatic provisioning for the Enreach Contact Orders. Here you can see the Bot name, wether it needs to be connected or not.

Bots

All the Bots you choose, according to your order will be stored here. With a nice and quick overview there are a couple of options to choose from, which are described down below in the using section.

How to use Home

As stated above everything in this view is drag & dropable. For instance, if you have an order (105 extension) and want to remove the connection, go ahead and drag it to the Not connected area. You will see that the 105 extension will be dropped. With this action you remove the existing license from your Bot.

Drag a new or existing Bot to either Whatsapp or Smart IVR license to create a new situation. This way the power of quickly rebuilding your situation will be easily managable. Check below for reference:

The settings of the Customer environment can be done from out the Administration section, or from out the Studio section.

1. Select the environment you want to maintain

2. Open the Settings page

The Customer settings page enables you to configure the Customer environment settings:

1. Settings

2. Advanced settings

3. Store settings

The following settings for a Customer Environment can be changed on the Settings page:

1. Display name

2. Organisation domain name(s)

3. Auto-invite role(s)

The Display name is used to show in the environment drop down in the header bar to find your environment.

The Organisational domain name(s) are used to automatically allow users to sign themselves up onto the platform (when there are enough user licenses) when they are recognized by their email domain name.

The roles that will apply for automatically invited users based on their email domain name is configured in the field Auto-invite role(s).

There are two advanced settings that can be managed by Customers and Agencies:

Require Multi-factor authentication

To secure the access to your environment the members can be forced to use Multi-factor authentication. The user will then be asked to provide another piece of information that only this user is supposed to have.

Now you can manage your personal authentication settings in the security section of your profile.

How does Multi-factor authentication work when a user has access to multiple environments?

When only one environment to which a user has access require Multi-factor authentication, this user will be required to login using Multi-factor authentication, even when the user isn't accessing this environment at all.

When will Multi-factor authentication not appears while it is enabled?

The Multi-factor authentication question at login is only offered when logging in using the email and password as credentials. For authentication using one of the SSO providers, this Multi-factor step is skipped, since the SSO provider is then trusted.

Customize conversation archival

Conversation and contact information will be collected and stored when users interact with your Bots. The system will store this information for an indefinite period of time unless you configure otherwise.

By enabling the Customize conversation archival in the Advanced Settings page of an environment, the amount of days conversation data is stored can be limited.

This settings will impact the following data:

• conversation contents (the messages)

• conversation variables

• user contents

• user variables

• attachments and media (including audio) that is send by a user to the Bot

TBD

The Audit log function provides a comprehensive and secure way to monitor user activities and system events. It records all significant actions, such as logins, logouts, configuration changes, call logs, and message handling, ensuring a detailed audit trail.

Each log entry contains critical details like the timestamp, user identity, action type, source, and outcome, which are essential for security, compliance and operational transparency.

Asking for access

Within the platform we have to ensure a certain security for environments to prevent easy access to customer data. With the asking for access request form (as shown down below) you can ask for access for the inbox to overview your specific customer data.

The Access Request is a feature that allows users to request specific permissions or access levels within the platform. This form is typically used to grant new users the appropriate access rights or to adjust the access for existing users based on their roles and responsibilities.

The form collects necessary information, such as the user's name, role, and the type of access required, and routes the request to an administrator or designated approver for review and authorization, ensuring secure and controlled access management within the platform.