# Zendesk Livechat connector
If you are using Zendesk live chat, you will find below the configuration steps required to set up interoperability between BMS Dydu and Zendesk.
## Step 1 – Configurations in BMS Dydu
### A – Activate the Livechat submenu:
1. Go to **Preferences – Bot – General**
2. In the **Livechat Escalation submenu > escalation type**, select **ZENDESK** from the dropdown list.
3. **Save** your selection.
### B – Link the Zendesk connector to your Dydu bot
Go to **Preferences > Livechat Settings > External Connector**.
In this section, you must provide 4 types of information:
* Mandatory – Zendesk connector (domain name, app id, integration id)
* Mandatory – Conversation API key (key id, secret key)
* Mandatory – Zendesk API (email address, API token)
* Optional – Identity mapping (sender id)
Below you will find details on how to fill in each field:
## Step 2 – Retrieving information from Zendesk
### Field 1 – Zendesk connector
These are the Zendesk connector data that you obtain via the Zendesk interface.
The domain name can be found in your browser's URL when you are logged into your interface. Here, the domain name is **dydu-32357.zendesk.com**
To obtain the last two required pieces of information, go to the Zendesk admin center to create an integration, as well as an API key for this integration.
To do this:
1. Click the **gear icon in the sidebar > Go to the admin center**
2. Go to **Apps and Integrations > Conversation Integrations > Create an integration**
3. Add a **name** and the **Webhook endpoint URL**, which you can find in the livechat settings in the section “**Webhook URL to provide to Zendesk**”.
4. Check all three boxes: **Include full user, Include full source, and Conversation message**, then click **Save**.
5. You do not need this information; you can click **Next**.
6. On the **details** page of the integration you just created, you can find the **app id** and **integration id** that need to be entered in the livechat settings.
7. Finally, you need to create an API key associated with your integration. To do this, in "**API Keys**," click on **Create an API key**.
8. Add a **name**, then click Next.
9. You do not need the information shown in the pop-up. **Simply creating the key is enough**.\
Click **Next** to generate the API key.
### Field 2 – Conversation API key
1. To obtain the two required fields for this section, go to the **admin center** and click on **Apps and Integrations > Conversation API > Create an API key**.
2. Add a **name** and click **Next**.
3. In the pop-up that appears, you will get the key id and the secret key, which you can copy and enter into your livechat settings.
### Field 3 – Zendesk API
1. To obtain the email address of the Zendesk account and the associated API token, go to the **admin center** and click on **Apps and Integrations > API Tokens > Add an API token**.
2. Add a **description and click Save**.
3. Your **API token** is now visible; **copy it** and **enter it** in your livechat settings. The Z**endesk account email field** corresponds to **the email address of the account that created the API token**.
If you have any doubts, you can find this information on the API Token page. The user's information is visible by clicking on it.
4. In **Apps and Integrations > API configuration**, make sure that the "**Allow API token access**" box is checked.
### Field 4 – Identity mapping
To provide a more personalized conversation experience, the Livechat operator can have additional information about the chatbot user. You can retrieve information that will be visible to the operator on their Zendesk interface. To do this, you need to create a knowledge item that uses a variable to capture the information the chatbot will share with the Livechat agent.
### Example configuration to retrieve the user's email address
1. Create a knowledge item as shown below with the variable "mail" as free input:
2. Use the variable name “mail” to fill in the Identity mapping > senderId field in your Livechat settings.
## Step 3 – Test escalation to Zendesk Livechat
1. Create a skill on the BMS
1. Go to **Preferences > Livechat settings > Skills**
2. Create a **skill** that will then be used for creating a knowledge item. To do this, click **Add**, enter a **name**, and click the **button on the right to confirm the creation** (example with the skill Animal).
If you already have an existing group in Zendesk and do not want to create a new one, simply use the same name.
When the skill is created, to create the group in Zendesk associated with the skill, go back to **Livechat Settings > External Connector** and click Update.\
If no group with the same name exists in Zendesk, you should see it appear on the Zendesk interface. In the **admin center**, click **Persons > Groups**.
{% hint style="info" %}
Skills in BMS correspond to groups in Zendesk. Using them in a knowledge item allows you to assign the ticket to a group when it is created. For this, the group must contain at least one user.
{% endhint %}
To add a user to a group, simply click on the group in question, then click the "+" button on the right next to the user you want to add.
2. Create a knowledge item on the BMS
Then add the context condition to the knowledge item. This context condition is automatically created when the skill is created in the BMS.
{% hint style="warning" %}
Don’t forget the “connect to livechat” GUI action in the response options of the knowledge item you just created.
{% endhint %}
3. Livechat escalation test
Don’t forget to publish the knowledge item. Open the preview page of your chatbox created via Channels and trigger the knowledge item created in step 2 to activate escalation to Zendesk Livechat.
### Expected results
* **In the Dydu Chatbox** : the end user switches to a conversation with a human operator while staying in the same conversation. They can receive messages and attachments sent by the operator in real time.
* **On the Zendesk interface** : when a new message arrives, the operator receives a notification. They can access the conversation from the notification or the ticket list, view the conversation history, reply to the user, and send attachments. The ticket must be assigned to a group if you have a context condition that matches a skill defined in the livechat escalation knowledge item.
