Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Smart App to create Callback Notes from incoming phone calls
The Callback Note Basic app is designed to streamline communication within your team by allowing agents to easily create callback notes during conversations. This smart app provides a straightforward way to track follow-up requests, ensuring that no important tasks are missed. It’s an essential tool for teams that prioritize efficient communication and task management.
The bot requires no extra information to get started.
To adjust the settings for Callback Note Basic:
Any of the following roles can be assigned to manage the CMS, and thus the contents of the survey:
Agent
Operator
Here’s how the Callback Note Basic app works. Fill in the necessary details, such as the follow-up date and a brief description. Once the note is saved, it appears in the Notes accessible by authorized users. When it’s time for the follow-up, the app will send a reminder to the assigned agent or supervisor via push notification or email. This can be set up in your personal profile. Completed callbacks can be marked as Resolved to keep the dashboard organized.
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
The opening hours have no effect on the Callback Note Basic.
Everything you need to know to get you started with DialoX.
This manual provides help setting up Smart Apps in the Enreach DialoX platform, formerly known as the Botsquad platform (the terms DialoX and Botsquad will be used in parallel throughout the documentation). The DialoX platform is the foundation for all Conversational AI solutions Enreach is offering.
Explore the full range of available Smart Apps under Store, where you can discover the latest tools to optimize your workflow.
Once you've familiarized yourself with the Smart Apps, delve into the Settings page to customize both Smart App configurations and user preferences, ensuring a tailored experience for your organization.
For guidance on managing customer interactions, the Inbox page offers comprehensive insights into conversation handling.
Additionally, the Administration page provides in-depth information on platform functionality and advanced configuration options.
Lastly, a wealth of common inquiries and solutions can be accessed in our FAQ section, offering quick and reliable answers to your questions.
Social Messaging Inbox; offers your team the ability to chat with your audience on your website and the major social messaging channels, like Whatsapp, Meta and Instagram. The bot can help route calls or provide automatic answers to questions.
Smart IVR; allows you to answer the phone using a bot to apply routing, note taking, call deflection or automatic answering to questions. to enable smart routing based on speech
Call Deflection; to deflect phone calls to Whatsapp using the capabilities introduced by the two solutions above.
Having trouble? Here’s how to find help:
Signing up to the Dialox platform to get access
When you are invited to the platform you will receive an email with the invite link. The link is presented as a blue button. Click on it.
Click on the blue button in the email to sign up. When you haven't signup before, you will be redirected to the signup form. You can sign up using a username and password, or using one of your accounts at Enreach (Operator), Microsoft, Google or Facebook.
When you sign up using a username and password you need to provide
Your name
Your email address
A password that is secure. Preferably 8 or more characters, containing at least a capital, a special character and a number.
By clicking on Accept invite using, you can choose between the following options depending on how to log in:
Then read the end user license agreement and agree to it by selecting the checkbox.
Click the "Sign up" button to proceed. This will continue to the apps overview page within the environment you were invited to. When you don't have a bot yet, you can do so now by clicking Create your first bot.
The Callback Note Basic will summarize the user's reason for calling.
The complete technical documentation for the DialoX platform is described at . However, this manual only focuses on the following three solutions that are built on top of the platform:
Login to your account at . If you don’t have an account, you can easily register by selecting the Sign Up option.
Eager to find out more about these solutions, please check out our .
Access detailed guides and troubleshooting tips within the platform for partners.
Access detailed guides and troubleshooting tips within the platform for development.
Contact Support: Reach out to us via live chat or create a ticket via the .
Smart App to forward incoming phone calls
The Smart IVR Basic app provides a user-friendly, customizable Interactive Voice Response (IVR) system. This app allows you to automate call routing, guiding callers to the right department or agent without needing manual intervention. Smart IVR Basic is designed to improve call efficiency and customer experience by offering clear menu options and seamless call management.
After installing the app, go to Content -> Configuration to register the forwarding options.
Label: Provide short and clear labels for each forward option. The labels are used by the app to let the caller know which options to choose from.
Description: In the description field the instructions to the AI need to be provided which helps the bot to decide to whom it will be forwarding the call.
Number: Fill out the extension or phone number
Any of the following roles can be assigned to manage the CMS, and thus the contents of the Smart IVR Basic:
Operator
Content Manager
Producer
The Smart IVR Basic app follows a streamlined workflow:
A caller dials into your business, and the Smart IVR greets them with a pre-recorded welcome message. The caller selects an option from the menu choices provided (e.g., "Press 1 for Sales"). The call is routed to the appropriate department or agent based on the caller's input. Supervisors can review the call flow and adjust the menu options as needed to optimize call handling. Administrators have full control over editing and updating the IVR menu and routing rules at any time.
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
The opening hours determine whether or not the call will be forwarded to the chosen destination. Make sure configure them correctly.
The Smart IVR Basic will route incoming callers to the designated area(s).
Make sure your are configured.
Make sure your channel is enabled.
Yes, you can use the feature to create custom call flows based on business hours, holidays, or other schedules.
Yes, the supported languages can be set in the Smart App . This allows you to offer the IVR menu in multiple languages, enhancing accessibility for your customers.
The On-call Router Basic app is a simple and effective solution for managing after-hours or emergency calls. This app allows your team to route incoming calls to the correct on-call staff member based on a predefined schedule. It ensures that urgent calls are handled promptly, improving customer satisfaction and internal efficiency.
In order for the router to work the system must know which agents there are to whom it can route the call. The on-call agents can be configured in the Content section.
Go to Content in the left menu, then open the On-call Phonebook.
Click on the Add button to add an agent to the phonebook.
To make sure you have a working On-call Router, you must have added users to the Phonebook. Users registered in the phonebook can call and set themselves as the current active on-call employee.
Any of the following roles can be assigned to manage the CMS, and thus the contents of the survey:
Operator
Content Manager
Producer
By registering your agents in the phonebook, the app can do two things. It can route incoming phone calls towards the agent that is currently on-call. When an agent calls towards the same app, it allows them to set themselves as the current on-call agent.
When the agents are configured we can configure the schedule. This will help the system to know when to route the call to which agent. Go to Content in the left menu, then open the On-call Schedule. Click Add to create a new entry in the schedule.
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
The opening hours have no effect on the On-call Router Basic. The schedule is solely based on the On-call Schedule.
Marketplace Smart Apps
The words Bot, App and Smart App all point to the same concept and are mixed through out the platform and documentation.
End of 2024 the Marketplace was introduced to the Enreach Contact portfolio. As part of this introduction the Apps (also referred to as Bots) are offered as part of an App Tier (also referred to as level). Each tier has their own price, conditions and capabilities.
The following table provides a rough overview of the differences between the levels (tiers).
The following apps were offered as part of the Enreach Contact portfolio between 2022 and 2024 before the introduction of the Marketplace.
Smart IVR
Whatsapp Calldeflector
The On-call Router Basic offers companies a service to their customers via phone that can set configuration schedules.
The DialoX platform supports the creation and maintenance of Apps. Apps are composed by one or more , which in their turn comprise of , , and that together automate one or more use cases to end users.
✅
✅
✅
✅
✅
✅
✅
✅
✅
Expert
✅
✅
✅
✅
✅
✅
✅
Most of the Smart Apps, still available today in the Marketplace were already available for these legacy tiers and some are decommissioned or replaced by newer versions. These can be found here.
Take a survey over the phone with audio transcription
The Survey Basic app allows you to ask a list of questions and route them through different outputs, such as a note or an email.
In the Email Settings page, you can configure the email sent after completing the survey. It's possible to change the subject, header, and any additional recipients via the CC.
The survey itself can be altered via the Questionnaire CMS.
The opening and closing text and the questions are freely configurable to your liking.
The Survey Basic records and transcribes every answer.
It keeps recording until the user presses the hash key (#) on their phone.
Make sure to mention it to your users in your questions to prevent confusion.
Any of the following roles can be assigned to manage the CMS, and thus the contents of the survey:
Content manager
Supervisor
Producer
The Survey Basic starts out by prompting the Opening text, followed by the questions defined in the CMS.
The user can talk back to provide the answers to the questions, followed by a hash key (#) to indicate the end of their answer.
After completing the round of questions, the app will wrap up the conversation with the Closing text.
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
The opening hours have no effect on the Callback Note Basic.
The Smart Group Voicemail app enhances voicemail management by allowing incoming messages to be routed and shared among specific teams or departments. This app streamlines how voicemails are handled, ensuring that each message reaches the right group without delay. It’s designed for organizations that prioritize quick responses and efficient communication.
The app can be configured with a welcome and a goodbye message. By default, the app will create a note with the details left by the caller. However when you provide an email address, the app will send the details to that email address instead of creating a note in the Inbox.
Any of the following roles can be assigned to manage the CMS, and thus the contents of Smart Group Voicemail:
Agent
Operator
Content Manager
The Smart Group Voicemail app can be used as an alternative voicemail box. Simply forward your calls to this app whenever you are unavailable. The app will ask for the callers name, phone number, and reason of the call. These details will be stored so you can follow up on the call on a later moment.
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
The opening hours have no effect on the Smart Group Voicemail.
Ordering and provisioning using Operator
Enreach wholesalers and customers use Operator to order their services with Enreach. The DialoX services are either ordered as standalone product in the Cloudstore or as embedded services as part of the Enreach portfolio, such as Managed Voice (MKB Pro and MKB Complete).
In the Operator Cloudstore you can find, depending on your local offering and configuration, the following products:
Orders of DialoX services in the Cloudstore are provisioned manually by the Support and Delivery team of Enreach. They will create an account for you if not already available and set or increase the contract limits. Then they will create an environment in the platform and contact you regarding the delivery. You can then create your bots within the limits set in the account (as per Operator order).
Smart Apps can be ordered as extensions in Operator. You can order per level depending on your needs. The marketplace allows you to choose from Basic, Advanced, Professional and Expert.
Smart Apps Expert
Smart App extensions ordered in Operator are automatically provisioned in the DialoX platform as "Premium channels". Automatic provisioning entails:
An account is created for your customer if not already existing.
An environment will be created when not already existing.
The account limits will be increased of the customer account.
A channel will be provisioned in the customer environment that is linked to the ordered extension.
Once the Premium channel is provisioned, you (as a Wholesaler) can now continue to deliver the bot in the DialoX platform. For this, open the DialoX platform and navigate to the (newly created) customer environment or simply navigate directly from Operator using the Edit in studio button which can be found in the action menu of your order.
In our platform we distinguish two area’s through our switcher, which you can find in the top right corner of your screen when you are inside our platform. With this switcher you can simply access either the Studio or the Administration area.
Inside the Studio view you can manage your bots, invite and manage members, grant access requests, settings and keep track of everything through an audit log. The Studio view will help you organise everything specifically your bots and the users.
Inside the Administration view, you an overall view of your partner status as a wholesaler. You can manage your agency settings, environment settings but also keep track of your end customers.
Deflect phone or web chat conversations to Whatsapp for easy re-engagement
The Call Deflector app enables your bot to answer incoming chat messages on your social channels. It can be used to configure any type of social messaging assistant. By default it is configured to forward messages to an employee (escalate) while sending an automatic reply, but it can also be configured for automatic answering on recognised questions.
On other channels than Whatsapp it will deflect to Whatsapp when it takes too long for an employee to join and respond. This way your audience is forced to continue in Whatsapp which makes them re-engageable, even when they are offline.
The app requires a chat channel to handle incoming messages. It can also handle the phone channel to redirect callers to a chat based channel.
The only settings required for the app are the opening hours. Based on the opening hours the Smart: Escalate node can redirect users to Whatsapp for easier re-engagement.
Agent
Operator
Supervisor
Producer
The app is configured up with 4 flow files
Playbook
Inbox
Phone2wa
Web2wa
The Phone to Whatsapp (Phone2wa) flow deflects incoming phone calls to Whatsapp. The app asks the user to which phone number it can send a whatsapp message:
The Web to Whatsapp (Web2wa) flow, pushes the chat conversation to Whatsapp. When it takes too long for an operator to join the chat, the user will be shown a QR code. If the user scans the QR Code, their phone will open Whatsapp, allowing them to continue the conversation there.
The deflection to Whatsapp is useful for two reasons:
It allows you to re-engage more easily. People don't tend to keep their browser tab with the chat widget open all the time. Whatsapp offers a familiar experience, and users know they can close a conversation.
On web, users expect to be answered directly, whereas on Whatsapp they're used to a more slow chat.
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
It's possible to add an "Ask: Language" node to allow users to switch to their preferred language.
The app will let the user know if they're reaching out within or outside office hours. This helps set the expectation on how long to wait for a reply.
Handle incoming calls both during and outside opening hours
The Smart IVR app can automate incoming phone calls. It directs callers to the appropriate department based on their inputs. If the office is closed or agents are unavailable it can capture callback notes or redirect to WhatsApp.
Go to 'Build - Flows'. There you will see the pre-configured flow of the app.
The flow is preconfigured with three departments. Change the departments to reflect to your business needs. You may for example need to forward to a marketing department instead of a billing department.
By default the app will redirect to the 'Note' flow, prompting users to leave some details for you to get back to them. It's possible to change this to the 'Whatsapp' flow. Then they'll be asked to continue the conversation on Whatsapp, making it easier for you to re-engage.
To make sure the Smart IVR correctly forwards to the departments, you need to set up a correct intent to match it. First remove the intent currently linked to one of the options.
Then, create a new intent via the intent picker and provide a label and a description.
You no longer need to add training phrases, as AI will use the description to check the intent of the user.
Operator
Analyst
Producer
Supervisor
When someone calls within opening hours, the Smart IVR will ask the user to whom they'd like to speak. It will then forward the call to the correct department.
If the IVR is unable to forward the call, e.g. when the user calls outside opening hours, or a department is unavailable, it will fall back to creating a callback note.
The handling of callback notes is done in the 'Note' flow in the flow editor.
Choosing the Whatsapp flow will cause the Smart IVR to send your caller a Whatsapp message so your caller only needs to respond in order to get in touch.
The Whatsapp flow is by default configured to verify the phone number of the caller and then send them a Whatsapp message.
You can customize this via the 'Whatsapp' flow in the flow editor.
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
It's possible to add an "Ask: Language" node to allow users to switch to their preferred language.
The opening hours are used to determine whether you are online or not. The IVR will only forward calls within opening hours.
The Survey Basic will record and transcribe answers provided over the phone.
If you leave this field empty, the answers will be stored in a .
The answers to the survey will be transcribed and stored in a . There you can read the transcription, as well as listen back to the audio input for the question. This can be useful when the transcribing did not completely get it right.
The Smart Group Voicemail will record and transcribe answers provided over the phone.
If you leave this field empty, the answers will be stored in a .
The bot will ask for name and phone number of the caller and the reason of the call. The text for these questions as well as adding or changing the questions is not possible in this basic app. For this you would need to buy the Advanced level Smart App called . In this bot the entire flow can be customized.
Members can be managed in the environment section as a Organisation Manager. You can add or remove individuals by members to the environment.
Expert level will require a Bubblescript training which you can apply for in the .
The app uses your to determine whether or not you are online. Via 'Settings - Opening hours' you can modify the availability of your bot.
The Call Deflector requires at least one social chat channel, such as .
The playbook allows starting the conversation on 3 separate channels in order to elicit the user intention. You can see this by inspecting the little badges at the entry point, this will be telephony, chat and whatsapp channel related situations. The user, depending on calling or chatting will then try to answer the questions created (in this case no questions are trained) therefore the unknown flow will trigger the auto reply flow.
The Inbox will open the conversation on Web using a and a in order to elicit the user intention. You can see this by inspecting the little badges at the entry point. The prompt will then try to answer the question (in this case no questions are trained) therefore the unknown flow will trigger the flow.
However, on Whatsapp the conversation is never started by the bot (unless a template message is sent) but only by a Contact. Therefore, the Escalate: smart kick in directly when a message is sent that isn't automatically replied by a .
Once the connected has been closed, the caller will receive a Whatsapp message based on the number the call has given up to be contacted on. See the for reference. After the caller reacts to the incoming Whatsapp message, the conversation moves from speech to chat.
Using the tags in the Smart: Escalate node, you can specify to which team or department the chat will be escalated. Please read for more information about setting up multiple departments for different scenarios.
Ensure the phone channel is enabled.
This channel is optional. You can use it to deflect users to WhatsApp when there is no-one available.
The app uses your to determine whether or not you are online. Via 'Settings - Opening hours' you can modify the availability of your bot.
To accept incoming calls, enable the via 'Settings - Channels'.
Depending on your use case you can change or extend the questions asked but at least you need to consider wether you want the callback notes to be collected in the or to be sent as an email.
By default the Smart IVR will create a note. You can change the node to '' instead when you want an email to be sent.
Notes that are generated by your Smart IVR are collected in the Notes section. There notes can be followed up by marking them as completed. Notes can also be integrated in your (back office) systems using the and .
The message sent to the customer has to be created and verified as a template in .
Yes, you can configure a to listen to any notes created. Then via the you can retreive and act on them.
Schedule one-on-one appointments in your private calendar
Introduction
The Appointment Planner allows you to have customers schedule appointments directly into your own personal calendar, for example a Google or Outlook calendar.
The app requires you to have at least one of the following channels:
Chatwidget Can be embedded on your website Chatwidget
PWA Can be hosted on a bsqd.me subdomain Progressive Web App (PWA)
The Appointment Planner comes with a predefined calendar and planner.
The only thing left for you to do is to link your personal calendar and create availability slots, in which people can schedule their appointment.
Link your Calendar
From there you can change the Data source of the calendar:
When choosing for Google Calendar or Microsoft Outlook, click the "Connect to .." button.
You will be shown a login screen if not yet logged in at Google or Microsoft.
After choosing the correct account, you need to grant the application access to your account, so it can create the appointments in your calendar:
Then choose the correct calendar, in which the appointments will be made:
Create availability slots
Go to "Planning" in the left menu.
Click and drag somewhere on the calendar view to create an availability slot. Optionally you can make the slot recurring, saving you from having to create the same slot every week.
The planner can be configured with the following settings:
Planning title A name for you to recognise the right planner.
Create a note For appointments to be visible in your external calendar, this option should be left unchecked. If you leave this option unchecked, they will not show up in the 'Notes' view, but they will show up in your external calendar.
Day limit Use this to limit how many days ahead customers can schedule their appointment
Minutes from now How many minutes need to be between the time of making the appointment and the start of the booking itself. This prevents customers from booking appointments that start in 5 minutes.
Free/busy or Slots The free/busy search strategy attempts to find gaps in the calendar that haven't been filled yet. As a result, events will not overlap. Free/busy can work with multiple calendars to find the first one that has an open spot.
Free/busy requires availability slots which determine the hours within which to search for an open spot (for example, your opening hours).
For scheduling one-on-one appointments, we strongly recommend to use the "Free/busy" strategy.
Operator To reply to inbox channels
Planner To manage the calendar and planners
The playbook is set up with an opening message and two flow files.
The Appointment flow handles the scheduling of the appointment.
The Request details flow is invoked after finding a slot for the appointment. It's used to elicit any information from the user to create the appointment, such as their name, email, reason for the appointment.
Once the date and time are selected, the plan node will fire the Request details flow for gathering the details needed to making the appointment, which are in this case asking for the name, email and the reason for the appointment:
When the details flow is finished, the appointment will be created in the configured calendar.
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
It's possible to add an "Ask: Language" node to allow users to switch to their preferred language.
The office hours have no effect on this app.
Redirect incoming calls via SMS to any chat based solution
The SMS Call Deflector app will redirect incoming calls to a chat based channel via SMS. The app will send a text message to the caller, containing a link to either a webpage, the PWA, or new Whatsapp chat to a number of your choosing.
The PWA of this app, accepts incoming messages and will escalate to an operator via the Inbox. Only when the operator doesn't join the chat within the preconfigured time, it will ask the customer to leave its contact details. This way the customer will receive either an email or a text message once the operator joins the chat, allowing them to re-engage in their own time.
Here you can change the destination of the deflection. The three options are:
SMS to Web URL The SMS will contain a link to a webpage of your liking.
Unlike the Whatsapp integration, available for Advanced apps, any conversation with the customers via the SMS to Whatsapp route will not be handled in the Inbox.
After being deflected to the Inbox via an SMS, the app will use a couple of predefined messages to welcome the user. These messages can be configured via the Auto responses in the Content section.
When a customer sends a message in the Inbox, it might take a while before your team is able to respond. Setting the expectations is crucial for customer success. Therefore the system is designed to send a short auto response, directly after a customer sends a message. In this response the expectations for the response time can be set. Go to the content section and open the Auto responses page. Here you can configure what auto response should be given when a new conversation is started.
The SMS Call Deflector will start the converstion with the Welcome message from the 'Deflector dialog'. Then it will ask the customer on which phone number they can be reached via a text message. After receiving their phone number, an SMS will be sent, followed by notifying the customer with the Close message of the dialog. Go to the content section and open the 'Deflector dialog'. Here you can configure the messages sent to the customer.
Any of the following roles can be assigned to manage the CMS, and thus the conents of the SMS Call Deflector
Agent
Operator
Content Manager
The SMS Call Deflector app operates as follows:
An incoming call triggers the app, which assesses the deflection criteria. If the call meets the deflection rules, the system automatically sends an SMS message using a predefined template. The SMS message offers the caller a choice to continue the conversation via text. Agents can monitor and respond to SMS interactions using the integrated SMS dashboard. Calls that do not meet the deflection criteria are routed through standard channels as usual.
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
When using the SMS Call Deflector to deflect to PWA, the office hours will let the user know if they're reaching out within or outside office hours. This helps set the expectation on how long to wait for a reply.
Takes the call and creates a note.
The Callback Note app is a valuable tool that enables your team to efficiently handle and track callback requests. This smart app is designed to streamline the follow-up process by creating detailed callback notes that can be shared with team members. The Callback Note app ensures that no customer request goes unanswered, helping you improve communication and customer satisfaction.
The bot requires no extra information to get started.
To configure the Callback Note app:
The Callback Note app includes the following roles:
Agent
Operator
Supervisor
The Callback Note app follows a straightforward workflow. An agent or operator receives a callback request during a customer interaction or from missed calls. The agent or operator handles relevant details such as the customer’s input. Predefined variables are populated from the nodes assigned in the configuration, ensuring consistent data capture. The callback note is stored in the platform and can be shared or assigned to the appropriate team member. Notifications are sent to the assigned agent or team when a callback is due. Once the callback is completed, the note is updated, and the status is marked as done.
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
It's possible to add an "Ask: Language" node to allow users to switch to their preferred language.
The office hours have no effect on this app.
Assists in submitting an order over the phone.
The Order Assistant app is a comprehensive tool designed to streamline and automate the ordering process for your customers. This app allows you to create an interactive ordering system, providing an efficient way to manage order placements, confirmations, and updates. The Order Assistant integrates seamlessly with your communication channels to deliver a smooth and hassle-free customer experience.
The bot requires no extra information to get started.
To adjust the settings for the Order Assistant:
It's essential to assign nodes to variables that you can include in your notes or emails. This allows you to capture specific details throughout the order process and ensure that important information is accurately communicated to customers.
You can assign a node to a variable via the Assign To input field.
Setting up your Send node using the following settings as an example:
Ask: name
/name
Asking the customers name
Ask: date
/birthday
Asking the customers date of birth
Ask: phone
/phone
Asking the customers phone number
Send: note/email
Put all your variables into your send node
When using the example above, you should have something like this:
The following roles can be assigned to manage the Flows for the Order Assistant.
Agent
Operator
Producer
Content Manager
The Order Assistant app follows a structured workflow:
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
It's possible to add an "Ask: Language" node to allow users to switch to their preferred language.
The office hours have no effect on this app.
Answer any incoming social chat message
The Website Chat requires a Chatwidget channel to be deployed on your own website. The Whatsapp channel is optional to handle chat conversations.
The only required settings for this app are the opening hours.
Agent
Operator
Content Manager
The app is configured with three flows:
Playbook: Configure initial greeting and prompts to understand user intent.
Auto reply Flow: Set up automatic responses and escalation behavior.
WhatsApp redirect Flow: Redirects users to WhatsApp if no agent is available on other channels.
Any incoming chat messages will be handled by the default Playbook found in the Flows section.
The Auto reply flow is configured to escalate to a human employee. You can use this flow also to ask some more preliminary or qualifying questions before escalating to a human. To change the behaviour, go to Flows and open the Auto reply flow.
When no agent is available, it will continue to the Whatsapp redirect flow.
As it is not possible to re-engage users on the Chatwidget or PWA channels, the Whatsapp redirect flow will only trigger on those channels. The little badges that are displayed next to the entry point indicate this fact.
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
It's possible to add an "Ask: Language" node to allow users to switch to their preferred language.
The app will let the user know if they're reaching out within or outside office hours. This helps set the expectation on how long to wait for a reply.
Previously called Bot Templates
Now you are logged in you can create your bot.
The button will open a popup to select which bot template to use when creating your bot. Depending on your role and environment settings, as well as order(s), you will get a list of templates to choose from.
The Whatsapp Calldeflector 2.0 bot app enables your bot to answer incoming chat messages on your social channels. It can be used to configure any type of social messaging assistant. In the basis it is configured to forward messages to an employee (escalate) while sending an automatic response, but it can also be configured for automatic answering on recognized questions.
On other channels then Whatsapp it will deflect to Whatsapp after waiting for too long on an employee to join and respond. This way your audience is forced to continue in Whatsapp which makes them re-engageable, even when they are offline.
For this, the Whatsapp Calldeflector 2.0 bot app is configured with three flows:
Playbook
Inbox
Phone2wa
Web2wa
At minimum you need to take care of the following
Make sure to review and change the following nodes in the Playbook flow. Click on Flows and then open your Playbook.
Also called Phone to Whatsapp is the functionality which causes Speech to deflect to Whatsapp, making the Whatsapp Calldeflector complete. When someone calls the extension the caller can be deflected to the Whatsapp inbox using the following flows:
Also call Webchat to Whatsapp is the functionality to drag the live Chatwidget based conversation to a Whatsapp conversation. When the user wants to connect via the Chat widget and it takes to long, the user will be shown a QR which can be scanned to deflect to Whatsapp, as shown down below.
On other channels then Whatsapp it will deflect to Whatsapp after waiting for too long on an employee to join and respond. This way your audience is forced to continue in Whatsapp which makes them re-engageable, even when they are offline.
At minimum you need to take care of the following:
When online
Automatic reply to give employee(s) time to join and respond.
When offline
Automatic reply to let the customer know your business is closed.
When unavailable
Wait timeout
Timer to wait for an operator before deflecting from Web to Whatsapp
Bot template to answer calls
The Smart IVR template enables your bot to answer incoming phone calls. A Smart IVR template can be used to configure any type of voice assistant. In the basis it is configured to forward your call to the right department based on an opening question. It also contains flows for taking a call back note and deflect to whatsapp when no agents are available or the office is closed.
For this, the Smart IVR is configured with three Flows:
Playbook
Note
Make sure to review and change the following nodes in the Playbook flow. Click on Flows and then open your Playbook.
Review the following nodes:
Now you need to decide what you like the Smart IVR to do when the office or one of the departments is closed. Either go to the Note flow, go to the Whatsapp flow or do something else.
Choosing the Whatsapp flow will cause the Smart IVR to send your caller a Whatsapp message so your caller only needs to respond in order to get in touch.
The Whatsapp flow is by default configured to verify the phone number of the caller and then send a whatsapp message. Go to the Whatsapp flow:
And change the following:
When you don't want to deflect to Whatsapp in case of inavailability of your team you can also choose to take a note (in order to call the caller back later).
The flow for this is configured in the flow Note.
Depending on your use case you can change or extend the questions asked but at least you need to consider wether you want the call back notes to be collected in the Notes section of the platform or to be send as an email. By default it will create a note (see 1). Change it to Send: email instead when you want an email to be sent.
Openings text
Welcome your customer with a simple text. Make sure that you explain the customer to use a hash sign at the end of each question to progress the survey.
Questions
Fill in your survey accoringly. If you want to add more questions click on the '+ Add question' button.
Closing text
Close your survey with a closing text.
Once you have completed all the input fields, the next step is to configure your specific output. This could be a note but also an email. In the screenshot below you can see how you can define your output in settings.
Go to Settings.
Click on Survey email settings.
Fill in the email Subject.
Fill in the the Header.
Optionally set an email domain as a CC.
Answers the phone, takes a message and sends it as an email
Make sure to review and change the following nodes in the Playbook flow. Click on Flows and then open your Playbook.
Review the following nodes:
say what is expected now (we need some details)
say what can be expected from here (we will call you back asap)
say goodbye
Go to "Settings - Calendars", and click on the Edit () button for the existing calendar.
The is responsible for having the dialog with the user to elicit the right date and time to make the appointment.
When the planner is configured to create notes for scheduled bookings, we export the appointments via Ical as a .
The SMS Call Deflector will redirect incoming calls to chat based channels.
(Optionally added channel).
When redirecting to PWA, also enable your PWA channel and/or channel
Make sure your are configured.
Make sure your channel is enabled.
your users and let them configure their settings, settings, and optionally , such as multi-factor authentication.
SMS to PWA This will include a link to the PWA (chat interface) of this app. When the chat is opened by the customer, the app will escalate the conversation to a human operator. The conversation can then be handled from the . .
SMS to Whatsapp If your license doesn't include a , you can also deflect to any other Whatsapp number. This doesn't need to be a Whatsapp Business account.
The Callback Note takes the call and creates a note.
Ask essential questions to your customer which you can convert to a or .
Go to the section in the DialoX platform, select the Callback Note smart app and fill in the required information. The template will automatically include the relevant variables. Feel free to change the context.
Yes, you can assign specific nodes to variables in the section, allowing you to track only the information you need.
In the interface, locate the Assigned Agent or Assigned Operator dropdown or field. Choose the agent or operator from the list of available team members. This selection assigns the note to them directly.
The Order Assistant takes on incoming order via phone.
Ask essential questions to your customer which you can convert to a or .
If you want to know more about variables and how to set them up, please take a look at .
Customers place an order via a supported communication channel, interacting with a predefined order menu or options. An order confirmation is sent to the company through the chosen notification channel such as or .
The Website Chat app allows you to manage and automate responses to incoming chat messages on your website via the and channels. It supports automatic responses, escalation to human agents, and deflection to WhatsApp for continued engagement.
Optional but recommended for fallback options.
The app uses your to determine whether or not you are online. Via 'Settings - Opening hours' you can modify the availability of your bot.
The playbook will open the conversation on Web using a and a in order to elicit the user intention. You can see this by inspecting the little badges at the entry point. The prompt will then try to answer the question (in case no questions are trained therefore the unknown flow will trigger the auto reply flow).
However, on Whatsapp the conversation is never started by the bot (unless a template message is sent) but only by a Contact. Therefore, the auto_reply will kick in directly when a message is sent that isn't automatically replied by a . The auto_reply flow is invoked by the node .
The Auto reply flow will just explain the fact that the message is escalated to a human. When closed or when no agents are available it can display another message. See the for explanation about the behaviour of this node.
We try to redirect the user to Whatsapp for easy re-engagement. The Show Whatsapp link node needs to be properly configured in order for it to work. See for more details.
Adjust the and nodes in the Playbook flow.
These are the legacy smart apps which will be no longer available after the Marketplace release on 21st of November 2024. Please go to the for the current list of Smart Apps available for your company and-or customers.
The bot template you have chosen will consist out of one or more skills. The skills provide the functionality and node types you need to configure the behaviour and content of your bot. See the for more information.
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
Read about flows in the section to understand what type of nodes your can use for configuring the Social Inbox for your use case.
Make sure your are configured
Make sure your is enabled (or another chat channel)
The playbook will open the conversation on 3 separate channels in order to elicit the user intention. You can see this by inspecting the little badges at the entry point, this will be telephony, chat and whatsapp channel related situations. The user, depending on calling or chatting will then try to answer the questions created (in this case no questions are trained) therefore the unknown flow will trigger the auto reply flow.
However, on Whatsapp the conversation is never started by the bot (unless a template message is sent) but only by a Contact. Therefore, the auto_reply will kick in directly when a message is sent that isn't automatically replied by a . The auto_reply flow is invoked by the node .
The Inbox will open the conversation on Web using a and a in order to elicit the user intention. You can see this by inspecting the little badges at the entry point. The prompt will then try to answer the question (in this case no questions are trained) therefore the unknown flow will trigger the flow.
However, on Whatsapp the conversation is never started by the bot (unless a template message is sent) but only by a Contact. Therefore, the Escalate: smart kick in directly when a message is sent that isn't automatically replied by a .
Once the connected has been closed, the caller will receive a Whatsapp based on the number the call has given up to be contacted on. See the for reference. After the caller reacts to the incoming whatsapp deflection template the conversation has officially been moved from speech to chat.
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
The Social Inbox template enables your bot to answer incoming chat messages via the and channels. It can be used to configure any type of social messaging assistant. In the basis it is configured to forward messages to an employee (escalate) while sending an automatic response, but it can also be configured for automatic answering on recognized questions.
Make sure your are configured
Make sure your channel is enable (or another chat channel)
Automatic reply for when / are currently not available to join or respond.
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
Read about flows in the section to understand what type of nodes your can use for configuring the Smart IVR for your use case.
Make sure your are configured
Make sure your is enabled
Optionally make sure a to your Social Inbox bot is configured
welcome text
and its labels
nodes with the right text, number and fallback logic
Customize the whatsapp flow: node.
Notes that are generated by your Smart IVR are collected in the Notes section. There notes can be followed up by marking them as completed. This way you'll never forget to follow up on made promisses by your bot. Notes can also be integrated in your (back office) systems using the and .
The node type is excluded in this template.
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
The Survey Extension allows you to ask a list of questions and route them through different outputs, such as a note or an email. The allowed channel on which the Survey Extension can be used is the. Once you have installed the correct template you can fill in the following fields.
Specify your customers email domain (leave open to create Note, which can be found in ).
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
The Group Voicemail (previously called Company Voicemail) template can be used as an alternative voicemail box. Simple forward your calls to this bot whenever you are unavailable. The Company Voicemail template is configured with only one Flow: playbook. Read about flows in the section to understand what type of nodes your can use for configuring the Voicemail bot for your use case.
Make sure your is enabled
Make sure to change the node to a node and fill in the email address, see step 6 below under playbook.
welcome text (can be used to be more specific about whoms voicemail it is)
for the reason of the call
(replace this for to receive an email instead of a note in the studio)
Notes that are generated by your Voicemail are collected in the Notes section. There notes can be followed up by marking them as completed. This way you'll never forget to follow up on made promisses by your bot. Notes can also be integrated in your (back office) systems using the and .
The node type is excluded from this bot template.
For companies that offer on call services to their customers it is quite a hassle to configure an on call schedule in their PBX. A bot with the Oncall Assistant template installed solves this issue quite easily.
After installing the skill you can simple add the node "Dial: On Call" to your flow and configure your agents and planning in the Content section of the platform. Using this approach even users without the right to edit your flows can change the On call schedule of your agents.
There will be a new flow node introduced to your bot called "Dial: on call". This node needs to be added to your flow in order to enable it.
Go to the Flows section of the platform
Find the place in your flow where you want to have the bot to dial the on call agent.
Click right mouse button, click on Dial and then on On call.
Now make sure your flow routes a link (Arrow) to your new Dial: on call node. In case this is the only node in your Flow, you need to connect it to the Entry trigger.
Open the side panel of the node by clicking on the title bar of the Dial: On call node.
Now fill in the text and the fallback number.
Now go to the Content section and add your agents to the On-call Phonebook.
Then configure who is available for on call services from when in the On-call Schedule page in the Content section.
SIP
The SIP method to use for dialing
Choose Refer
Text
The text the bot should say just before dialing
By embedding #{oncall_name} the name of the agent can be used in the text
Fallback
In order for the On call function to work the system must know which agents there are to route the call to. The on call agents can be configured in the Content section.
Click on Content
Click on On-call Phonebook
Click Add
Name
Name of the agent
Number
Number of the agent
Make sure to enable or disable the extension option depending on the number you need
Extension
Uncheck for public numbers
To make sure the number is validated on correctness
When the agents are configured we can configure the schedule. This will help the system to know when to route the call to which agent.
Click on Content
Click on On-call Schedule
Click Add
From
The date and time at which this schedule becomes active
Route to
The agent to route the call to
Bot template to forward incoming phone calls
The Smart IVR Basic enables your bot to answer and forward incoming phone calls. The Smart IVR Basic is configured to forward your call to the right department based on an opening question.
Add a welcome text
Configure the various forwarding options to whom the bot will be forwarding incoming calls
After installing the app, go to Content -> Configuration to register the forwarding options.
Label: Provide short and clear labels for each forward option. The labels are used by the bot to let the caller know which options to choose from.
Description: In the description field the instructions to the AI need to be provided which helps the bot to decide to whom it will be forwarding the call.
Number: Fill out the extension or phone number
During the callback request process, the Callback Note bot may prompt the user to provide certain information such as their name, phone number, reason for callback, and preferred callback time. This information helps ensure that the callback note is efficient and relevant to the customers needs.
Once the user submits the callback request along with the required information, the Callback Note schedules the callback based on the specified preferences. This scheduling functionality ensures that the callback occurs at a convenient time for the user and helps manage the workload for representatives handling callbacks.
Once your customer has spoken in the variables as stated above, this will eventually result in a Callback Note. Handle accordingly by Marking it as done or Assigning it to one of your colleagues in the manage panel on the right side.
Status
Either To Do or Done
Note
Subject of a note
Start at
Start of a note to be handled accordingly
Mostly used with calendering feature
Due at
Deadline for note to be handled accordingly
Mostly used with calendering feature
Tags
Added tags to categorize a specific note.
Created at
Date of creation
Take short surveys over the phone
The Survey app allows you to ask a list of questions and route them through different outputs, such as a note or an email.
The app then stores all that information in a note.
Phone The app is configured to take the survey via a phone conversation. Phone
The following roles can be assigned to manage the Flows for the Survey.
Producer
Operator
Supervisor
The app starts by asking the preferred language of the user, as this isn't always the same as the country code of the phone number.
After receiving the feedback the app asks the user whether or not the support team can reach out to the customer for any further details. If so, the app asks for the users phone number.
Finally the results are stored in a note, which can be viewed when going to 'Manage - Notes'.
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
It's possible to add an "Ask: Language" node to allow users to switch to their preferred language.
The opening hours have no effect on this app.
Find more info here:
Schedule callback appointments in your own calendar when you're unavailable to take a call right now
The Callback Planner uses a calendar and a planner to schedule callback appointments.
Use a planner to create slots
The planner allows for some extra configuration such as how many days in advance appointments can be made.
Phone The Callback Planner can be used to deflect incoming calls and plan callback appointments. Phone
The Callback planner comes with a predefined calendar and planner. The only thing left for you to do is to create availability slots, in which callers can schedule their callback appointment.
Go to "Planning" in the left menu.
Click and drag somewhere on the calendar view to create a slot. You can set the capacity per slot, meaning how many appointments can be scheduled in that time window. Optionally you can make the slot recurring, saving you from having to create the same slot every week.
The planner can be configured with the following settings:
Planning title A name for you to recognize the right planner.
Create a note If a note is created, the appointment will be listed in the 'Notes' view. They will also show up in the Inbox - Today view.
It's important to have this option checked to be able to work with the notes from the Inbox
Day limit Use this to limit how many days customers can schedule their appointment
Minutes from now How many minutes need to be between the time of making the appointment and the start of the booking itself.
Free/busy or Slots The free/busy search strategy attempts to find gaps in the calendar that haven't been filled yet. As a result, events will not overlap. Free/busy can work with multiple calendars to find the first one that has an open spot.
Free/busy requires availability slots which determine the hours within which to search for an open spot (for example, your opening hours). The slots search strategy requires you to create specific slots up-front. Each slot has a maximum capacity. The planner then tries to find slots that haven't been completely filled yet, and plans an event that matches the starting and ending time of the slot. Events will overlap if the capacity is greater than one.
Operator To reply to inbox channels
Planner To manage the calendar and planners
The playbook is set up with an opening message and two flow files.
The Appointment flow handles the scheduling of the callback appointment.
The Details flow is invoked after finding a slot for the callback appointment. It's used to elicit any information from the user to create the appointment, such as their name, phone number, reason for calling, etc.
Once the date and time are selected, the plan node will fire the Details flow for gathering the details needed to making the callback appointment, which are in this case asking for the name, the phone number and the reason for the call:
The app will determine the language of the user based on their phone number. The app falls back on the default language of the app in case the language cannot be determined (e.g. French or Dutch in Belgium).
It's possible to add an "Ask: Language" node to allow users to switch to their preferred language.
The office hours have no effect on this app.
It is only built to forward messages to an employee (escalate) while sending an automatic response.
On other channels then Whatsapp it will deflect to Whatsapp after waiting for too long on an employee to join and respond. This way your audience is forced to continue in Whatsapp which makes them re-engageable, even when they are offline.
At minimum you need to take care of the following
Configure the auto reply behaviour in the contect section, see below
When a customer sends a message it might take a while before your team is able to respond. Setting the expectations is crucial for customer success. Therefore the system is designed to send a short auto response, directly after a customer sent a message. In this response the expectations for the response time can be communicated.
Go to the content section and open the Auto responses page. Here you can configure what auto response should be given when a new conversation is started.
Click on Content in the main menu on the left hand side
Click on Auto responses
Fill in the text that you want to reply when the company is open (online), e.g. Thank you for your question, we generally respond within 1 hour.
Fill in the text that you want to reply when the company is closed (offline), e.g. Sadly we are closed right now. We will come back to you when our office is open again.
Fill in the text that you want to reply when the company is open (online) but there are no operators available
Choose the timeout amount in seconds after which the system will deflect to whatsapp.
When the call calls the number and nobody is available to take the call, setting up your call deflector flow will give you(r) and or your team the opportunity to deflect the customer to Whatsapp. Therefore the system is designed to send a couple of questions before sending out a call deflection template to which the customer can reply to start the conversation via Whatsapp.
Go to the content section and open Call deflector page. Here you can configure what questions should be given before you can deflect your customer to a Whatsapp conversation.
Welcome
Explain the customer what is about to happen via a welcome text.
Reuse question
Ask the customer their phonenumber to deflect to Whatsapp.
Try again
Second try if the first question fails to ask the customer their phonenumber to deflect to Whatsapp.
Phone question
Let the customer type in their phone number and close with a hash key.
Try again
Second try to let the customer type in their phone number and close with a hash key.
Close
Close your conversation with a result and goodbye text.
The Basic Group Voicemail app can be used as an alternative voicemail box. Simple forward your calls to this bot whenever you are unavailable.
The bot will ask for the callers name, phone number, and reason of the call. These details will be stored so you can follow up on the call on a later moment.
The app can be configured with a welcome and a goodbye message. By default, the bot will create a note with the details left by the caller. However when you provide an email address, the bot will send the details to that email address instead of creating a note in the Inbox.
Provide the welcome and goodbye text
(Optional) Provide an email address
Notes that are generated by your Voicemail are collected in the Notes section. There notes can be followed up by marking them as completed. This way you'll never forget to follow up on made promises by your bot.
The Callback Based Router allows you to route directly from number to number. This can be from external to extension, extension to external, extension to extension and vice versa. This creates a structured workflow in which you can create the desired routings without any effort.
When you want to start routing numbers you need to do the following steps:
Navigate to the left menu.
Click on Content.
Go to Routing Table.
Fill in the Caller.
Then fill in the designated destination that the caller needs to be routed to.
As you can see in the image above, you see that the caller, the person who is calling, is routed to the target, or the desired destination. After you connected a public number to your Caller Based Router and start calling this number, the caller (+31612345678 in this situation) will be routed to the target.
Common flow nodes that are useful on any of the supported communication channels
The Base flows skill contains the following node types:
Send:
Ask:
Control flow:
Put together a Progressive Web App (Web App) in just a few seconds. Users would be able to interact with your bot directly within the Web app interface. This could involve asking questions, receiving responses, and engaging in conversation as they would with a traditional chatbot interface.
Choose Progressive Web App
Fill in a subdomain to use for your Web App.
Manage your Web app by using the three tabs after following the setup steps above. Click on the buttons below for more information.
Bot template to create callback notes from incoming phone calls
The Basic Callback Note app can be used as to create notes when you are unable to take the phone call.
The app can be configured with a welcome and a goodbye message. By default, the bot will create a note with the details left by the caller. However when you provide an email address, the bot will send the details to that email address instead of creating a note in the Inbox.
Provide the welcome and goodbye text
Notes that are generated by your Voicemail are collected in the Notes section. There notes can be followed up by marking them as completed. This way you'll never forget to follow up on made promises by your bot.
The callback note can be handled accordingly by Marking it as done or Assigning it to one of your colleagues in the manage panel on the right side.
The Callback Planner schedules callback appointments in your own calendar for you. Useful for when you're unavailable to take on calls right now.
Can't answer the phone during peak moments? Or are you contacted outside of your service hours? Have the Callback Planner offer your customers some convenience by making it easy for them to plan a callback appointment.
This way callers don't need to wait in the queue or remind themselves to call back sometime later.
The Callback planner will try to find the right date and time together with the customer. You can configure the planner to either directly offer one or multiple suggestions, or even ask the customer directly for a desired date and time.
The user can either confirm or decline. When the user declines, the bot will find the next possible slot. When users ask for a specific alternative, the bot will try to find the best possible option that corresponds to the request. In the below example, the bot found the next available slot that comes closest to the question to be Monday at 10:00:
After finding the right point in time for the callback appointment, the planner will ask the customer for their name, phone number, and reason for the call.
The Bot App is plug and play. It does however need to know when it can plan appointments. To do this we will hook up a planner for the bot. The planner is a view across one or multiple calendars (e.g. different colleagues or departments). But it is also fine to just use a single calendar for the planner.
Let's configure our first calendar and planner.
Go to 'Settings', and then 'Calendars'
From there, click on 'Add calendar', name your first calendar and hit 'Save'.
Now that we have a calendar we can link it to a planner.
In the left sidebar, go to Planning.
Then via the planner selector in the top left, click 'Add new planner'
Provide a name, configure the limits and choose between a free/busy or a slots planner, then click 'Save'.
You can create a slot by selecting and dragging a time window on the planner.
You will then be shown a modal where you can set up the recurrence of the slot, and the maximum capacity.
This Bot App comprises three Flow files:
Playbook, to start the conversation
Appointment, to make the appointment
Details, to capture the details for the appointment
Once the date and time are selected, the plan node will fire the Details flow for gathering the details needed to making the callback appointment, which are in this case asking for the name, the phone number and the reason for the call:
This bot is composed out of the following skills. Click on the skill to read the details.
Adds flow nodes that are only relevant on Web Chat channels
Node types:
The Web flows skill introduces a specific settings page to manage the availability of the input bar in the conversation.
When the input bar is disabled your bot doesn't need to be able to respond to off topic user intents. Your users will keep on the path you've set out for them in your dialogs easier compared to when you leave the input bar open for free format text messages.
You can disable the input bar by going to the settings page of this skill, called Settings for web.
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
What number to dial when no schedule is found in the section
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
Make sure your are configured
Make sure your is enabled
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
The node capture a few variables such as , & reason. These will be sent to the folder which you can find in the menu on the left.
The app is preconfigured to take an (Net promotor score) by phone. Based on the score given, the app replies appropriately and asks whether or not the user can be contacted by the support team for feedback.
Then it asks to rate the their customer service on a scale from 1 to 5. The rating can be given either through speech or via DTMF. After receiving the rating, the user can give extra feedback on why that score was given via the '' node.
Because this flow takes place on the phone, the '' node can ask the user if they can be reached via the phone number currently calling.
Ratings are stored both in the , accessed via 'Manage - Notes', and on the contact itself.
In the , any given ratings are directly visible via the tag.
Yes, when using different '' nodes, assign the answer to a variable.
After you've assigned the answer to a variable, you can insert that variable in the '' node by typing a "/" (slash) followed by the name of the variable.
The is responsible for having the dialog with the user to elicit the right date and time to make the appointment.
When the details flow is finished, the appointment will be planned in the calendar of this bot. Inbox users will be able to find the callback appointments in the .
The created callback appointments are visible in the view.
When the planner is configured to create notes for scheduled bookings, we export the appointments via Ical as a .
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
The Whatsapp Calldeflector 1.0 bot app allows you to respond to incoming chat messages on your social channels (primarily Whatsapp and Web). This template doesn't allow for , so little customization is possible.
Make sure your are configured
Make sure your is enabled
Optionally configure your channel
your users and let them configure their , , and optionally , such as multi-factor authentication.
Another way to deal with this situation is to prevent web chat when there are no operators available. This you can configure in the design page.
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
Make sure your is enabled
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
The Base flows skill provides the basic framework for your bot and the capability to design your bot using Flows. Without it you cannot design Flows using the visual modeller and your bot will not function unless you write your own scripts.
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
Click on
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
The bot will ask the caller for their name, phone number, and reason for calling. It will then create a note with the provided details in the folder which you can find in the menu on the left.
Make sure your is enabled
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
When finishing the conversation, the bot will create a Todo item with the registered details in the for a human agent to handle.
The Playbook and the Details flows use common Flow nodes which you can read all about in the .
The Appointment flow is specific for this Bot App and introduces a new Flow Node type called "Planner - Plan". It is introduced by the .
The is responsible for having the dialog with the user to elicit the right date and time to make the appointment.
When the details flow is finished, the appointment will be planned in the calendar of this bot. Inbox users will be able to find the Callback appointments in the .
The Web flows skill introduces node types and functions that only apply to chat on Web channels, like the Web PWA or the .
Status
Either To Do or Done
Note
Subject of a note
Start at
Start of a note to be handled accordingly
Mostly used with calendering feature
Due at
Deadline for note to be handled accordingly
Mostly used with calendering feature
Tags
Added tags to categorize a specific note.
Created at
Date of creation
Adds flow nodes that are only relevant for the Email channel
This skill enables you to add Email as a channel to your bot.
This option is currently only supported in custom propositions.
Installation of the skill in your bot is at own risk.
On other channels then Whatsapp it will deflect to Whatsapp after waiting for too long on an employee to join and respond. This way your audience is forced to continue in Whatsapp which makes them re-engageable, even when they are offline.
At minimum you need to take care of the following:
Make sureto review and change the following nodes in the Playbook flow. Click on Flows (1) and then open your Playbook (2).
The auto_reply flow is configured to escalate to a human employee. You can use this flow also to ask some more preliminary or qualifying questions before escalating to a human. To change the behaviour, go to Flows (1) and then open the Auto_reply flow (2).
By default it will continue to the Whatsapp flow when no agent is available, see next paragraph.
The Whatsapp flow will only kick off on the Web Widget or Web PWA channels, since these channels have no way to re-engage the Contact. So on Whatsapp this is flow is skipped (we are already on Whatsapp). The little badges that are displayed next to the entry point indicate this fact.
Adds flow nodes that use Large Language Models using Knowledge bases for their functioning
The LLM Knowledge base skill adds two capabilities to your Smart App to generate responses to users and operators using a large language model AI service that uses a predefined Knowledge base as its content.
Depending on your license, the LLM Knowledgebase skill can be installed in the packages section of the platform.
Not all Smart Apps support the LLM Knowledgebase skill. When they do however you can perform the following steps to install the skill to your App.
Go to packages
Click on Browse skills
Click on LLM Knowledgebase
Click on Install
Publish the app to gain access to the 'AI - Knowledgebases' page
If you want to use the knowledge base and the LLM Prompt in the inbox to generate suggestions to the operators and agents, make sure to configure the Prompt and Knowledgebase in the Settings page called "Inbox AI", see below:
The LLM Knowledgebase skill introduces the following flow nodes to your Flow designer in order to provide responses that are generated by the LLM to users of your Smart App:
The LLM Knowledgebase skill also introduces an Inbox Command for generating response suggestions using the LLM. The Inbox Command is available in the input bar when an operator or agent has joined the conversation.
When clicking the inbox commands button a list appears with the available commands. Depending on the skills you have installed you get zero, one or more options. When the LLM KB Skill is installed you should at least see the option "AI Suggestions".
You can click the AI suggestions option directly (so without having typed anything yet in the input bar) as shown above, or first type a hint to the AI and then click on the AI suggestions option to hint the AI into a specific direction for its answer:
You should configure the prompt and/or knowledge base in the Settings section, see above, when you get this message.
Furthermore, this skill introduces the following system intents in the AI section:
System intents are intents that are managed by the DialoX team since they are needed for other platform skills to work properly, like Yes, No, etc.
Yes
When the user says yes
Sure, yep, absolutely
No
When the user says no
Not at all, nope, negative
Escalate
When the user asks for a human
I want to speak to a human please
Hello
When the user says hello
Hi there, hello, hi
Thanks
When the user thanks the agent
Thank you, thank you so much
Finish
When the user indicates to be done
Thanks, that's it
Adds flow node that uses Google Maps for address lookup
The Address Flows skill can be used to ask a user for an address. The skill will perform an address lookup via Google Maps to validate whether or not it exists.
Depending on your license, the Address Flows skill can be installed in the packages section of the platform.
Not all Smart Apps support the Address Flows skill. When they do however you can perform the following steps to install the skill to your App.
Go to packages
Click on Browse skills
Click on Address Flows
Click on Install
Enter the generated API key in the 'Integrations - Secrets' section.
The Address Flows skill introduces a new Ask node to ask for a users' address:
Ask: Address
Adds flow nodes that use Large Language Models for their functioning
The LLM Flows skills adds capabilities to your Smart App to generate responses to users using a large language model AI service. The capabilities are exposed in the following flow nodes that you can add to your flow canvas:
A Large Language Model (LLM) is a type of artificial intelligence (AI) model designed to understand and generate human-like text based on the input it receives. These models are trained on massive datasets of text from books, articles, websites, and other written content, enabling them to process and generate coherent language.
The DialoX platform uses mainly the ChatGPT models from Open AI, hosted on the Microsoft Azure platform and Gemini models from google hosting within Google cloud.
Depending on your license the LLM Flows skill can be installed in the packages section of the platform.
Not all Smart Apps support the LLM Flows skill. When they do however you can perform the following steps to install the skill to your App.
Go to packages
Click on Browse skills
Click on LLM Flows
Click on Install
Adds flow nodes that are only relevant on chat channels
In case of lunch time you need to add a Timeplan that looks like this:
Now you can change your Flow to branch specifically on the tag timeplan:lunch
the same way we implemented the out of office logic.
Click on the link to the Say node and change the Link details on the right hand side:
Select the Timeplan tag and provide a label for explanatory purposes.
And now you have a flow that handles lunch breaks too!
Read this if you have Smart Apps in use that have been ordered before 21 october 2024. New Smart Apps documentation can be found within the .
The Social Inbox 2.0 template enables your bot to answer incoming chat messages via the and channels. It can be used to configure any type of social messaging assistant. In the basis it is configured to forward messages to an employee (escalate) while sending an automatic response, but it can also be configured for automatic answering on recognized questions.
Make sure your are configured
Make sure your channel is enable (or another chat channel)
The playbook will open the conversation on Web using a and a in order to elicit the user intention. You can see this by inspecting the little badges at the entry point. The prompt will then try to answer the question (in case no questions are trained therefore the unknown flow will trigger the auto reply flow).
However, on Whatsapp the conversation is never started by the bot (unless a template message is sent) but only by a Contact. Therefore, the auto_reply will kick in directly when a message is sent that isn't automatically replied by a . The auto_reply flow is invoked by the node .
The Auto_reply flow will just explain the fact that the message is escalated to a human. When closed or when no agents are available it can display another message. See the for explanation about the behaviour of this node.
The Show Whatsapp link node needs to be properly configured in order for it to work. See for more details.
The prompts can be configured in the Prompts page in the AI section, see for more details.
Knowledgebases can be configured in the Knowledgebases page in the AI section, see for more details.
As part of the phone flows the content page Voice lexicon is exposed. Using this content page translations can be made for words to their phonatic versions when text to speech fails or can be improved. See for more information.
The platform defaults skill is a framework containing all default behaviour and logic that is needed for the skill to support its flow nodes.
For the lookup in Google Maps to work, you need an API key. An API key can be obtained by .
The chat interface introduces a content page called to manage the default response provided when opting in or opting out of business initiated conversations on Whatsapp.
The opening hours settings of your bot don't allow for specific exceptions or additional timeplans. For this the can be very helpful. The Timeplan skill allows you to set a specific tag for specific time plans. This way you could configure specific logic for a certain time plan.
Add a link (1) from a to a (2) that explains it is lunch time. This Say node will then link to the Note flow using the (3).
OAuth Flows lets your users authenticate via third parties as Google, Microsoft or Operator.
You can do this to verify users' identity in the app.
The skill allows users to authenticate both via phone or via chat channels.
When authenticating users via phone, the skill will send the caller an SMS, containing a link to a login page for either Google, Microsoft or Operator.
After logging in with their personal user credentials, the app will be notified, and receive the authenticated details of the caller.
The user will be updated based on the identity received by the third party.
When authenticating users via chat, the skill will show the users a login button for the selected third party. After logging in, as in the phone channel, the app will receive the identity from the third party.
However, sometimes more flexibility is required. For this the Timeplan skill can be used. It allows users to define one or more alternative timeplans, for instance to allow for Lunch time.
A timeplan is a scheduled event that can overwrite your online or offline status set by the default Opening hours settings and even set an additional tag so you can define specific behaviour in your flow that needs to happen when this scheduled event occurs.
A timeplan can trigger weekly, yearly or at one single date and time. Examples:
use a yearly timeplan to schedule Christmas closing
use a weekly timeplan to schedule daily lunch time closing
use a one time timeplan to schedule closing due to a company offsite or event
The skill adds a page to manage your timeplans in the Settings section.
Go to settings and click Timeplans.
Click Add to add a new timeplan.
This will add a new line:
Click on the newly created line to unfold the form
Now provide a description (for you to keep track of the different timeplans)
Select what kind of Timeplan it is: One time, Yearly or Weekly.
Choose the "Set system status" to be nothing when your timeplan doesn't affect the online or offline status of your bot, otherwise choose online or offline when it does impact the status.
Choose to add a specific tag which then can be used in your flow to make specific logic based on this tag, for instance when you want to say to the user "We are currently having lunch" or something.
Now, dependent on what kind of Timeplan you selected you can fill in the details (see examples below for more information):
Weekly: days of the week followed by a from and until time
Yearly: month, day and a from and until time
One time: date and a from and until time
Description
A human readable description
For you to keep track of your timeplans. It has no utilitarian purpuse.
Kind
What type of timeplan? Weekly, Yearly or One time
This has effect on what date and time details are asked below
Set system status
Does your timeplan affect the online or offline status of your bot?
Choose online when it should set the status to online. Set offline when it should set the status to offline and leave empty if it doesn't impact the status.
Add tag
Sets a specific tag when this Timeplan is active.
This helps you to define specific logic in your flows for this Timeplan, for instance a special text that explains the company is heaving lunch.
Office hours
Define a time period per week day
Only visible when Kind is configured with "Weekly"
Month and day
Define the month and day at which this Timeplan should be active on a yearly basis
Only visible when Kind is configured with "Yearly". Notice that when 29/2 is selected for example, the system will automatically fallback to 28/2
Date
Define the exact date at which this timeplan becomes active
Only when Kind is configured as "One time"
From
Define the exact time at which this timeplan becomes active on the given day
Until
Define the exact time until this timeplan is active on the given day
A one time Timeplan that sets the general status to offline and even adds a tag to indicate there is a beach day going on that day.
A yearly timeplan to manage Christmas day as a closed day can be configured as following:
A weekly recurring schedule to manage a closed situation due to lunch can be configured as such:
The tags you can add as part of a timeplan need to be part of the Timeplan group. This group is automatically added to your bot Tags at install of the Timeplans skill. This way, whenever you add a tag in your timeplan, it will group it as a Timeplan tag:
So simply type the name of your tag and click on the "+ Create tag…" button that appears to create the tag inside the tag group "timeplan".
To create a well-functioning time plan, you must ensure that your time plan comes before all other system tags. For instance, if you have the online and offline situations, you must put your timeplan on the left side of these statuses. This way the system knows that it must execute the time plan on that specific day and will overwrite the other statuses.
The Zendesk skill enables you to interact with Tickets and Users, providing a direct integeration with your support desk.
The skill isn't installed automatically with your template. Therefore you need to install it manually.
Go to Skills -> Browse -> search for the Zendesk integrations skill.
To connect the bot to your Zendesk environment you will need to prepare the following information.
URL to your Zendesk environment
Zendesk API Token
The Zendesk API Token is your access token that needs to be created in the Zendesk 'Apps and integrations' section. To create this token:
Log in with your admin user in Zendesk and go to the Admin Centre.
Go to Apps and integrations > APIs
Click into Add API Token and name it "DialoX".
Save the API Key.
Navigate back to your app in DialoX, then to 'Settings - Zendesk'.
Fill the form with your Zendesk URL, the account email used to create the token, and the token itself.
After installing the skill and storing the credentials. You can use the Zendesk nodes in your flow.
Zendesk: Create ticket This will allow you to create new support requests in your Zendesk environment.
Zendesk: Get ticket Retrieve the current status of a ticket. Useful for customers when their ticket might be pending.
Zendesk: Create ticket comment Allow users to leave some extra details on a ticket. Can also be used to log private comments on tickets for internal use.
Zendesk: Create user Create a Zendesk end-user based on contact details extracted in the conversation.
Zendesk: Search user Look up a Zendesk user via their phone number or email address. The details of the user found will be stored in the Zendesk User variables.
Zendesk: Ask choice Allow users to select a value from a Zendesk custom field, providing predefined options for streamlined ticket creation.
When looking up a ticket or a user from Zendesk, the following "Ticket" and "Zendesk User" variables will be filled:
For companies that offer on call services to their customers it is quite a hassle to configure an on call schedule in their PBX. A bot with the Oncall dialer skill installed solves this issue quite easily.
After installing the skill you can simple add the node "Dial: On Call" to your flow and configure your agents and planning in the Content section of the platform. Using this approach even users without the right to edit your flows can change the On call schedule of your agents.
To install the skill go to Skills -> Browse
Click the On-call schedule skill so the following popup opens:
Click on the Install On call schedule button to install the skill in your bot.
Publish your bot
Now the skill should appear in the Installed page of your Skills section.
This skill introduces a new flow node to your bot called "Dial: on call". This node needs to be added to your flow in order to enable it.
Go to the Flows section of the platform
Find the place in your flow where you want to have the bot to dial the on call agent.
Click right mouse button, click on Dial and then on On call.
Now make sure your flow routes a link (Arrow) to your new Dial: on call node. In case this is the only node in your Flow, you need to connect it to the Entry trigger.
Open the side panel of the node by clicking on the title bar of the Dial: On call node.
Now fill in the text and the fallback number
Now go to the Content section and add your agents to the On-call Phonebook
Then configure who is available for on call services from when in the On-call Schedule page in the Content section.
In order for the On call function to work the system must know which agents there are to route the call to. The on call agents can be configured in the Content section.
Click on Content
Click on On-call Phonebook
Click Add
Fill in the following fields:
When the agents are configured we can configure the schedule. This will help the system to know when to route the call to which agent.
Click on Content
Click on On-call Schedule
Click Add
No fill in your first schedule:
One of the outcomes of a bot might be a human action that needs to be executed, like changing an appointment, processing a product return or update a database. In most cases these actions need to be performed by human employees that work out of tickets created in a ticketing system, like Jira.
This skill exposes the following new nodes to your Flow designer:
Jira: Create ticket
Jira: Get ticket
The skill isn't installed automatically with your template. Therefore you need to install it manually.
Go to Skills -> Browse -> search for the Jira integrations skill.
To connect the bot to your Jira or Service Desk instance you will need to prepare the following information.
URL to your Jira or Service Desk instance
Personal API Token
The email address of the user to whom the Personal API token belongs
The Personal Access Token is your own personal access token that needs to be created in your Jira profile. To create this token:
Log in to your Jira environment
Click on your profile button in the upper right corner and go to Profile
Go to Manage account, and then to 'Security', and click on 'Create and manage API tokens'
Provide a name of your token (any name is sufficient)
Set the expiration date to next year and make a note in your calendar to create a new token in time
Hit Create and store the API Token somewhere safe
Before you can use the Jira integration in your flow you need to configure the credentials needed for the bot the make the connection. This can be done in the settings.
Fill in the fields as described. Read the previous chapter to read how to get an API Token.
The user email must be the same as the user which created the API token.
The following flows shows how the skill can be used to create a ticket and then retrieve the ticket and display a certain piece of information from the ticket.
This flow introduces the following two nodes which are described in the Flows -> Nodes section:
Jira: Create ticket
Jira: Get ticket
The Planner skills can deliver the following type of outcomes
For the skill is able to support two different ways for determining which moments to allow to be scheduled. The availability of a certain moment in time can be determined according the following two strategies:
The planner can be configured to either create events (by not creating notes) or by creating todo's (by creating notes).
The planner will return availability based on either the free/busy or the slots strategy mentioned earlier.
Then there are two more settings.
Day limit This limits the amount of days a customer can plan ahead. E.g. for scheduling an appointment at a barbershop, we might want to have a much higher limit than for scheduling a callback appointment for pharmacies.
Minutes from now This prevents users from scheduling appointments that take place shortly after making the appointment. E.g. for realtors you might need to prepare a lot for an appointment, so there should be at least 4 hours between now and the start of the appointment. For callback appointments of an ISP it might be much shorter.
This node allows for four different conversation strategies for eliciting the plan:
In order to work with this data this skill is producing, the skill introduces the following variables to your Flow designer. They can be used to interpolate with your texts and questions in your Flow.
You can also store the made appointment in a variable. This variable holds the entire planned appointment. This allows you to take a more custom approach on what to do with the result.
The Security page allows you to change your password and to enable or disable multi-factor authentication.
Your password must contain at least 8 characters of which minimally one capital, one lower case and one numeric digit.
Note: You cannot change your password here if you log in with Microsoft, Google, Facebook or Operator.
The Hubspot skill enables you to interact with Tickets and Contacts from your own Hubspot environment.
The skill isn't installed automatically with your template. Therefore you need to install it manually.
Go to Skills -> Browse -> search for the Hubspot integration skill.
To connect the bot to your Hubspot environment you will need an API token.
The API Token is your access token that needs to be created in the Hubspot 'Integrations' section. To create this token we need to create a Private app:
Log in with your admin user in Hubspot and go to Hubspot Settings > Account Management > Integrations > Private App
Create a private app
Fill in the Basic information (name, logo…):
Choose the Scopes for the App (the scopes are the access permissions to the app: read contacts, create tickets…). For example:
To create and search tickets choose the scopes
Other > tickets
To create and search contacts choose the scopes:
CRM > crm.objects.contacts.read
CRM > crm.objects.contacts.write
Create the app and copy the access token
Navigate back to your app in DialoX, then to 'Integrations - Secrets'.
Paste the token which was provided when creating the private app
After installing the skill and storing the credentials. You can use the Hubspot nodes in your flow.
Hubspot: Create ticket This will allow you to create new tickers in your Hubspot environment.
Hubspot: Get ticket Retrieve the current status of a ticket. Useful for customers when their ticket might be pending.
Hubspot: Create contact Create a Hubspot contact based on contact details extracted in the conversation.
Hubspot: Search contact Look up a Hubspot contact via their phone number or email address. The details of the user found will be stored in the Hubspot contact variables.
When looking up a ticket or a user from Hubspot, the following "Hubspot Ticket" and "Hubspot contact" variables will be filled:
The standard bot skills work with the opening hours that are managed in the Bot settings section, see .
The skill will set a predefined tag when the current time fall within the defined day and time. Using the tag you can define in flow nodes, for instance to skip over a node or to .
Read more about tags .
The skill will set a predefined tag when the current time fall within the defined day and time. Using the tag you can define in flow nodes, for instance to skip over a node or to .
The Planner enables working with calendars, like scheduling a meeting or planning a callback appointment. The skill implements the Calendaring features of the DialoX platform. Developers could have a look for more details.
SIP
The SIP method to use for dialing
Choose REFER
Text
The text the bot should say just before dialing.
By embedding #{oncall_name} the name of the agent can be used in the text
Fallback
What number to dial when no schedule is found in the Content section
Name
Name of the agent
Number
Number of the agent
Make sure to enable or disable the extension option depending on the number you need
Extension
Uncheck for public numbers
To make sure the number is validated on correctness.
From
The date and time at which this schedule becomes active
Route to
The agent to route the call to
Event
An event is like any regular calendar event you would find in your Google or Microsoft calendars having a date, start time and duration.
Todo
A todo is modelled as a Note in the DialoX platform, but with a due date.
Free/busy
Scheduling is based on free space in the calendar since there can only be one event on any given moment in time. Once planned, this moment in time is no longer available for planning.
Slots
Scheduling is based on the predefined capacity for a certain moment in time, called a slot. This slot capacity depletes once all slots are planned causing this slot to be no longer available.
directly suggest 1 option
The bot will directly propose the first available option to which the user only has to reply with yes or no. When answering no, the bot will propose the next available option.
directly suggest multiple options
The bot will directly propose a couple of options out of which the user can choose. The user can also ask for more options after which the bot will present the next couple of slots.
first ask before suggesting 1 option
The bot will ask for the user's preferred date and time first before proposing an option that comes closest to the user's preference. The user can then answer with either yes or no.
first ask before suggesting multiple options
The bot will ask for the user's preferred date and time first before proposing a couple of options that come close to the user's preference.
Plan date
Start date of the plan (friendly formatted)
Monday 5 January
Plan ISO
Start date and time in ISO format
2014-01-05T10:00:00Z
Plan datetime
Friendly formatted start date and time
Monday 5 January at 10:00
Plan day
Name of the start date (relative)
Tomorrow
Plan time
Start time of the plan
10:00
Plan until
End time of the plan
11:00
Plan until ISO
End date and time in ISO format
2014-01-05T11:00:00Z
How to configure the settings of your app.
This section explains the usage of the inbox.
How to set up your User and Profile settings.
Here are the arcticles in this section:
The first page in your Profile is used for generic profile settings such as name, contact details and working hours.
Profile picture
The profile picture is used to show in the Web Widget and in the menu bar of DialoX studio to indicate your presence.
Full name
Your name.
Alias
The name you want to show in the chat to customers (to hide your own name for privacy reasons).
Your email address, used for notifications by the platform.
Mobile phone number
Your phone number, used for testing voice apps.
Time zone
So the app knows how to interpret your office hours.
Language
The language of the Inbox user interface. Note: It can only be selected in the Inbox environment and the language only applies to the Inbox.
Office hours
Your personal working hours. The system will use this to determine your presence.
Where do I configure the opening hours of our business?
Rules for escalation (i.e. forwarding to an agent, taking a note or deflecting to another channel) are often dependent on the opening hours of the business.
Go to Settings.
Click on Openings hours.
Enable or disable a day with the toggle.
Enter the opening and closing times in the time boes for the enabled days.
Click on the Save button.
Generally office hours will dictate the bots behavior according to the openings hours you have defined in the first tab of the opening hours.
Operator occupancy will show you a list of yourself and/or coworkers that are Available for chat through the bot's opening hours.
The studio settings section will give you the ability to save specific contact fields such as Last seen, Email, Phone, Language which will be converted into User details once contact has been made. Our Contacts page will store them accordingly.
To use tags in Flows or other parts of the system it is recommended to explicitly configure them in the Tags Settings. This way both the system as well as you and your colleagues can understand what tags are set. Even the system tags are listed here.
Get insights into your Apps performance by turning these toggles on (optionally):
Show as funnel on dashboard.
Show as KPI in dashboard.
Get insights and manage your Inbox by turning these toggles on (optionally):
Show as assignable in inbox (this will give you the opportunity to categorise a specific conversation into a designated inbox).
Show in inbox sidebar.
Get insights into your tag based conversation by turning these toggles on (optionally):
Show in tag analysis.
This paragraph gives an overview of all the tags that are set by the system.
online
offline
web_capable
The conversations happens on a web like channel (PWA, widget or studio)
The following tags are automatically set based on the basic user fields for name, email, phone and language.
user:phone
The phone number of the contact is known.
user:name
The name of the contact is known
user:email
The email of the contact is known
The use of specific tags can be used to quickly filter in your CRM. This way you ensure that you can create groups in your contact list using a tag. You can assign tags per user, but also in bulk (multiple) tags. For example, you could use this for quick filtering for a campaign.
Make sure to set the inbox tags as shown down below. You can set the tags via Contacts.
The first thing you need to take care of when setting up your app is to configure the languages and time zone you want to support.
Click on Settings in the main menu on the left hand side
Click on Identity to open the app Identity page (should be selected by default)
Type the name of your Bot
Change or add languages by clicking in the language field. Repeat this for all additional languages you want to support
Configure the Timezone to your preferred time zone
Configure the Country of origin
If your company has a privacy policy page, fill in the URL in the Privacy policy URL. There will be a button shown in the chat window with the customer so it will always be available to them, see Privacy below.
Click Save (you might need to scroll first to find the save button)
Click the Publish button to publish your changes
The privacy URL that you provide under Identity settings will be displayed in the Web Widget as "Privacy statement".
From time to time new supported languages are added. At the moment of writing this documentation the following languages are supported:
Dutch
German
French
Spanish
Danish
Finnish
Portuguese
Russian
Swedish
Turkish
Ukranian
Japanese
Polish
Latvian
Italian
Arabic
Hindi
And many more...
Some of the languages have a FORMAL option. It will enable the language produced by your bot to be in formal writing. For the dutch it means using "u" and "uw" rather than "je" and "jouw".
Optionally the icon can be replaced by your own. Click on it to see the options:
The logo is used for displaying in the chat widget (see image under privacy policy) and as avatar of the app when chatting.
The backups will support manual and automatic bot backups, automatically backup on bot upgrade and support mass upgrade of bots.
The Availability Settings in DialoX allow you to manage your online status and control when you are available to receive calls, chats, and other customer interactions. By configuring your availability, you ensure that communication is handled effectively and during appropriate hours, enhancing the customer experience.
To adjust your availability in DialoX:
Under Profile, specify your active working hours by setting start and end times. You can create different schedules for each day of the week to accommodate varying work patterns.
Once you've assigned the conversation to yourself you can either reassign the conversation to someone else you find more suitable (press the Reassign button and choose a team member) or take it yourself by pressing the Join button.
When joined, the input bar shows and the following new options become available to you.
Send your responses to the contact.
Stop being joined and be able to reassign or close this conversation.
Use this button to activate the team chat, to consult with one of your colleagues about this conversation.
When a new conversation is escalated to the Inbox it will arrive in the New folder where it will wait to be assigned to a user. The general idea is that you and your team strive to keep this folder as empty as possible. As soon as a new conversation is escalated into this folder it needs to be assigned as soon as possible.
Either users with the role Agent or Operator can then assign the conversation to themselves by selecting the conversation and clicking the Assign to me button. Now the conversation will move from the New folder to the Mine folder. Your colleagues can see the conversation move to the Assigned folder. This way, conversations don't get lost and remain transparent to the entire team. Once assigned, you can join the conversation in order to start responding.
You can also have someone else to handle the conversation by using the Reassign button. This buttons is only available when you or someone else is already assigned to the conversation.
There is an option for Organisation Managers to be able to take control of their bot by having a general settings section which is called Extra options. You will be able to Export (download a copy of a bot's code as backup) or Import (restore a backup of this bot from a zip file).
Optionally: there is a possibility to get the source code of a bot to be synchronizeed to a Git respository. Each time a publish is done, a git commit is made and is pushed to the configured respository. The synchronization works one-way only.
Even more options such as:
To use tags in or other parts of the system it is recommended to explicitly configure them in the Tags Settings. This way both the system as well as you and your colleagues can understand which tags are set. Even the system tags are listed here.
To make items in the Content section conditional to a specific state we use . Conditions are based on the existence or non-existence of tags. Any flow node can be configured to set a tag when executed. Tags can also be set automatically by the system based on a context or system event.
The conversation happens within
The conversation happens outside
The remember option in , , etc will store their value in the user object as well as set a user tag using the Assign-to property.
Click on your profile picture.
Click on the drop down list below your name in the menu bar.
Regularly update your status to accurately reflect your availability. Leverage settings to ensure you’re alerted to important updates while minimizing distractions.
Availability settings
Profile settings
Security
Notifications
Deactivate (bot name)
Deactive this bot to make it (temporarily) unavailable for new conversations.
Clone bot
You can clone this bot to make a backup copy or start a new bot based on this one.
Move bot
You can move this bot to one of your other environments.
Delete bot
With this button you can remove your bot, deleting all files and user data.
Some messages are quite generic for your business and can be re-used for more conversations. These messages can be added to the Canned Responses list so next time they are needed they can be "auto completed".
Click on the canned responses icon in the input bar when you joined a conversation.
Now a popup appears in which you can change, remove or add canned responses. When you click Save the canned responses are stored in the database, ready to be used.
Now you can start to type a sentence in the input bar. When the system finds a matching canned response it will offer it for selection.
Using the team chat function you can consult a colleague about the conversation you are having with a contact without the contact being able to see it.
Click on the little icon on the left hand side to open the team chat panel in the conversation.
Now you can invite a colleague to the conversation by typing the @ character which will allow you to pick one of your colleagues from a list.
Just pick one of your colleagues, type a message and press Send. This will notify your colleague about the question or remark. The conversation will now automatically be watched by your colleague.
There are two ways to get a conversation in the watched folder.
When the Watch button is used.
When invited to a Team Chat.
The Watch button can be found in top of a conversation.
Now the conversation will be available in your Watched folder.
The watching is continued until the Unwatch button is clicked which is now displayed instead of the Watch button at the top bar of a conversation.
When promises are made by your app that need follow up by a human agent, the app is able to create a Todo entry in your Today view in the Inbox view.
A Todo is like a note, except for the fact that a Todo has a due date whereas a note doesn't. So when a task or promise set out by an app has a specific due date, it is better to create a Todo.
The details of a Todo item can be opened by clicking on the drop down icon in front of the Todo item. The Todo will then unfold.
When the Todo is handled, in the above example that would mean this person is called back, the Todo can be marked as done by clicking on the checkmark button. This way you can easily recognize the handled Todo's compared to the ones that are still open:
On the left you will find the Notes which are made from via channels, in situations such as:
Notes will give Operators the opportunity to handle notes such as callback requests, additional information, etc, accordingly.
To Do
New note that hasn't been handled yet
Done
Note that has been handled accordingly
Assigned To
Assigning a note to a specific user
Mark as done
Marking the note as done
Unmark as done
Unmarking the note as done
Delete
Deleting a note
Open conversation
Re-engage the conversation
Export
Create an export of all notes inside of an environment
When you are joined you can use the input bar to type your message:
The icons displayed on the bottom within the input bar represent additional options for composing your response.
Team chat
Switch to 'team chat' mode.
Toggle formatting toolbar
Shows toolbar to enable bold, italic, etc.
Send file(s)
To upload and send a file (not image) from your device to the contact.
Canned responses
To manage canned responses.
Auto translate
Enable automatic translation.
Images can also be send by simply pasting them into the input bar (Ctrl+V on Windows and Cmd+V on Mac). Additionally, you can drag-and-drop files and images from the file manager onto the input bar to have them uploaded.
Either auto detect or choose the language by clicking on the "User speaks" field and then click on Enable. You might need to close this popup in order to continue chatting. From now on all incoming chat messages will be translated to your language and your replies will be translated to the language of the contact.
Your contact may respond to your message via emoji and not via text. This works both ways. Incoming messages via emoji will be rendered in the inbox as shown down below. Its good to know that emojis can only used on WhatsApp currently... so no other channel supports the emoji reactions yet besides WhatsApp.
By hovering over the text you can now choose to reply via Emoji. If you click on the + you can choose from a variety of emojis. Outbound reactions via emoji will be rendered in the inbox as shown down below.
Inside of a conversation it is now possible to reply to a direct message which allows for a more clear conversation method. This will also be shown in WhatsApp as a reply.
Push notifications use your browser to notify you even when the web page is closed. You will need to make sure your are correctly setup in order for this to work.
In the Inbox view, go to your Profile > Notifications and turn on the option to "enable browser push notifications".
The button Enable will register DialoX to your browser in order to send Push Notifications. Your browser will then, depending on settings, ask for your permission.
After confirming your permission, the Notifications page will show that the push notifications are enabled. From now on DialoX will be able to send you push notifications.
Your personal notification preferences can be accessed by clicking on Profile in the bottom left of your Inbox view. See below:
You can get various types of notifications and decide whether you want to get them via browser push or via email:
notifications about new conversations, or conversations that are forwarded to you
notifications when someone mentions you in a team chat
notifications when settings of the environment have changed
notifications when it is outside of office hours
notifications when new messages have come into a conversation you are assigned to (automatic after a new message has not been seen for 15 minutes)
Only when you are assigned to a conversation you are in a position to close it. The close button can be found on the right hand side in the bottom, next to the team chat button.
When a conversation is closed, it will be moved from the Mine folder to the Closed folder so you can always look back and see its contents.
(outside of office hours/no one available/closed)
(outside office hours/closed)
(outside of office hours/no one available/closed)
In team chat mode (), the input bar changes color and any messages will not be delivered to the end user but will stay internal. This way you can leave notes for your colleagues and @mention them.
When clicking on the auto translation () button you can specify which language to translate from and too when chatting to this contact. Clicking on the button will open the following popup page.
TBD
For every supervisor there is a function in the Studio view where you can filter the assigned operator conversations by using a operator picker and date picker. With this control you can get a quick overview of your current and handled conversations based on the operator you want to supervise.
By default the filter is off.
Make sure you have invited your operators in the specific environment on which you want to filter out the conversations. Below you will find an example of how to use the filter functions.
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.
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 platform will generate notifications from time to time to draw your attention to events that require your attention. These notifications will be collected in the notifications panel, so even when you miss a notification, or when you were to quick clicking it away, you can still find it in this panel.
You can find the notifications panel behind the button showing a little icon of a Bell in the upper right corner. The red dot in the icon indicates there are still unhandled notifications.
In the top of the panel there are three small icons and one larger button. From left to right:
Settings: links to the Notification settings
Mute / unmute: toggles between muting and unmuting new notifications
Unread / all: toggle between showing only the unread notifications or all the notifications
Mark all read: little power feature to mark all notifications as "read", so they dissapear from the unread list.
Clicking on a notification will bring you to the page that caused the event, for instance an Inbox escalation. This action will even mark the notification is read which therefore removes it out of your sight (when the unread toggle is enabled, see previous paragraph).
Besides helping you to address the event that caused the notification to happen, you can click on:
Unread: to mark the notification as unread or even delete it completely
Delete: to completely remove the notification from the database
When the amount of conversations is too much for a hand full of agents, or when the diversity of the conversation topics is too wide for one team to handle, you might want to consider multiple inboxes. This way you can setup an inbox for the different topics or different teams that you have.
Another good reason of having multiple inboxes is when you are using MS Teams for answering incoming messages and you want conversations to be handled on different Teams channels depending on their topic.
Inboxes are tags that are stored in a special tag group called Inbox. To manage the inbox tags, go to Settings -> Tags and open the tag group Inbox.
If the tag group doesn't exist, create it by clicking Add tag group.
Fill out the form as presented in the image above. Make sure to choose Tag type Single since we don't want conversations to end up in multiple inboxes at the same time.
The Show in inbox sidebar is optional. This setting will make sure the tag is also shown in the inbox sidebar and also enable filtering in the inbox.
Now add a tag for each of the inboxes you want to have using the Add tag button.
Click on Manage Environment in the bot switcher:
Now click on Members in the main menu.
Now add the inbox tags by clicking on the little pen icon.
The drop down will only show the tags from the bots in your environment that are marked by the Show as assignable in inbox toggle as you have read previously.
A flow can immediately assign a conversation to an inbox using the Tag option in the Escalate nodes:
An agent can also decide to assign a conversation to a certain inbox by using the Assign to button for any new conversation or Reassign button for existing conversations:
The Contacts page shows the contacts (end users) that engaged with your bot and operators.
By clicking on the + Create user button (Inbox view) or +Add Contact button (Studio view) a form will popup where you can fill in general contactdetails such as first name, last name, email, phone, choose language, insert a timezone and an optional free-form external id to identify your user(s).
By clicking the Save button the contact you will store the newly made contact in your CRM. By making new contacts, you will see functionalities to start connecting. It should look something like this:
In some situation you want to name your contacts, you can now change your contact by clicking on the name in the contactname field and adjust it accordingly.
By setting specific tags on a user you can categorise the user related to the specific subject. You can find the tags under Inbox by clicking on the name of the user, under the "start new conversation" the tags will be stored.
Get a quick export of your contactlist by clicking on Export. Choose from the following formats such as:
Excel (.xlsx)
CSV (.csv, ; as delimiter)
CSV (.csv, , as delimiter)
The settings of the Customer environment can be done from out the Administration section, or from out the Studio section.
Select the environment you want to maintain
Open the Settings page
The Customer settings page enables you to configure the Customer environment settings:
Settings
Advanced settings
Store settings
The following settings for a Customer Environment can be changed on the Settings page:
Display name
Organisation domain name(s)
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).
Notifications are generated by the platform based on several conditions. Please check that these conditions are met before calling upon support.
Is the user who expects to get notifications currently logged into the DialoX platform or is he the user who was last logged into the DialoX platform from your browser? (If not, the notification settings from the other user will apply.)
Is your browser open or is it at least running as a on your computer?
When you didn't enable push notifications or your browser or OS doesn't support them, the notifications will appear within the browser page:
Also when you have the Studio or Inbox opened in a visible browser tab, the system will show the notification as part of the browser page.
Only when all conditions for push notification settings described above are met, and you are currently not looking at a browser page with the Studio or Inbox loaded in it, the system will push the notifications to your PC. The way your PC will show this notification is dependent on your personal settings and specific browser you are using. On Mac OSX, working with Chrome as browser, this will look like:
For instance this way you can navigate as a team to create a workflow between Environments which have no but has a functional . And a client Environment in which you take on calls, conversations or .
Once you have made an order in Operator, it will be visable in your Home screen due to automatic provisioning for the Enreach Contact . Here you can see the Bot name, wether it needs to be connected or not.
All the 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.
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 .
The toggle Show as assignable in inbox is required to make it into an inbox filter. This way agents and flows (using the ) can use the tags in this tag group to assign conversations to.
Is the chat coming in during the of your application?
Are your configured as operator? Is the chat coming during your personal working hours? Have your colleagues check their settings too.
Did you check your ?
Do you have the in the same environment as the app? (being a member of the environment inherited from your agency is not the solution)
Toggle your own from unavailable to available to reset your notification preferences in the platform.
You get notifcations from Chrome on a Windows Desktop that look like this:
In Windows, go to Settings > System to configure the notification settings:
Turn on Notifications in general and for Google Chrome in particular. Also decide whether or not you want the notification to play a sound on your computer and if you want to see it on the lock screen.
If you want to receive the notifications even when you are in "Do Not Disturb" status in Windows (e.g. when you're in a video call, a call or you have put yourself manually on "Do Not Disturb"), you need to set priority notifcations for the Chrome app: Make sure that Chrome is shown in the list of apps that are allowed to send priority nofications even when you are in "Do Not Disturb status": or add Chrome to that list:
Go to the website and turn on the notifications for this website in Chrome:
Go to the Site settings and double check that notifications are turned on for :
You meet the criteria defined in ""
If you have set the MS Teams integration to monitor and respond to incoming conversations from the DialoX app integrated in MS Teams, you can define to be notified about new incoming conversations by MS Teams with an extra toast on your desktop that will look like this:
To get notifications form MS Teams about new conversations you need to have these settings:
Go to Notifications and activity and make the settings according to your general notification preferences:
Go to the MS Teams Channel that is connected to the DialoX chat application where the new conversations are shown, and click on More options > Channel notifications. Select to get Banner and feed notifications for all new posts.
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.
There are two advanced settings that can be managed by Customers and Agencies:
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.
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.
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.
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
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.
The functionality of the Dashboard serves as a homepage for your Bot(s). Here you can find specific details such as the traffic of the last 7 days, conversations/messages, your agency contract and a Get support page which leads you to the DialoX Helpdesk.
In your MS Teams client, click on the three dots next to your profile image and open Settings.
Now you can manage your personal authentication settings in the .