Chatbot settings

Here you can change the parameters to customize your chatbot and its behavior.

General settings

Here, you can control the availability of the chatbot and whether to include the links to the responses.

Disable the plugin temporarily

Selecting this option disables the AI bot, so you can speak to your customers without its interruptions.

Data source information

If you want the chatbot to include the most relevant links in its response, check the Show source links in response checkbox.

This is how the response with links looks:

We include 5 found links, the first one is marked as "Source", and others as "Additional sources" - by default. The titles are automatically translated into the user's language:

You can change the number of shown links:

Both numbers could be zero, and no links will be shown. By default, if you don't change this setting, we show 1 main link and 3 additional links.

Collect button click statistics

You can select this option to allow our system to collect the stats on the button clicks.

You can review the statistics for your project in the corresponding tab (opens in a new tab).

Widget settings

Here, you specify how your chatbot and its responses look:

Chatbot icon

You may choose from 3 options:

• the default Crisp userpic
• a "cute" Enum robot userpic
• your own URL to a userpic.

Default Crisp userpic:

a cute robot:

your own URL:

Chatbot name

This name is shown as grey text beside the chatbot's icon. You may leave it empty or enter your chatbot/company name.

The Crisp label

Switch this setting on to hide the label "bot" by Crisp.

Custom behaviour & Automation

Here are 7 sections, all collapsed by default:

Chatbot in session

Here you define your chatbot's automatic behaviour during the sessions:

Never translate predefined messages automatically (like greeting and other predefined messages)

By default, all the messages you enter, are translated automatically into the language the question was asked in. If you set this settings on, the messages will be sent as is, without translation.

Wait to reply

Check this flag if you want the chatbot to reply only after the user gives their phone number or email. Use this option only if you ask for contact data in Crisp. The example of the Crisp settings:

These settings can be found in the Settings --> Website settings --> Chatbot & Email Settings --> Chatbox behavior (in the Crisp dashboard).

Pass the user name to the chatbot, when known

If you collect email during the conversation (this setting can be found on your website on Crisp) Crisp will extract the name from email.

This name will be passed to the chatbot if you set up this setting on.

Here is how the chatbot is using the name:

Send this message when a conversation starts

When a user starts the conversation and says hi, you may want the chatbot to greet the user back. Enter your message in the field if you want this behavior.

Do not show buttons on the greeting message

With this setting set ON, the chatbot will not show the buttons on the greeting message.

Pause the chatbot when agent joins the conversation

If this checkbox is checked, then every time when you or your agents join a conversation with the chatbot, the chatbot will be quiet.

Re-run chatbot when conversation is resolved

This indicates to re-run the chatbot when you click the "Mark this conversation as resolved" in the Crisp dashboard:

Send this message when re-running chatbot

It's a good idea to let your user know that the chatbot is running again so they can enjoy your support 24/7.

Set Crisp conversation segment when a session starts

You can assing one or more Crisp segments when the conversation starts. It may be very useful for a statistical analysis later, for instance, to distinguish conversations with chatbot from others. You add one or more segments separated by commas:

User requests human assistance

Specify what the chatbot should do when user wants to talk to human beings.

1. Send this message when user requests for human

Enter a message you want to be sent to the chat when a user requests human assistance. Usually, it's just a piece of information that humans will join the conversation soon.

2. Pause the chatbot when user requests human assistance

Turn this checkbox on if you want the chatbot to be quiet after a user requests for assistance.

4. Notify me when user requests assistance

Currently, you can only send email(s) to notify you that somebody waits for you (we will add more notification channels in the future).

To add an email, click the "Add a notification" button, enter email, and press the Return button.

Here is the example notification sent by email:

Note The chatbot now recognizes when users request assistance, even when initiated by the chatbot itself, and acts accordingly. Previously, the chatbot's decisions were based solely on analyzing the user's request. For example, if a user said, "Connect me to a human agent," it was recognized as a request for human assistance, and the chatbot could send a notification (if this feature was enabled). Now, the chatbot can also base its decision on its own response. For instance, if it replies, "I'm going to pass your request to my human colleagues," it may send the notification as well!

Standard Buttons

Here, you can specify some standard buttons that are attached to every message.

Below each option, there are preview buttons where you can see how they would look in your chatbox.

This is how the buttons look for a user:

1. Feedback buttons

They allow a user to give your chatbot feedback: good or bad. You can enter your own text labels for both buttons:

In your Crisp dashboard, you will see the feedback:

2. Mark resolved button

This button allows a user to mark the conversation resolved (or closed).

When a user clicks the button, it's resolved what you see in your Crisp dashboard:

3. Request a human operator

