# Settings

# Bot Information

In this part you can find all the "basic" information about your chatbot.

  • Name of the chatbot: This is the name of your version.
  • Description of the chatbot: Description of your version

# Webview

The webview is a window that can be displayed on the web to give more information to respondents. You can customize the content of the webview. Here is how the picto that opens the webview is displayed: Webview button

And the opened webview Webview content

You can modify:

  • The title: This is the title of the help window
  • Description: This is the content of the page. You can add HTML code that will allow you to format the content and add images if you wish in the help window as in the image above.
  • Text Displayed on Mouseover: On mouseover of the information icon (hover to see geek language) you can customize the text that will be displayed for your respondents.

# Analytics

  • Activate Google Analytics: You can activate Google Analytics with your tracking code. All data will then go directly into your GA
  • Activate Google Tag Manager: You can do the same with GTM. However for the moment we do not track events in GTM for data privacy reasons.

# Push Notification (in the browser)

Sometimes you may need to receive push notifications to alert you that a respondent needs help, for example. There are workflow actions to send push notifications to the chatbot management team. To receive this notification, you simply need to enable push notifications.


Everyone who wants to receive the notification will have to enable this option on the dashboard. It is specific to each user.

# Reset on resumption of a conversation

This option allows you to resend the introduction message to respondents who haven't interacted with the chatbot for a while (10 min). (design.shouldReinitConversation) This option will only be valid for web chatbots

# Text of the input modification buttons

In action type skills, we recommend to always put validation resources. These resources are automatically generated by Vizir with messages to validate the retrieved data and buttons to allow the respondent to validate the answer or modify each answer.

In the case of the modify buttons, we start with a very simple principle of modify {resource_title}

You can change the value of these buttons for all your skills actions from this interface! Warning however, since we want to keep the ability to edit a particular response, changes made here will not be passed on to existing resources, but only to new resources created after this 'Modify' is changed.

So, if you want all the modify buttons to be a particular color with a particular text, you have to do it before creating the validation resource.

You can customize the design of the button types in the design part of this page.

# Email service

In 2020, we encountered difficulties with our "historical" email provider Sendgrid. (design.emailProvider)

So we decided to let the customers choose their own provider if they want. The deliverability is assured for vizir.co domain names but if you wish to use your own domain name please contact our technical team (it@vizir.co) so they can tell you how to proceed.

# Design

See the page dedicated to the design.

# Login

To activate this option please contact it@vizir.co

# Notation

The rating module will allow your respondents to give their opinion on the chatbot.

It will be displayed on the respondent's conversation in this way Rating module

You can decide to display it on the left of the screen in the advanced settings of the rating module on the Vizir dashboard Rating module


The data will be saved if (and only if) the user has already spoken with the bot. We do not save the data of a user who has not yet interacted with the bot. We believe that this data is not "legitimate".

# Questions

You may add as many questions as you wish. However, we recommend limiting the number of questions (2 or 3) if you want the respondent to achieve their desired outcome. Question settings

You have different options for the questions which are shown below Scoring module: options

  • Question
  • Subtitle
  • Question type: note, email or free text
  • Next: value of the button to go to the next question
  • Predefined value for the free text field: Placeholder that will be visible before the respondent writes the answer. Give an example of the type of feedback you expect.
  • Error message value: If the respondent enters an invalid answer, we will display this message (very useful to validate an email, for example)

# Advanced settings:

  • Button text: Value that is displayed on the button for the respondent.
  • End message: Message that will be displayed when the respondent has answered all the questions. The purpose here is often to thank them for their feedback 😃
  • Single Response: If you enable this option, if the same respondent answers the scoring module twice, we will overwrite the first answers with the update.
  • Position: Allows you to display the module on the left or right side of the screen as you wish.

Advanced settings of the scoring module

# Options

The procedure and FAQ options can be activated on the FAQ or scenario skills. Activate procedure options

The procedure and FAQ options will allow you to automatically display buttons on all resources of your skills.
You can disable the display of any (or all) of the buttons on a particular resource See Resources / Show option buttons.
Here are the different types of buttons that can be displayed:

  • Problem resolution button: This button will allow you to validate that a respondent has solved his problem with the chatbot. You can trigger a workflow when a respondent clicks on this button to store this value in an excel or send an email to congratulate you for the time you saved to this respondent 😃.
    You can disable the display of this button at the resource level if necessary.

  • Escalation Ticket Button: This button is the natural counterpart of the first one. It will allow your user to tell you when they have not succeeded in solving their problem independently. In most cases, we recommend creating a ticket in your support tools (IT or HR) to forward the request to the appropriate people in the company.

  • Next button: Visible only in scenario type skills. This button will allow the respondent to navigate to the next resource without you having to add a next button by hand. The advantage of using this button vs. a button in each resource is of course the time savings at setup but also the maintainability of the chatbot; you will only have to change the value in one place if you want to change it.

  • Menu button: Visible only in FAQ type skills. This button will allow respondents to go directly to the Menu (or any other resource of your choice) from the FAQ resources. We have chosen to display it only on FAQ questions because in the other cases (action and scenario skills) our goal is that the user goes to the resolution of his problem (or the end of the action). You can activate or deactivate the display of this button in the resource.

  • Back button: Visible only in the FAQ type skills. As the name suggests, this button will allow the respondent to return to the previous question. We looked for many ways to make this button "different" but our desire to remain compatible with the various third party platforms (Slack, Teams, Hangout) pushed us to leave it as a button.

The last option accessible in the procedure options is the option to choose the position of these buttons. It's simple, either you position them before the other buttons (if there are any) or after them. If the option is true, then the "procedure options and FAQ" buttons will be positioned before the buttons of the sent resource.

More information in this documentation