> For the complete documentation index, see [llms.txt](https://docs-en.dydu.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-en.dydu.ai/contents/global-sentences.md).

# Global sentences

Global sentences represent bot answers during a dialog that are not handled directly by the knowledge base and that can be used to handle particular situations.

Go to **Content > Global sentences** to handle global sentences in your bot.

### Misunderstood sentences

* **Answer for misunderstood sentences**

This sentence is provided by the bot when it has not been able to understand the user's request.

* **Too many misunderstood sentences**

This response is provided by the bot when it has failed to understand several questions from the user during the same conversation. By default, this phrase is disabled, so you must enable it to make it operational. Once activated, you must specify the number of misunderstandings necessary for it to be triggered then click on "Update".

You can leave this general phrase disabled in case, for example, you use a [complementary answer](https://docs-en.dydu.ai/contents/knowledge/knowledge-types/complementary-answer.md) type knowledge to trigger a Livechat escalation after 3 misunderstood phrases.

### Invalid questions

* **Default answer for too long questions**

When a user question is too long (more than 1,000 characters), the bot will give this answer.

* **Answer for empty sentences**

The bot will provide this answer when the user sends an empty request.

### Links

* **Click on links**

When the user clicks on a link (redirection to an external URL for example), the bot will provide this response.

* **Links open in new tabs**

The bot tells the user that the link they just clicked has opened in a new window.

### Livechat

* **Automatic welcome sentence when a livechat is accepted by an operator**

You can activate this phrase so that it is sent automatically when the operator picks up the conversation. This saves your operators from having to manually enter a greeting phrase.

**Note**: after defining the welcome sentence, you need to click on **"Enable this answer"** to make it effective.

{% hint style="info" %}
You can display the Livechat operator's first name using the following syntax: **${account.firstname}**.

Make sure that a first name is correctly entered for each Livechat operator on the BMS.
{% endhint %}

{% hint style="info" %}
If you use the [Salesforce Livechat connector](https://docs-en.dydu.ai/livechat/salesforce-livechat-connector), the welcome sentence is sent automatically as soon as a Salesforce operator joins the conversation. To display this operator's name, use the following syntax: **${capture.operatorName}**.

The name displayed is the operator's name as defined in Salesforce.

Example: "Hello, I'm ${capture.operatorName}, how can I help you?"
{% endhint %}

* **Automatic sentence at the end of the Livechat dialog**

You can add a phrase like “The conversation ended”.

* **Sentence sent to reengage the user**

This message is automatically sent to the user when there is a [period of inactivity](https://docs-en.dydu.ai/livechat/dydu-livechat/dydu-livechat-setup/general-settings.md). The length of this period is configurable in the live chat settings, and it starts from the moment the user last sent information.\
The goal is to re-engage the user and ensure they are still present, in order to avoid an automatic closure of the conversation ([conversation timeout](https://docs-en.dydu.ai/livechat/dydu-livechat/dydu-livechat-setup/general-settings.md)).\
If the operator's status is "searching for information," the message is not sent.\
*Example: "Are you still online?"*

* **Reengage sentence sent to the livechat user**&#x20;

This message is automatically sent to the user when the operator they are chatting with sets their status to one of the following: "searching for information," "consulting with supervisor," or "on the phone." The length of this period is configurable in the live chat settings, and it starts from the moment the user last sent information.\
The purpose is to ask the user to wait, keep them informed about the situation, and ensure they are still present to avoid an automatic closure of the conversation ([conversation timeout](https://docs-en.dydu.ai/livechat/dydu-livechat/dydu-livechat-setup/general-settings.md)).\
*Example: "Please wait a moment while I gather the necessary information."*

{% hint style="info" %}
The durations before sending the sentence to reengage the user and the re-engagement message can both be configured in the Preferences menu -> Livechat parameters -> General -> Timeouts.
{% endhint %}

* **Sentence when the livechat automatically ends**

This phrase is sent to the user when the Livechat session has reached a defined [period of inactivity](https://docs-en.dydu.ai/livechat/dydu-livechat/dydu-livechat-setup/general-settings.md). Its purpose is to notify the user when the Livechat session has ended and provide them with instructions on what to do next.

* **Sentence to welcome users to the livechat on the debug mode**

This phrase is only sent when a user requests a Livechat escalation using the keyword **#livechatconnectiondebug#** and an operator is available with status **'debug'**.

This allows you to debug or perform Livechat tests without disrupting the production service. The operator logs in with the status **'debug'** and the end user sends the keyword, which ensures that escalation is only done to the operator in debug mode. The greeting phrase confirms that the connection is established for debugging.

* **Sentence when no operator is available**

This is a phrase that appears when the user asks to speak to an operator and there are none available.

* **Sentence when the Livechat service is closed**

This is a phrase that appears when the user asks to speak to an operator while [Livechat is closed](https://docs-en.dydu.ai/livechat/dydu-livechat/dydu-livechat-setup/general-settings.md).

### Inaccessible answer

* **Default answer for disabled knowledges**

When a knowledge is not published, your bot explains to the user that he has been able to understand it but can not provide an answer.

* **Default answer when action is empty**

When a knowledge answer is empty, your bot explains to the user that he has been able to understand it but can not provide an answer.

### Various

* **Refocus sentence**

This sentence is added at the end of the non-business bot's answers to refocus the dialog.

* **Answer in case of internal errors**

When an internal error occurs, the bot will provide this answer.

* **Rewords introduction**

Sentence to introduce reword when the bot isn't sure.

* **Global suggestion for rewords**

This global sentence allows you to add a reword sentence (when the bot did not understand the user sentence) and allows you to redirect the user to another knowledge. To do so:

1. Activate the answer with the **Enable this answer** button.
2. Select the knowledge to which the reword will redirect the user and fill in the title (via the text editor > **Edit**) which will be displayed from the dialog box.

<figure><img src="https://264031769-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPMvi3Izk7dvjl9HitZpp%2Fuploads%2FdI6u8qGhIDMnbqQZhRkn%2Fimage.png?alt=media&amp;token=c03b59c9-f0e5-47f7-afb5-e875502397ba" alt=""><figcaption></figcaption></figure>

3. Click **Update**.

Thus, when the bot does not understand a reword, it will propose to the user (in this example) to click on **No suggestions can answer my question.** which will return it to the knowledge **Other** (in this example) created previously.

Note: consider disabling satisfaction surveys on knowledge items to which the global suggestion redirects.

### Livechat waiting queue

* **Sentence when leaving Livechat queue**

Sentence when the user enters the queue but decides to close the window.

* **Sentence when no operator is available for queuing users**

### Livechat operators

These are sentences describing the status of the operator and the user when he is writing his answer.

### Mail

These are sentences related to email options.

### User feedback

These sentences are displayed in the chatbox when the user indicates that an answer does not satisfy them (satisfaction survey enabled in the chatbox).

* **Introduction sentence when the user is not satisfied with the answer**

Sentence displayed above the dissatisfaction reasons. *Default value: "I'm sorry I wasn't able to answer your request. Can you tell us why?"*

* **Sentence asking the user to leave a comment**

Label of the comment field, inviting the user to leave a comment. For example, you can change it to state that the comment will not lead to a call back from an advisor. *Default value: "Do you have a comment ?"*

* **Placeholder of the comment field**

Text displayed in the comment field as long as the user has not typed anything. *Default value: "Enter your comment..."*

* **Sentence displayed after the comment has been sent**

Sentence displayed once the comment has been sent. *Default value: "You can count on me to pass on the information!"*

<figure><img src="https://264031769-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPMvi3Izk7dvjl9HitZpp%2Fuploads%2FFTtAEHvbmhmzubZEn1dW%2FCapture%20d%E2%80%99%C3%A9cran%20du%202026-11-10%2009-06-55.png?alt=media&amp;token=b0e944e4-f111-453b-837c-3d4fc3132235" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
These sentences are displayed as plain text in the chatbox: formatting applied in the editor (bold, links, etc.) is not kept. If a sentence is not customized, the default value is used.
{% endhint %}