When a user clicks this button, the corresponding response and notification will be sent if you set them up as described here (opens in a new tab).

Custom buttons

You can define to show the custom buttons depending on the class of user request. By "class", we mean some "mood of the query". For example, the "How are you?" query can be classified as just a "query" and the "Why is that? I don't like it!" can be classified as "frustration". We have bunch of predefined classes:

• Human assistance request
• greeting
• thanking
• apologizing
• question
• welcoming
• opinion
• query
• user wants help.

Now, you can use one of our predefined classes or add your own class and assign the corresponding button to it. The button could have the following properties:

• label
• icon (emoji)
• value (for inner using)
• URL of a page to show on click (that can be shown right in the Crisp chat, or opened in a separate browser tab).

Let's see how it works.

1. Click the Add a rule button:

2. A new rule is added to the end of the rules:

3. Select from the class of query "thanking" and then add two standard buttons:

Save the settings and let's test it in our chatbot:

4. Now, let's create our own class and add a custom button on it. Say, our website is about technical stuff and we want a button to be shown as soon as a question is about drones. This time, add a custom button instead of a standard one:

Let's test it in the chatbot:

After scrolling to the end of the response, we see our button:

5. Let's make the button to redirect to the website about drones, for example to this website: https://dronelaunchacademy.com/resources/how-do-drones-work/ (opens in a new tab)

Just add this URL and make sure that the Where to show parameter is "in the chatbox":

So, now, when you click the button, this page will be shown right in the chat (to return back, click the button with arrow in the top left corner):

Some ideas on using this redirection feature

Why would you use this feature? It's actually can enrich your users' experience and collect more valuable information for you and your users. For example, you can :

• redirect to the feedback website with the form to collect some data
• show users some information from other pages (like weather report, flight's stats, or anything else)
• create a ticket
• participate in a poll
• even sell goods.

Automation based on a schedule

You can specify the time slots where you want the chatbot to be quiet or active. Click the Open schedule calendar to create a schedule:

Open the calendar:

First, decide if you want to specify the timeslots for your chatbot to be active, or paused (select what is less), then double-click in the corresponding place to create a time slot. Specify the parameters for your time slot:

To create a series of similar timeslots, just select the Repeat value for the corresponding dropdown and specify the recurrency parameters. After you've done it, save the settings and your calendar will be updated. You can change the action for the timeslots as well as the series parameters - just double-click on a time slot.

Also, you can change a separate slot: use your mouse to drag the start and end, or double-click to change the parameters.

Here, an example of the schedule:

Click the Ok to close the schedule window, then the Save changes button.

Automation based on the operators online presence

Set the chatbot to automatically turn on or off based on your online presence! When you're stepping away from your computer, you can update your status in Crisp, and our chatbot will activate to handle your incoming requests. Here is where you set this up in the Crisp (Settings -> Availability):

When you return, simply change your status, and the chatbot will be disabled until next time. To enable this behavior, toggle one or two switches.

Coordinate the chatbot with Crisp Triggers

If you use Crisp triggers, you may consider using these options to avoid duplicating answers (from triggers and the chatbot).

1. Wait for Crisp Trigger response Check this option to make the chatbot wait for the trigger's response. If not checked, the chatbot will answer without waiting.

2. Wait time (in seconds) for Crisp Trigger response Specify how many seconds to wait. From our experience, 4 seconds is good but you may find it too fast or too slow, depending on your trigger's parameters.

Control the chatbot via Crisp bot, or from JavaScript

If you want that the chatbot doesn't start answering immediately, you may pause it until it gets the corresponding signal. The signal can be sent by the Crisp chatbot as described in the article about the integration of Enum and Crisp chatbots, or controlling it via JavaScript (opens in a new tab).

If you don't want such behavior leave the default option (the first one) as is:

Paused sessions

Here you will see data regarding any chat sessions in which AI has been deactivated due to an agent joining the conversation (if you have the setting toggled on).

Use the chat page button to jump into the active chat inside Crisp:

Click "Run again" to reactive the AI in the paused session:

The AI will resume answering questions; however, if you join the conversation again, the AI chatbot will be deactivated again.

Crisp integrations

We support most of Crisp's integrations. All you need to do to integrate our chatbot into Crisp's integrations is to set it up with Crisp, and then select the corresponding integration in this tab:

The live test

You can test your chatbot right from the Enum dashboard before exposing it to the public. Just click the Show Crisp chatbox button and you will see the button on the right bottom corner (wait several seconds if it does not appear immediately). Click on it and interact in the same way as if it's placed on your website.

Here, you also can specify whether you want the chatbot to run everywhere or only here, in this test environment. By default, this switch is off but if you set it on, the chatbot will work only here.