# About Blinger.io

## General information

**Blinger.io** is an omnichannel solution, enabling companies to communicate with their customers via various channels in a "unified interface"

![](/files/-LpDl8uOyQinxqyjLFp7)

**The solution supports 15 integrations:** WhatsApp, Facebook (Messenger and comments), Instagram (Direct), WeChat, Skype, Telegram, Viber, Vkontakte (Dialogues and comments), Odnoklassniki, Line, Kik, Twitter (direct messages and comments), Twilio Chat, Email, Online chat

![](/files/-LpDlE0cD4aUH26fvDeY)

**You can enable omnichannel customer support with the help of Blinger.io in:** Zendesk, Intercom, Salesforce, Kayako, Bpm'online. For a more flexible integration you can use **API и Webhooks.** 

## Technical requirements

|              |                                                                                      |
| :----------: | ------------------------------------------------------------------------------------ |
| **Network:** | High-speed internet                                                                  |
| **Browser:** | Google Chrome, Mozilla Firefox, Opera, Safari                                        |
| **Address:** | <https://blinger.io/[> or 95.213.151.140]\(<http://95.213.151.140>),  95.213.199.157 |

{% hint style="info" %}
We don't advise using Internet Explorer - it doesn't let you work in real-time mode.
{% endhint %}


# Quick launch

## General information

This is a manual that helps you to configure Blinger.io and start working with it.

First you need to decide what channels (social networks, instant messengers, email) you plan to add. The geography of messaging apps' popularity is presented below:

![More info here: https://www.messengerpeople.com/global-messenger-usage-statistics/](/files/-Lp2WD8La4aBTxYxTj1B)

Blinger.io provide you to work in 3 different ways:

* using Blinger.io interface
* in the interface of one of helpdesk/CRM solutions that [**we have integrated**](https://help.blinger.io/documentation/integrations)
* in a third-party solution using [**Blinger.io API**](https://help.blinger.io/documentation/api)

depending on this, there are 3 options for “quick starts”

## Using Blinger.io interface

Follow these steps to configure Blinger.io:

1. Add the channels to the "Applications" tab ([**manual**](https://help.blinger.io/documentation/section-apps/adding-accounts))
2. Add operators ([**manual**](https://help.blinger.io/documentation/tab-operators))
3. Place the widget on your website ([**manual**](https://help.blinger.io/documentation/tab-widget))
4. Set up an autoresponder ([**manual**](https://help.blinger.io/documentation/settings/autoresponder))

**You can get to work!**

{% hint style="info" %}
Before starting work, we suggest you look at the following manuals:

* [How to work with "Conversations" tab](https://help.blinger.io/documentation/conversations)?
* [What are the additional settings?](https://help.blinger.io/documentation/settings)
* [How to set up notifications?](https://help.blinger.io/documentation/notifications-for-new-messages)

(links is clickable)
{% endhint %}

## Work through integration

Follow these steps to configure Blinger.io:

1. Add the channels to the "Applications" tab ([**manual**](https://help.blinger.io/documentation/section-apps/adding-accounts))
2. Integrate with one of the helpdesk/CRM solutions ([**manual**](https://help.blinger.io/documentation/integrations))
3. Place the widget on your site ([**manual**](https://help.blinger.io/documentation/tab-widget))

**You can get to work!**

{% hint style="info" %}
Check how you can integrate Blinger.io widgets and:

* [Freshdesk](https://help.blinger.io/documentation/integrations/freshdesk)
* [Zendesk](https://help.blinger.io/documentation/integrations/zendesk)

(links is clickable)
{% endhint %}

## Using Blinger.io API

Follow these steps to configure Blinger.io:

1. Add the channels to the "Applications" tab ([**manual**](https://help.blinger.io/documentation/section-apps/adding-accounts))
2. Get the Blinger.io Token API from Support
3. Integrate with a third-party solution using the API methods from the documentation ([**manual**](https://help.blinger.io/documentation/api))
4. Place the widget on your site ([**manual**](https://help.blinger.io/documentation/tab-widget))

{% hint style="warning" %}
Use Webhooks for incoming messages (from clients), and for outgoing messages (from operators) you need to use "Send message" method
{% endhint %}


# Customer cases

## Belavia supports customers only in social networks and messaging apps

**Problem:** The airline had problems with the speed of reaction to message requests from their customers, which were contacting them via online chat. A not processed message request from a customer quickly turned into a "lost message request", because the customer was leaving the site of the company due to a long waiting for an answer (the expected reaction time to a message request in online chat is 2 minutes). The company decided to take a risk - it disabled the online chat and left social networks and messaging apps as customer support support channels, despite of the fact, that before disabling the online chat 50% of text message requests were coming from it.

**Result:** The volume of text message requests after disabling of online chat didn't change - it was redistributed towards other channels (social networks and messaging apps). Hence, Belavia has won the battle with "lost message requests", because the contact point of the customer shifted from the site to social networks and messaging apps. When working with social networks and messaging apps, there is a 100% probability that the customer will get a response, the open rate of such messaging is not less than 96%. Transfer of customer support to social channels helped the company to reduce the speed of reaction to message requests of the customers, without making satisfaction with the company's service worsen (the expected reaction time to a message request in social networks and messaging apps is 5-10 minutes). In the mean time, it helped the company to process all incoming message requests with a 100% result.

## **KupiVip is saving money**

**Problem:** The internet shop KupiVip (.ru, .by, kz) had a problem with high costs associated with support of telephony, which their contact-center was using for customer support:

**Result:** The company integrated social networks and messaging apps for customer support. After 6 months of work, 50% of phone traffic shifted to social channels (social networks and messaging apps), which reduced the costs associated with telephony by about 50%.

## BSB-Bank survived

**Problem:** BSB-Bank in summer of 2017 year temporarily lost its license in the National Bank of the Republic of Belarus to conduct transactions with individuals, which caused panic among client, which in turn created maximum load for the bank's contact-center. That day it was close to impossible to reach the contact-center by phone, the customers had to remain in a "queue" (when a robot tells you on the phone "Your call is very important for us, hold on the line), hence even more stress was created for customers.

**Result:**  Based on the situation (peak load on the contact-center), some clients chose alternative communication channel - social channels (that day bank also decided to disable online chat due to the potential effect of "lost message requests"). This tactic enabled the bank to evenly redistribute the load, process several message requests of the customers in a single moment, who contact vie those channels, and respond to all customers, which were worried about the question of safety of their financial savings.

## BelVEB fired their social media company

**Problem:** Before Blinger.io integration, BelVEB didn't support customers in social channels by themselves. It was done by a third-party company, which was also doing their social media. Due to that the quality of consultations on the bank's services suffered (the quality of the response and speed of the response).

**Result:** Due to Blinger.io, customer support in these channels was transferred to the contact-center of the bank, which enabled the bank to follow SLA, introduced in the bank. The social media company was "fired". A similar case was resolved with Gazprombank.

## Multilingual customer support in RoboForex and Exness

**Problem:** All Forex brokers care about the quality of customer support and try to be in close touch with the customers. Many brokers work with customers worldwide. To improve the quality of customer support, some brokers decide to start supporting customers in social channels. The man task of RoboForex and Exness was to redistribute message requests from messaging apps to separate language agent groups - English, Spanish, German and Chinese.

**Result:** Flexible settings of Blinger.io allowed to redistribute message requests to a specific language agent group in automatic mode, which helped the companies to process the message requests from their customers even faster.

## In Teztour sales offices = contact-center

**Problem:** The problem of the company was lack of fast and effective routing of the customers, which contacted the company from its social channels, and wanted to buy a tour or have already bough it, but have questions. It's important to note, that Teztour is a tour operator, and doesn't sell the tours by itself, the tours are sold through their agents.

**Result:** The company got the opportunity to connect to Blinger.io all sales office of their agents, convert each message request from social networks into a lead and quickly route it to the closest to the customer sales office. The second benefit - with such an approach, TexTour created a decentralized contact-center from their agents' sales offices.

## MTBank and 2 lines of support

**Problem:** MTBank was one of the first in Belarus to start using Blinger.io for customer support in messaging apps and social networks. Initially via this channels the bank conducted only consultation services by the contact-center (issuing bank cards, loads, deposits).

**Result:** In a year of working with Blinger.io the bank made a decision to scale its service and created full-cycle customer support on the base of Blinger.io (front- and middke- office). Meaning , 1st line - contact center of the bank, 2nd line - transfer to the sales office, solving questions of current clients (for example, technical questions).

## Yandex.Taxi implemented omnichannel support in Zendesk

**Problem:** Yandex.Taxi gets more than 1000 message requests a day on various matters from their drivers. The company chose WhatsApp as a contact channel. Yandex.Taxi provided a number for the drivers to contact the company. Customer support agents used to process them directly in WhatsApp Web interface, which caused the company several problems: it's difficult to process these message requests by one operator (WhatsApp Web can be authorized only on 1 device), such message requests are difficult to classify under SLA.

**Result:** The company contacted Blinger.o, because the solution has integrations with WhatsApp and Zendesk Support- a helpdesk-solution, used by Yandex.Taxi. The company managed to deploy the omnichannel module from Blinger.io in Zendesk SUpport, where the default communication channel is e-mail. With the help of the omnichannel module the company connected a WhatsApp number so that the drivers were able to contact it. All message requests from them started to transform into the habitual for the agents tickets and get processed based on the SLA, approved in the company. As a result, Yandex.Taxi managed to connect more support agents to support WatsApp and make the work process with message requests transparent.

## SOVCOMBANK supports mobile managers via messaging apps

**Problem:** One of the largest banks in Russia - SOVCOMBANK - had difficulties when working with mobile managers. High staff turnover in this group of employees prevented solution of the problem of low quality of knowledge of the bank's products.

**Result:** Bank created a support group to solve the questions, which arrived from those managers. WhatsApp became the main communication channel. Now a mobile manager of SOVCOMBANK can contact support anytime via a WhatsApp number, and the agents will receive the message request in the unified interface of Blinger.io. The huge benefit of such communication is in the fact, that agents and managers can exchange other content types, which simplifies communication in many aspects. Besides, lack of the knowledge level of the bank's products for mobile managers is compensated with the qualified support in the headquarters.

## Recruiters of Profi.ru hire employees via messaging apps

**Problem:** Profi.ru actively searched qualified employees for various projects. Before recruiters used to use the phone for calls, but that used to take too much time, especially if the candidate didn't pick up the phone at the first call attempt.

**Result:** The company connected a WhatsApp number and activated in Blinger.io the possibility to send outgoing messages to the candidates with vacancy proposals. In that case, the company changed the business-process: a call, if the phone wasn't picked up, outgoing message from the Profi.ru number with links to additional materials, in the case of a response, the candidate is moved to the next stage, if the candidate didn't pick up then you made an additional attempt. Sometimes it's better to send a message before the call if the number is not familiar, so the person would know why he's getting a call.


# Definitions

**Company** - a behalf who registers a super-admin account in Blinger.io to use the solution in the company, for example, for customer support.

**Super-admin** - account with full access to all the functions and settings of Blinger.io; super-admin account can add operators.

**Operator** - account that is used for working with customer requests.

**Role** - the set of permissions that can be assigned to an account of the "Operator" type to expand the list of its possibilities.

**Client** - a behalf who contacted the company via a social network, messaging app, email or livechat, as a result of which a query was created in Blinger.io.

**Message**  - a sentence containing some meaning, transmitted by the client to the operator and back, and which is part of the client query.

**Query** - a set of messages from the client and the operator, that make a completed dialogue; in the Blinger.io interface it is considered to be from the moment of clicking "Start conversation" and clicking on "Closed" after.

**Conversation** - the set of messages with one client who accessed through any channel (social network, instant messenger, email, online chat); in the interface, the conversation is the history of correspondence with the client in a specific channel in the "Conversation" tab.

**Channel (or&#x20;*****"messaging app"*****)** - general definition for a social network, instant messenger, email or livechat that is integrated with Blinger.io

**Account channel** - page, group, bot-channel or number added to "Apps" tab, for example, a specific bot-channel (account channel) in Skype (channel)

**Operator group** - one or more operators united on some criteria (language, geography, competence, etc.)

**Widget** - it is a javascript-application that redirects a client from the web page where the widget is placed to the channel account added to Blinger.io


# Sign up and Login

## General information

To start using solution Blinger.io, you need to register. For this you will need a name, current email address and phone number.

By default there are 2 different types of accounts:

* **Super-admin** is the major account that is used for making settings and. Also, Super-admin has an opportunity to work directly with end-user conversations.
* **Operator** is account is created ([**How to add operators?**](https://help.blinger.io/documentation/tab-operators/manage-operators#how-to-add-operators)) by a super-admin and aimed to work directly with end-user conversations. Also, there is the possibility to expand the permissions for this type of account ([**Role permission details**](https://help.blinger.io/documentation/tab-operators/manage-roles#role-permission-details)[)](https://help.blinger.io/documentation/tab-operators/manage-roles\))

{% hint style="warning" %}
Only super-admin can invite operators.&#x20;
{% endhint %}

{% hint style="info" %}
**Hint**

If you need the account that will be used to manage (control, analyze, etc.) performance of operators, we suggest to use super-admin account or create a separate operator account and expand the permissions for this one.
{% endhint %}

## How to register in Blinger.io?

{% hint style="warning" %}
The instruction is relevant just for the Super-admin
{% endhint %}

To create a super-admin account, please follow the link: <https://app.blinger.io/site/registration>

![](/files/-LnlTzSw3n4IEFQbdemQ)

Enter the necessary info for registration (name, valid email, contact phone number), agree to the [**Terms of Use**](https://blinger.io/terms), go through an anti-robot check and click "Register"

{% hint style="warning" %}
According to the terms of Blinger.io it is established that emails that start with **info@** are not accepted for sign up
{% endhint %}

After that, a letter will be sent to the email that was used in the sign up form to complete the registration.

![](/files/-LnlVO-SDBRErMWS1CyM)

Follow the link in the letter to set a password for the super-admin account and click "Save Password"

![](/files/-LnlVd4TV5oWsu210oUy)

After  completion of registration, you will automatically login to Blinger.io  for subsequent configuration.

## How to login?

{% hint style="warning" %}
The instruction is relevant for the Super-admin and Operator accounts
{% endhint %}

To log in to your account (Super-admin or Operator), you must follow the link: [**https://app.blinger.io/site/login**](https://app.blinger.io/site/login) and write down the information that was used during registration (email and password)

![](/files/-LnXw35NarzY_7edS1Nw)

### Forgot the password?

To recover the password, you must follow the link: [**https://app.blinger.io/site/forgot**](https://app.blinger.io/site/forgot) or click "Forgot your password?" on the login page. In the window that appears, write down the email  and click "Send Email."

![](/files/-LnXybJlFbmhD0gOWTMT)

If the email is entered correctly, you will get an email with a link for set a new password

{% hint style="info" %}
Remember your password.
{% endhint %}


# Tab: Apps

**In section Apps of Blinger.io you can do the following:**

* add channel accounts (social networks, messaging apps), message requests from which you plan to process in Blinger.io - [**go to description**](https://help.blinger.io/section-apps/adding-accounts)
* tag added accounts - [**go to description**](https://help.blinger.io/section-apps/tagging-accounts)
* set up assignment of channel accounts to specific operator groups - [**go to description**](https://help.blinger.io/section-apps/assigning-account-to-a-group)

![Image - Section: Apps](/files/-LmKAnekdZwA6ehYN9wm)


# Adding accounts

In this section are represented step by step instructions on adding the accounts, with which Blinger.io has integrations.

{% hint style="warning" %}
**Important!**

Only a person with **Super-administrator** rights can add accounts in Blinger.io account.
{% endhint %}

{% hint style="warning" %}
**Advice!**

Carefully follow each step of the instructions, which will help you **save time**.
{% endhint %}


# Facebook

## **General information**

**The integration allows to:**

* **connect Pages** to Blinger.io (no personal accounts)
* **reply to messages** form Facebook Messenger of the connected Page
* **reply to comments** of users under the publications, which are posted in the feed of the Page by those, who have management rights for the Page

{% hint style="warning" %}
**Before setting up Facebook integration you should:**

* get authorized in Facebook under the account, which has "Administrator", "Editor", "Moderator" role on the Page being connected
* double check, that the Page being connected has the function "Message exchange" activated in Settings (section "General")
  {% endhint %}

## Connect Facebook Messenger?

### **Step 1. Open a tab «Apps» and click «Add new app**»

![](/files/-LmKFnlMqp7XxWeZk8II)

### **Step 2. Choose channel «Facebook» and click «Add Facebook»**

![](/files/-LmKFxeA6jeHlbJHCfLZ)

### **Step 3. Click «Start» in the window that appeared**

![](/files/-LmKGBkFgQ0WQw2ObvxR)

{% hint style="info" %}
After clicking "Start" you will be automatically redirected to the Facebook page, where it is necessary to **allow access for the Blinger.io application**, to be able to search for the "Pages", which you can manage.

**Step 1.**

![](/files/-LlqpNS_IS8LW73V20Q6)

#### Step 2.

<img src="/files/-LlqpnKEl_RnkxGHFffX" alt="" data-size="original">

#### Step 3.

![](/files/-Llqq7u__jiaD6KNIpAe)
{% endhint %}

### **Step 4. Choose the «Page» required for connection and click «Add»**&#x20;

![](/files/-LmKHZXWmPhjC5LRb9bF)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}

## **Connect Facebook Comments**

### **Step 1.** Click on "Edit" in Facebook integration <a href="#shag-1-nazhat-izmenit-v-integracii-s-facebook" id="shag-1-nazhat-izmenit-v-integracii-s-facebook"></a>

![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LB1W87r5cFc0hgB5qdy%2F-LlqqTrIVR72PMfLeoWD%2F-LlqqhyhAnz7oFLNYdDg%2Fimage.png?alt=media\&token=8897904e-9cd0-479d-9eee-abdbc00e813c)

### Step 2. Tick the box next to Enable and click on "Save" <a href="#shag-2-postavit-galochku-naprotiv-ot-enable-i-nazhat-sokhranit" id="shag-2-postavit-galochku-naprotiv-ot-enable-i-nazhat-sokhranit"></a>

![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LB1W87r5cFc0hgB5qdy%2F-LlqqTrIVR72PMfLeoWD%2F-Llqqt_VQqtf_XDzzfwA%2Fimage.png?alt=media\&token=0a572121-8316-41aa-a368-263d94444043)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}


# WhatsApp

## General information

The integration allows you to connect regular accounts as well as WhatsApp Business accounts and doesn't require access to WhatsApp Business API.&#x20;

WhatsApp integration is custom development of Blinger.io, created according to the "reverse engineering" principle.&#x20;

{% hint style="info" %}

#### Do you have access to WhatsApp Business API (direct or indirect)?

Contact Customer Support of Blinger.io to get information about connection possibilities.&#x20;
{% endhint %}

## Connect WhatsApp?

### **Step 1.** Open the tab Apps and click on "Add new app"

![](/files/-LlqAvctzb5OCngjsdci)

### **Step 2.** Choose WhatsApp channel and click on "Add WhatsApp"

![](/files/-LlqAm0EJh6kgyanYQ-3)

### **Step 3.** In the window which appeared click on "Add" to load the QR-code

![](/files/-LlqBB-ZGCKUb4MBu84N)

### Step 4. Open on your smartphone the menu for QR-code scanning in WhatsApp / WhatsApp Business messaging app

{% hint style="warning" %}
WhatsApp / WhatsApp Business should be connected to the phone number, which you're planning to use for Blinger.io connection.
{% endhint %}

#### How to do it in your smartphone?

{% tabs %}
{% tab title="iOS" %}
1\. Open the section **"Settings"** and click on "**WhatsApp Web / Desktop"**

![](/files/-LB6_C2r-VD9d-TAD9lN)

2\. Before scanning you should click on **"Log out from all computers"**, after which **"Scan QR-code"**

![](/files/-LBBKtSkvcF3pPhIIdDx)
{% endtab %}

{% tab title="Android" %}
1\. Go to the messaging app menu and select **«WhatsApp Web»**

![](/files/-LBBLWyTlNKx_N6EYq79)

2\. In the window which appeared click on **"Log out from all computers"**, and then **"+"**, to turn on the camera for QR-code scanning.

![](/files/-LmKONuHaYGo6XVd9daq)
{% endtab %}
{% endtabs %}

### Step 5. Scan the generated QR-code with your smartphone

![](/files/-LlqJ_ZeQNEXMKtvJsO0)

{% hint style="success" %}

### The integration is completed!

{% endhint %}


# Telegram

## General information

The integration allows to connect Telegram-bots (not personal accounts). Telegram-bots are not chat-bots, it's a specific name of  Telegram channels, which let you set up a communication channel of the user with a business.

The instruction was crafted based on the fact, that the Telegram-bot had already been created and you need to connect it to Blinger.io. If you haven't created a Telegram-bot, then we propose the following instruction: [**How to create a Telegram-bot?**](https://help.blinger.io/faq/messaging-channels/telegram)

## Connect a Telegram-bot?

### **Step 1.** Open the tab Apps and click on "Add new app"

![](/files/-LlqAvctzb5OCngjsdci)

### **Step 2.** Select channel Telegram Bot and click on "Add Telegram Bot"

![](/files/-LlqSk2EK_nT8-VyN1YC)

### **Step 3. Fine and open in Telegram BotFather bot**

![](/files/-LEtFvsMELLGknsBvdVc)

### **Step 4. Enter in message line of BotFather the following value** `/mybots`

![](/files/-LEtGN1L_0Ov__-Itxqb)

### Step 5. Select the Telegram-bot, which you want to connect

![](/files/-LEtH3SHr2ivrohjhHKp)

### Step 6. Click on the button «API Token»

![](/files/-LEtHFdJ2SOWOtcjFK8Q)

### **Step 7. Copy the Token value**

![](/files/-LEtK2wPUIHqDN0pyG89)

### **Step 8. Go back to** Blinger.io, paste the copied Token and click on "Add"

![](/files/-LlqXCjFTsbScDeEE-nd)

{% hint style="success" %}

### The integration is completed!

{% endhint %}


# Viber

## General information

The integration allows you to connect Viber Bot Account (not personal accounts). Viber Bot Account is not a chat-bot, it's a specific name of a channel in Viber, which lets you set up a communication channel of the user with a business.&#x20;

The instruction was crafted based on the fact, that the Viber Bot Account had already been created and you need to connect it to Blinger.io. If you haven't created a Viber Bot Account, then we propose the following instruction: [**How to create a Viber Bot Account?**](https://help.blinger.io/faq/messaging-channels/viber)

Earlier the Viber Bot Account used to be called Public Account, but the technology behind them hasn't changed.

## Connect Viber Bot Account?

### **Step 1.** Open the tab Apps and click on "Add new app"

![](/files/-LlqAvctzb5OCngjsdci)

### **Step 2.** Select Viber channel and click on "Add Viber"

![](/files/-LlqYOUxqRf4I_ULONpj)

### **Step 3.** Log in to Viber Admin Panel

**The link to Viber Admin Panel:** <https://partners.viber.com/login>

To log in you must enter the phone number, to which the Viber account is attached, and click on Login. After that in Viber application on your smartphone there will be a message displayed with the code, which you should enter to log in to Viber Admin Panel.

![](/files/-LEy44NHlevKYgSdjqKq)

After that you'll receive a 6-digit password in the app from Viber, which you must enter within 2 minutes

![](/files/-LEy7XLvPdYS-GaY1moJ)

### **Step 4.** Click on the section "Info" and copy the Url

![](/files/-LEyE5LEwNk9RTPS7unj)

### **Step 5.** Got to Blinger.io and paste the copied Url in the field "URL"

![](/files/-LlqicZff4Ewy_hqbbi-)

### Step 6. Go back to Viber Admin Panel and copy the Token value

![](/files/-LEyJ9CQ-1s-X249JG4b)

### **Step 7.** Go to Blinger.io, paste the copied Token in the field "Auth key" and click on "Add"

![](/files/-LlqiYLqdssgJg5FEqzr)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}


# Twitter

## General information

#### The integration allows you to:

* **reply to messages** from the users
* **reply to comments** of the users under the tweets, which were posted in the feed of the connected account

## Connect Twitter Messages?

### **Step 1.** Open the tab "Apps" and click on "Add new app"

![](/files/-LlqAvctzb5OCngjsdci)

### **Step 2.** Select Twitter channel and click on "Add Twitter"

![](/files/-Llqm0-sifW5QHfqgjvb)

### **Step 3.** Click on "Start" in the window which appeared

![](/files/-LlqmEbnW2XVGfAKQikH)

{% hint style="info" %}
After clicking the button "Start", you will be automatically redirected to the Twitter pade, where you must **allow access for Blinger.io application**, to search for the account which you manage.&#x20;
{% endhint %}

### Step 4. Click on "Authorize"

... Twitter is added to Blinger.io as a channel

![](/files/-LmKcjPfO5SmyPmehGT3)

![](/files/-Llqn1Zq4DNVf_92wxzy)

### **Step 5.** Log in to the connected Twitter account, click on "More" and select "Settings and Privacy"

![](/files/-LmKdNkS0RA4kkHe6BSk)

### **Step 6.** Go to section "Privacy and safety" and activate the option "Receive messages from anyone"

![](/files/-LmKd_TS2y7cPXdovd3M)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}

## Connect Tweet Comments?

### **Step 1.** Click on "Edit" in Twitter integration

![](/files/-LlqrqBrXxb1YdNAlAmC)

### Step 2. Tick the box next to Enable and click on "Save"

![](/files/-LlqsJqx3IfLeyVPz8nj)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}


# WeChat

## General information

The integration allows you to connect the accounts of "Subscription" or "Service" type, which must have status confirmed or *verified*.

{% hint style="warning" %}
**Before the integration with WeChat you should do the following:**

* check that in the section Interface Privilege in category "Conversation Service" the items of the paragraph "Interface" have statuses "Obtained"
  {% endhint %}

## Connect WeChat?

### **Step 1.** Open the tab Apps and click on "Add new app"

![](/files/-LlqAvctzb5OCngjsdci)

### **Step 2.** Select the channel WeChat and click on "Add WeChat"

![](/files/-Llvca17_fjxM-QVesk0)

### Step 3. Scan QR on WeChat website using your WeChat app on mobile phone (your personal WeChat must be assigned with WeChat Official account)

![](/files/-MZT2CHotigeMJn1B4vb)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}

{% hint style="info" %}
**The integration's functionality has its specifics.**

After finalizing all integration related work, message exchange starts working **in 0-60** minutes. Such a delay is caused by internal business processes of the company of WeChat messaging app.
{% endhint %}


# Vkontakte

## General information

#### The integration allows you to:

* **connect Communities / Groups** to Blinger.io (not personal accounts)
* **reply to messages**, being sent by the users to the Community
* **reply to comments** of the users under the publications, which were posted on the wall of the Community by those, who has the possibility to manage this Community

{% hint style="warning" %}

#### **Before the Vkontakte integration you should:**

* get authorized in Vkontakte under the account, which has the role of "Administrator" in the Community / Group being connected
* double check that the Community being connected has **the function "Write a message" activated** (path: Manage - Messages - Community messages: On)
  {% endhint %}

## Connect Dialogues?

### **Step 1.** Open the tab Apps and click on "Add new app"

![](/files/-LlqAvctzb5OCngjsdci)

### **Step 2.** Select VK channel and click on "Add VK"

![](/files/-LlquFt8nHp4m2r4hL71)

### **Step 3.** Click on "Start" in the window that appeared

![](/files/-Llqv9iOaqyeDIEZyiMc)

### **Step 4.** Select the Community, which you plan to connect

![](/files/-LlqvLgo91l9M7VRWo48)

... click on "Allow" fo the possibility to connect the application to Blinger.io

![](/files/-LmP_HC8UHVdtThbvmhA)

... after that, in Blinger.io the status that the integration was finalized will appear. **But the integration has not been completed yet!!!**

### **Step 5.** Click on "Edit" in the Vkontakte integration

![](/files/-LlqwVTaTkzytCzU3lwn)

### **Step 6.** Go to Vkontakte and browse to section "Manage" of the community, which has been connected

![](/files/-LmKbSJ3-CVnFMMhDPHm)

### **Step 7.** Browse to section «API usage», and switch to tab «СаllBack API»

![](/files/-LmKc36JUEqqJm3SmcTk)

### **Step 8.** Copy the value of "String to be returned"

![](/files/-LmKdP6z1-GHj8yWZ-2W)

### **Step 9.** Go to Blinger.io and paste the copied value in the field "Webhook key" and click on "Add"

{% hint style="info" %}
After the Secret key (shown in the image) has been generated, you should copy it
{% endhint %}

![](/files/-LmKe1oyvS8yoxVDjUsM)

### **Step 10.** Go to Vkontakte, paste Secret key in the field "Secret key" and click on "Save"

![](/files/-LmKeubNjY-zFsGlpeoQ)

### **Step 11. Fill in the "URL" field, install API v.5.50 version and click on "Confirm"**

The value for the field "URL": [**https://api.blinger.io/vk\_webhook**](https://api.blinger.ru/vk_webhook)

![](/files/-LmKfkzA2JKoY_qPhNUO)

### **Step 12.** Activate in the tab "Event types" the item "Message received"

![](/files/-LmKgr7-PlX5IFWq3ona)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}

## Connect Comments?

#### **Step 1.** Click on "Edit" in the Vkontakte integration

![](/files/-LmPY57WY99e1Am0263R)

#### **Step 2.** Click "Get access token" in the window that appeared

{% hint style="warning" %}
Upon each click on «Get access token», the toked for work with comments will be updated
{% endhint %}

![](/files/-LmPYGIgJKd0az5jkDA1)

#### **Step 3.** Copy in the window that appeared the token value from the address bar of the browser between the values `access_token=` and `&`

![](/files/-LEoImDS663UMF-zlvGp)

#### **Step 4.** Go to Blinger.io, paste the copied value and click on "Save"

![](/files/-LmPYnStm2guQa0Zw1hU)

#### **Step 5.** Open in a new tab Vkontakte, browse to the main page of the connected "Community" and browse to section "Manage"

![](/files/-LmKbSJ3-CVnFMMhDPHm)

#### **Step 6.** Click on "API usage" in the menu to the right, switch to tab "СаllBack API»

![](/files/-LmKc36JUEqqJm3SmcTk)

#### **Шаг 7.** Switch to the tab "Event types" and tick the box "New" in "Wall comments" block

![](/files/-LmPZVh1H0cvRcf4lZx5)

{% hint style="success" %}
**The integration is completed!**
{% endhint %}


# Odnoklassniki

## General information

#### The integration allows you to:

* **connect Groups** to Blinger.io (not personal accounts)
* **reply to the messages**, sent by the users to the Group&#x20;

{% hint style="warning" %}
**Before the Odnoklassniki integration you should:**

* get authorized in the Odnoklassniki account, which has "Administrator / Supermoderator / Moderator" roles in the Group being connected
* in Group settings (section: Messaged) **set the value "Can write messages" to "Guests and participants"**
* send any message to the Group from the account, **not being a participant of the Group** before the moment of its integration.
  {% endhint %}

## Connect Odnoklassniki Group?

### **Step 1.** Open the tab Apps and click on "Add new app"

![](/files/-LlqAvctzb5OCngjsdci)

### **Step 2.** Select Odnoklassniki channel and click on "Add OK"

![](/files/-Llvl97XPNPofn5QvrRT)

### **Step 3. Go to Odnoklassniki group, which you're planning to connect and browse to "Settings"**

![](/files/-LmPbDk1S6BtBLfkmgIc)

### **Step 4.** Select section "Messages" and click on "Generate access key"

![](/files/-LmPbnAm-3Pzha_UgIXb)

### **Step 5.** Click on "Obtain new access key" and copy the generated key

![](/files/-LmPm0AZEtD6upO0wG99)

### **Step 6.** Go to Blinger.io and paste the access key in "Token" field

![](/files/-LlvoKUUSUEbTNfY7jzX)

### **Step 7.** Go to Odnoklassniki and copy the value of Group ID

ID of the Group can be found between "'/group/" and "/messages". Besides you can copy that value in the field ID, if you browse to section "General"

![](/files/-LmPcFfT5ECpOadlUiFd)

### **Step 8.** Go to Blinger.io, paste the ID in the field "Group name" and click on "Add"

![](/files/-LlvoPO7NOoZ4IzFwBRO)

{% hint style="success" %}

### The integration is completed!

{% endhint %}


# Skype

## General information

The integration allows you to connect Skype Bots (not personal/regular accounts). Skype Bot is not a chat-bot, it's a specific name of a Skype channel, which lets you set up a communication channel of users with a business.

The instruction was crafted based on the fact, that the Skype bot had already been created and you need to connect it to Blinger.io. If you haven't created a Skype Bot, then we propose the following instruction: How to create a Skype Bot?

## Connect a Skype bot?

### **Step 1.** Open the tab Apps and click on "Add new app"

![](/files/-LlqAvctzb5OCngjsdci)

### **Step 2.** Select Skype channel and click on "Add Skype"

![](/files/-LlvtaXVqMUOMoF_stM8)

### **Step 3.**  Log in to your Microsoft Azure account and select the Skype bot, which you're planning to connect

{% hint style="info" %}
If you don't have an account on Microsoft Azure portal, then follow this instruction: How to create a Microsoft Azure account?
{% endhint %}

Direct link to **Microsoft Azure:** <https://portal.azure.com/#home>

You can select a specific Skype bot in section "All resources".&#x20;

![](/files/-Lm4PF-SYsGMhm2_4c_5)

{% hint style="info" %}
Skype-bot always has the following type: **Bot Channels Registration**
{% endhint %}

### **Step 4.** Change "Messaging endpoint" in Settings section

Define Messaging endpoint: `https://api.blinger.ru/skype_webhook/`and click on "Save"

![](/files/-LEyUfSg5hGZWcUOCQFl)

### **Step 5.** Copy the value of Microsoft App ID field

![](/files/-Lm4U1V1ecU7X-LcuBKr)

### Step 6. Open Blinger.io and paste Microsoft App ID in the field "Application id"

![](/files/-Lm4ULNaFHXJd0ej-mlj)

### **Step 7.** Copy the value of the field Client secret

Click on "Manage" in the field Microsoft App ID

![](/files/-Lm4UzNQPFjHDpS0LfgJ)

... delete the current Client secret

![](/files/-Lm4VCyvzMN3N7b1lJF7)

... create a new Client secret by clicking on the button "New client secret"

![](/files/-Lm4VQdG6CTqzpNZCtJ6)

... copy the value **Сlient secret**

{% hint style="info" %}

* you can fill in the field Description with any value
* enter Never in the field Expires
  {% endhint %}

![](/files/-Lm4WIljv2Kqmx8jRY0q)

### Step 8. Go to Blinger.io, paste **Сlient secret** in the field "Application Secret" and click on "Add"

![](/files/-Lm4Won223Cz260pmhXZ)

### **Step 9.** Go back to Microsoft Azure portal, browse to section Channels and add Skype channel

![](/files/-Lm4Y9W73_COEaY5lE1x)

### **Step 10.** Fill in Publish according to the requirements and click on "Submit for Review"

{% hint style="info" %}
Filling out Publish section is necessary, to be able to search for the created Skype Bot in the search bar in Skype application.

Pay attention to the fields, where you must define the links to "Terms of use" and "Privacy policy" of your resource.
{% endhint %}

![](/files/-Lm4acUvpTBbtgdlRFXD)

**Optional:** you can add a logo for the Skype Bot - path: Settings - Bot profile - Icon

![](/files/-Lm4bkKHpXr2jEgMrXhM)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}

{% hint style="info" %}
**The integration's functionality has its specifics.**

After finalizing all integration related work, message exchange starts working **in 5-15** minutes. Such a delay is caused by internal business processes of the company of WeChat messaging app.
{% endhint %}


# Line

## General information

The integration lets you connect Line Business Channels.

{% hint style="warning" %}

#### **Before the Line integration you should:**

* install mobile app Line on your smartphone and create an account

**Important:** The new version of Line in Appstore on the territory of Russian Federation is not available for download
{% endhint %}

## Connect Line?

### **Step 1.** Open the tab Apps and click on "Add new app"

![](/files/-LlqAvctzb5OCngjsdci)

### **Step 2.** Select the channel Line and click on "Add Line"

![](/files/-Lm4pctr9e_HRuDccpFa)

### **Step 3.** Log in to your account **LINE Business ID**

Direct link to **LINE Business ID**: [**https://account.line.biz/login**](https://account.line.biz/login)

You're prompted to choose from 2 authorization methods ("Log in with Line Account" selected)

![](/files/-Lm4vH-wsrCbkTgkM30n)

Credentials of **LINE Business ID** - login (e-mail) and password, which have been used during account registration in the mobile application.

![](/files/-Lm4w-LizbcT_gZQj6Te)

{% hint style="info" %}
Besides you can use the QR-code login method
{% endhint %}

### **Step 4.** Browse to section Accounts and select the one, based on which you will be adding the channel for the integration

![](/files/-Lm4worX2_6SlMP6O-Hb)

### Step 5. Copy Basic ID

{% hint style="info" %}
The value should be copied without the symbol @
{% endhint %}

![](/files/-Lm4yz8Mt353qgXGsx63)

### Step 6. Go back to Blinger.io and paste Basic ID in the field "Bot id"

![](/files/-Lm4zMY-85J25l_dAvdG)

### Step 7. Open section Messaging API and click on [LINE Developers](https://developers.line.biz/en/)

![](/files/-Lm52WfKJu6mCpM9mqk1)

### Step 8. In LINE Developers portal select Messaging API and then click on "Start"

![](/files/-Lm52ggAkq3oCbYumDBd)

![](/files/-Lm5310JMc3K2XxS-89C)

### Step 9. Select already existing provider entry or create a new one

![](/files/-Lm53K1AjdvcM4jooyvj)

### Step 10. Select one of the existing channels or create a new one

![](/files/-Lm55OnYlT59n23dFP4T)

### Step 11. Copy Channel ID and Channel secret from Channel Settings tab

![](/files/-Lm57jU0pSMTWTcHkp8u)

### Step 12. Go back to Blinger.io and paste Channel ID and Channel secret in the fields "Client id" and "Channel secret" accordingly

![](/files/-Lm56icLkNOeXRkcQ5wx)

### Step 13. Define Webhook URL

To do that you need to click on "Edit" and paste Webhook URL. After than you should confirm the address by clicking "Verify"

{% hint style="warning" %}
In the field Webhook URL you should specify the address, which comprises of two parts:

1. **Address** - [`https://api.blinger.ru/line_webhook?channel_id=`](https://api.blinger.ru/line_webhook?channel_id=)
2. **Value** - `Channel ID`

Note: after symbol "=" you should paste the value **Channel ID** (without spaces and etc.)
{% endhint %}

![](/files/-Lm58JfpyDzYk4D6xvUN)

### Step 14. Generate and copy Channel access token

![](/files/-Lm5701zhC1-H1pGZdZz)

### Step 15. Go back to Blinger.io and paste Channel access token in the field "Channel access token" and click on "Add"

![](/files/-Lm57P9MZveY4Xg0j4qc)

{% hint style="success" %}

### The integration is completed!

{% endhint %}


# Email

## General information

The integration allows you to connect emails from various email services (public and internal). The instruction was crafted with the examples of connecting **Gmail/ G Suite** and **Yandex**

Before the integration - set up email forwarding&#x20;

### Set up email forwarding&#x20;

{% hint style="warning" %}
Setting up forwarding isn't a stop factor to proceed to the next set up steps&#x20;
{% endhint %}

You should set up email forwarding to the following email: **<forwarding@mail.blinger.io>**&#x20;

You can find the examples below of how to set up email forwarding from Gmail/ G Suite and Yandex &#x20;

{% tabs %}
{% tab title="Google" %}
Path:

1. Open "Settings"
2. Browse to section "Forwarding and POP/IMAP"
3. In the field "Forwarding" define the Email for forwarding

![](/files/-Lm9mG_sJkVn2Of-UaD2)
{% endtab %}

{% tab title="Yandex" %}
Путь:

1. Открыть"Настройки"
2. Перейти в раздел "Правила обработки почты"
3. В разделе создать правило "Все письма пересылать по адресу:" и указать Email для пересылки

![](/files/-LmPXG8_U9AwAw33Tx5F)
{% endtab %}
{% endtabs %}

{% hint style="info" %}
After setting up forwarding, you should notify Customer support (or your personal manager), that you've performed this setting. It is necessary so that Blinger.io would confirm on its end the forwarding possibility.

**For your reference:** in the case of Gmail the confirmation often happens automatically
{% endhint %}

### How to add Gmail

Open Settings field of your email account. Browse to section "Forwarding and POP/IMAP" and enable IMAP

![](/files/-M2gaKHidQ2EOioDbrVE)

Open **Google Account** (link <https://myaccount.google.com/security>). In the **Security tab** find the **Less secure app that have access to your account** and click ON

![](/files/-M2gcGXf_hLT_XyIPBHZ)

Open **application tab** and click on **"Add new app"** and find **Email**

![](/files/-M2gdg4db_eXXVwhxxkm)

Fill in the **required fields:**

![](/files/-M2gdxbPKW4iuwShRk4I)

| Field                     | Meaning                          |
| ------------------------- | -------------------------------- |
| **Email and Email login** | email that is going to be added  |
| **Host**                  | smtp.gmail.com                   |
| **Port**                  | 587                              |
| **Password**              | password from your email account |
| **From name**             | sender name                      |

And click on **"Add"**...

### How to add G Suite

Open **G Suite GoogleAdmin Panel** (link: <https://admin.google.com/>) and find the **Security** tab&#x20;

Select **Less Secure Apps**, set the value next to **Allow users to manage their access to less secure apps** and click **Save.**

![](/files/-M2giHWpqLY77VywjzzG)

Return to the main menu of the G Suite admin panel and open the Apps tab, then go to G Suite and select the Gmail service.

![](/files/-M2gjtkgWcsgJ8BqF2Jt)

Select **Advanced Settings**&#x20;

![](/files/-M2gkOHSvMWhZEXSWhtt)

In the **Routing** section, click ADD under **SMTP relay** service. Set the settings as in the picture below and click **Save**

![](/files/-M2glW8qWlWgpIwN3Y6h)

Open **Google Account** (link <https://myaccount.google.com/security>). In the **Security** tab find the **Less secure app that have access to your account** and click **ON**

![](/files/-M2gm2pJHnOvIy7kI8xw)

Open application tab and click on **"Add new app"** and find Email

![](/files/-M2gnfC3MsHyhNXAg7P2)

Fill in the **required fields**:

![](/files/-M2gdxbPKW4iuwShRk4I)

| Field                     | **Meaning**                      |
| ------------------------- | -------------------------------- |
| **Email and Email login** | email that is going to be added  |
| **Host**                  | smtp-relay.gmail.com             |
| **Port**                  | 587                              |
| **Password**              | password from your email account |
| **From name**             | sender name                      |

And click on **"Add"**...

### How to add Yandex

Open **Yandex.Mail account** (link: <https://mail.yandex.by>) and select **All Settings**  > **Email tools**

![](/files/-M2gsDD5NGZISBDIebdT)

&#x20;Tick on the **C imap.yandex.ru server via IMAP** and then click **Save Changes**

![](/files/-M2guGLvhkwVo69lXLml)

Open **Yandex Profile** (link: <https://passport.yandex.by/profile>) and click on **Create Password**

![](/files/-M2gug6ntL47okbgdJOi)

Fill in the fields as in the image below and click **Create**

![](/files/-M2guz_1VisnTHA4K9xc)

After that the window with the password will appear

![](/files/-M2gvJVykmctG6q4IYM4)

Save the password

Open **application tab** and click on **"Add new app"** and find **Email**

![](/files/-M2gnfC3MsHyhNXAg7P2)

Fill in the **required fields:**

![](/files/-M2gvqFT9UL1Hr1ISaLq)

| Field                     | **Meaning**                      |
| ------------------------- | -------------------------------- |
| **Email and Email Login** | email that is going to be added  |
| **Host**                  | smtp.yandex.ru                   |
| **Port**                  | 587                              |
| **Password**              | password from your email account |
| **From name**             | sender name                      |

And click on **"Add"**...

{% hint style="warning" %}
If the integration failed, try again checking the correctness of the input data and the conformity of the steps according to the manual
{% endhint %}


# LiveChat

The integration allows you to exchange messages with the visitors of your site.

## General information

Channel Livechat is online-chat by Blinger.io

## Connect LiveChat?

### Step 1. Open the tab Apps and click on "Add new app"

![](/files/-LlqAvctzb5OCngjsdci)

### **Step 2. Select LiveChat channel and click on "Add LiveChat"**

![](/files/-Lm4hZg0sfoRm3-i-U2l)

### Step 3. Click on "Add"

![](/files/-Lm9BGsycNf4KnwoDYxt)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}

## **Set up** Livechat for authorized zone?

This function enables you to transmit the data of a logged in account directly in Blinger.io.

### Step 1. **Get Secret key**

To get Secret key, proceed to the tab "Apps", click on "Edit" in Livechat box and copy on the settings page the value in **Secret key** field&#x20;

{% hint style="warning" %}
If the field **Secret key** is empty, then you should delete and re-add LiveChat again
{% endhint %}

![](/files/-LoV7jQBkD300zJYh95r)

### Step 2. Place the additional code on the widget page

Before the  js-code of the Widget, you must place the following code on the same page:&#x20;

{% hint style="info" %}
You can pass any quantity of parameters
{% endhint %}

```javascript
<script>
 var customBlingerConfig = {
   customLivechatFields: {
     your_custom_param_1: 123,
     your_custom_param_2: 'my value',
     your_custom_param_n: 999,
     sign: 'ff127a29530759df7752f6ffab2a78fd'
   }
 };
</script>
```

### Step 3. Calculate the value of parameter `sign`

The value of parameter `sign` depends on the values, passed parameters - that's hash of the parameter values. Hash is calculated on your server side and is needed to secure the parameters passed from changes made by third parties.

It is calculated as follows:

1. concatenation of all values of the parameters passed + **Secret key**
2. calculation of MD5 hash from the line received

{% hint style="info" %}
**Example:**

1. let's take any parameters, for example, **`Rdr9ucDi19nixmpevci5EiOvlFVyXbCT`**
2. doing concatenation of the values of the parameters: **`“123my value999Rdr9ucDi19nixmpevci5EiOvlFVyXbCT”`**
3. calculating hash: **`md5(“123my value999Rdr9ucDi19nixmpevci5EiOvlFVyXbCT”)`**
4. pasting the obtained hash as a value\
   **`sign: 'ff127a29530759df7752f6ffab2a78fd'`**
   {% endhint %}

### Step 4. Calculation of the parameter on the side of Blinger.io

On the side of Blinger.io an analogous operation will be performed. After that the obtained hash will be matched with the one which arrived from your side. If there is a match the client will be tagged with the following icon in Blinger.io <img src="/files/-LoVBzInCLRCLq3GtM7-" alt="" data-size="original"> . Example below:&#x20;

![](/files/-LoVC8y8-gnMKdIHUhCV)

When you click on <img src="/files/-LoVBzInCLRCLq3GtM7-" alt="" data-size="original"> or the client's avatar, you can see in the table Сustom Fields the values of the parameters, which have been added at step 2.

![](/files/-LoVCjIbv3bH2qP2XSd0)


# Custom app

## General information

#### The integration allows you to connect: <a href="#integraciya-pozvolyaet-podklyuchit" id="integraciya-pozvolyaet-podklyuchit"></a>

* your own(or flexible 3rd party) online-chat
* chat in mobile application
* any 3rd party messaging app (if it's not present in tab "Apps")
* chat-bots in messaging apps according to the following scheme " Messaging app - chat-bot - Blinger.io",

to process customer message requests in Blinger.io, Zendesk, Intercom, Kayako or SalesForce.

## Connect Custom app? <a href="#podklyuchit-custom-app" id="podklyuchit-custom-app"></a>

### Step 1. Open the tab Apps and click on "Add new app"

![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LB1W87r5cFc0hgB5qdy%2F-Llpe99u5FiBf_oc410Z%2F-LlqAvctzb5OCngjsdci%2Fimage.png?alt=media\&token=b4095bfb-4510-4a53-a27e-c3b5a6583011)

### Step 2. **Select channel Custom app and click on "Add Custom App"**

![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LB1W87r5cFc0hgB5qdy%2F-Lm981Kn8OJ7FyAaHu19%2F-Lm9roVGkKfvYEJMBiQM%2Fimage.png?alt=media\&token=481628f1-e94a-4ae0-8d79-45ce3ddaff75)

### Step 3. Set up a**dding the channel** <a href="#adding-the-channel" id="adding-the-channel"></a>

| **Field**           | Type    | Description                               |
| ------------------- | ------- | ----------------------------------------- |
| **Name\***          | varchar | App name                                  |
| **Custom app ID\*** | varchar | Unique App ID                             |
| **Webhook URL\***   | varchar | URL for sending a message from Blinger.io |

### Step 4. Set up sending and receiving messages from end-user <a href="#receiving-messages-from-end-user" id="receiving-messages-from-end-user"></a>

{% hint style="info" %}
The messages arrive in **json-format**
{% endhint %}

**Receiving messages from end-user**

| Field                     | Type    | Description                                                                                                                          |
| ------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **token\***               | varchar | Authorization token. It is passed in the title Authorization: Bearer TOKEN. It is generated upon adding the app in Blinger interface |
| **custom\_channel\_id\*** | varchar | Unique field. Is defined upon adding the app in Blinger interface                                                                    |
| **client\_id\***          | varchar | End-user ID                                                                                                                          |
| **client\_name**          | varchar | End-user name                                                                                                                        |
| **client\_phone**         | varchar | End-user phone number                                                                                                                |
| **info**                  | json    | End-user additional information                                                                                                      |
| **type\***                | varchar | <p>Message type:</p><ul><li>text</li><li>image</li><li>file</li></ul>                                                                |
| **data\***                | text    | Message text or file URL                                                                                                             |
| **echo**                  | boolean | echo message from third-party solution                                                                                               |
| **echo\_outgoing**        | boolean | outgoing echo message                                                                                                                |

### **Sending end-user messages** <a href="#sending-end-user-messages" id="sending-end-user-messages"></a>

| **Field**               | Type    | Description                                                                   |
| ----------------------- | ------- | ----------------------------------------------------------------------------- |
| **token**               | varchar | It is passed in the title Authorization: Bearer TOKEN.                        |
| **custom\_channel\_id** | varchar | Unique field. Is defined upon adding the app in Blinger interface             |
| **client\_id**          | varchar | End-user ID                                                                   |
| **type**                | varchar | <p>​</p><p>Message type:</p><ul><li>text</li><li>image</li><li>file</li></ul> |
| **data**                | text    | Message text or file URL                                                      |

### Step 5. Set up Webhooks <a href="#webhooks" id="webhooks"></a>

You can check the webhooks for incoming and outgoing messages on the app settings page.

Example:

![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LB1W87r5cFc0hgB5qdy%2F-LaytOe5FzhRNt6RIS04%2F-Laz4QZLCEb1ks4S6urm%2Fassets--LB1W87r5cFc0hgB5qdy--LayMdAozVVCqfVxbzK9--LayY9rwYgT8OAdOYFvE-image.png?alt=media\&token=af3c8b07-cf34-4d55-ac36-bdbbe9a3d77a)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}


# Tagging accounts

## General information

The function "Account tagging" is necessary, if you need to help the operators distinguish the accounts from which the users came, to be able to analyze them further.

Use case:

* a company needs to connect several accounts of one channel, for example, 4 WhatsApp accounts and they need to understand, which user and from which channel contacting them.

## How to set up?

### Step 1. In Apps tab click on "Edit" for the integration with one of the channels

![](/files/-Lmdl_rUeNclrf_jyCW2)

### Step 2. Enter in "Tags" field the value, which you would like to define for the integration

To delete a tag you should click on "x".

![](/files/-LmdleB800uQAayViFy8)

{% hint style="success" %}

### The function is set up!

{% endhint %}


# Assigning channel to a group

## General information

Function "Assigning channel to a group" is necessary, when you need the message requests from specific channels to get to specific operator groups.

Use cases:

* you need to set up omnichannel customer support for several projects and for each of the projects you have a specific operator group
* you need to set up multilingual customer support (one operator group - Europe, the other operator group - China) and for each of the regions you want to have specific channels

## How to set up?

### Step 1. Browse to "Assign to groups" in Apps tab

![](/files/-LW2gWF2VjU8VkjW9j-P)

### Step 2. Set up the function

#### Way 1. If you need the message requests to return to the Default group if had been transferred or closed in another group

Select the groups which you need to assign to the account of the channel.

![](/files/-LW2iDX6BUB8Haj_T8gb)

Tick the box in front of "Assign closed conversations to chosen groups" and specify the minimum amount of time (in hours), which should pass before the new message requests from the assigned channel gets into the Default group. <br>

![](/files/-LmdnOjvW62abKCmEk2b)

#### Way 2. If you need the message requests remain in the group after closing.

Select the groups that need to be assigned to the specific channel.

![](/files/-LnlyAExKAAUzrtMiokx)

Open "Settings" tab, after click on "Auto assign messages" tab and activate the function.

![](/files/-Lnlz72TiZxawZybNq7Y)

Click on "Save"

{% hint style="success" %}

### The function is set up!

{% endhint %}


# Tab: Integrations


# Freshchat

## General Information

The integration allows to process messages from messaging apps and social networks directly in Freshchat interface. Each message request gets converted into a "Conversation".&#x20;

{% hint style="info" %}
Blinger.io acts solely as "transport" role, which delivers messages from users to Freshchat interface. The set up of message processing is performed in Freshchat interface, Blinger.io doesn't influence the standard business process of the helpdesk in any way.
{% endhint %}

## How to set up Freshdesk integration?

### Step 1. Go to Apps tab in Blinger interface and click on "Add integration" in front of Freshchat

![](/files/-MZT4Sbbv9OxR-D347js)

### Step 2. Put your Freshchat token to the field

![](/files/-MZT4sjGqs-u0Kw-i_k_)

{% hint style="success" %}
**The integration is completed!**
{% endhint %}


# Freshdesk

## General information

The integration allows to process messages from messaging apps and social networks directly in Freshdesk interface. Each message request gets converted into a "Ticket".&#x20;

{% hint style="info" %}
Blinger.io acts solely as "transport" role, which delivers messages from users to Freshdesk interface. The set up of message processing is performed in Freshdesk interface, Blinger.io doesn't influence the standard business process of the helpdesk in any way.
{% endhint %}

## How to set up Freshdesk integration?

### Step 1. Go to Apps tab in Blinger interface and click on "Add integration" in front of Freshdesk

![](/files/-LbcELdgEsox_Sp5iGPH)

### Step 2. Fill out the fields and click on "Add Freshdesk integration"

![](/files/-LbcEg3ul14iMZaH75cv)

{% hint style="info" %}
**Note**

**Subdomain** - located in address bar of the opened Freshdesk account.\
**E-mail and password** - values for Freshdesk account authorization.
{% endhint %}

{% hint style="warning" %}
**Important**

If you're getting an **error message** when attempting to add the integration, then you should check whether the values you entered for authorization and the subdomain are correct.
{% endhint %}

### Step 3. Go to "Admin" menu in Freshdesk account and click on "Automations" in "Helpdesk Productivity" section

![](/files/-LkxIYUO2OO1GhT3zNAB)

### Step 4. Open tab "Ticket updates" and press on "New Rule" to create a rule to work with Blinger.io

![](/files/-LkxIksPS5oNTQBTbBfZ)

### Step 5. Fill out the necessary fields, set the following values and click on "Save"

| Field                                | Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Rule name**                        | **-** any value                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| **When an action performed by...**   | - value "Agent" with the tag "Any"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| **Involves any of these events**     | - value "Reply is sent"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| **On tickets with these properties** | - value "Match ALL of the below"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| **Perform these actions**            | <p> - complete follow actions:</p><ol><li>choose value <em>Trigger webhook</em></li><li>specify <em>Request Type: POST</em></li><li>copy the value <em>Webhook URL</em> from the integration's page in Blinger.io account and insert that value in the filed <em>Callback URL</em></li><li>specify the value  <em>Encoding: JSON</em></li><li><p>check in <em>Content</em> значения<em>:</em> </p><ul><li><em>Ticket ID</em></li><li><em>Subject</em></li><li><em>Description</em></li><li><em>Tags</em></li><li><em>Last public comment</em></li><li><em>Status</em></li><li><em>Contact Unique External Id</em></li></ul></li></ol> |

![](/files/-LkxKe6j6ShiQ0hIzlOm)

![](/files/-LkxKs2vIg0z00DK7aZU)

![Value for Callback URL](/files/-LbcMI1UfT3Uc0N03cSw)

{% hint style="success" %}
**The integration is completed!**
{% endhint %}


# Zendesk

## General information

The integration allows to process messages from messaging apps and social networks directly in interface **Zendesk Support**. Each message request gets converted into a "Ticket".&#x20;

{% embed url="<https://www.youtube.com/watch?v=m2vIanMPl5w&t=7s>" %}

{% hint style="info" %}
Blinger.io acts solely as "transport" role, which delivers messages from users to Zendesk Support interface. The set up of message processing is performed in Zendesk Support interface, Blinger.io doesn't influence the standard business process of the helpdesk in any way.
{% endhint %}

## Set up the integration with Zendesk?

### Step 1. Browse to Integrations tab and click on "Add Integration" in front of Zendesk

![](/files/-Lm9zAL-PbGiH3QjVQZE)

### Step 2. Log in to your Zendesk account, select "Settings", "Account" section and copy the value of the field "Subdomain"

![](/files/-LmiMGxus8AnB361Nmpd)

### Step 3. Go to Blinger.io, paste the Subdomain and click on "Add Zendesk Integration"

![](/files/-Lm9zXb_DvOLaf3xpgHU)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}


# Intercom

## General information

The integration allows to process messages from messaging apps and social networks directly in Intercom interface. Each message request gets converted into a "Conversation".&#x20;

{% hint style="info" %}
Blinger.io acts solely as "transport" role, which delivers messages from users to Intercom interface. The set up of message processing is performed in Intercom interface, Blinger.io doesn't influence the standard business process of the helpdesk in any way.
{% endhint %}

## How to set up the integration with Intercom?

### Step 1. Browse to Integrations tab and click on "Add Integration" in front of Intercom

![](/files/-Lcf3eWlo2mUAaQZzbci)

### Step 2. Open Intercom account and browse to "Settings"

![](/files/-LcezgT03hlIBb5X0KvD)

### Step 3. In "Developers" section select "Developer tools"

{% hint style="info" %}
After clicking on "Developers tools" a redirect to Intercom Developer Hub will happen
{% endhint %}

![](/files/-LcewMu1o3jXba7H3DbW)

### Step 4. Click on "New app" and define any name for the application being created

![](/files/-LcewgCST2hqysSGdEJP)

### Step 5. Copy the "Access token" value

![](/files/-LcexmNFHhNPlZmLNTUO)

### Step 6. Go to Blinger.io, paste "Access token" in the field of the same name

![](/files/-LmA-S-ZnnpsvVgH_Z79)

### Step 7. Go back to Intercom and copy the value of App id

App id is specified in address bar between `app/../`, as shown in the example in the image below

![](/files/-Lcf-S4uBi187xVhJdoq)

### Step 8. Go to Blinger.io, paste "App id" in the field of the same name and click on "Add Intercom integration"

![](/files/-LmiRBQU1aFa6gvYI6V0)

### Step 9. After adding the integration, click on "Edit" in the block with Intercom integration and copy the value "Webhook URL"

![](/files/-Lcf1PvnoAL_LfiD9b3L)

### Step 10. Set up in Intercom Developers Hub "Webhook URL"

On the page Intercom Developers Hub in the section Configure select Webhooks. Paste "Webhook URL" in the field "Your request endpoint URL", in the section Webhook Topics select **`conversation.admin.replied`** and click on "Save".

![](/files/-Lcf2ClzYAH81MZTQBVK)

{% hint style="warning" %}
Choose API version 2.2 in section "Basic information"
{% endhint %}

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}


# Salesforce

## General information

The integration allows you to work with messages from messaging apps and social networks directly in Salesforce Multichannel

## How to set up the integration with Salesforce?

### **Step 1.​ ​Open Setup in SalesForce account**

Navigate to "Apps -> App Manager" and click "New Connected App"

![](https://lh4.googleusercontent.com/qgkwOMulnqZfxnQmjQTpzj68BhumSGSxz9Bkf0UwJxDoTTADjCNvMAEXLzVrCLhZv_-z8gdG7yLz2GyxZ3Kx1gn_H_E2Tfsb_CGpM6qNyWql2JN07tjkQuKVtKzuEQdzjf_sQG7776e7AtTMAw)

### **Step 2. Set up "New Connected App"**&#x20;

**​**Fill out the fields as you see in the image below and click "Save". Use the following callback URL names:&#x20;

* <https://app.blinger.io/integrations/salesforce/oauth>
* <https://app.blinger.io/integrations/salesforce/operator-oauth-callback>

![](https://lh6.googleusercontent.com/vLYHNGu4EoBh7YQNdcsXuqLqBqu_EU0qoglzRbaOmtUR53JgxhwDkmRAkxTwOxoRdeo0Otj6lWsX20-HST9qlRVxdtUKoyE0yojV0ZvCp5ngsqz8PwFtGFrvkTWMPVXgyYKSvKu9PbcpuP7T3g)

### **Step 3. Open "Manage" in Blinger.io**

Click "Manage" in the dropdown list of Blinger.io application on the "App Manager" page.

![](https://lh6.googleusercontent.com/wrweKxz9Wxxdxt7RevzDJcq0u8NBiTJPPIF96KRlebKvvrGN97LVOATaI7GLH1ZgWUTlz-WGNjbFVin1KsASUm_pFvrSVGKBorewYEepRICSptAqBV6I54TQteeTSwAdcvb1teZDtivKjwMHTg)

### **Step 4. Choose profiles for Blinger.io**

Click "Manage Profiles" and select the profiles that you wish to authorize for working with Blinger.io

![](https://lh4.googleusercontent.com/usT0ewoGUsbJHQqI4yPRA3kn0V_X-sGtXmpMr5uvmcJNS6n943MeDLKsadP8sTY05Rz9LWzHvEk5e3vqrgNG867Vs5nLk1st5Uz74Stnp0cqhIP2QvN8Hp-grv9ScI9-wj21nIcQoGlQO688sA)

### **Step 5.​ ​Set up OAuth policies**

On the same page click "Edit Policies" and set the following settings in OAuth policies section

![](https://lh5.googleusercontent.com/SOi5HSlbaNrv6TjaVKMmGulZ226KGX4gv2_hn2rvungnaFf1sqp4UascwOpHlGcvB8o9_a4N5jc8DMlpnrhg4w3ZvNMVDxKv9aQGw8KOKEVm3ebAc7ZZGspSMV6SoEllRSgOYzLgE74rje5apw)

### **Step 6. Save Consumer Key and Consumer Secret values**

Return to the App Manager page and click "View" for Blinger.io application, then copy **Consumer Key** and **Consumer Secret** to Notepad or another application. These values will be required later.

![](https://lh3.googleusercontent.com/lp07d1SNfXYRAhkkQZTpN9oi--RgQrdaWAqDVXYtPJvCrrwkuna1QyKl3cXCsK8J2ri0-sGiHen0vBUVG4J-AkJrCu3rMQ7jwHoSVcWaRheAQj9kw1yUP5TYsQfMrey7Dr4NsJZGgxvcSRXzNA)

### **Step 7. Choose queue that you will use for Blinger.io messages**

**​**In the left menu open "Users -> Queues", then click on a Queue that you will use for Blinger.io messages.

![](https://lh3.googleusercontent.com/Bt-v4ycC_o2IPmCPSvM5BadYigufvrxArGfty8TYbNnEYc96O4aLbGZ8BxkxXEm62J6J3HHlG5MasHNZ1tMjJvjP4RTIMg4zTSBObmIdEIWlGEQxJor9eRN16utwvEC_StSNB1Qj_9VMn1C5Dg)

### **Step 8. Save** Queue ID

Look to the browser address field in the opened window. Copy last 15 symbols of the web address that start with “00”.

![](https://lh6.googleusercontent.com/uqAE1rjMezeCzDV-NSK0yRAS8DYFQPHz5rcpXyCxe8SdOrlOSrq_2Cxtc3rW__La4HRTmLgfHEFLqxWV80XRK6-KVAYUFQudxfOIavqpAMsmMey_qKLLPSNu2dOuZa8rCqSxUBujXEgaAC228g)

### **Step 9.** Browse to Integrations tab and click on "Add Integration" in front of Salesforce

![](https://lh3.googleusercontent.com/OXWLCnRWlCjEpl043Rn8JtfPa1cjTWxU4EERNIPpaLefaW2B7nH6bWZCcqrKlOcSb8Tz_7pcN6_oQG_K_uM9jPs05ur-caQXQtcQvhC-D3_tk_3B9gC3F7liTSGJiQZck9sobPws)

### **Step 10. Insert the previously saved parameters in the matching fields**

![](https://lh5.googleusercontent.com/4Mn2RiLbNtE1aLG9KbK-QvUAYEgc2UDZcYvFZNa2W9-3SGWXPpW-4D1IGC-OMTgv7KyoTcwSQrv_L6tSrpODIWlenhMMoekDhdt5rAq5_SbAJtx8j2RJGgTiWSuxlztOrCK9RuMX)

Put the following values:&#x20;

| Value             | Description                 |
| ----------------- | --------------------------- |
| **Client Id**     | insert here Consumer Key    |
| **Client Secret** | insert here Consumer Secret |
| **Queue Id**      | insert here Queue Id        |

Click **"Add Salesforce integration"**.

### **Step 11. Save generated Salesforce ID**

Click "Edit" under Salesforce integration in "Integrations" tab and copy Salesforce ID to Notepad or another application.

![](https://lh5.googleusercontent.com/_y9Wn7dYkUY_8F6CckD_3BpmOGEq6-koYbfgD9KzpOQheqo_6_7B6bceiosNWEH1XBvYO2VsAbxHmzOYRGJY1-Ti-p2BYwXwL1D7BlZbwTnnzK_dZdd9E7Xy4pm885_U9dghUy2c)

### **Step 12. ​Open "Visual Pages" in Salesforce account**

Go to Setup and ​navigate to "Custom Code -> Visual Pages" in the left panel.

![](https://lh5.googleusercontent.com/a86x5Xkb8UXCROwj-L0On-ByU6E2sF_z5PZR2tD_datJVyElW7ptKwaRP0gEU5AwpsMyjwZNXho8SLCnOt2_905xZa-Q4CP3y4Exsjq4qD_MEttjgNDjRfqKaPbluNjeucf0C8mz)

### **Step 13.​ ​Fill out the fields in Page information section.**

Click "New button" and ​fill out the fields as you see in the image below

![](https://lh5.googleusercontent.com/ukhMSTtCg7G9BFQf2J9HVgSJKVRHzJFkXAoFXwz2c3vVz3712CZiXfMrO1X77eK8x3qr7GE-YCpRZ1B9lRc5XNz8xHEPqfcF3myzQDgSdNP4oZiQGdK0ihSD3UOb0OgEK-ic2Q7R)

### **Step 14. Paste the specified code in Visualforce Markup window**

![](https://lh5.googleusercontent.com/BJZuUEbFTDCK60Nb6vwT-AC9Ej-v4hjB4U7jYA1z9yh4LF_RRo8bXDtOn3h5rQzQwkf7sf-a7pnKS0PDRaJ5CfiLTpy7izKtya3dYlItm7RozpcMuNHK61D62J3t-1LHdSdt9YCr)

Clear the window Visualforce Markup and paste the following code

{% hint style="warning" %}
Replace **%SERVICE\_ID%** with the generated Salesforce ID in Blinger.io at step 11
{% endhint %}

```javascript
<apex:page standardController="case">
<apex:includeScript value="/support/console/42.0/integration.js"/>
<style>
html, body {
height: 100%;
padding: 0 !important;
}
</style>
<apex:iframe id="theIframe" height="100%"
src="https://app.blinger.io/site/salesforce-iframe?serviceId=​%SERVICE_ID%​&caseId={!$CurrentPage.parameters.id}&serviceUserId={!$User.Id}" scrolling="true"/>
<script>
var formatCaseNumber = function(num) {
while (num.length < 8) {
num = "0" + num;
}r
eturn num;
} f
unction receiveMessage(event) {
if (event.origin == 'https://app.blinger.io') {
if (event.data.operatorAnswer === false) {
sforce.console.setTabTitle(formatCaseNumber('{!Case.CaseNumber}') + ' (1)');
} else if (event.data.operatorAnswer === true || event.data.focused === true) {
sforce.console.setTabTitle(formatCaseNumber('{!Case.CaseNumber}'));
}
}
}
window.addEventListener("message", receiveMessage, false);
</script>
</apex:page>
```

Then click **"Save"**

### **Step 15. Open Salesforce Cases**

![](https://lh6.googleusercontent.com/YX4HOLKArKbzm9iuqHkEOGb4m1Akxmp4eTgybMNs61nIrZjf3JvJN6WvLSsjIi7OpWHgCBdec0P0P2i5fRbPItYeYPrbZMN4eeDqNPkYd-8K3QBHtimm-X0OKOAPb9Sne1k30kG3)

### **Step 16. Open any case and click "Edit" page in Settings**

![](https://lh3.googleusercontent.com/I-XPhIVrWsdxsRidB0amISfgDKU5COpOJ0q6qI2uRhVZVdjogHyQpH_GstvNlgohViw2hhqKurg392CbtuW-3M5FU0nMBNY1muyG6dis9TtPX6sGbzoBxZPf5o8Jktd0OQkJvULU)

### **Step 17. Drag Visualforce component to the editor page**

In the opened editor page select Visualforce in the left menu and drag this component to the page

![](https://lh3.googleusercontent.com/8OGK4HkJ2kKuu9Dk8o5TswMT4G1ZW52beSUWd74nENrV4wR1dS20zRhNc7Hoa0FxbFGI_geimmHElSzzr2Z3GaPhEQLyR1lVRjuzbdY5y3dsNAYG-nsMOHZBIugsVzgovl-wnqul)

### **Step 18.​ Set up Blinger.io iframe window**

**​**Blinger.io iframe window should appear on the page. Make sure that the name «Blinger conversation» is specified in the right menu.&#x20;

Enter the desired height value for the iframe in the Height field (default = 300px) and click "Save".

![](https://lh3.googleusercontent.com/U3LJFzlZg2r2yT8ma5cgBMo6-qMALs7ygMvhsnul6lQYXppCS5PvQ8bUpD0rpHBVYQ45Bw1xkJ5eoeXcPdqZSPum9Dy7fkxObkvFaInB0Y09P7tkGsnVQbcEelkD5sVZB0621X5l)

### **Step 19. ​Click "Login with Salesforce" to start using**

"Blinger.io conversation" window should appear on the Case page.&#x20;

Click "Login with Salesforce" to start working

![](https://lh5.googleusercontent.com/_ox5ApTtCEOBj_9G9kYjOKK1C4BRWGWypYHJ7IkABp3A331y6VaZZ_BuLJcKsrzLH3kQHkyqJnocmOKBQg6e30LyvgDqNaf8glDIUC8jMenK0wBi9x0Y_WBGxt3fx0ZQ0fULUBQx)

{% hint style="success" %}

### The integration is completed!

{% endhint %}


# Kayako

## General information

The integration allows to process messages from messaging apps and social networks directly in Kayako Inbox interface. Each message request gets converted into a "Conversation".&#x20;

{% hint style="info" %}
Blinger.io acts solely as "transport" role, which delivers messages from users to Kayako interface. The set up of message processing is performed in Kayako interface, Blinger.io doesn't influence the standard business process of the helpdesk in any way.
{% endhint %}

## How to set up the integration with Kayako?

### Step 1. Got to Integrations tab and click on "Add Integration" in front of Kayako

![](/files/-LmA4j-8hRxLjILunXtR)

### Step 2. Log in to your Kayako account and copy the subdomain of the account

![](/files/-LFMVdmNh4KlItp-ynvz)

### Step 3. Go back to Blinger.io, enter the e-mail address and Kayako admin-account password, paste the copies subdomain and click on "Add Kayako Integration"

![](/files/-LFMXML8j0ER7YGnA7ld)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}


# BPM'online

## General information

The integration allows to process messages from messaging apps and social networks directly in interface. Each message request gets converted into a "Lead" or "Case" (these sections must be supported by your Bpm'online version).&#x20;

{% hint style="info" %}
Blinger.io acts solely as "transport" role, which delivers messages from users to Kayako interface. Blinger.io doesn't influence the standard business process of the helpdesk in any way.
{% endhint %}

{% hint style="warning" %}
The integration works with the following versions:&#x20;

* Bpm'online Sales
* Bpm'online Service Desk

**Important:** by default the integration is set up to work with "Lead" section, if you need to set up the integration for the section "Case", then contact Customer Support of Blinger.io.
{% endhint %}

To perform the integration in your Bpm'online account, you need installed and set up **Blinger.io connector for bpm’online** application.

{% hint style="info" %}
To install **Blinger.io connector for bpm’online** you need to register at Bpm’online marketplace - registration link:  <https://marketplace.bpmonline.com/user/register?destination=>&#x20;
{% endhint %}

Steps 1 through 11 of the instruction outline the actions to install and set up the application **Blinger.io connector for bpm’online**. If this application is already installed and set up, then you should proceed to step 12.

## How to set up the integration with Bpm'online?

{% hint style="info" %}
The instruction was crafted using product version Bpm'online Sales
{% endhint %}

### **Step 1. Log in to your Bpm'online account and browse to "Settings" section**

![](https://lh6.googleusercontent.com/MpedsDr-lHkqpRKnAWbsjS-2CE4V0xVCHV0kKzQKqcdTTFmiHp1gF9NY4wjjpUrznXdu54vJxgAYjdIKSJ8hjkVsA4BqlSXRW86XqQp91e-FOTaPsoHqgzTWWsQX6qk29D5VQhdiSo2xVYFxsQ)

### **Step 2. Select on the page which appeared "Installed applications"**

![](https://lh4.googleusercontent.com/DLWonk_tr1dagNMFX5Ww-Zmc6RYP7DE7WnZwuxSeMx2c2CbgUfnJ0yJxIlKsc3wti723bkizsx2REVC9TVJ-CJTdLt_ZbXfBkOSxKtmfP9haC8JbdQ6Pmqj8U1SqwQIjbw2q_mQciuwqZJybag)

### **Step 3. Select on the page which appeared "Add Application", and then click on "Choose from Marketplace"**

![](https://lh4.googleusercontent.com/jeWpAuJ1mDWwqOIlIQhu3rwZEeYIVrs-zho0JpUriimK51w3MMFetzkBLwK079Wx-fLUZt3ZYr2CaPhTeIT-osxfvr7fhawFNnPsCLUTzhS2y3rWsb4Udx96SrJ41lWOlndGOm4NrjXN8k27Pg)

### **Step 4. Search for application "Blinger" at Bpm’online marketplace and click on it**

![](https://lh4.googleusercontent.com/hznrEuAhRBMIGJr7ezEfJfusX9HShMnCE_-1oqGxhmO8BNrrdDST2gerldEXVFJv6FG7ZaRI7wnf2PPdgTtVexArMoYpor0MPNbSKLOENDh0uBVw8QpO1L_gobF-yB4AAtrzhznd7UUHUEyavA)

### **Step 5. In the window which opened click on "Install"**

![](https://lh3.googleusercontent.com/QK87EyxocvfK9sdE2c3o46kK4mwhf7LG9o4kxe0vVolNyM5Urwf7sCu6xZ8R6zXyleKF2BPfKBfPg2GdQGijVKhGBGeP9XyTNhlOueurCx89b-nAEOQ0WFsWmgx30uVdA_Jm1mnFwHIIIeTGSg)

{% hint style="warning" %}
If you haven't logged in to Bpm’online marketplace, then enter Bpm'online Marketplace Login and Password in the window which opens and click on "Login".
{% endhint %}

### **Step 7. Double check whether the domain of Bpm’online, to which you are going to install the applications, is specified correctly, and click on "Install"**

![](https://lh6.googleusercontent.com/HGcpoB5EXFlX4T1oJQZ4TljAxv99EskiHweVSPLp1W4gAfhebU-KrBcpODl1Bquv27A9HSVTQBjlPVDiO59U6UfdBd-LeaL8CZTF9vOtqCu7T5bxwy7UxP0jOUzOE2BuiiMhXgypAS1P7J7zkA)

{% hint style="info" %}
If during installation of Blinger.io connector Bpm'online you got an error, then simply ignore that message and close the window which opens.
{% endhint %}

### **Step 8. After successful installation, you should browse to "Settings" secton and select "Workplace setup" on the page which appeared**

![](https://lh5.googleusercontent.com/zuz1Oo7hoIFbawz8YNcaKAF4LJ4l4TU57yg2KLdOSwX3hkOzWGAHiEX2eGFYHN0shHv3KvLgsy0df9QRFcJUPA7UhJiVdbXdjcV8-k2hgUp2MT_6aZrwIVFpyXUVh-VNboWicBWPJ5lYIUydOw)

### **Step 9. In the window which appeared select one of the workplaces (for exmaple, "Sales") and click on "Open"**

![](https://lh4.googleusercontent.com/4-tsQPZ6Om22Xxk5DWmejwAL24uAFEuxFXP2Ef1ll3s6sXB9OIDUq0zI-osCAo_F-pD9M0R2FSQC4uBj92rMAq9_E_rwB-TFSgPKr9fHinJ0pr3k0MzX_ymVE-eM75MmRZWFGbZa2bFI6VmSUg)

### **Step 10. Select section Blinger and click on "Select"**

{% hint style="info" %}
Besides, you can find Blinger section with the help of the search bar.

**Important:** if Blinger section is not present on the list, then Blinger.io connector bpm'online wasn't installed. You must reinstall it.&#x20;
{% endhint %}

![](https://lh5.googleusercontent.com/y1ItndJ2ix30kK6Ca7-IOKL6TpJx2oj9Qb0mVZ9X7Bwr-EU2ToMpQGqs1TyXyKcqhb_X-EHiyUvDopebsOCIfjsONdK0OV_NiCY9Fd7KbOFy6Cnm1HStuIRDA0QmUIUoQBqj56trXKWG2SKX3g)

### **Step 12. Go to Blinger.io, browse to Integrations tab and click on "Add Integration" in front of Bpm'online**

![](/files/-LmjAsCamM4nx2jUq3we)

### **Step 13. Fill in the required fields and click on "Add bpm'online Integration"**

{% hint style="warning" %}
You should enter the following values in the fields:

* bpmonline site url - can be found in the address bar of the opened account "bpm'online"
* bpmonline login and bpmonline password - login credentials for Bpm'online<br>
  {% endhint %}

![](/files/-LmjBUKwjzatxKCWDQjF)

### **Step 14. Click on "Edit Integration" in the integration with Bpm'online**

![](/files/-LmjE0OcVjfUcIqtOpAr)

### **Step 15. In the window which appeared copy the value of "App key"**

![](/files/-LmjExWC3o2ldZtbhVuH)

### **Step 16. Go back to bpm'online, in settings select "Blinger integration setup"**

![](https://lh6.googleusercontent.com/karTWCLVzITFNH-VbAakE2gG-MaxZjvZXjpX8L0GvjErVaNi5BlL19FMszxLXMd6GizroDU_iP3gvUcqf8W-63mD6Dwy77vVpI1tTK6qIpxEd1RUDG_BQ5yb9aqXEMWFpTLi2QEPYTbrrQLv0w)

### **Step 17. Paste App key in the field "Blinger key" and click on "Save"**

![](https://lh4.googleusercontent.com/5zFXbuKOgxCMW1Hyoo3w9KYX_7WWZpdxGMegRBZIFKH6ZPA7Ilmz8mrq2vqVoCgWXp6V9d283j2IMqRFycrb3XT7IrqF-Xfzpl9DMbvQlfHP9Cu8r-wPZ7pYCz60rFvqHg_I2RcP4flV3jgBsQ)

### **Step 18.  Browse to Blinger section in the workplace Bpm'online: where the connection has been installed, and you can start working**

{% hint style="warning" %}
Before performing step 17, you should log out and log back in in your Bpm'online account.
{% endhint %}

{% hint style="info" %}
If the integration was successful, a window for working with Blinger conversations will appear
{% endhint %}

![](https://lh6.googleusercontent.com/xjRsepMS2b36KsItmgjcMPiDK_dkLzXS8eBdUago4l8Dhxn19FWHLGp87TICoekXbyLKefP5KdmDZJxF9g5tFTno3-6jh_w8gPS4Eah_ML9J04e37t7VyC50iT7JF3vYh2jsqmOwdKduVsrgyQ)

{% hint style="success" %}

### The integration is completed!

{% endhint %}


# Slack

## General information

The integration allows you to get notifications about new messages in Blinger.io in Slack application (on desktop and mobile platforms)

An example of the appearance of the messages:&#x20;

![](/files/-LmAP3EaR0pK9CC1HpJl)

## Set up the integration with Slack?&#x20;

### Step 1. Go to Integrations tab and click on "Add Integration" in front of Slack

![](/files/-LmAN4X9xBZCPBuPvTTW)

### Step 2. Log in to your Slack account

![](/files/-LFHbaCesxU9EeWeLT2I)

### Step 3. Select the channel, which you will use to get notifications and copy the ID of the channel.&#x20;

{% hint style="info" %}
I​D of the channel can be found in address bar after <https://blingersupport.slack.com/messages/**\\[ID\\_Channel>]\*\*
{% endhint %}

![](/files/-LFHx7JpI3Jcpmczb6rx)

### **Step 4.** Go back to Blinger.io and paste the ID of the channel in the field "Channel"

![](/files/-LmANibrX1aQonWUfLCX)

### Step 5.  Generate and copy the token for Slack account

Path:

1. Follow the link:​​ <https://api.slack.com/custom-integrations/legacy-tokens>
2. ​​Generate the token by clicking the button "Create token"
3. Copy token value

![](/files/-LFHyh3GWgl4roWK9YA2)

### Step 6. Go back to Blinger.io and paste the token in the field "Token", then click on "Add Slack Integration"

![](/files/-LmAOT3Ep_aLxsA9kU-_)

{% hint style="success" %}

### **The integration is completed!**

{% endhint %}


# Iframe

## General information

Iframe allows you to embed part of the Blinger.io web interface in a third-party web solution.

An example of implementing integration through iframe with bpm'online: <https://marketplace.bpmonline.com/app/blingerio-connector-bpmonline>

{% hint style="warning" %}
Access to integration will be through [advanced features](https://help.blinger.io/documentation/settings/advanced)
{% endhint %}

## How to make integration via iframe?

### Step 1. Open [advanced settings ](https://help.blinger.io/documentation/settings/advanced)

{% hint style="info" %}
By default, access to this feature is limited. To receive the access contact Blinger.io Support
{% endhint %}

![](/files/-LqHEPHVEeMxUV395y9p)

### Step 2.  Select " iframe integration "

![](/files/-LqHEouFJShdTQq9kf43)

### Step 3. Press "Add iframe integration"

![](/files/-LqLEpctHcQGl03ApA__)

### Step 4. Set up according to the instructions on the page

![](/files/-LqLF-msjF5snH2Qpukh)

{% hint style="success" %}

### **The integration is completed!** <a href="#the-integration-is-completed" id="the-integration-is-completed"></a>

{% endhint %}


# Tab: Conversations

## General information

In "Conversations" tab the operator communicates directly with the client. The documentation describes the business process of working with conversations, the main elements of it and the functions of working with the conversations.

{% hint style="info" %}
Super-admin also has the possibility to work in "Conversations" tab like any other operator.
{% endhint %}

## Conversation elements

![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LB1W87r5cFc0hgB5qdy%2F-Lo5LPL2MfNZboghQBTx%2F-Lo5LwUgD_HnjFuLt-eG%2Fimage.png?alt=media\&token=565ae90c-4fa9-419c-89cc-d04ed394f47f)

Element #1 - User name **-** Information that is transmitted by the channel to Blinger.io‌

Element #2 - channel - logo of the channel through which the client reaches the company‌

Element #3 - The element indicates that the last message was left by the operator.‌

Element #4 - Responsible operator - indicates the name of the operator who works / worked with the conversation.‌

Element #5 - New message - indicates that a message has arrived from the client and it hasn't been read by an operator.‌

Element #6 - Operator's group - indicates the group of operators in which this conversation is located.‌

Element #7 - Processing status - indicates at what stage of processing the conversation is.

{% hint style="warning" %}
There are 3 statuses:

* Unassigned
* My inbox
* Closed
  {% endhint %}

Element #8 - Message time - indicates the time the message arrived, regardless of the sender. The "Unassigned" tab displays the time when the "Unassigned" status is assigned.

{% hint style="warning" %}
The "Unassigned" tab displays the time when that status is assigned to the conversation. The tab “Closed” displays the time of assigning the status “Closed”.‌
{% endhint %}

Element #9 - indicates the number of conversations that are in "My Inbox" of the particular operator.‌

Element #10 - indicates that there are messages from the clients that are not viewed by the operator.

## How to work with conversations?

The work of the operator is focused on 3 tabs in this section:

* Unassigned - "Unassigned" tab shows new conversations from clients
* My inbox - "My inbox" tab shows the conversations that are being processed by the operator
* Closed - "Closed" tab shows conversations that were closed (resolved) by the operator

You can find more information below:

![](/files/-Lo5cMfwo6CRlMtfiPEm)

{% hint style="info" %}
The "Blacklist" and "All tabs" become available if the operator is assigned a role "Conversations management"  or "Show tab "All" in conversations" (for more details: [**Manage roles**](https://help.blinger.io/documentation/tab-operators/manage-roles)).
{% endhint %}

### "Unassigned" tab

All new clients' message requests appear in the “Unassigned” tab. By default, conversations in this tab are visible to all operators. However, if the operator is in a separate group (s), then he will see only  those conversations that are distributed in this group (s).

In Blinger.io, manual distribution of conversations works, i.e. either the operator takes the conversations, or the admin distributes the received conversations to the operators.

In order to take away the conversation from “Unassigned”:

1. select the appropriate conversation (preview of the conversation is available)
2. click on "Start conversation"

After these actions have been performed, the conversations will go to “My inbox” tab of this operator and will be assigned to him (this will be indicated in the conversation log).

![](/files/-LoUVirWF9OOzFXek1gn)

### "My inbox" tab

After the operator has taken the conversation, it goes to “My inbox” tab, and after that he can start a conversation with the client.

To send a message to the client, you must click "Send" or use the "hot keys" (MacOS: Command + Enter, WinPC: Ctrl + Enter)&#x20;

{% hint style="info" %}
An indication that a message has been sent to the user is signed by the icon <img src="/files/-LoeGbgOyvjzM3FNeQjM" alt="" data-size="line"> . If the message is not delivered, the operator will see the icon <img src="/files/-LoeGm8lovFv5SxZ-g-D" alt="" data-size="line">.
{% endhint %}

![](/files/-LoeGr7lrXsruswEpzUO)

If the operator understands that the client’s conversation has been resolved, then it can be closed by clicking on "to closed" button. Also, the conversation can be returned to “Unassigned” by clicking on “To Unassigned” button&#x20;

![](/files/-LoeHqYf85l79ti2pN8E)

{% hint style="info" %}
More information you can find below
{% endhint %}

### "Closed" tab

The "Closed" tab displays all conversations that the operator closed. If the previous operator worked with this client and after another operator worked with this client, then when the last operator closes the dialog, the previous operator will not have this dialog in this tab. But all movements of the dialogue are stored in the access logs&#x20;

![](/files/-LoeIfrvCI8DeQwNEKRP)

From this tab, you can start a new conversation (outgoing) with the client by clicking on "Start conversation", after which it will appear in "My inbox" tab

![](/files/-LoeJ5nthed8XRx4J9xc)

## Functions for processing conversations

### How to attach files?

![](/files/-LoeLM-2lAX6w3vFjUWt)

The operator can send any types of files to the client. To do this, click "Attach file" and select the file you want to upload. You can select only one file, uploading and sending the file begins immediately.

{% hint style="info" %}
The types of files supported by Blinger.io can be found in the instructions for the channels.
{% endhint %}

### Canned responses

![](/files/-LoeP-y4XXt09DbmtULi)

For quick responses to common clients' questions, the operator can use canned responses. You can start using it by entering the character "/" or "\\" in the text field.

The following roles can set template database by clicking "Add answer":

* super-admin - the templates set by him will be available to all operators regardless of the groups
* operator - the templates set by him will be available only to this operator

Canned responses can be divided by topic (for example to greet, end the conversation). This can be done while creating the template in the "Title" field:

![](/files/-LoeYfvbkVru6j85ja4G)

Canned responses can be either edited or deleted:

![](/files/-LoeZ-IidIN00vpF5aWC)

### Change client name

![](/files/-LoeZ5nEYXikF0e6S9uc)

Clients in messaging apps or social networks can name themselves in a different way, as channels transfer to Blinger.io. If there is a need to rename the client  the operator can click on <img src="/files/-Loef42lgXXPbjPxVhGG" alt="" data-size="line"> and make changes.

The original name is stored in the client profile:

![](/files/-LoefUZlJZhpyS6MnO2I)

### Add notes

![](/files/-LoefbVUefyP_HHjvK-y)

Notes allow you to save some information about the client, for example, to communicate when the conversation is assigned to another operator, or for the admin. The user doesn't see the note. To add a note, you must click <img src="/files/-Loemq-AZfAuuRoY0Ofl" alt="" data-size="original"> , in the window that appears, write down the text in the note and click "Add"

### Adding emoji

![](/files/-Loeo1zOQkhQuW5KXmQL)

Emoji allows you to add emotions in communication with the client. To add emoji to the text, you must click <img src="/files/-LoeoPM1Orzi3C4DLYVY" alt="" data-size="original"> and select the emoji you want to add.

### Adding a note in client profile <a href="#dobavlenie-zametki-v-profil-klienta" id="dobavlenie-zametki-v-profil-klienta"></a>

If you need to add additional information for a client, you can use the function "Notes". Click on the client's logo - his profile will appear. In the field "Note" click on "Add" and enter the information.

![](/files/-LqLtmpWFjWQWbi31FMd)

### Assign conversation to another operator

![](/files/-LoeoaRh95N_fbAj0C4U)

You can assign the conversation to another operator for example, when this operator has already communicated with this client. To do this, you must click on "Assign to" and select a specific operator.

{% hint style="warning" %}
If the operator is in a specific group (s), then the operators who are also in this group (s) will be available for assigning this conversation to them
{% endhint %}

### Assign the conversation to another group

![](/files/-LoeptvgMIZbi2ZXtyWB)

Assigning a conversation to another group allows you to assign conversations from the operator of one group to the operators of another group. For example, groups of operators are divided by type of conversations, or it is necessary to build the 1st and 2nd support lines. To assign the conversation to another group, click on <img src="/files/-LoeqzWbhdoAUSeBUO9X" alt="" data-size="line"> (the name of the group and the color of the button may be different, depending on your Blinger.io settings). After that, in the drop-down list, select the group to which the сonversation should be assigned.

{% hint style="warning" %}
After assigning, the conversation will be displayed in the "Unassigned" tab of the group to which it was assigned.
{% endhint %}

### Send conversation to Email

Allows you to upload either all correspondence with the client or specific messages.

#### **Option 1**&#x20;

To upload all correspondence, click "Send to Email"

![](/files/-Loessp6T2tHLTdIqRv3)

specify the subject of the e-mail and the recipient in the window that appears and click "Send conversation". An e-mail with the correspondence will be sent to the indicated email address.

#### **Option 2**

To upload the correspondence, it is necessary to select messages. You can select the necessary messages for uploading by clicking <img src="/files/-LoewKfHO_vciWkXtpsL" alt="" data-size="original"> in the right upper corner of the message.

![](/files/-LoexFDp0NAeiHnqTkuy)

Click "Send to Email" after selecting messages

![](/files/-LoexNMfQLBEI38g6Mwf)

specify the subject of the e-mail and the recipient in the window that appears and click "Send conversation". An e-mail with the correspondence will be sent to the indicated email address.

### Tagging

The function is useful for capturing attention to client messages. For example, mark a client’s message that contains a complaint, then collect these messages and analyze them (using the tag analytics section).

To "tag" the message (s), you must select these messages. You can select the necessary messages by clicking on the message block in the upper right corner.

![](/files/-Loyoz6DS1qx9dGfZhA_)

After selecting messages click "Add Tag"

![](/files/-Loyp7NQxWvuMVQX1YXC)

in the window that appears, select the tag from the drop-down list, or create a new one&#x20;

![](/files/-LoypM9wPKJS1UArBI5t)

{% hint style="warning" %}
The created tag is automatically saved in the tag list, and next time it will appear in this list.

Tags cannot be deleted / edited.
{% endhint %}

### Blacklist

If it is necessary that messages from a specific client don't arrive to operators, then it can be added to the Blacklist. To do this, select "Send to the black list" in the drop-down menu

![](/files/-LozIbdYcoCclrgCTKdn)

To remove a client from the black list, you need to open "Black list" tab (available for super-admin or operator with advanced privileges - [more](https://help.blinger.io/documentation/tab-operators/manage-roles#role-permission-details)) select a dialogue with the client and click "Unlock conversation"

![](/files/-LozJH2_79l2SanK32ol)

### Search by message

![](/files/-LozK1JMB70AO79810UY)

Search works both by customer name and by messages in conversations. At least 3 characters must be entered in the search bar. Search starts at the beginning of a word, not from the end.

### Conversation filter

![](/files/-LozMRi155p1Fa8SmwXo)

You can filter conversations by:

* groups of operators
* operators
* status  (unassigned, in progress, closed)

There are filters on:

* operators' groups works in each tab
* processing status works in the "All" tab
* operators works in the "All" and "Blacklist" tabs

{% hint style="warning" %}
If the operator belongs to a specific group(s) and is assigned a role with the permission "Show tab "All" in conversations", the filter will display a list of operators in the groups in which the operator itself is located.&#x20;
{% endhint %}

### Outgoing messages

![](/files/-LozNJgsAZQgVl9Xgi0H)

The function allows you to initiate a dialogue with the client by phone number via the WhatsApp.

To initiate a dialogue, you should click "Outgoing message", enter the phone number

![](/files/-LozOubAhBmfysEkReFp)

Get an answer from WhatsApp if the app is installed on the client's phone number. If yes, then click "Send message"

![](/files/-LozPBMKZhBw4d_DgkDg)

write down the name of the client with whom you will communicate, enter a message, the group that will be used to send the message (if one operator is in several groups) and click "Send".

![](/files/-LozP_BSoZnI1X-HEm90)

After that the message that was initiated by the operator will appear in “My inbox” tab

{% hint style="warning" %}
The paid function "Outgoing messages" is hidden by default. For access, contact Blinger.io Support
{% endhint %}

### Client assignment to an operator

![](/files/-LozVQdHXdDubomvD4Gz)

The function allows you to assign a specific client to the operator. It is convenient to use if the company has a certain number of clients assigned to each operator / manager.

To assign a client to an operator, it is necessary to assign a conversation to the operator, click on the icon  <img src="/files/-LozXlB63OSuNfUQ0vjI" alt="" data-size="original"> and select "Fix (name)" from the list. Write down in brackets the name of the operator who plans to assign the user to himself.

The function "Client assignment to an operator" contains the following logic:

* only operator or super admin can pin the user
* operator can detach the client, and super admin can detach the user from any operator
* in case of a new conversation from the client, after the operator or super-administrator has assigned this client, the conversation will bypass the “Unassigned” stage and immediately display in “My Inbox”.
* if you want to assign a client to another operator, the current operator detaches the client and transfers him to a new operator (or the new operator takes the client), who assigns this client to himself.
* If the operator or super-admin, to whom the client is assigned, transferred the client’s conversation to another operator, and the operator sent the message  to “Closed”, then if the client will contact again, the conversation will be displayed in the “My inbox” tab of the operator or super-admin to whom the conversation is assigned.

A pinned client has three statuses:

|                                                                |                               |
| -------------------------------------------------------------- | ----------------------------- |
| For the operator or super admin to whom the client is assigned | <p>Detach</p><p>(\[name])</p> |
| For an operator for whom the client isn't assigned             | Pinned (\[name])              |
| For super-admin for whom the client isn't assigned             | Detach (assigned to \[name])  |

**\[name]** - this is the name or email of the operator or super-admin to whom the client is assigned


# Tab: Widget

## General information

Tab "Widget" at Blinger.io is necessary to create widget(s), manage, set up for further use on web pages as a point of contact between the user and the company.

## Create a widget?

Browse to the tab Widget and click on "Create new widget"

{% hint style="info" %}
After that you will get on the page with widget settings
{% endhint %}

![](/files/-LmAaohcjRo1JCECB5kZ)

## Set up the widget?

The description of widget's settings can be found below

#### **Block "Settings":**

![](/files/-LmAkDBK4oSsMHB2_AO4)

* **Language** - allow you to automatically change the interface language depending on the site's language
* **Ring animation** - allows you to turn on/off the widget's animation
* **Position** - allows you to change the position of the widget on the web page: left or right
* **Widget color** - allows you to change widget color, provides the possibility to define colors using HEX-code
* **Widget scale** - allows you to adjust the scale of the widget (100%, 90% or 70%)
* **Active invitation** - allows you to display the welcome message to each user of the web page at the beginning of the session. The content can be defined in the field "Invitation text" (connected with widget language settings). Besides, you can define the display time for the active invitation with the help of the option "Invitation delay (sec)".

#### **Block "Channels"**

This block allows you to manage the display of the connected channels in the widget.&#x20;

![](/files/-LmAkMp-V6fZRmwkvUAR)

To display a specific account in the widget you must tick the box next to the account.

To set up a specific account in the widget, click on the "gear" <img src="/files/-LmPqBNk2dr6jSg7jXLS" alt="" data-size="original"> . Settings allow you to edit the name of the channel in the widget and the channel logo.&#x20;

To add your own button in the widget, click on "three dots" and further set up the created button (for example, you can create an Instagram button this way).&#x20;

To edit the vertical placement of the buttons in the widget you should click on the "arrows up/down" <img src="/files/-LmPqQIVkMQE9eviqEmR" alt="" data-size="original"> and drag up or down

#### **Block “Widget preview”**&#x20;

Let's you visually control the process of widget set up

![](/files/-LmAkcD8Bezk_avSuixK)

{% hint style="warning" %}
If the widget was set up right after its creation, you should click on "Save", to generate the javascript-code, which you will further use to place the widget on the web pages.
{% endhint %}

{% hint style="warning" %}
After manipulations with widget edit (is the widget was created before), you should click on "Save".&#x20;
{% endhint %}

{% hint style="info" %}
**To see the edits on the web page, where the widget it placed**, you should either open it in incognito mode, or clear cache of the web page (use "hot keys": MacOS - Command+R, Win - Ctrl+F5)
{% endhint %}

## Place the widget?

You should place the javascript-code, shown on the image below,  in html-code of the web page before the tag `</body>`

{% hint style="warning" %}
If the block isn't displayed, you should click on "Save"
{% endhint %}

![](/files/-LmA_AwFQ6xCOAd7XBGs)

## Remove widget?&#x20;

To remove the widget from the web page, you should remove the javascript-code from the code block, where it was placed..

To delete the widget in Blinger.io you should browse to Widget tab and click on the "Trash can" in front of the widget, which you're planning to delete.

![](/files/-LmJwzZKn10yfc-Y4gzP)


# Tab: Operators

## **General information**

In the tab Operators you can do the following:

* manage operators
* assign roles to the operators
* manage operators’ groups
* auto assign messages between groups by keywords

{% hint style="warning" %}
Only admin has the access to all the settings
{% endhint %}

The overall picture of the operators / groups / roles can be tracked on the main page of tab Agents

![](/files/-LmKCUX8HPmTJni8DCNW)


# Manage operators

## **General information**

Operators are involved in answering clients’ questions in Blinger.io interface. Their authority can be expanded with role permissions.

Initially, only super-admin can have the access to all of the settings

## **How to add operators?**

### **Step 1 Open tab Operators and press the button “Invite new operator”**

![](/files/-LmKCUX8HPmTJni8DCNW)

### **Step 2. Specify the details of the operator(s) whom you plan to invite**

#### **Option 1. Single invitation**

![](/files/-LmKF_OLFVrG_irD11Ye)

Steps:

1. In field “User email” - write down the email of operator whom you plan to add
2. In field “Operator groups” - choose the group to which you plan to add the operator
3. Press “Send invitation to email”

{% hint style="warning" %}
If there is no groups - choose the group Default (automatically created group when the super-admin register the account)
{% endhint %}

#### **Option 2. Bulk invitation**

![](/files/-LmKGEAneHaCQVH4o50Z)

Steps:

1. Write down the list of operators’ email addresses (.csv)
2. Upload this file
3. In field “Operator groups” - choose the group to which you plan to add the operators
4. Press “Send invitation to email”

{% hint style="warning" %}
After sending the invitation, the letter will be sent to the specified email addresses to complete registration in Blinger.io&#x20;
{% endhint %}

![](/files/-LmKHgPpMxZxDlXPjC6Q)

### **Step 3**. **Track operator registration status**

You can track the status of operator registration in the Operators section. If the operator has completed registration, there will be the status "Active" - otherwise "Not registered".

![](/files/-LmKJE1XamRr1HskmOQr)

## **How to delete agents?**

![](/files/-LmPrkywjk_TNlqzL2Z2)

To remove an operator, you need to go to the tab Operators, first click "Deactivate" and then "Delete".<br>

\ <br>


# Manage operator groups

## **General information**<br>

Groups allow operators to be divided into different responsibilities.&#x20;

For example, you need:

1. Create 1st Line and 2nd Line Support Groups
2. Divide according to the type of issues (sales, support)
3. Divide according to the language&#x20;

and other.

Initially, all the settings can be done by super-admin

{% hint style="warning" %}
Group “Default” automatically created when super-admin register his account
{% endhint %}

## **How to create the groups of operators?**

Firstly, need to press button “Groups”

![](/files/-LmPg3MBybl6F8zZuK_-)

Make some settings:

1. Write down the name of the group
2. Set priority
3. Specify group color
4. Add agents
5. Set group working hours

{% hint style="info" %}
The priority of the group must have a different value from the priority value of other groups.&#x20;

The priority of the group is used only if it is planned to configure the distribution by groups depending on the topic of conversation.
{% endhint %}

{% hint style="info" %}
Group working hours need to be set only if you want to see separate analytics: during working hours and during non-working hours.
{% endhint %}

![](/files/-LmPjmB6xUr0ONPj9q0l)

To complete the process of creating a group, you must press "Create". After that, the group will be available in the list below for its management.

## **How to manage the groups of agents?**

The management of the group(s) is available from the "Groups" page, where a list of all created groups is presented (picture is below)

Just click "Show" to see the list of operators in each group

![](/files/-LmPm7ITVhJRjDRcbccZ)

You can also change the parameters of the group (click "Pencil" <img src="/files/-LmPpwpv24yeNSOJcaoi" alt="" data-size="original">): participants, working hours, priority, color, name. To delete a group, you must click on the "Trash" <img src="/files/-LmPpODW03dWQtRmx1Wt" alt="" data-size="original">

![](/files/-LmPowFT1Y1cTYq73p84)

{% hint style="info" %}
The created group "Default" can also be renamed, but you cannot delete it!
{% endhint %}


# Manage roles

## **General information**

it is possible to expand its roles for each "Operator" account. You can configure the role and then assign it to the operator in the “Operators” tab in the “Role management” field.

Initially, the super-admin can make all the settings

## **How to create a role?**

To create a role you need to click on “Role management”

![](/files/-LmQ0XLH8oQaL4-xkvPy)

and in the new window click "Create Role"

![](/files/-LmQ1ue6vY0tECSxNnGC)

write down any name of the created role, mark the permissions and click "Save"

![](/files/-LmQ2eQqPoRMcgcVGOuq)

{% hint style="info" %}
**Click here** to get more details about role permissions.
{% endhint %}

## **How to assign the role?**

To assign a role to a specific operator, you need to open the "Operators" tab and click "Roles"

![](/files/-Lme6fl51ca5wiDBi8kc)

in the window select the certain role from the list for the selected operator by clicking on "Assign Role"

![](/files/-Lme6tL2NFakQ75y4e_9)

{% hint style="info" %}
To revoke a role (for example, you need to change the level of authority),  click "Revoke role"
{% endhint %}

## How to change the role?

To change the permissions in one of the roles, you must click "Role Management" in the "Operators" tab

![](/files/-LmQ0XLH8oQaL4-xkvPy)

click "Update" in the window

![](/files/-Lme82rCspGbathq1Uf_)

in the next window it is possible to change the permissions, turning them on or off with the checkmark <img src="/files/-Lme8MbKWkVSg04hgmQK" alt="" data-size="original">.

{% hint style="info" %}
If you want to set a new role name, we recommend to delete the role and create a new one, and then assign this role to the operators.
{% endhint %}

![](/files/-Lme947xGhtuqoN9cin_)

## Role permission details

{% hint style="info" %}
Super-admin account has full access to Blinger.io settings
{% endhint %}

| Permission                            | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Apps management**                   | provides an opportunity for the "Operator" account to work without restrictions with the "Applications" tab                                                                                                                                                                                                                                                                                                                                                                                          |
| **Integrations management**           | provides an opportunity for the "Operator" account to work without restrictions with the "Integrations" tab                                                                                                                                                                                                                                                                                                                                                                                          |
| **Widget management**                 | provides an opportunity for the "Operator" account to work without restrictions with the "Widget" tab                                                                                                                                                                                                                                                                                                                                                                                                |
| **Operators management**              | provides an opportunity the "Operator" account  to add / remove operators, assign roles to them                                                                                                                                                                                                                                                                                                                                                                                                      |
| **Conversations management**          | <p>provides an opportunity for the “Operator” account to see and manage the “Black List” tab in the “Dialogs” section, as well as the “All” tab, which allows this account to see all conversations processed and closed by other operators, as well as assign these conversations to another operators. This permission allows you to see all conversations in the "All" tab</p><p>By default, the All and Blacklist tabs in the Dialogs section are not available for an operator type account</p> |
| **Comments management**               | provides an opportunity for the “Operator” account to work with comments that users leave under posts (tweets) on social networks like Facebook, Vkontakte, Twitter                                                                                                                                                                                                                                                                                                                                  |
| **View analytics**                    | provides an opportunity for the “Operator” account to see the current analytics by operators (Dashboard), as well as detailed analytics separately by: tags, operators, dialogs and clients                                                                                                                                                                                                                                                                                                          |
| **Operator groups management**        | provides an opportunity for the "Operator" account to manage groups in the "Operators" tab                                                                                                                                                                                                                                                                                                                                                                                                           |
| **Operator groups assign management** | provides an opportunity for the “Operator” account to configure and manage the distribution of conversations between groups depending on the context                                                                                                                                                                                                                                                                                                                                                 |
| **Settings management**               | provides an opportunity for the “Operator” account to set up an auto responder, distribution of conversations, names of topics, the order of conversations and also gets access to advanced settings                                                                                                                                                                                                                                                                                                 |
| **Show tab "All" in conversations**   | the permission allows you to see the Black List and All conversations tabs, in which you can manage only those conversations that is connected to  the group (s) of which this operator is a member                                                                                                                                                                                                                                                                                                  |


# Distribution by keywords

## General information

The function allows to **distribute new message requests** automatically in specific operator groups, depending on the message request's context.

{% hint style="info" %}

### Cases

For example, distribution by keywords can be set up, if you need to distribute message requests based on:

* message request's language
* message request's theme (question, incident and etc.)
  {% endhint %}

Mechanism of work:

1. A new message request from a client appears in the tab "Unassigned"
2. Within the defined time frame, Blinger.io expects other messages from the client (often the conversation can start from a message: *"Hello!"*). You can call the client to describe his question in detail by means of an autoresponse. (*note: in that period operators can't assign the message requests to themselves*).
3. Keywords search is being performed.&#x20;
4. Depending on the keyword weight and group priority, Blinger.io decides, to which operator group to distribute the message request.
5. The distribution cycle is repeated for each new message request from the client, if the previous message request was in the status "Closed" for more than the defined period of time in any of the groups.

Distribution logic:

* If in the text of messages there were no keywords found, then the message request will be distributed in the primary operator group - Default.
* If there were one or several keywords found in the text, which are connected to one operator group, then the message request will be distributed to that group.
* If in the message text there were several keywords found, which correspond to various operator groups, then the message request will be distributed in the operator group, the keywords in which have the biggest sum of weights.
* If in the text of the message requests there were several keywords found, which correspond to various operator groups and the sums of keyword weights are equal, then the message request will be distributed to the operator group, which has the highest priority.

{% hint style="warning" %}
If you have the function [**Assigning channel to a group**](https://help.blinger.io/documentation/section-apps/assigning-account-to-a-group) or [**Autoresponder**](https://help.blinger.io/faq-1/faq/about-functions/autoresponder) enabled, then before setting up the function **distribution by keywords**, you should disable assigning channels.
{% endhint %}

## Step 1. Define the keywords

Highlighting of the keywords, which are frequently used by the clients at the beginning of the message request, helps Blinger.io to detect the context of the message request. Based on the contents a decision is made to which group to distribute the message request.

![](/files/-Loue_URGyv_N-o_RPzA)

The sequence of the actions is as follows:

1\. For starters you should put together a list of the keywords, which are being used by the clients and which help on the conscious level to define the general line of the message request

{% hint style="info" %}
To put together the keywords list you can analyze phone calls and correspondence (email, chats, social networks and etc.)
{% endhint %}

2\. Specify in the keywords the root and/or the suffixes, because Blinger.io can't ignore the endings

3\. Open tab **"Operators"> "Groups">"Groups assign"**

4\. In the field **"Mask"** enter one keyword

{% hint style="warning" %}
You must follow the entry format for the keyword: `/[keyword]/gi`

where `[keyword]` - the defined keyword value&#x20;
{% endhint %}

5\. In the field **"Test text"** you can perform a check of specific entry, by writing some phrase with that keyword. For example, the keyword *"buy"*, the test sentence *"I want to buy a car"*

6\. Assign weight (point) to the keyword, The weight defines the extent to which presence of this keyword will be decisive for distribution in a specific group

7\. (optional) add a comment to the keyword, for example, "purchase"

8\. Specify in which operator group to distribute the message request, if the keyword will be found in messages of the client and/or its weight will exceed the weight of other keywords, associated with other groups

## Step 2. Define the priority for groups

Priority for groups is enabled (additional step for decision making), when the sum of weights of the keywords from one operator group is equal to the sum of weights of keywords from another group.

To set up prioritization, you must navigate to "Groups" in "Operators" tab

![](/files/-LouKYGaG25FMepLin7V)

click on <img src="/files/-LouQ0jcneuCHrFhnpz7" alt="" data-size="original">, to open the additional parameters settings menu, and define the priority

![](/files/-LouQZfAaN-x9TI-RHn1)

and click on "Refresh"

{% hint style="warning" %}
The lower the value, the lower the priority for distribution
{% endhint %}

## Step 3. Set up distribution timing

Distribution timing is responsible for settings of:&#x20;

* autresponder content (to obtain additional information from the client)
* time, within which Blinger.io will be expecting other messages from the client
* limit of of the amount of words in all mesages
* time, during which the distributed message request must remain in the status "Closed", to repeat the distribution cycle again.

To set up timing, you must navigate to "Auto assign messages" tab of "Settings" section

![](/files/-Lou8JgKIT4zZAX5ANPv)

and specify the parameters of the function:

1. click on **"Enabled"**
2. fill in with any content the filed **"Auto answer"**
3. define a limit of the words in messages from a client at the beginning of message request, exceeding which will enable the distribution at once in the field **"Min words count"**
4. define the value of the time frame, within which Blinger.io will be waiting for other messages from the client, if the limit in "Min words count" is not exceeded , in the field **"Wait minutes"**
5. define in the field **"Close hours"** the time frame, within which the distributed message request must stay in status "Closed", to repeat the distribution cycle in case of a new message request from a client

then click on "Save".


# Tab: Analytics


# Tags

Tags Analytics displays the amount of messages marked with a particular tag for a selected period of time.

Click "Filter" in the upper right corner of the page, select the period of time and click to confirm.&#x20;

Switch between the tabs to see the tag-marked messages. Follow the links in "Conversation" column next to a particular message and you'll see the conversation containing this tag.

## NB!

{% hint style="info" %}
Click <img src="/files/-LZd2TYPvQoEPELQ7vEy" alt="" data-size="original"> to download csv-file with data analytics.
{% endhint %}


# Clients

Clients analytics displays the amount of clients:

"All clients" tab displays the amount of the clients who contacted Customer Support Center for the entire period of time.

"Contacted clients (all)" displays the amount of (new and old) clients who contacted during a particular period of time selected by clicking "Filter".

"Contacted clients (new)" displays the amount of new clients who contacted during a particular period of time selected by clicking "Filter".

"Recurring message requests from clients" displays the amount of recurring message requests from clients who contacted during a particular period of time selected by clicking "Filter". The amount of requests is counted as follows:

Recurring message requests = amount of requests/amount of the clients who contacted Customer Support Center. &#x20;

"Messaging channels" pie chart displays the most popular messaging apps via which clients prefer contacting during a particular period of time selected by clicking "Filter".

"Messaging channels" pie chart (app breakdown) displays the most popular messaging channel accounts among the clients during a particular period of time selected by clicking "Filter" (It's a useful functionality when several accounts are linked to one messaging channel).

## NB!

{% hint style="info" %}
Click <img src="/files/-LZd2TYPvQoEPELQ7vEy" alt="" data-size="original"> to download csv-file with data analytics.
{% endhint %}


# Agents

Agents Analytics displays the following:

"Solved Conversations" column displays the amount of solved and closed conversations by an agent during a particular period of time selected by clicking "Filter".

"Solved Conversations and re-assigned of them" column displays the amount of solved and closed by an agent and the amount of the conversations which were re-assigned to an agent during a particular period of time selected by clicking "Filter".&#x20;

"Resolution time" column displays the time an agent needs to solve the conversation. The time is counted from the moment a conversation goes into "unassigned" inbox till the moment it goes into "closed" one.

"Messages per conversation" column displays an average amount of messages an agent sends to solve a conversation. The amount of agent's messages from all conversations, which were closed, divided by the amount of closed conversations.

"Response time (excluding first response time)" column displays an average time an agent needs to respond to a client's request in a conversation.&#x20;

"Active time per day" column display an average time an agent spends on solving the conversations during the day.

"Full active time" column displays an average time an agent spends solving the conversations during a particular period of time selected by clicking "Filter". If an agent was offline during the day the data isn't taken into account.&#x20;

**NB!**

{% hint style="info" %}
**If an agent sent a conversation back from "My inbox" into "Unassigned".**\
The parameters are taken into account anew from the moment a conversation goes into "Unassigned" to the moment it goes into "My inbox" again. It doesn't matter if there are any messages from the previous agent who sent the conversation back into "Unassigned".

**If an agent assigned a conversation to another agent.**\
A conversation is still active.

**If an agent assigned a conversation to another group.**\
A conversation is still active.

**If an agent sent a conversation back from "Closed" into "My inbox".**\
If a conversation was closed less than 30 minutes ago the parameters renew till the moment a conversation goes to "Closed" again. If a conversation was closed more than 30 minutes ago and an agent sent it back into "My inbox" then a conversation is considered as a new one.

Click <img src="/files/-LZd2TYPvQoEPELQ7vEy" alt="" data-size="original"> to download csv-file with data analytics.

{% endhint %}


# Conversations

#### Conversations Analytics displays the following:

**"Conversations" chart** displays the amount of conversations which were solved during a particular period of time selected by clicking "Filter".

**"First response time" chart** displays the time agents need to give the first response to the clients.&#x20;

**"Resolution time" chart** displays the time agents need to solve the conversations. The time is counted from the moment a conversation goes into "Unassigned" till the moment it goes into "Closed".

**"Messages" chart** displays the whole amount of messages sent by agents and groups. The messages in closed conversations are counted only.

**"Response time (excluding first response time)" chart** displays the time an agent spends on giving a response in an active conversation.&#x20;

**"Conversations by issues" chart** displays the issues with which the clients contact Customer Support Center. Click "Settings" to customise conversations issues.

{% hint style="info" %}

## **NB!**

**Conversation** is a messaging request from a client. It's considered active from the moment it goes into "Unassigned" till the moment it goes into "Closed". Conversation should include at least 1 client's and 1 agent's messages. Notes aren't included.&#x20;

**Is it possible to view analytics of working and non-working hours separately?**&#x20;

You can customise the parameters in "Group settings" to view analytics of working and non-working hours separately.

\
Click <img src="/files/-LZd2TYPvQoEPELQ7vEy" alt="" data-size="original"> to download csv-file with data analytics.
{% endhint %}


# Tab: Settings


# Subtab: General

## General information

In the "General" tab, you can configure the order in which conversations are displayed and change the view of the tab panel (Applications, Integrations, Widget, etc.)

## How to hide panel tabs?

By default, the Blinger.io window looks like this:

![](/files/-Lnm1CSJ8Fp1wmWh13xu)

However, you can hide the panel with additional tabs (see below)

![](/files/-Lnm1UOJNuWXBQ8U9yTr)

To hide the panel tab ((Applications, Integrations, Widgets, etc.), open "Settings" and activate "Full conversation size" in the general tab and click "Save"

![](/files/-Lnm2oiOO9AyWDhYxuXr)

To show the panel tab, click on the burger icon:

![](/files/-Lnm3gTOT9U4wEH3DOLH)

{% hint style="info" %}
**To see the changes on the web page** you need to reset the cache - use the "shortcuts": MacOS - "Command+R", Win - "Ctrl+F5"
{% endhint %}

## **Display "old" conversations on the top in "Unassigned"?**

If you need that the earlier conversations always appear on the top in the "Unassigned" tab, go to "Settings" and activate "Start from old messages in the" Unassigned "tab in the "General" tab and click "Save".

{% hint style="info" %}
It is useful to make operators start the conversations with the end-users who have been waiting for a response for a long time.
{% endhint %}

![](/files/-Lnm66ATiqaUqM23rI0P)

{% hint style="warning" %}
The time that is used to sort conversations by the time is the time when it come to "Unassigned" tab. Thus, if the operator returned the conversation to “Unassigned” from the “My inbox”, then the time of the last status update will be taken.
{% endhint %}

## Display "old" conversations above in "My Inbox"?

If you need that conversations received earlier in the operator’s “My inbox” always appear at the top, then open “Settings” and activate “Start from old messages in the“ inbox” tab" in the “General” tab and click “Save”

![](/files/-Lnm80dZO63WkYnsRD0a)


# Subtab: Autoresponder

## General information

“Autoresponder” allows you to configure the auto-message sending in response to a new end-user conversation. In other words, this function is useful in the case of an auto-greeting of end-user (without the efforts of operators) and to provide him to additional information: operating time, about the soonest connection with operators, about the need to provide additional information for processing the conversation, etc.

![](/files/-LnmAS0JoTwqUA98Hfl8)

## How to set up autoresponder?

{% hint style="warning" %}
**Pay attention!**

If the function "Auto assign messages" is enabled "Autoresponder won't work
{% endhint %}

### Step 1. Open Settings

![](/files/-LnmB7ABn0YiBuNxuG1N)

### Step 2. Click on "Autoresponder"

![](/files/-LnmBIxy-yG0GzmFrTjj)

### Step 3. Configure the function parameters and click "Save"

1. Activate the function - click "Enable"
2. Fill the "Text" field with the content of the autoresponse.
3. Set the value of the “Number of hours for repeated auto answer” parameter to configure: how much time (minimum) should pass in order to repeat the autoresponse to the next client’s message again.

{% hint style="warning" %}
**About the parameter "Number of hours for repeated auto** autoresponse":

If you set the value = 0, then the autoresponder will work only once in response to the first message from the client.
{% endhint %}

![](/files/-LnmCYc1KBD_Ov3orSIY)


# Subtab: Auto assign messages

## General information

{% hint style="info" %}
This setting is necessary only in 2 cases:

* if you need to assign channels to specific groups ([How to do it?](https://help.blinger.io/documentation/section-apps/assigning-account-to-a-group))
* if you need to configure the conversation distribution by keywords&#x20;

**In other cases this function isn't used!**
{% endhint %}


# Subtab: Topics of conversations

## General information

The function allows you to log the topics of users' requests. Further, this information is accumulated in the "Analytics" tab for further study.

![](/files/-LnmIB6BHG3wzlt0715g)

## How to set up the function?

### Step 1. Open "Settings"

![](/files/-LnmIb2vPJbM_ZTsrXk2)

### Step 2. Open "Topics of conversations"

![](/files/-LnmIq51_L9FW6LbWzBj)

### Step 3. Add the topics&#x20;

After entering the topic you need to click "Add"

![](/files/-LnmJH9uxfjmY0HA-wEW)

{% hint style="warning" %}
If you use Topics of conversation, firstly, you must select a topic and then you're able to click "Closed" to close the conversation
{% endhint %}

![](/files/-LnmJf_0CShqjXvuizLu)


# Subtab: Advanced

## General information

In this tab you can receive the access to:

* Action log
* Block send/receive files to a specific group of operators
* Email whitelist for downloading conversations
* Hide personal data from operators
* IP address whitelist
* Iframe integration
* Manage Webhooks

{% hint style="info" %}
By default, the access to these settings is restricted. Contact Blinger.io Support to get the access
{% endhint %}

## Action log

![](/files/-LnmNa7OQ3xIJC8N93Zk)

Information on each committed action of a super-admin or operator is recorded and displayed in the Action log. Information is displayed in the following order:

* the name of the account that performed the action
* account name for which the action was committed
* type of action
* IP address of the account that committed the action
* date and time of action
* action note

## Block send/receive files

This function allows you to prohibit receiving and sending files to specific groups of operators.

To configure, it is necessary to mark the type of action (receiving / sending), which must be prohibited for a particular group of operators.

![](/files/-LnmR-0O4DiN5tGwrMlW)

## List of email addresses for downloading conversations

The function allows you to limit the ability for operators to download correspondence with end-users and write down specific email addresses to which downloading is possible.

{% hint style="warning" %}
Super-admin account is not affected by this feature.
{% endhint %}

To configure, you must activate the "Restrict email addresses" and enter the email addresses to which the downloading of correspondence will be allowed.

![](/files/-LnmSb4VRwuLFnelcq0N)

## Hide personal data

The function allows you to hide from the operators of specific groups the personal data (contact) of end-users transmitted by social networks and instant messengers to Blinger.io.

{% hint style="warning" %}
Super-admin account is not affected by this feature.
{% endhint %}

To configure you need:

1. Activate "Hide data for all operators besides Super-Admin
2. If you want to hide the avatars there will activate "Hide avatars"
3. Select those groups of operators for which this function won't work
4. Click "Save"

![](/files/-LnmTsPkZ-4xZ6Rroe3y)

## IP address whitelist

The function allows you to set specific IP-addresses by which operators can have access to Blinger.io.

To configure you need:

1. Activate function
2. Enter IP-addresses to whitelist which you can log in your Blinger.io account
3. Click "Save"

![](/files/-LnmY24LA_g7GfiNrZPF)

## Iframe integration

Iframe allows you to embed part of the Blinger.io web interface in a third-party web solution.

The example of implementing iframe integration with bpm'online: [**https://marketplace.bpmonline.com/app/blingerio-connector-bpmonline**](https://marketplace.bpmonline.com/app/blingerio-connector-bpmonline)

More information about the setup steps on the page.

{% hint style="info" %}
For full integration via iframe, we recommend using [**webhooks**](/documentation/webhooks)
{% endhint %}

## Manage Webhooks

Webhooks allow you to transfer json-formatted data about events that occurred in Blinger.io. A detailed description of all the features is available [**here**](https://help.blinger.io/documentation/webhooks).

This section allows to receive the direct access to the Webhooks panel.

![](/files/-LnmZUy6-pOJM9d324Kt)

{% hint style="warning" %}
Just Super-admin account has the access to Webhooks panel
{% endhint %}


# New message notifications

### General information

In Blinger.io it is possible to configure 3 tools for notifying the operators about new messages:&#x20;

* via Slack ([**How to configure notifications in Slack?**](/documentation/integrations/slack))
* via API, using such methods as *Get unassigned conversations, Get unread conversations, Get not answered conversations* ([**more info about the methods**](https://help.blinger.io/documentation/api/conversation-1))
* via push-notifications

{% hint style="info" %}
Here is the guide for setting up push notifications in **Google Chrome.** The notifications can work also in Mozilla Firefox and Opera.
{% endhint %}

### How to turn on push-notifications?

To enable push notifications, you need to click on "Lock" in the left part of the address bar and opposite the Notifications item set the value "Allow"

![](/files/-LnXX71qTXyxOfxVz5ol)

After that you need to reload the page. Probably, you need to exit and enter the browser again.

### How to turn off the notifications?

To turn off push notifications you need to do the following: click on "Lock" on the left side of the address bar and next to the Notifications item set the value "Block"

After that you need to reload the page. Probably, you need to exit and enter the browser again.


# Webhooks

Version 1.0

{% hint style="warning" %}
For provision of access to the setting of webhooks, please, contact with our Support Team.
{% endhint %}

{% hint style="success" %}
Your server must return **HTTP 200 status** if the request is received successfully.
{% endhint %}

Webhooks can trigger the third-party solution on the following events occurred:

### Event: Conversation is unassigned

{% hint style="info" %}
Trigger when a conversation status changed to unassigned
{% endhint %}

{% code title="" %}

```javascript
{
    "webhook":"on_conversation_unassigned",
    "conversation":{
        "id":181,
        "application":"telegrambot",
        "status":"unassigned",
        "date_created":1513351579,
        "date_updated":1513353161,
        "from_user":{
            "user_id":374,
            "role":"default",
            "title":"Yuri Dzabaev",
            "avatar":"https://app.blinger.io/images/users/no-user.png",
            "page_title":"Blinger – Messengers for business", //only for livechat
            "page_url":"https://blinger.io", //only for livechat
            "status":"enabled",
            "service_user_id":"ta4ta4",
            "date_created":1513262192
        }
    }
}
```

{% endcode %}

### Event: Conversation is assigned to operator

{% hint style="info" %}
&#x20;Trigger when a conversation is assigned to operator.
{% endhint %}

{% code title="" %}

```javascript
{
    "webhook":"on_conversation_assigned",
    "conversation":{
        "id":180,
        "application":"telegrambot",
        "status":"inbox",
        "date_created":1513350728,
        "date_updated":1513351289,
        "operator":{
            "id":11,
            "name":"Supervisor",
            "email":"ta4@tut.by"
        },
        "from_user":{
            "user_id":374,
            "role":"default",
            "title":"Yuri Dzabaev",
            "avatar":"https://app.blinger.io/images/users/no-user.png",
            "page_title":"Blinger – Messengers for business", //only for livechat
            "page_url":"https://blinger.io", //only for livechat
            "status":"enabled",
            "service_user_id":"ta4ta4",
            "date_created":1513262192
        }
    }
}
```

{% endcode %}

### Event: Conversation is closed

{% hint style="info" %}
Trigger when a conversation is closed.
{% endhint %}

```javascript
{
    "webhook":"on_conversation_closed",
    "conversation":{
        "id":181,
        "application":"telegrambot",
        "status":"closed",
        "date_created":1513351579,
        "date_updated":1513353917,
        "operator":{
            "id":11,
            "name":"Supervisor",
            "email":"ta4@tut.by"
        },
        "from_user":{
            "user_id":374,
            "role":"default",
            "title":"Yuri Dzabaev",
            "avatar":"https://app.blinger.io/images/users/no-user.png",
            "page_title":"Blinger – Messengers for business", //only for livechat
            "page_url":"https://blinger.io", //only for livechat
            "status":"enabled",
            "service_user_id":"ta4ta4",
            "date_created":1513262192
        }
        "messages":[
            {
                "id":634,
                "from_blinger_user_id":547,
                "to_blinger_user_id":374,
                "from_user_id":547,
                "to_user_id":374,
                "type":"text",
                "application":"telegrambot",
                "message":"123",
                "blinger_message_id":4717,
                "date_created":1513353914,
                "status":"sent",
                "is_outgoing":true,
                "is_inner_message":false,
                "from_user_name":null,
                "to_user_name":"Yuri Dzabaev",
                "fromBlingerUser":{
                    "id":299,
                    "service_blinger_id":18,
                    "blinger_user_id":547,
                    "is_active":true,
                    "date_updated":1513346127,
                    "date_created":1513346127,
                    "tags":"[]",
                    "name":null,
                    "role":"customer",
                    "avatar":null,
                    "application":"telegrambot",
                    "service_user_id":null,
                    "status":"enabled"
                },
                "toBlingerUser":{
                    "id":294,
                    "service_blinger_id":18,
                    "blinger_user_id":374,
                    "is_active":true,
                    "date_updated":1513262192,
                    "date_created":1513262192,
                    "tags":null,
                    "name":"Yuri Dzabaev",
                    "role":"default",
                    "avatar":"https://app.blinger.io/images/users/no-user.png",
                    "application":"telegrambot",
                    "service_user_id":"ta4ta4",
                    "status":"enabled"
                }
            }
        ],
        "tags":[
            {
                "id":"id",
                "title":"test1",
                "message_id":"634"
            },
            {
                "id":"id",
                "title":"test1",
                "message_id":"634"
            },
            {
                "id":"id",
                "title":"test1",
                "message_id":"634"
            }
        ],
        'close_group' => [
            'title' => 'Duplicate',
        ],
    }
}
```

### Event: Incoming message

{% hint style="info" %}
Trigger when a new incoming message received.
{% endhint %}

```javascript
{
    "webhook":"on_message_incoming",
    "from_user_id":481,
    "to_user_id":542,
    "message_id":546,
    "message_blinger_id":4627,
    "conversation_id":173,
    "conversation_token":"G67iEBrRWGx6tz1Q84X5kREL2UhGC8XxzmbLszr60fLep_l6hjGghQ5Umdvac_8U",
    "operator":{
        "id":11, // null if conversation is not assigned to operator
        "name":"Supervisor", // null if conversation is not assigned to operator
        "email":"ta4@tut.by" // null if conversation is not assigned to operator
    },
    "from_user":{
        "user_id":481,
        "role":"default",
        "title":"Yuri Dzabaev",
        "avatar":"https://app.blinger.io/images/users/no-user.png",
        "page_title":"Blinger – Messengers for business", //only for livechat
        "page_url":"https://blinger.io", //only for livechat
        "status":"enabled",
        "application":"vk",
        "service_user_id":"101786025",
        "date_created":1513329664
    },
    "to_user":{
        "user_id":542,
        "role":"customer",
        "title":null,
        "avatar":null,
        "status":"enabled",
        "application":"vk",
        "service_user_id":null,
        "date_created":1513329654
    },
    "message":{
        "id":546,
        "from_user_id":481,
        "to_user_id":542,
        "type":"text",
        "application":"vk",
        "date_created":1513338128,
        "message":"test",
        "tags":["tag1", "tag2"]
    }
}
```

### Event: Outgoing message

{% hint style="info" %}
Trigger when a new outgoing message received
{% endhint %}

```javascript
{
    "webhook":"on_message_outgoing",
    "from_user_id":542,
    "to_user_id":481,
    "message_id":545,
    "message_blinger_id":4626,
    "conversation_id":173,
    "conversation_token":"G67iEBrRWGx6tz1Q84X5kREL2UhGC8XxzmbLszr60fLep_l6hjGghQ5Umdvac_8U",
    "operator":{
        "id":11,
        "name":"Supervisor",
        "email":"ta4@tut.by"
    },
    "from_user":{
        "user_id":542,
        "role":"customer",
        "title":null,
        "avatar":null,
        "page_title":"Blinger – Messengers for business", //only for livechat
        "page_url":"https://blinger.io", //only for livechat
        "status":"enabled",
        "application":"vk",
        "service_user_id":null,
        "date_created":1513329654
    },
    "to_user":{
        "user_id":481,
        "role":"default",
        "title":"Yuri Dzabaev",
        "avatar":"https://app.blinger.io/images/users/no-user.png",
        "page_title":"Blinger – Messengers for business", //only for livechat
        "page_url":"https://blinger.io", //only for livechat
        "status":"enabled",
        "application":"vk",
        "service_user_id":"101786025",
        "date_created":1513329664
    },
    "message":{
        "id":545,
        "from_user_id":542,
        "to_user_id":481,
        "type":"text",
        "application":"vk",
        "date_created":1513337982,
        "message":"123",
        "tags":["tag1", "tag2"]
    }
}
```

### Event: Incoming comment

{% hint style="info" %}
Trigger when a new incoming comment received
{% endhint %}

```javascript
{
    "webhook":"on_comment_incoming",
    "from_user_id":481,
    "to_user_id":542,
    "comment_id":546,
    "comment_blinger_id":4627,
    "conversation_id":173,
    "conversation_token":"G67iEBrRWGx6tz1Q84X5kREL2UhGC8XxzmbLszr60fLep_l6hjGghQ5Umdvac_8U",
    "operator":{
        "id":11, // null if conversation is not assigned to operator
        "name":"Supervisor", // null if conversation is not assigned to operator
        "email":"ta4@tut.by" // null if conversation is not assigned to operator
    },
    "from_user":{
        "user_id":481,
        "role":"default",
        "title":"Yuri Dzabaev",
        "avatar":"https://app.blinger.io/images/users/no-user.png",
        "status":"enabled",
        "application":"vk",
        "service_user_id":"101786025",
        "date_created":1513329664
    },
    "to_user":{
        "user_id":542,
        "role":"customer",
        "title":null,
        "avatar":null,
        "status":"enabled",
        "application":"vk",
        "service_user_id":null,
        "date_created":1513329654
    },
    "comment":{
        "id":546,
        "from_user_id":481,
        "to_user_id":542,
        "reply_comment_id":544,
        "type":"text",
        "post_id":"123123",
        "post_url":"https://vk.com/id1?w=wall1_2307813",
        "post_title":"Пост из вк",
        "application":"vk",
        "date_created":1513338128,
        "message":"test"
    }
}
```

### Event: Outgoing comment

{% hint style="info" %}
Trigger when a new outgoing comment received
{% endhint %}

```javascript
{
    "webhook":"on_comment_outgoing",
    "from_user_id":542,
    "to_user_id":481,
    "comment_id":545,
    "comment_blinger_id":4626,
    "conversation_id":173,
    "conversation_token":"G67iEBrRWGx6tz1Q84X5kREL2UhGC8XxzmbLszr60fLep_l6hjGghQ5Umdvac_8U",
    "operator":{
        "id":11,
        "name":"Supervisor",
        "email":"ta4@tut.by"
    },
    "from_user":{
        "user_id":542,
        "role":"customer",
        "title":null,
        "avatar":null,
        "status":"enabled",
        "application":"vk",
        "service_user_id":null,
        "date_created":1513329654
    },
    "to_user":{
        "user_id":481,
        "role":"default",
        "title":"Yuri Dzabaev",
        "avatar":"https://app.blinger.io/images/users/no-user.png",
        "status":"enabled",
        "application":"vk",
        "service_user_id":"101786025",
        "date_created":1513329664
    },
    "comment":{
        "id":545,
        "from_user_id":542,
        "to_user_id":481,
        "reply_comment_id":544,
        "type":"text",
        "post_id":"123123",
        "post_url":"https://vk.com/id1?w=wall1_2307813",
        "post_title":"Пост из вк",
        "application":"vk",
        "date_created":1513337982,
        "message":"123"
    }
}
```

### Event: New client

{% hint style="info" %}
Trigger when a new user is created
{% endhint %}

```javascript
{
    "webhook":"on_user_new",
    "user":{
        "id":294,
        "blinger_user_id":374,
        "name":"Yuri Dzabaev",
        "avatar":"https://app.blinger.io/images/users/no-user.png",
        "application":"telegrambot",
        "service_user_id":"ta4ta4",
        "date_created":1513262192
    }
}
```

<br>


# Widget API (beta version)


# Conversation

\
Assign Agent
------------

<mark style="color:green;">`POST`</mark> `https://widget.blinger.io/api/external/v1/conversation/:id/assign-agent`

#### Path Parameters

| Name | Type   | Description             |
| ---- | ------ | ----------------------- |
| id   | string | ID of the conversation. |

#### Headers

| Name          | Type   | Description          |
| ------------- | ------ | -------------------- |
| Authorization | string | Authorization token. |

#### Request Body

| Name    | Type   | Description      |
| ------- | ------ | ---------------- |
| agentId | string | ID of the agent. |

{% tabs %}
{% tab title="200 Cake successfully retrieved." %}

```javascript
{
    "status": 200,
    "data": {
        "id": "e1d247c8-5cd8-4f93-b9d7-15fd3259ac22",
        "assignedAgent": {
            "id": "c671d030-584e-4422-8710-9215c04b6a64",
            "serviceUserId": "12345",
            "name": "Vadim Belorusov",
            "status": "online",
            "avatar": {
                "id": "76d94b6b-a45c-4d62-8010-bd2f52d8c846",
                "type": "image",
                "meta": {
                    "width": 400,
                    "height": 400
                },
                "info": {
                    "ext": "jpeg",
                    "name": "5d1db8373db3a",
                    "path": "/c2/b1/62/be16b35869e9491a6761c013cbae7548f23b17abb225eaa82efd214264779825.jpeg",
                    "size": 5106,
                    "mimeType": "image/jpeg"
                },
                "url": {
                    "120x120": "http://static.widget.blinger.io/120x120/c2/b1/62/be16b35869e9491a6761c013cbae7548f23b17abb225eaa82efd214264779825.jpeg",
                    "520x400": "http://static.widget.blinger.io/520x400/c2/b1/62/be16b35869e9491a6761c013cbae7548f23b17abb225eaa82efd214264779825.jpeg",
                    "default": "http://static.widget.blinger.io/c2/b1/62/be16b35869e9491a6761c013cbae7548f23b17abb225eaa82efd214264779825.jpeg"
                },
                "createdAt": 1562198400,
                "updatedAt": 1562198400
            },
            "active": true,
            "createdAt": 1562228791,
            "updatedAt": 1562228791
        },
        "locked": false,
        "createdAt": 1562228238,
        "updatedAt": 1562241579
    }
}
```

{% endtab %}
{% endtabs %}

## Send Text Message

<mark style="color:green;">`POST`</mark> `https://widget.blinger.io/api/external/v1/conversation/:id/send-text-message`

#### Path Parameters

| Name | Type   | Description             |
| ---- | ------ | ----------------------- |
| id   | string | ID of the conversation. |

#### Headers

| Name          | Type   | Description          |
| ------------- | ------ | -------------------- |
| Authorization | string | Authorization token. |

#### Request Body

| Name | Type   | Description                         |
| ---- | ------ | ----------------------------------- |
| uuid | string | Unique generated ID of the message. |
| text | string | Simple text message.                |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "status": 200,
    "data": {
        "id": "554f11c1-ec1e-4fdb-9953-bfad33013f58",
        "status": "delivered",
        "type": "text",
        "body": "Hello",
        "file": null,
        "review": null,
        "bot": null,
        "agent": null,
        "endUser": {
            "id": "3132ad01-1d3c-4d14-ad05-19ae73c07556",
            "websocketToken": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIzMTMyYWQwMS0xZDNjLTRkMTQtYWQwNS0xOWFlNzNjMDc1NTYifQ.cjKtgNraxCceKS-44SLH1SrKGsksvPgzlTX523C7lPw",
            "createdAt": 1562228238,
            "updatedAt": 1562228238
        },
        "microseconds": 1562242173465326,
        "createdAt": 1562242173,
        "updatedAt": 1562242173
    }
}
```

{% endtab %}
{% endtabs %}

## Send File Message

<mark style="color:green;">`POST`</mark> `https://widget.blinger.io/api/external/v1/conversation/:id/send-file-message`

#### Path Parameters

| Name | Type   | Description             |
| ---- | ------ | ----------------------- |
| id   | string | ID of the conversation. |

#### Headers

| Name          | Type   | Description          |
| ------------- | ------ | -------------------- |
| Authorization | string | Authorization token. |

#### Request Body

| Name | Type   | Description                        |
| ---- | ------ | ---------------------------------- |
| file | string | Url of the file.                   |
| uuid | string | Unique generated ID of the message |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "status": 200,
    "data": {
        "id": "b01f7d2f-7003-4cc2-9a95-ac20d6374358",
        "status": "delivered",
        "type": "file",
        "body": null,
        "file": {
            "id": "6350e4fa-7b69-4f6b-b24e-228a05d62c21",
            "type": "image",
            "meta": {
                "width": 1920,
                "height": 1080
            },
            "info": {
                "name": "phpanbHIN",
                "ext": "png",
                "mimeType": "image/png",
                "size": 327743,
                "path": "/c2/9b/f1/734b2fce15c08f9ddae842c2daae809d1362e3d98ead08c26678f0707a776b72.png"
            },
            "url": {
                "120x120": "http://static.widget.blinger.io/120x120/c2/9b/f1/734b2fce15c08f9ddae842c2daae809d1362e3d98ead08c26678f0707a776b72.png",
                "520x400": "http://static.widget.blinger.io/520x400/c2/9b/f1/734b2fce15c08f9ddae842c2daae809d1362e3d98ead08c26678f0707a776b72.png",
                "default": "http://static.widget.blinger.io/c2/9b/f1/734b2fce15c08f9ddae842c2daae809d1362e3d98ead08c26678f0707a776b72.png"
            },
            "createdAt": 1562242573,
            "updatedAt": 1562242573
        },
        "review": null,
        "bot": null,
        "agent": null,
        "endUser": {
            "id": "3132ad01-1d3c-4d14-ad05-19ae73c07556",
            "websocketToken": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIzMTMyYWQwMS0xZDNjLTRkMTQtYWQwNS0xOWFlNzNjMDc1NTYifQ.cjKtgNraxCceKS-44SLH1SrKGsksvPgzlTX523C7lPw",
            "createdAt": 1562228238,
            "updatedAt": 1562228238
        },
        "microseconds": 1562242573548953,
        "createdAt": 1562242573,
        "updatedAt": 1562242573
    }
}
```

{% endtab %}
{% endtabs %}

## Request Review

<mark style="color:green;">`POST`</mark> `https://widget.blinger.io/api/external/v1/conversation/:id/request-review`

#### Path Parameters

| Name | Type   | Description            |
| ---- | ------ | ---------------------- |
| id   | string | ID of the conversation |

#### Headers

| Name          | Type   | Description          |
| ------------- | ------ | -------------------- |
| Authorization | string | Authorization token. |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "status": 200,
    "data": {
        "id": "b2737f3a-eaee-4271-b705-2bc9bb951ca1",
        "status": "delivered",
        "type": "review",
        "body": null,
        "file": null,
        "review": {
            "id": "6bc1f3b9-c972-400d-b5cd-1ca4e2d9a8fc",
            "agent": {
                "id": "c671d030-584e-4422-8710-9215c04b6a64",
                "serviceUserId": "12345",
                "name": "Vadim Belorusov",
                "status": "online",
                "avatar": {
                    "id": "76d94b6b-a45c-4d62-8010-bd2f52d8c846",
                    "type": "image",
                    "meta": {
                        "width": 400,
                        "height": 400
                    },
                    "info": {
                        "ext": "jpeg",
                        "name": "5d1db8373db3a",
                        "path": "/c2/b1/62/be16b35869e9491a6761c013cbae7548f23b17abb225eaa82efd214264779825.jpeg",
                        "size": 5106,
                        "mimeType": "image/jpeg"
                    },
                    "url": {
                        "120x120": "http://static.widget.blinger.io/120x120/c2/b1/62/be16b35869e9491a6761c013cbae7548f23b17abb225eaa82efd214264779825.jpeg",
                        "520x400": "http://static.widget.blinger.io/520x400/c2/b1/62/be16b35869e9491a6761c013cbae7548f23b17abb225eaa82efd214264779825.jpeg",
                        "default": "http://static.widget.blinger.io/c2/b1/62/be16b35869e9491a6761c013cbae7548f23b17abb225eaa82efd214264779825.jpeg"
                    },
                    "createdAt": 1562198400,
                    "updatedAt": 1562198400
                },
                "active": true,
                "createdAt": 1562228791,
                "updatedAt": 1562228791
            },
            "endUser": {
                "id": "3132ad01-1d3c-4d14-ad05-19ae73c07556",
                "websocketToken": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIzMTMyYWQwMS0xZDNjLTRkMTQtYWQwNS0xOWFlNzNjMDc1NTYifQ.cjKtgNraxCceKS-44SLH1SrKGsksvPgzlTX523C7lPw",
                "createdAt": 1562228238,
                "updatedAt": 1562228238
            },
            "mark": 0,
            "confirmed": false,
            "text": "",
            "createdAt": 1562242470,
            "updatedAt": 1562242470
        },
        "bot": {
            "id": "ad92f7ab-388f-4e86-a20a-4425885bfa40",
            "name": "Blinger bot",
            "createdAt": 1562228206,
            "updatedAt": 1562228206
        },
        "agent": null,
        "endUser": null,
        "microseconds": 1562242470285931,
        "createdAt": 1562242470,
        "updatedAt": 1562242470
    }
}
```

{% endtab %}
{% endtabs %}


# Agent

## Get All Agents

<mark style="color:blue;">`GET`</mark> `https://widget.blinger.io/api/external/v1/agents`

This endpoint allows you to get free cakes.

#### Headers

| Name          | Type   | Description          |
| ------------- | ------ | -------------------- |
| Authorization | string | Authorization token. |

{% tabs %}
{% tab title="200 Cake successfully retrieved." %}

```javascript
{
    "status": 200,
    "data": [
        {
            "id": "5475272c-3bc0-40e9-83c4-0a1cd50bc721",
            "serviceUserId": "12345",
            "name": "Vadim Belorusov",
            "status": "online",
            "avatar": {
                "id": "856a906b-b55e-493a-b04c-df019fff6c8f",
                "type": "image",
                "meta": {
                    "width": 400,
                    "height": 400
                },
                "info": {
                    "ext": "jpeg",
                    "name": "5d1dbd5e921f6",
                    "path": "/91/44/41/96b85c57f9ae26a2376154c82dd55b9f6cb33ea2b038db8057b8db04a559c7f0.jpeg",
                    "size": 5106,
                    "mimeType": "image/jpeg"
                },
                "url": {
                    "120x120": "http://static.widget.blinger.io/120x120/91/44/41/96b85c57f9ae26a2376154c82dd55b9f6cb33ea2b038db8057b8db04a559c7f0.jpeg",
                    "520x400": "http://static.widget.blinger.io/520x400/91/44/41/96b85c57f9ae26a2376154c82dd55b9f6cb33ea2b038db8057b8db04a559c7f0.jpeg",
                    "default": "http://static.widget.blinger.io/91/44/41/96b85c57f9ae26a2376154c82dd55b9f6cb33ea2b038db8057b8db04a559c7f0.jpeg"
                },
                "createdAt": 1562198400,
                "updatedAt": 1562198400
            },
            "active": true,
            "createdAt": 1562230110,
            "updatedAt": 1562230110
        },
        {
            "id": "c671d030-584e-4422-8710-9215c04b6a64",
            "serviceUserId": "123456",
            "name": "Vadim Belorusov",
            "status": "online",
            "avatar": {
                "id": "76d94b6b-a45c-4d62-8010-bd2f52d8c846",
                "type": "image",
                "meta": {
                    "width": 400,
                    "height": 400
                },
                "info": {
                    "ext": "jpeg",
                    "name": "5d1db8373db3a",
                    "path": "/c2/b1/62/be16b35869e9491a6761c013cbae7548f23b17abb225eaa82efd214264779825.jpeg",
                    "size": 5106,
                    "mimeType": "image/jpeg"
                },
                "url": {
                    "120x120": "http://static.widget.blinger.io/120x120/c2/b1/62/be16b35869e9491a6761c013cbae7548f23b17abb225eaa82efd214264779825.jpeg",
                    "520x400": "http://static.widget.blinger.io/520x400/c2/b1/62/be16b35869e9491a6761c013cbae7548f23b17abb225eaa82efd214264779825.jpeg",
                    "default": "http://static.widget.blinger.io/c2/b1/62/be16b35869e9491a6761c013cbae7548f23b17abb225eaa82efd214264779825.jpeg"
                },
                "createdAt": 1562198400,
                "updatedAt": 1562198400
            },
            "active": true,
            "createdAt": 1562228791,
            "updatedAt": 1562228791
        }
    ]
}
```

{% endtab %}
{% endtabs %}

## Get Agent

<mark style="color:blue;">`GET`</mark> `https://widget.blinger.io/api/external/v1/agents/:id`

#### Path Parameters

| Name | Type   | Description      |
| ---- | ------ | ---------------- |
| id   | string | ID of the agent. |

#### Headers

| Name          | Type   | Description          |
| ------------- | ------ | -------------------- |
| Authorization | string | Authorization token. |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "status": 200,
    "data": {
        "id": "5475272c-3bc0-40e9-83c4-0a1cd50bc721",
        "serviceUserId": "12345",
        "name": "Vadim Belorusov",
        "status": "online",
        "avatar": {
            "id": "856a906b-b55e-493a-b04c-df019fff6c8f",
            "type": "image",
            "meta": {
                "width": 400,
                "height": 400
            },
            "info": {
                "ext": "jpeg",
                "name": "5d1dbd5e921f6",
                "path": "/91/44/41/96b85c57f9ae26a2376154c82dd55b9f6cb33ea2b038db8057b8db04a559c7f0.jpeg",
                "size": 5106,
                "mimeType": "image/jpeg"
            },
            "url": {
                "120x120": "http://static.widget.blinger.io/120x120/91/44/41/96b85c57f9ae26a2376154c82dd55b9f6cb33ea2b038db8057b8db04a559c7f0.jpeg",
                "520x400": "http://static.widget.blinger.io/520x400/91/44/41/96b85c57f9ae26a2376154c82dd55b9f6cb33ea2b038db8057b8db04a559c7f0.jpeg",
                "default": "http://static.widget.blinger.io/91/44/41/96b85c57f9ae26a2376154c82dd55b9f6cb33ea2b038db8057b8db04a559c7f0.jpeg"
            },
            "createdAt": 1562198400,
            "updatedAt": 1562198400
        },
        "active": true,
        "createdAt": 1562230110,
        "updatedAt": 1562230110
    }
}
```

{% endtab %}
{% endtabs %}

## Create Agent

<mark style="color:green;">`POST`</mark> `https://widget.blinger.io/api/external/v1/agents`

#### Headers

| Name          | Type   | Description          |
| ------------- | ------ | -------------------- |
| Authorization | string | Authorization token. |

#### Request Body

| Name          | Type    | Description                                                        |
| ------------- | ------- | ------------------------------------------------------------------ |
| active        | boolean | Is agent active or not.                                            |
| serviceUserId | string  | Simple string identificates your service.                          |
| name          | string  | Agent's Name.                                                      |
| avatar        | string  | Url of the Agent's Avatar.                                         |
| status        | string  | <p>Status of the agent. Possible values:<br>offline or online.</p> |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "status": 200,
    "data": {
        "id": "c2e53dee-ad8d-45dc-909a-465746932f11",
        "serviceUserId": "12345",
        "name": "Vadim Belorusov",
        "status": "online",
        "avatar": {
            "id": "366baf52-920e-4483-96b1-36955d49f65f",
            "type": "image",
            "meta": {
                "width": 400,
                "height": 400
            },
            "info": {
                "name": "5d1df34c0a573",
                "ext": "jpeg",
                "mimeType": "image/jpeg",
                "size": 5106,
                "path": "/1c/a8/7a/405bb573328256eebf41c6c99fc1c445271acb9a594bb91fddabc963d1e6ba70.jpeg"
            },
            "url": {
                "120x120": "http://static.widget.blinger.io/120x120/1c/a8/7a/405bb573328256eebf41c6c99fc1c445271acb9a594bb91fddabc963d1e6ba70.jpeg",
                "520x400": "http://static.widget.blinger.io/520x400/1c/a8/7a/405bb573328256eebf41c6c99fc1c445271acb9a594bb91fddabc963d1e6ba70.jpeg",
                "default": "http://static.widget.blinger.io/1c/a8/7a/405bb573328256eebf41c6c99fc1c445271acb9a594bb91fddabc963d1e6ba70.jpeg"
            },
            "createdAt": 1562243916,
            "updatedAt": 1562243916
        },
        "active": true,
        "createdAt": 1562243916,
        "updatedAt": 1562243916
    }
}
```

{% endtab %}
{% endtabs %}

## Update agent

<mark style="color:orange;">`PUT`</mark> `https://widget.blinger.io/api/external/v1/agents/:id`

#### Path Parameters

| Name | Type   | Description      |
| ---- | ------ | ---------------- |
| id   | string | ID of the agent. |

#### Headers

| Name          | Type   | Description          |
| ------------- | ------ | -------------------- |
| Authorization | string | Authorization token. |

#### Request Body

| Name          | Type    | Description                                                        |
| ------------- | ------- | ------------------------------------------------------------------ |
| active        | boolean | Is agent active or not.                                            |
| serviceUserId | string  | Simple string identificates your service.                          |
| name          | string  | Agent's Name.                                                      |
| avatar        | string  | Url of the Agent's Avatar.                                         |
| status        | string  | <p>Status of the agent. Possible values:<br>offline or online.</p> |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "status": 200,
    "data": {
        "id": "c2e53dee-ad8d-45dc-909a-465746932f11",
        "serviceUserId": "12345",
        "name": "Vadim Belorusov",
        "status": "online",
        "avatar": {
            "id": "366baf52-920e-4483-96b1-36955d49f65f",
            "type": "image",
            "meta": {
                "width": 400,
                "height": 400
            },
            "info": {
                "name": "5d1df34c0a573",
                "ext": "jpeg",
                "mimeType": "image/jpeg",
                "size": 5106,
                "path": "/1c/a8/7a/405bb573328256eebf41c6c99fc1c445271acb9a594bb91fddabc963d1e6ba70.jpeg"
            },
            "url": {
                "120x120": "http://static.widget.blinger.io/120x120/1c/a8/7a/405bb573328256eebf41c6c99fc1c445271acb9a594bb91fddabc963d1e6ba70.jpeg",
                "520x400": "http://static.widget.blinger.io/520x400/1c/a8/7a/405bb573328256eebf41c6c99fc1c445271acb9a594bb91fddabc963d1e6ba70.jpeg",
                "default": "http://static.widget.blinger.io/1c/a8/7a/405bb573328256eebf41c6c99fc1c445271acb9a594bb91fddabc963d1e6ba70.jpeg"
            },
            "createdAt": 1562243916,
            "updatedAt": 1562243916
        },
        "active": true,
        "createdAt": 1562243916,
        "updatedAt": 1562243916
    }
}
```

{% endtab %}
{% endtabs %}


# Webhook

## Create webhook

<mark style="color:green;">`POST`</mark> `https://widget.blinger.io/api/external/v1/webhooks`

This endpoint allows you to get free cakes.

#### Headers

| Name          | Type   | Description          |
| ------------- | ------ | -------------------- |
| Authorization | string | Authorization Token. |

#### Request Body

| Name | Type   | Description  |
| ---- | ------ | ------------ |
| url  | string | Webhook url. |

{% tabs %}
{% tab title="200 Cake successfully retrieved." %}

```javascript
{
    "status": 200,
    "data": {
        "id": "f3f5e2ea-cc20-43cb-b609-7afdf9899afa",
        "url": "https://www.yoururl.com/62a7c920-d2f4-4e1b-bb1b-ba8dddadaab6",
        "createdAt": 1562231752,
        "updatedAt": 1562244363
    }
}
```

{% endtab %}
{% endtabs %}

## Remove webhook

<mark style="color:red;">`DELETE`</mark> `https://widget.blinger.io/api/external/v1/webhooks`

#### Headers

| Name          | Type   | Description          |
| ------------- | ------ | -------------------- |
| Authorization | string | Authorization Token. |

{% tabs %}
{% tab title="200 " %}

```
```

{% endtab %}
{% endtabs %}


# API Token

{% hint style="warning" %}
Contact to Support Team to get **Bearer Token.**
{% endhint %}

{% hint style="warning" %}
For authentication in API send **Bearer Token** in headers.

`Authorization: Bearer <token>`
{% endhint %}


# API

Version 1.0

{% hint style="info" %}
Need to use for outgoing messages, i.e. from agent.&#x20;

Use [**Webhooks**](/documentation/webhooks) for inbound messages, i.e. from end-users.
{% endhint %}

### Use navigation:

{% content-ref url="/pages/-LhG11c3EmTwAw0SA55J" %}
[API Token](/documentation/api/api-token)
{% endcontent-ref %}

{% content-ref url="/pages/-Lgxcasq5s25Mo56z5Z8" %}
[Conversation](/documentation/api/conversation-1)
{% endcontent-ref %}

{% content-ref url="/pages/-Lh1LuzlcS3fa2iq6k0I" %}
[Operator](/documentation/api/operator)
{% endcontent-ref %}

{% content-ref url="/pages/QR4D2pLlMdKotM54Bwvs" %}
[User](/documentation/api/user)
{% endcontent-ref %}


# API Token

{% hint style="warning" %}
Contact to Support Team to get **Bearer Token.**
{% endhint %}

{% hint style="warning" %}
For authentication in API send **Bearer Token** in headers. \
`Authorization: Bearer <token>`
{% endhint %}


# Conversation

## Start conversation

<mark style="color:green;">`POST`</mark> `https://app.blinger.io/api/conversations/start`

This endpoint allows you to start the conversation.

#### Headers

| Name           | Type   | Description          |
| -------------- | ------ | -------------------- |
| Authentication | string | Authentication token |

#### Request Body

| Name             | Type    | Description     |
| ---------------- | ------- | --------------- |
| conversation\_id | integer |                 |
| operator\_id     | integer | Default - Admin |
| disable\_webhook | integer | Default - 0     |

{% tabs %}
{% tab title="200 Conversation successfully started." %}

```javascript
{
    "status": 200,
    "data": {
        "id": 2,
        "user_id": 1,
        "operator_user_id": 1,
        "from_blinger_user_id": 5,
        "to_blinger_user_id": 4,
        "from_user_name": "LiveChat client #5",
        "to_user_name": "user@gmail.com",
        "application": "livechat",
        "last_message": "124124",
        "unread_count": 0,
        "status": "inbox",
        "date_created": 1559737532,
        "date_updated": 1560107366,
        "from_user_avatar": null,
        "is_outgoing": false,
        "token": "A0N_JeEemP_2TItFDcw-RrvuIrJ4ZWcdQixrkYB1PBJP7c5ZKLN0Mm200XCr8ABU",
        "is_new_conversation": false,
        "waiting_operator_response": false,
        "group_id": 1,
        "is_inner_message": null,
        "is_operator_last_message": true,
        "is_group_closed": false,
        "close_group": null,
        "type": "message",
        "comment_post_id": null,
        "comment_post_url": null,
        "comment_post_title": null,
        "comment_post_img": null,
        "unassigned_date": 1559807929,
        "last_message_date": 1559826168,
        "from_user_custom_name": null,
        "toBlingerUser": {
            "id": 4,
            "service_blinger_id": 1,
            "blinger_user_id": 4,
            "is_active": true,
            "date_updated": 1559737517,
            "date_created": 1559737517,
            "tags": null,
            "name": null,
            "role": "customer",
            "avatar": null,
            "application": "livechat",
            "service_user_id": null,
            "status": "enabled",
            "group_id": null,
            "is_comments": null,
            "page_url": null,
            "page_title": null,
            "extra_fields": null,
            "extra_field_secret_key": "g9k0jUSfIBdr12zgMJWLVKoi-WdhSyaf",
            "custom_name": null
        }
    }
}
```

{% endtab %}

{% tab title="400 Could not to start the conversation." %}

```javascript
{
    "error": "The c    onversation was assigned to another operator",
    "status": 400
}
```

{% endtab %}
{% endtabs %}

## Close conversation

<mark style="color:green;">`POST`</mark> `https://app.blinger.io/api/conversations/close`

This endpoint allows you to close the conversation.

#### Headers

| Name           | Type   | Description          |
| -------------- | ------ | -------------------- |
| Authentication | string | Authentication token |

#### Request Body

| Name             | Type    | Description     |
| ---------------- | ------- | --------------- |
| conversation\_id | integer |                 |
| operator\_id     | integer | Default - Admin |
| disable\_webhook | integer | Default - 0     |

{% tabs %}
{% tab title="200 Conversation successfully closed." %}

```javascript
{
    "status": 200,
    "data": {
        "id": 2,
        "user_id": 1,
        "operator_user_id": 1,
        "from_blinger_user_id": 5,
        "to_blinger_user_id": 4,
        "from_user_name": "LiveChat client #5",
        "to_user_name": "artemylapko@gmail.com",
        "application": "livechat",
        "last_message": "124124",
        "unread_count": 0,
        "status": "closed",
        "date_created": 1559737532,
        "date_updated": 1560187173,
        "from_user_avatar": null,
        "is_outgoing": false,
        "token": "A0N_JeEemP_2TItFDcw-RrvuIrJ4ZWcdQixrkYB1PBJP7c5ZKLN0Mm200XCr8ABU",
        "is_new_conversation": false,
        "waiting_operator_response": false,
        "group_id": 1,
        "is_inner_message": null,
        "is_operator_last_message": true,
        "is_group_closed": false,
        "close_group": null,
        "type": "message",
        "comment_post_id": null,
        "comment_post_url": null,
        "comment_post_title": null,
        "comment_post_img": null,
        "unassigned_date": 1559807929,
        "last_message_date": 1560185816,
        "from_user_custom_name": null,
        "toBlingerUser": {
            "id": 4,
            "service_blinger_id": 1,
            "blinger_user_id": 4,
            "is_active": true,
            "date_updated": 1559737517,
            "date_created": 1559737517,
            "tags": null,
            "name": null,
            "role": "customer",
            "avatar": null,
            "application": "livechat",
            "service_user_id": null,
            "status": "enabled",
            "group_id": null,
            "is_comments": null,
            "page_url": null,
            "page_title": null,
            "extra_fields": null,
            "extra_field_secret_key": "g9k0jUSfIBdr12zgMJWLVKoi-WdhSyaf",
            "custom_name": null
        }
    }
}a
```

{% endtab %}

{% tab title="400 Could not close the conversation." %}

```javascript
{
    "error": "The conversation is closed.",
    "status": 400
}
```

{% endtab %}
{% endtabs %}

## Unassign conversation&#x20;

<mark style="color:green;">`POST`</mark> `https://app.blinger.io/api/conversations/unassign`

#### Path Parameters

| Name           | Type   | Description          |
| -------------- | ------ | -------------------- |
| Authentication | string | Authentication token |

#### Request Body

| Name             | Type    | Description     |
| ---------------- | ------- | --------------- |
| conversation\_id | integer |                 |
| operator\_id     | integer | Default - Admin |
| disable\_webhook | integer | Default - 0     |

{% tabs %}
{% tab title="200 " %}

```
{
    "status": 200,
    "data": {
        "id": 2,
        "user_id": 1,
        "operator_user_id": 1,
        "from_blinger_user_id": 5,
        "to_blinger_user_id": 4,
        "from_user_name": "LiveChat client #5",
        "to_user_name": "artemylapko@gmail.com",
        "application": "livechat",
        "last_message": "124124",
        "unread_count": 0,
        "status": "closed",
        "date_created": 1559737532,
        "date_updated": 1560187173,
        "from_user_avatar": null,
        "is_outgoing": false,
        "token": "A0N_JeEemP_2TItFDcw-RrvuIrJ4ZWcdQixrkYB1PBJP7c5ZKLN0Mm200XCr8ABU",
        "is_new_conversation": false,
        "waiting_operator_response": false,
        "group_id": 1,
        "is_inner_message": null,
        "is_operator_last_message": true,
        "is_group_closed": false,
        "close_group": null,
        "type": "message",
        "comment_post_id": null,
        "comment_post_url": null,
        "comment_post_title": null,
        "comment_post_img": null,
        "unassigned_date": 1559807929,
        "last_message_date": 1560185816,
        "from_user_custom_name": null,
        "toBlingerUser": {
            "id": 4,
            "service_blinger_id": 1,
            "blinger_user_id": 4,
            "is_active": true,
            "date_updated": 1559737517,
            "date_created": 1559737517,
            "tags": null,
            "name": null,
            "role": "customer",
            "avatar": null,
            "application": "livechat",
            "service_user_id": null,
            "status": "enabled",
            "group_id": null,
            "is_comments": null,
            "page_url": null,
            "page_title": null,
            "extra_fields": null,
            "extra_field_secret_key": "g9k0jUSfIBdr12zgMJWLVKoi-WdhSyaf",
            "custom_name": null
        }
    }
}
```

{% endtab %}

{% tab title="400 " %}

```
{
    "error": "The conversation is already unassigned.",
    "status": 400
}
```

{% endtab %}
{% endtabs %}

## Assign operator

<mark style="color:green;">`POST`</mark> `https://app.blinger.io/api/conversations/assign-operator`

This endpoint allows you to assign the operator to the conversations

#### Headers

| Name           | Type   | Description          |
| -------------- | ------ | -------------------- |
| Authentication | string | Authentication token |

#### Request Body

| Name             | Type    | Description |
| ---------------- | ------- | ----------- |
| conversation\_id | integer |             |
| operator\_id     | integer |             |
| disable\_webhook | integer | Default - 0 |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "status": 200,
    "data": {
        "id": 2,
        "user_id": 1,
        "operator_user_id": 3,
        "from_blinger_user_id": 5,
        "to_blinger_user_id": 4,
        "from_user_name": "LiveChat client #5",
        "to_user_name": "artemylapko@gmail.com",
        "application": "livechat",
        "last_message": "124124",
        "unread_count": 1,
        "status": "inbox",
        "date_created": 1559737532,
        "date_updated": 1560188161,
        "from_user_avatar": null,
        "is_outgoing": false,
        "token": "A0N_JeEemP_2TItFDcw-RrvuIrJ4ZWcdQixrkYB1PBJP7c5ZKLN0Mm200XCr8ABU",
        "is_new_conversation": false,
        "waiting_operator_response": false,
        "group_id": 1,
        "is_inner_message": null,
        "is_operator_last_message": true,
        "is_group_closed": false,
        "close_group": null,
        "type": "message",
        "comment_post_id": null,
        "comment_post_url": null,
        "comment_post_title": null,
        "comment_post_img": null,
        "unassigned_date": 1559807929,
        "last_message_date": 1560185816,
        "from_user_custom_name": null,
        "toBlingerUser": {
            "id": 4,
            "service_blinger_id": 1,
            "blinger_user_id": 4,
            "is_active": true,
            "date_updated": 1559737517,
            "date_created": 1559737517,
            "tags": null,
            "name": null,
            "role": "customer",
            "avatar": null,
            "application": "livechat",
            "service_user_id": null,
            "status": "enabled",
            "group_id": null,
            "is_comments": null,
            "page_url": null,
            "page_title": null,
            "extra_fields": null,
            "extra_field_secret_key": "g9k0jUSfIBdr12zgMJWLVKoi-WdhSyaf",
            "custom_name": null
        }
    }
}
```

{% endtab %}

{% tab title="400 " %}

```javascript
{
    "error": "The conversation has already been assigned to this operator.",
    "status": 400
}
```

{% endtab %}
{% endtabs %}

## Assign group

<mark style="color:green;">`POST`</mark> `https://app.blinger.io/api/conversations/assign-group`

This endpoint allows you to assign the group to the conversation

#### Headers

| Name           | Type   | Description          |
| -------------- | ------ | -------------------- |
| Authentication | string | Authentication token |

#### Request Body

| Name             | Type    | Description |
| ---------------- | ------- | ----------- |
| conversation\_id | integer |             |
| group\_id        | integer |             |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "status": 200,
    "data": {
        "id": 2,
        "user_id": 1,
        "operator_user_id": 3,
        "from_blinger_user_id": 5,
        "to_blinger_user_id": 4,
        "from_user_name": "LiveChat client #5",
        "to_user_name": "artemylapko@gmail.com",
        "application": "livechat",
        "last_message": "124124",
        "unread_count": 1,
        "status": "inbox",
        "date_created": 1559737532,
        "date_updated": 1560188258,
        "from_user_avatar": null,
        "is_outgoing": false,
        "token": "A0N_JeEemP_2TItFDcw-RrvuIrJ4ZWcdQixrkYB1PBJP7c5ZKLN0Mm200XCr8ABU",
        "is_new_conversation": false,
        "waiting_operator_response": false,
        "group_id": 1,
        "is_inner_message": null,
        "is_operator_last_message": true,
        "is_group_closed": false,
        "close_group": null,
        "type": "message",
        "comment_post_id": null,
        "comment_post_url": null,
        "comment_post_title": null,
        "comment_post_img": null,
        "unassigned_date": 1559807929,
        "last_message_date": 1560185816,
        "from_user_custom_name": null,
        "toBlingerUser": {
            "id": 4,
            "service_blinger_id": 1,
            "blinger_user_id": 4,
            "is_active": true,
            "date_updated": 1559737517,
            "date_created": 1559737517,
            "tags": null,
            "name": null,
            "role": "customer",
            "avatar": null,
            "application": "livechat",
            "service_user_id": null,
            "status": "enabled",
            "group_id": null,
            "is_comments": null,
            "page_url": null,
            "page_title": null,
            "extra_fields": null,
            "extra_field_secret_key": "g9k0jUSfIBdr12zgMJWLVKoi-WdhSyaf",
            "custom_name": null
        }
    }
}
```

{% endtab %}

{% tab title="400 " %}

```javascript
{
    "error": "The operator group has already been selected.",
    "status": 400
}
```

{% endtab %}
{% endtabs %}

## Send message

<mark style="color:green;">`POST`</mark> `https://app.blinger.io/api/conversations/send-message`

#### Headers

| Name           | Type   | Description          |
| -------------- | ------ | -------------------- |
| Authentication | string | Authentication token |

#### Request Body

| Name             | Type    | Description     |
| ---------------- | ------- | --------------- |
| conversation\_id | integer |                 |
| text             | string  |                 |
| operator\_id     | integer | Default - Admin |
| disable\_webhook | integer | Default - 0     |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "status": 200,
    "data": {
        "id": 178,
        "from_blinger_user_id": 4,
        "to_blinger_user_id": 5,
        "blinger_message_id": 178,
        "application": "livechat",
        "type": "text",
        "message": "124124",
        "date_updated": 1560188469,
        "date_created": 1560188469,
        "is_outgoing": true,
        "status": "sent",
        "is_inner_message": false,
        "date_read": null,
        "date_real": 15601884680000,
        "error": null,
        "is_history": false,
        "echo": false,
        "echo_outgoing": false
    }
}
```

{% endtab %}

{% tab title="400 " %}

```javascript
{
    "error": "text is empty",
    "status": 400
}
```

{% endtab %}
{% endtabs %}

## Send file message

<mark style="color:green;">`POST`</mark> `https://app.blinger.io/api/conversations/send-file-message`

#### Path Parameters

| Name           | Type   | Description          |
| -------------- | ------ | -------------------- |
| Authentication | string | Authentication token |

#### Request Body

| Name             | Type    | Description     |
| ---------------- | ------- | --------------- |
| conversation\_id | integer |                 |
| file\_url        | string  |                 |
| operator\_id     | integer | Default - Admin |
| disable\_webhook | integer | Default - 0     |

{% tabs %}
{% tab title="200 " %}

```
{
    "status": 200,
    "data": {
        "id": 178,
        "from_blinger_user_id": 4,
        "to_blinger_user_id": 5,
        "blinger_message_id": 178,
        "application": "livechat",
        "type": "image",
        "message": "https://static-api.blinger.io/files/new/67/cf/67cf7f4783de908d9723696d295c5252_5e60f6d59964e.png",
        "date_updated": 1560188469,
        "date_created": 1560188469,
        "is_outgoing": true,
        "status": "sent",
        "is_inner_message": false,
        "date_read": null,
        "date_real": 15601884680000,
        "error": null,
        "is_history": false,
        "echo": false,
        "echo_outgoing": false
    }
}
```

{% endtab %}

{% tab title="400 " %}

```
{
    "error": "file_url is empty",
    "status": 400
}
```

{% endtab %}
{% endtabs %}

## Send note

<mark style="color:green;">`POST`</mark> `https://app.blinger.io/api/conversations/send-note`

#### Path Parameters

| Name           | Type   | Description          |
| -------------- | ------ | -------------------- |
| Authentication | string | Authentication token |

#### Request Body

| Name             | Type    | Description     |
| ---------------- | ------- | --------------- |
| operator\_id     | integer | Default - Admin |
| text             | string  |                 |
| conversation\_id | integer |                 |

{% tabs %}
{% tab title="200 " %}

```
{
    "status": 200,
    "data": {
        "id": 178,
        "from_blinger_user_id": 4,
        "to_blinger_user_id": 5,
        "blinger_message_id": null,
        "application": "livechat",
        "type": "text",
        "message": "My private note",
        "date_updated": 1560188469,
        "date_created": 1560188469,
        "is_outgoing": true,
        "status": "sent",
        "is_inner_message": true,
        "date_read": null,
        "date_real": 15601884680000,
        "error": null,
        "is_history": false,
        "echo": false,
        "echo_outgoing": false
    }
}
```

{% endtab %}
{% endtabs %}

## Get unassigned conversations

<mark style="color:blue;">`GET`</mark> `https://app.blinger.io/api/conversations/unassigned`

This endpoint allows you to get unassigned conversations. Conversations are sorted by date updated in descending order (limit 1000).

#### Path Parameters

| Name      | Type    | Description |
| --------- | ------- | ----------- |
| group\_id | integer |             |

{% tabs %}
{% tab title="200 " %}

```
{
    "status": 200,
    "data": [
        {
            "id": 300,
            "group_id": 21,
            "status": "unassigned",
            "application": "livechat",
            "from_blinger_user_id": 2,
            "from_user_name": "LiveChat client #2",
            "is_new_conversation": true,
            "unassigned_date": 1563894618,
            "custom_name": "John Doe"
        }
    ]
}
```

{% endtab %}
{% endtabs %}

## Get unread conversations

<mark style="color:blue;">`GET`</mark> `https://app.blinger.io/api/conversations/unread`

This endpoint allows you to get unread conversations with status "inbox" for a specific operator. Conversations are sorted by date updated in descending order (limit 1000).

#### Path Parameters

| Name         | Type    | Description |
| ------------ | ------- | ----------- |
| operator\_id | integer |             |
| group\_id    | integer |             |

{% tabs %}
{% tab title="200 " %}

```
{
    "status": 200,
    "data": [
        {
            "id": 300,
            "group_id": 21,
            "operator_user_id": 18,
            "status": "inbox",
            "application": "livechat",
            "from_blinger_user_id": 2,
            "from_user_name": "LiveChat client #2",
            "is_new_conversation": false,
            "unread_count": 2,
            "last_message_date": 1563895196,
            "custom_name": "John Doe",
            "operator_email": "operator@gmail.com"
        }
    ]
}
```

{% endtab %}
{% endtabs %}

## Get not answered conversations

<mark style="color:blue;">`GET`</mark> `https://app.blinger.io/api/conversations/not-answered`

This endpoint allows you to get not answered conversations with status "inbox" for a specific operator. Conversations are sorted by date updated in descending order (limit 1000).

#### Path Parameters

| Name         | Type    | Description |
| ------------ | ------- | ----------- |
| operator\_id | integer |             |
| group\_id    | integer |             |

{% tabs %}
{% tab title="200 " %}

```
{
    "status": 200,
    "data": [
        {
            "id": 300,
            "group_id": 21,
            "operator_user_id": 18,
            "status": "inbox",
            "application": "livechat",
            "from_blinger_user_id": 2,
            "from_user_name": "LiveChat client #2",
            "is_new_conversation": false,
            "unread_count": 0,
            "last_message_date": 1563895196,
            "custom_name": "John Doe",
            "operator_email": "operator@gmail.com"
        }
    ]
}
```

{% endtab %}
{% endtabs %}

## Get conversation by ID

<mark style="color:blue;">`GET`</mark> `https://app.blinger.io/api/conversations/get`

This endpoint allows you to get conversation info by **ID**

#### Query Parameters

| Name                                               | Type    | Description |
| -------------------------------------------------- | ------- | ----------- |
| conversation\_id<mark style="color:red;">\*</mark> | integer |             |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "status": 200,
    "data": {
        "conversation_id": 5867,
        "operator_id": 457,
        "from_blinger_user_id": 12654,
        "to_blinger_user_id": 64456,
        "from_user": {
            "id": 10,
            "service_blinger_id": 2,
            "blinger_user_id": 12654,
            "is_active": true,
            "date_updated": 1634559429,
            "date_created": 1634559429,
            "tags": null,
            "name": "Alex",
            "role": "default",
            "avatar": null,
            "application": "telegrambot",
            "service_user_id": "253560468",
            "status": "enabled",
            "group_id": null,
            "is_comments": null,
            "page_url": null,
            "page_title": null,
            "extra_fields": null,
            "extra_field_secret_key": "7YCH_DHyQIHsMB1rfuQM85tgbFX3Qrfq",
            "custom_name": null,
            "dialog_id": null,
            "comments_group_id": null,
            "phone": "+37529576375",
            "service_user_nickname": "alex"
        },
        "to_user": {
            "id": 44,
            "service_blinger_id": 2,
            "blinger_user_id": 64456,
            "is_active": true,
            "date_updated": 1635854447,
            "date_created": 1635854447,
            "tags": null,
            "name": null,
            "role": "customer",
            "avatar": null,
            "application": "telegrambot",
            "service_user_id": null,
            "status": "enabled",
            "group_id": null,
            "is_comments": null,
            "page_url": null,
            "page_title": null,
            "extra_fields": null,
            "extra_field_secret_key": "TSrwT2DvVJZFX9nJu3AQEcCFVMxQa3P4",
            "custom_name": null,
            "dialog_id": null,
            "comments_group_id": null,
            "phone": null,
            "service_user_nickname": null
        },
        "application": "telegrambot",
        "status": "inbox",
        "date_created": 1635856462,
        "date_updated": 1643971557,
        "messages": [
            {
                "id": 7532,
                "message": "/start",
                "type": "text",
                "date_created": 1635856462
            },
            {
                "id": 7543,
                "message": "Hello, can I help you?",
                "type": "text",
                "date_created": 1635856464,
                "operator_id": 457
            },
            {
                "id": 8634,
                "message": "Hello!",
                "type": "text",
                "date_created": 1635863152
            }
        ]
    }
}
```

{% endtab %}
{% endtabs %}


# Operator

## Get operators

<mark style="color:blue;">`GET`</mark> `https://app.blinger.io/api/operators/all`

This endpoint allows you to get operators.

#### Headers

| Name           | Type   | Description           |
| -------------- | ------ | --------------------- |
| Authentication | string | Authentication token. |

{% tabs %}
{% tab title="200 Cake successfully retrieved." %}

```javascript
{
    "status": 200,
    "data": [
        {
            "id": 1,
            "user_id": 1,
            "owner_user_id": 1,
            "invite_email": "user1@gmail.com",
            "conversations_token": "5c763415ee6c7"
        },
        {
            "id": 2,
            "user_id": 3,
            "owner_user_id": 1,
            "invite_email": "al@blinger.io",
            "conversations_token": "5cf8c80657eec"
        }
    ]
}
```

{% endtab %}

{% tab title="401 Could not find a cake matching this query." %}

```javascript
{
    "error": "Empty token",
    "status": 401
}
```

{% endtab %}
{% endtabs %}

## Get groups

<mark style="color:blue;">`GET`</mark> `https://app.blinger.io/api/operators/groups`

#### Headers

| Name           | Type   | Description          |
| -------------- | ------ | -------------------- |
| Authentication | string | Authentication token |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "status": 200,
    "data": [
        {
            "id": 1,
            "user_id": 1,
            "title": "Default",
            "priority": 1,
            "color": "#22539c",
            "is_default": true
        }
    ]
}
```

{% endtab %}

{% tab title="401 " %}

```javascript
{
    "error": "Empty token",
    "status": 401
}
```

{% endtab %}
{% endtabs %}

## Create operator

<mark style="color:green;">`POST`</mark> `https://app.blinger.io/api/operators/create`

#### Path Parameters

| Name           | Type   | Description          |
| -------------- | ------ | -------------------- |
| Authentication | string | Authentication token |

#### Request Body

| Name               | Type   | Description |
| ------------------ | ------ | ----------- |
| operator\_email    | string |             |
| operator\_password | string |             |

{% tabs %}
{% tab title="200 " %}

```
{
    "status": 200,
    "data": {
        "invite_email": "bbb@bb.bb",
        "owner_user_id": 47,
        "id": 14758,
        "user_id": 14432
    }
}
```

{% endtab %}

{% tab title="400 " %}

```
{
    "error": {
        "invite_email": "Email \"bbb@bb.bb\" has already been taken."
    },
    "status": 400
}
```

{% endtab %}
{% endtabs %}

## Delete operator

<mark style="color:green;">`POST`</mark> `https://app.blinger.io/api/operators/delete`

#### Path Parameters

| Name           | Type   | Description          |
| -------------- | ------ | -------------------- |
| Authentication | string | Authentication token |

#### Request Body

| Name         | Type    | Description |
| ------------ | ------- | ----------- |
| operator\_id | integer |             |

{% tabs %}
{% tab title="200 " %}

```
{
    "status": 200,
    "data": {
        "success": true
    }
}
```

{% endtab %}

{% tab title="400 " %}

```
{
    "error": "Operator not found",
    "status": 400
}
```

{% endtab %}
{% endtabs %}


# User

## Get user

<mark style="color:blue;">`GET`</mark> `https://app.blinger.io/api/users/get`

This endpoint allows you to get user by **ID**

#### Query Parameters

| Name                                                | Type    | Description |
| --------------------------------------------------- | ------- | ----------- |
| blinger\_user\_id<mark style="color:red;">\*</mark> | integer |             |

{% tabs %}
{% tab title="200 User successfully retrieved." %}

```javascript
{
    "status": 200,
    "data": {
        "id": 9757,
        "service_blinger_id": 2,
        "blinger_user_id": 121876,
        "is_active": true,
        "date_updated": 1643803693,
        "date_created": 1643803693,
        "tags": null,
        "name": "Alex",
        "role": "default",
        "avatar": null,
        "application": "telegrambot",
        "service_user_id": "888719349",
        "status": "enabled",
        "group_id": null,
        "is_comments": null,
        "page_url": null,
        "page_title": null,
        "extra_fields": null,
        "extra_field_secret_key": "4VQdxv9CHRzw7j7Xd0S-zx2sHtVxsck9",
        "custom_name": null,
        "dialog_id": null,
        "comments_group_id": null,
        "phone": null,
        "service_user_nickname": "alex"
    }
}
```

{% endtab %}
{% endtabs %}

## Update user

<mark style="color:green;">`POST`</mark> `https://app.blinger.io/api/users/update`

#### Query Parameters

| Name                                                | Type    | Description |
| --------------------------------------------------- | ------- | ----------- |
| blinger\_user\_id<mark style="color:red;">\*</mark> | integer |             |

#### Request Body

| Name  | Type   | Description |
| ----- | ------ | ----------- |
| name  | string |             |
| phone | string |             |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "status": 200,
    "data": {
        "id": 97,
        "service_blinger_id": 2,
        "blinger_user_id": 121973,
        "is_active": true,
        "date_updated": 1643803693,
        "date_created": 1643803693,
        "tags": null,
        "name": "Alex",
        "role": "default",
        "avatar": null,
        "application": "telegrambot",
        "service_user_id": "879739591",
        "status": "enabled",
        "group_id": null,
        "is_comments": null,
        "page_url": null,
        "page_title": null,
        "extra_fields": null,
        "extra_field_secret_key": "4VQdxv7CHRzw1j3Xd0S-zq2sHjVxsck4",
        "custom_name": null,
        "dialog_id": null,
        "comments_group_id": null,
        "phone": "35799756493",
        "service_user_nickname": "alex"
    }
}
```

{% endtab %}
{% endtabs %}


# Frequently asked questions


# About functions

## **How to configure this function?**

Click here

## **Is it possible to assign the channel to a particular agent?**

## **What will happen to the messages reassigned to another agent group, if “assign closed conversations to chosen groups”?**

All new messages will be seen in the agent group, which a customer was assigned to

{% hint style="info" %}

## **Still have questions?**

Contact Blinger support service
{% endhint %}

\
\
\
\ <br>


# Autoresponder

## **How to configure this function?**

Click [**here**](broken://pages/-LWB1J15-Q2QmfmhO8tQ)

## **Is it possible to set autoresponse up depending on language?**

Blinger.io doesn’t support this functionality

## **Is it possible to set autoresponse schedule up?**

Currently Blinger.io doesn’t support this functionality but it’s in the near future releases

## **Is it possible to send several autoresponses one by one?**

Blinger.io doesn’t support this functionality

## **“Autoresponder” doesn’t work**

Please pay attention to the mannual with the description how this functionality works. If you follow the mannual but autoresponder still doesn’t work, please, contact Blinger Customer Support

{% hint style="info" %}

## **Still have questions?**

Please contact Blinger customer support
{% endhint %}

\
\
\
\
\
\
\ <br>

\
\
\
\ <br>


# Assign channels to groups

## **How to configure this function?**

Click here

## **Is it possible to assign the channel to a particular agent?**

Yes, it can be done. The operator must be allocated to a separate group and a specific channel  should be assigned to a group.&#x20;

## **What will happen to the messages reassigned to another agent group, if “assign closed conversations to chosen groups”?**

All new messages will be seen in the agent group, which a customer was assigned t&#x6F;**.**

{% hint style="info" %}

## **Still have questions?**

Pleas&#x65;**,** contact Blinger customer support
{% endhint %}

\
\
\ <br>


# About intergrations


# Viber

### How to create a bot-channel in Viber?

#### **Step 1.** Open the[ link to Viber Admin Panel](https://partners.viber.com/login), enter the phone number, for which you have created a public-account in the messaging app, and click on "Login"

![](/files/-LEy9KjHG-g9-e_0oveC)

After that you will receive a 6-digit password to your Viber application, which you should enter within 2 minutes

![](/files/-LEy9Sblgm6XaDP4rePE)

#### Step 2. Click on «Сreate Bot Account», fill in all the necessary fields, tick the box I accept the Terms and Conditions and click on "Create"

![](/files/-LEyCvpJn9jkCgnzpGSG)

{% hint style="success" %}
**Bot-channel is created!**
{% endhint %}

{% hint style="info" %}

### Haven't found an answer to your question?

Contact Customer support of Blinger.io
{% endhint %}


# Telegram

### How to create a Telegram-bot? <a href="#telegram-bot-create" id="telegram-bot-create"></a>

#### **Step 1.** Open Telegram application and enter [@BotFather](https://t.me/BotFather) in search bar

![](/files/-LEtPxCx0-LShLa5b99E)

#### **Step 2.** Enter in message bar the following value `/newbots`&#x20;

![](/files/-LEtQXyf-sz5r2E0hJ-W)

#### **Step 3.** Enter in message bar the name for the bot being created and click on "Enter"

![](/files/-LEtQyuiyyynssElKgsU)

#### **Step 4. Enter in message bar** "Username" ("username" must be unique and end with `_bot`) and click on "Enter"

![](/files/-LEtRWIAt49eecC1TqC1)

{% hint style="success" %}
**The bot is created!**
{% endhint %}

### Can I connect a chat-bot to Blinger.io?

Yes, it is possible. To do that at the moment when the message from the chat-bot user is forwarded to Blinger.io, the server of the chat-bot would send the message to the url-address we provide in the format, in which it's sent by Telegram API. Get more information from our Customer support.

{% hint style="info" %}

### Haven't found an answer to your question?

Contact Customer support of Blinger.io
{% endhint %}


# Freshdesk

## How does Blinger and Freshdesk integration work?

The integration Blinger and Freshdesk allows you to connect any modern messaging channels (social networks, messaging apps) to your Freshdesk account, which enables you to process message requests from those channels directly in Freshdesk interface. The integration solves many questions: it provides new opportunities for working with customers in terms of sales and support, saves development costs for programming your own solution and employee training, customer data is in order,  what helps process it better.

## How to merge Blinger widget with Freshdesk web messenger?

![](/files/-LbcPBcbYFGhBFnaaHeC)

### Step 1. Place the following code before the closing tag **`</body>`**:

```markup
<!-- Add custom styles for Freshchat widget -->
<style>
    .custom_fc_frame {
        right: 100px !important;
    }
</style>

<!-- Freschat widget source. You can put it to the header html section -->
<script src="https://wchat.freshchat.com/js/widget.js"></script>

<!-- Init and customize Freshchat widget -->
<script>
    window.fcWidget.init({
        "config": {
            "headerProperty": {
                "hideChatButton": true
            },
            cssNames: {
                widget: 'custom_fc_frame',
                expanded: 'custom_fc_expanded'
            },
        },
        token: "freshchat_widget_token",
        host: "https://wchat.freshchat.com"
    });
</script>

<!-- Init and customize Blinger Widget -->
<script>
    window['blingerBeforeRender'] = function () {
        var channel = new Blinger.Channels.SimpleActionChannel();
        channel.tooltip = 'Онлайн чат';
        channel.color = '#75b145';
        channel.imageUrl = 'https://app.blinger.io/images/widget2/livechat.png';
        channel.action = function () {
            window.fcWidget.open();
        };

        Blinger.channelsWidget.addChannel(channel);
        Blinger.channelsWidget.resizeEnabled = true;
    };

    (function (d) {
        var s = d.createElement("script");
        s.async = true;
        s.charset = "utf-8";
        s.src = "https://app.blinger.io/uploads/widgets2/[Value].js";
        d.head.appendChild(s);
    })(window.document);
</script>
```

### Step 2. Replace **`token: "freshchat_widget_token"`** (line 23) with the token from your Freshchat account (path: Settings > Web Messenger)

![](/files/-LbcQJBMlT7XBxc3Rvwr)

### Step 3. Define in the line the necessary widget's number instead of `[Value]`

```
  s.src = "https://app.blinger.io/uploads/widgets2/[Value].js"
```

{% hint style="warning" %}
The necessary widget's number can be found after the value "Widget #", if you login to your Blinger administrator's account and proceed to "Widget" module
{% endhint %}

{% hint style="info" %}
**Useful**

Color and caption for Freshdesk online-chat button can be defined using parameters\
**`channel.tooltip = 'Live chat'`** и **`channel.color = '#75b145'`**&#x61;ccordingly.
{% endhint %}

## Is it possible to edit the name in Freshdesk customer profile, which was created upon getting a message request via the integration with Blinger?

Yes, it's possible. Besides, you can merge profiles, if the customer contacted you in different channels (you can understand that with the help of tags), but if you want to continue communication with the customer you need to reopen the last message request (ticket) in the corresponding channel and continue responding in that channel. **You can't create a message request via "New Ticket"!**<br>

## What will happen, if the customer sent a new message request via the integration with Blinger, but his previous message request had been closed?

A new message request will be created. This is the default setting. If there is a need to continue the conversation in the initially created message request, then you should activate the option "Reopen ticket" in the integration's settings in your Blinger admin.

![](/files/-LbcY4lifnUDKRSJwSOX)

{% hint style="info" %}
**Didn't find an answer to your question?**

Contact Blinger Support Center
{% endhint %}


# Zendesk

## How to merge Blinger widget with Zendesk live-chat?

![](/files/-LbSs1YLtHRx9mk7zBm_)

Step 1. Place the following code before the closing tag `</body>`:

```markup
<!-- Zendesk widget source -->
<script id="ze-snippet" src="https://static.zdassets.com/ekr/snippet.js?key=[your_zendesk_key]"> </script>

<!-- Init and customize Freshchat widget -->
<script>
    window.zESettings = {
        webWidget: {
            offset: {
                horizontal: '100px'
            },
        },
    };

    zE('webWidget:on', 'close', function() {
        zE('webWidget', 'hide');
    });
</script>

<!-- Init and customize Blinger Widget -->
<script>
    var showBlinger = function () {
        if (typeof Blinger !== 'undefined' && !Blinger.launcherWidget.isOpen) {
            document.getElementById('blinger-launcher-iframe').style.display = 'block';
        }
    };

    window['blingerBeforeRender'] = function () {
        var channel = new Blinger.Channels.SimpleActionChannel();
        channel.tooltip = 'Livechat';
        channel.color = '#75b145';
        channel.imageUrl = 'https://app.blinger.io/images/widget2/livechat.png';
        channel.action = function () {
            zE('webWidget', 'show');
            zE('webWidget', 'open');
        };

        Blinger.channelsWidget.addChannel(channel);
        Blinger.channelsWidget.resizeEnabled = true;
    };

    window['blingerInit'] = function () {
        document.getElementById('blinger-launcher-iframe').style.display = 'none';
    };

    var count = 0;
    var waitForZEWidgetloading = function () {
        var zEwidgetDisplay = zE('webWidget:get', 'display');

        if (zEwidgetDisplay === 'launcher') {
            var element = document.getElementById("launcher");
            element.parentNode.removeChild(element);
            showBlinger();
        } else {
            if (count < 20) {
                setTimeout(function () {
                    waitForZEWidgetloading();
                }, 300);
                count++;
            }
        }
    };

    waitForZEWidgetloading();

    (function (d) {
        var s = d.createElement("script");
        s.async = true;
        s.charset = "utf-8";
        s.src = "https://app.blinger.io/uploads/widgets2/[Value].js";
        d.head.appendChild(s);
    })(window.document);
</script>
```

Step 2. Insert widget's token from your Zendesk admin instead of `[your_zendesk_key]`.

```markup
<script id="ze-snippet" src="https://static.zdassets.com/ekr/snippet.js?key=[your_zendesk_key]"> </script>
```

{% hint style="info" %}
You can find widget's token in: **Admin > Widget > "Setup" tab**\
Token value goes after "key="
{% endhint %}

Step 3. Define the necessary number of the widget instead of `[Value]`.

```
 s.src = "https://app.blinger.io/uploads/widgets2/[Value].js"
```

{% hint style="info" %}
You can find the number of the widget you need after the value "Widget #", if you login to the administrator's account in Blinger and proceed to Widget module
{% endhint %}

{% hint style="info" %}
**Useful!**

The color and caption of Zendesk online-chat button can be defined using parameters **`channel.tooltip = 'Online chat'`**` ``and` **`channel.color = '#75b145'`**&#x61;ccordingly.
{% endhint %}


# WhatsApp

## How to integrate **WhatsApp (WhatsApp Business)?**

See WhatsApp integration manual :point\_right: [**here**](broken://pages/-LIqhw0wCXloyWC0qbHx). There are some integration related specifics, which require additional control of its functionality. See below :point\_down:&#x20;

{% hint style="warning" %}

## **Working principles:**

**Stable integration tips:**

* Use Android/iOS smartphone for integration
* Smartphone have to charge constantly
* Smartphone must have stable Internet (3G/Wi-Fi) connection
* Disable "Low Power Mode"
* Add WhatsApp application to exceptions of "Low Power Mode"

:question: **How to disable "Low Power Mode" on a smartphone (Android/iOS)?**
{% endhint %}

|          **iOS**          |                   Android OS                  |
| :-----------------------: | :-------------------------------------------: |
| Settings > Low Power Mode | Settings > Device Maintenance > Battery > Off |

{% hint style="info" %}

## **Our experience:**

**For WhatsApp integration we use:**

* Samsung A3 (2016)
* iPhone 4s

**Results:**

These devices work stably. 5-6 disconnection episodes may happen during the day, but connection restores within 15-20 seconds automatically. We recommend using 3G connection (if it works stably in your location). The frequency of disconnection is much lower compared to Wi-Fi.

**Photo:**

![](/files/-LUdReRE5jA6hCmbCa8D)
{% endhint %}

## WhatsApp messages aren't delivered?

### 1. If you get the notification: “Connection with WhatsApp has been lost...”.

![](/files/-LUaIioQLvX3_n-nA_hg)

See below and :point\_right: [**click here**](/faq-1/faq/messaging-channels/faq-on-whatsapp#see-a-notification-the-connection-with-whatsapp-has-been-lost).

### 2. If you don’t get the notification: “Connection with WhatsApp has been lost...” make sure you haven’t connected WhatsApp with Blinger account before.

#### Have you ever added WhatsApp channel to Blinger accout before?

Send a message from another WhatsApp account to check.

{% hint style="info" %}
Blinger doesn’t support sending messages between WhatsApp accounts that are both connected to Blinger platform.
{% endhint %}

**I don’t get messages from other accounts?**

Please, contact Blinger Customer Support providing the e-mail address you used to sign up for Blinger and explain your issue in detail.

## **Get alert: “The connection with WhatsApp has been lost…”?**

This alert warns about that the integration with a WhatsApp has been interrupted.

{% hint style="warning" %}
WhatsApp integration restores usual in 20-30 seconds automatically.

After this the notification *“The connection with WhatsApp has been restored…”* will pop-up.

![](/files/-LUk0ni6Z7C_A6XberHx)
{% endhint %}

#### **If the connection is still lost then:**

1. Send a message from another WhatsApp account to the one connected to Blinger. If the connection is still lost (disconnection message keeps popping up) proceed with the next step.
2. Open WhatsApp on the smartphone used for the integration and try to edit “Menu” settings to be sure the app works properly. If the connection is still lost (disconnection message keeps popping up) proceed with the next step.
3. Log in to Blinger system through an admin-account, click “Apps” and delete WhatsApp channel. Open WhatsApp on the smartphone and click “Log out from all devices”. Follow the link :point\_right: **“WhatsApp - step 4”** to repeat WhatsApp integration.

{% hint style="warning" %}

#### If messages are still not getting delivered?

Please, contact Blinger Customer Support providing the e-mail address you used to sign up for Blinger and explain your issue in detail
{% endhint %}

## **Get “Error” notification when trying to delete WhatsApp integration?**

Please, contact Blinger Customer Support providing the e-mail address you used to sign up for Blinger and explain your issue in detail.

## **Get “Error” notification when trying to add WhatsApp integration?**

![](/files/-LUfA6UYcchHx4wJ6HtT)

You used up the number of slots for adding social networks and messengers. Blinger provides you with 1 channel package by default. Learn more: <https://blinger.io/pricing>. Please contact Blinger Customer Support to increase the number of slots.

## **Nothing happens after QR-code scanning?**

Please, contact Blinger Customer Support providing the e-mail address you used to sign up for Blinger and explain your issue in detail.

{% hint style="info" %}
Blinger allows to connect only one WhatsApp number to one Blinger account.
{% endhint %}

## **QR-code doesn’t load?**

Please, contact Blinger Customer Support providing the e-mail address you used to sign up for Blinger and explain your issue in detail.

## **What file formats does integration support?**

| **Customer** | Company |
| :----------: | :-----: |
|    Images    |   All   |

{% hint style="warning" %}
The message sent from a customer: `“ptt audio/ogg; codecs=opus”` means that currently Blinger doesn’t support audio format files.
{% endhint %}

{% hint style="info" %}
Soon we will increase the number of format files that will be able to sen&#x64;**.**
{% endhint %}

## **Is it possible to create one WhatsApp account on two smartphones (one without a SIM card)?**

Sure. It’s a good solution when one smartphone is for integration and another one - for business.

## **Is it possible to fetch the messages that customers sent during disconnection?**

Yes, it's possible.

## **Is it possible to initiate a dialogue with a customer?**

Please, contact Blinger Customer Support providing the e-mail address you used to sign up for Blinger and explain your issue in detail.

{% hint style="info" %}

## **Still have questions?**

Please contact Blinger customer support
{% endhint %}


# Widget

## Is it possible to change a location of the widget?

Sure. Necessary js-code is below:&#x20;

```javascript
<script>
window['blingerInit'] = function () {
var newStyles = "#blinger-launcher-iframe {bottom: 40px !important;}.blinger-channels-iframe{bottom: 136px !important;}";
newStyles = newStyles + ".blinger-channels-iframe.blinger-channels-iframe-mobile {bottom: 160px !important;}.blinger-invitation-iframe {bottom: 130px !important;}";
newStyles = newStyles + "@keyframes blinger-channels-desktop-show{0%{bottom:70px;opacity:0;}100%{bottom:136px;opacity:1;}}";
newStyles = newStyles + "@keyframes blinger-channels-desktop-hide{0%{bottom:136px;opacity:1;}100%{bottom:70px;opacity:0;}}";
$( "<style>" + newStyles + "</style>" ).appendTo( "body" )
};
</script>
```

It allow changing a location of the widget vertically. Change value of `bottom`

## Is it possible to place the widget under a custom button?&#x20;

Yes, it is possible. You should place the following code under the widget's code:

```javascript
<script>
    window['blingerInit'] = function () {
        document.getElementById('blinger-launcher-iframe').style.display = 'none';
    };

    var showBlinger = function () {
        if (typeof Blinger !== 'undefined' && !Blinger.launcherWidget.isOpen) {
            Blinger.launcherWidget.onLaunchButtonClick();
        }
    };

    var hideBlinger = function () {
        if (typeof Blinger !== 'undefined' && Blinger.launcherWidget.isOpen) {
            Blinger.launcherWidget.onLaunchButtonClick();
        }
    };
</script>
```

The function `showBlinger` is responsible for display of a channel (list of channels), the function `hideBlinger` hides the list.&#x20;


# Changelog

Be sure not to miss out on new features and improvements!

## Our Telegram-channel

👷 Improved “Search” function. Details are below:

* You will see search results if you enter 3 and more symbols in the “Search” field
* Now "Search" function works from anywhere.  Previously, it worked only from the beginning of the word.
* Now you are able to search by user name. Previously, only by phone number in case of WhatsApp integration.
* Now you can searching for the whole phrase, for example, “Good afternoon”.
* Improved ranking of search results.
* New messages are indexed within 1 minute. Thus, searching for these messages will begin immediately.

## October 4, 2019 - v.1.0.4019

👷 Added a field for notes in client profile. If you wish to add additional information about the client, you can do that by clicking on the client's logo.

![](/files/-LqLowO3VfgJsqPE8uZ9)

## September 27, 2019 - v.1.0.3919

:construction\_worker:Now upon registration or login attempt to Blinger.io the occasional spaces at the beginning or at the end won't have an effect upon the action being performed

:construction\_worker: Now the operators are able to see the activity statuses (online/offline) of each other. It's a very useful "feature", when you need to re-assign a conversation to another operator. The activity statuses of the operators are available in:

* menu for reassignment of a conversation
* filter by operators
* tab "All conversations"

![](/files/-Lpn5zAK6rt3j36wkeP8)

:construction\_worker:Added in Live chat a "Send" button, before you could send a message only by pressing "Enter"

![](/files/-Lpn8CC-Qmyoe4mm3Aky)

:lady\_beetle:Fixed a bug, due to which in the account of  Super-administrator a second Super-Administrator account appeared. It used to happen when the first Super-Administrator invited a new operator in the account, while the invited operator registered in Blinger.io bypassing the link from the e-mail.

:lady\_beetle: Fixed a bug with the invitation window in the widget, before this moment it used to have a square shape

## September 5, 2019 - v.1.0.3619

:robot: Developed a filter by operators in "Conversations" tab, which will be convenient for the administrator or supervisor of customer support to filter the conversations real-time, by selecting a specific operator from the list. Documentation is available at the following link: <https://help.blinger.io/documentation/conversations/conversation-filter>

:robot: Developed assignment of conversations with a customer to a specific operator. As in some companies customers are assigned to specific managers. If the customer contacts the company, the message request gets assigned to a specific operator. Hence, the customer always knows who to contact if questions arise. Documentation is available at the following link: <https://help.blinger.io/documentation/conversations/end-user-assignment-to-an-operator>

## July 30, 2019 - v.1.0.3119

:man\_construction\_worker: Developed an option, which lets you set up the sequence of message requests display (in "Unassigned" section) and messages (in "My inbox" section). The option can be defined in "Settings" section, tab "General". For example, if you activate "Start from old messages in "Unassigned" tab", message requests will be displayed from old to new depending on the time when they were received. It's convenient to use this option to sort out through the message requests which were in the queue for the longest time.

:robot: Developed the function "IP address whitelist", which lets you whitelist specific IP-addresses to access Blinger.io. This option can be defined in "Settings" section , tab "Advanced" (contact Customer Support to access it).

:robot: Developed the function "Block send/receive files", which lets you disable the option to receive files from users and send them to the agents. This option can be defined in "Settings" section, tab "Advanced" (contact Customer Support to access it).

:robot: Developed the function "Action log", which displays a list of all actions, performed by the administrator or the agents. This option can be defined in "Settings" section, tab "Advanced" (contact Customer Support to access it).

:robot: Developed the function "Hide personal data", which lets you hide contact information of the users. This option can be defined in "Settings" section, tab "Advanced" (contact Customer Support to access it).

:robot: Developed the function "Email whitelist for downloading conversations", which lets you export the conversations with users only to specific e-mail addresses. This option can be defined in "Settings" section, tab "Advanced" (contact Customer Support to access it).

:man\_construction\_worker: Now the function "Manage Webhooks" is in direct access, it lets you access the management panel to define the address for receiving webhooks. This option can be defined in "Settings" section, tab "Advanced" (contact Customer Support to access it).

:man\_construction\_worker: Now the function "Iframe integration" is in direct access, it enables you to set up the integration of Blinger.io with a third-party service using iframe (API alternative). This option can be defined in "Settings" section, tab "Advanced" (contact Customer Support to access it).

:man\_construction\_worker: Changed the location of Blinger.io interface language settings. Now you can change the default interface language in "Profile" section.

## June 21, 2019 - v.1.0.2519

:mega: On March 27 of this year we developed the "Custom App" integration (it can be found in "Apps" module). Custom app lets you, for example, connect your chatbots, 3rd party online-chats (for example, from a mobile app), and etc. This week Blinger.io together with Spotware Systems Ltd. (an award-winning fintech company which develops software for brokers) released an integration with their cTrader Live Chat on the base of Custom App, which allows to add cTrader Live Chat as one of the channels at Blinger.io. What's the purpose of the integration? Now every trader on cTrader platform can contact his broker directly from the platform's terminal, while every broker can offer their customers multiple channels via which the traders can contact them and unify all the message requests in one interface of Blinger.io.

:lady\_beetle: Fixed a bug in Twitter integration functionality - direct messages weren't functioning properly.

:lady\_beetle: Fixed a bug which didn't let make changes to the autoresponder settings from a regular account, which had settings management permissions.

:lady\_beetle: Fixed a bug with deletion of an agent - when deleting an agent there were 2 messages displayed (about successful deletion and about being unable to delete the account).

## June 13, 2019 - v.1.0.2419

:robot: Made messaging API a part of our interface (which wasn't the case before :slight\_frown:). It will allow to connect to Blinger.io third-party solutions, for example, universal chat bots (another name "IVR-bots") or  integrate any SaaS solution with Blinger.io, in which you need to realize the possibility of customer support in messaging apps, social networks, e-mail or live chat. Examples of such integrations, which we realized ourselves: Zendesk, Freshdesk, Intercom, Kayako and etc. Messaging API documentation is available at the following [**link**](https://help.blinger.io/settings/integrations-1/api).

:man\_construction\_worker: Improved integration with Freshdesk. Now in the Subject of a message request a part of the first message of the message request is displayed. Before in the Subject was displayed, for example, the following text "New conversation #\[number]".

:man\_construction\_worker: Improved stability of the integration with WhatsApp.

:man\_construction\_worker: Changed the time format in messages. Before, if a message was sent within 24 hours, it had the following time format: "13 hours ago". Now the format looks as follows: "13 June 2019, 15:34:16".

:lady\_beetle: Fixed a bug with display of edited end-user name. There was the following error before - the edited name was displayed in all Blinger.io accounts in which the end-user had written via one of the channels.

:lady\_beetle: Fixed a bug with incorrect display of agent's name. The agent used to see the e-mail of super administrator in conversations with the customer, who sent a message a message request via WhatsApp.

:lady\_beetle: Fixed a bug when a new agent didn't see new messages, the ones that were displayed in Unassigned section.

:lady\_beetle: Fixed a bug with incorrect display of parameter "The oldest unassigned conversation" in dashboard.

:lady\_beetle: Fixed a bug with search issues when searching edited names.

## April 25, 2019 - v.1.0.1719

:man\_construction\_worker: Implemented the possibility to edit contact name field. It's helpful in case when client name in your system, CRM for example, is different from the one in WhatsApp, Telegram and etc.

:man\_construction\_worker: When initializing a conversation with a customer in WhatsApp (*our premium feature*), now you can define the name for the customer beforehand. Before you only had the opportunity to provide the phone number and message text.

:man\_construction\_worker: You can initialize a conversation with a customer, in case when he has WhatsApp installed, directly from your CRM, it's sufficient to set up calling our service for outgoing messages from the third party solution, while the conversation will be assigned to the manager, who initializes the conversation. Important: all phone numbers of your customers are encrypted when transferred into our solution.

:lady\_beetle: Fixed a bug which didn't let to send text with emoji when pressing (instead of "Send" button) Ctrl+Enter (Win PC) or Cmd+Enter (MacOS). The message was sent without smileys instead.

:man\_construction\_worker: Implemented the possibility to integrate Blinger as an iframe. Contact our Customer Support for additional information.

:man\_construction\_worker: Implemented the possibility to hide personal data from agents (phone numbers, direct links to customer profiles). Contact our Customer Support for additional information.

## April 18, 2019 - v.1.0.1619

:lady\_beetle: Fixed a bug with disappearing of the button "Load more messages", when there were more than 20 conversations in "My inbox" section.

:man\_construction\_worker: Developed pagination of conversations and messages, which improves the process of conversations/messages navigation, especially it can be noticed with a large amount of conversations/messages.

:lady\_beetle: Fixed a bug with selecting statuses "Inbox" or "Closed" in "All conversations" section and then clicking on "Load more messages" in conversations list to load more conversations. The filter broke at that step and showed all conversations with all statuses (e.g. "Inbox" and "Closed").

## April 4, 2019 - v.1.0.1419/1

:robot: Freshdesk integration has been developed. The integration Blinger and Freshdesk allows you to connect any modern messaging channels (social networks, messaging apps) to your Freshdesk account, which enables you to process message requests from those channels directly in Freshdesk interface. The integration solves many questions: it provides new opportunities for working with customers in terms of sales and support, saves development costs for programming your own solution and employee training, customer data is in order,  what helps process it better.

How to setup? [**Link**](https://help.blinger.io/settings/integrations-1/integrations/freshdesk)\
FAQ? [**Link**](https://help.blinger.io/faq/messaging-channels/freshdesk)

![](/files/-Lbc_aQWGBPoLhGexVvx)

:lady\_beetle: Fixed a bug with outgoing WhatsApp messages: when sending the first message to the customer, the default group was not selected and the conversation wasn't assigned to the agent, who initiated the outgoing message.

## April 2, 2019 - v.1.0.1419

:man\_construction\_worker: Described how to add Zendesk online-chat in our widget - link [**here**](https://help.blinger.io/faq/messaging-channels/zendesk)**.**

![](/files/-LbT7QBZhmeiTC3MYNgc)

:lady\_beetle: Fixed a bug with incorrect display of the agent's name: often instead of the name of the agent administrator's e-mail was displayed.

:lady\_beetle: Fixed a bug with adding WhatsApp integration: there was a problem with adding a WhatsApp account in case when messages had been sent before from the number to the number which had already been added in Blinger.

:lady\_beetle: Fixed a bug with Twitter functionality: the messages were not delivered in Blinger in case when the account from which the messages were sent had been added as an integration before or is added at present in Blinger account.

## March 27, 2019 - v.1.0.1319

:robot: Custom App integration has been developed (details at the following [**link**](https://help.blinger.io/settings/integrations-1/channels/custom-app)). Custom app is useful, if there is a need to integrate your own/third party online-chat, chat in a mobile application, chatbots in messaging apps with the following framework: **"messaging app - chatbot - blinger"**, in order to have an opportunity to process message requests from customers in a unified workspace.

{% hint style="info" %}
**Use case:**

Our partner (a big fintech company) has customers, who use their solution, and the partner integrated online-chat, to support their customers directly from the interface of the solution. We have common clients with the partner, so it has been decided to develop a Custom App, to be able to process message requests from the third-party online chat in Blinger interface. This way we combined all message requests in a unified workspace, thus having improved productivity of support agents.
{% endhint %}

## March 14, 2019 - v.1.0.0919

:man\_construction\_worker: Improved WhatsApp integration. Fixed a bug with fetching the message requests, which were sent by clients during WhatsApp disconnect and were not being delivered in Blinger.io interface.

## March 13, 2019 - v.1.0.0919

:robot: **Analytics** module has been updated. Now it has become more informative.

Added in the module:

* **Dashboard** - helps to get a current day information snapshot for employees' work.

Updated in the module:

* **Conversations analytics** - improved processed message requests analytics, added information on the time of a message request resolution and reaction on it, the total amount of messages and separately for the operators and clients is displayed, revised analytics of themes of message requests, besides added ranking of data depending on work time and time off of support team.
* **Clients analytics** - improved analytics for the following data: how many clients sent message requests in all time, for the specified time period, how many were new, added coefficient of recurring requests, and data on the channels of inbound clients.
* **Operators analytics** - improved operators analytics, specifically how many message requests was processed by each operator, how fast they were processed, how fast was the first reaction to the message request and how much time was sent on it in total.
* **Tags analytics** - improved tags analytics interface, now it contains a visual component and convenient tags navigation and switching to those message requests, in which messages were tagged.

## January 22, 2019 - v.1.0.0419

:man\_construction\_worker: Possibility to assign conversations to the system administrator added

:man\_construction\_worker: Toolbar design changed, online-chat added as a separate button, improved navigation to account settings, Help-center and Changelog added as a separate button

:man\_construction\_worker: Changed agent's message display method in the navigation window among conversations

:lady\_beetle: Fixed a bug (error: *Integrity constraint violation #23505*), which appeared in the process of new account registration as per administrator's invitation

:lady\_beetle: Fixed a bug, which didn't let highlight a word when searching for it

:lady\_beetle: Fixed a bug with adding themes

:lady\_beetle: Fixed a bug with popping up phrase in the widget

:lady\_beetle: Fixed a bug with scrolling effect when opening the widget

:lady\_beetle: New messages push-notifications' work restored

:lady\_beetle: Fixed a bug with displaying of the amount of conversations in "Unassigned", "My inbox",  at the moment when the account was in one of the groups and had role "Conversations management"

:lady\_beetle: Fixed a bug with a long response time of the message selection button

## January 15, 2019 - v.1.0.0319

:man\_construction\_worker: Parameter `"tags"`added in Outgoing message, Incoming message Webhooks

{% code title="Outgoing message, Incoming message" %}

```
"message":{
        "tags":["tag1", "tag2"]
    }
```

{% endcode %}

:man\_construction\_worker: Improved search in "Conversations" module: eliminated "jumping" of the search results, increased speed of search results delivery,  highlighting of search results with color

:man\_construction\_worker: Improved performance of "Conversations" module: Websocket breakage was happening due to unstable Internet connection, which required continuous page refreshes to load new messages

&#x20;:lady\_beetle: Bug fix with line spacing in "Autoresponder"

:lady\_beetle: Bug fix with sticky button when changing agent group, that started to work only after page refresh

## January 8, 2019 - v.1.0.0219

:lady\_beetle: Restored work on the delivery of images from customers via WhatsApp

## December 18, 2018 - v.1.0.5118

:man\_construction\_worker: Possibility to specify data-center region added in Twilio Chat integration&#x20;

:man\_construction\_worker: Parameter `"email"`added in Outgoing message, Incoming message, Conversation is assigned to operator Webhooks

{% code title="Outgoing message, Incoming message, Conversation is assigned to operator " %}

```
"operator":{
        "email":"agent@mail.com"
    },
```

{% endcode %}


# О приложении

## Общая информация

**Blinger.io** - это омниканальное решение, позволяющее общаться с клиентами через различные каналы в "одном окне"

![](/files/-Lm9vTTxnkEcuCfrtbr7)

**Решение поддерживает 15 интеграций:** WhatsApp, Facebook (Messenger и комментарии), Instagram (Direct), WeChat, Skype, Telegram, Viber, Вконтакте (диалоги и комментарии), Одноклассники. Line, Kik, Twitter (личные сообщения и комментарии), Twilio Chat, Email, Онлайн-чат

![](/files/-Lm9vwwmqNE0f_LAVQQx)

**Омниканальную поддержку с помощью Blinger.io можно развернуть в:** Zendesk, Intercom, Salesforce, Kayako, Bpm'online&. Для более гибкой интеграции можно использовать **API и Webhooks.**&#x20;

## Технические требования

|              |                                                                                       |
| :----------: | ------------------------------------------------------------------------------------- |
|   **Cеть:**  | Высокоскоростной интернет                                                             |
| **Браузер:** | Google Chrome, Mozilla Firefox, Opera, Safari                                         |
|  **Адрес:**  | <https://blinger.io/[> или 95.213.151.140]\(<http://95.213.151.140>),  95.213.199.157 |

{% hint style="info" %}
Не советуем использовать Internet Explorer - не позволяет работать в режиме real-time.&#x20;
{% endhint %}


# Быстрый старт

## Общая информация

Это небольшой навигатор, который расскажет, как самостоятельно настроить Blinger.io и начать в нем работать.&#x20;

Сперва необходимо определиться какие каналы (социальные сети, мессенджеры, электронная почта) вы планируете добавить. География популярности каналов общения представлена ниже:

![Подробнее по ссылке источника: https://www.messengerpeople.com/global-messenger-usage-statistics/](/files/-LozgcU_Hhy-a-fAM1kq)

Blinger.io позволяет работать с обращениями 3 путями:

* в интерфейсе Blinger.io,
* в интерфейсе одного из helpdesk/CRM-решения, [**с которыми имеется интеграция**](/russian/opisanie-raboty/integrations)**,**
* в интерфейсе стороннего решения, [**используя Blinger.io API**](/russian/opisanie-raboty/api)**,**

в зависимости от этого, ниже представлены 3 варианта "быстрых стартов".

## Работа в интерфейсе Blinger.io?

Для настройки Blinger.io выполните следующие действия:

1. Подключите свои аккаунты каналов в раздел "Приложения" ([Инструкция](/russian/opisanie-raboty/channels/dobavlenie-kanalov))
2. Добавьте операторов ([Инструкция](/russian/opisanie-raboty/razdel-operatory))
3. Разместите виджет на сайте ([Инструкция](/russian/opisanie-raboty/razdel-vidzhet))
4. Настройте автоответчик ([Инструкция](/russian/opisanie-raboty/settings/avtomaticheskii-otvet))

**Можно приступать к работе!**

{% hint style="info" %}
Перед стартом работы предлагаем ознакомиться:

* [Как работать с разделом "Диалоги"?](/russian/opisanie-raboty/dialogue)
* [Какие есть дополнительный функции?](/russian/opisanie-raboty/settings)
* [Как настроить push-уведомления о новых сообщениях?](/russian/opisanie-raboty/uvedomleniya-o-soobsheniyakh)

(ссылки кликабельны)
{% endhint %}

## Работа через готовую интеграцию?

Для настройки Blinger.io выполните следующие действия:

1. Подключите свои аккаунты каналов в раздел "Приложения" ([Инструкция](/russian/opisanie-raboty/channels/dobavlenie-kanalov))
2. Выполните интеграцию с одним из решений из списка готовых интеграций ([Инструкция](/russian/opisanie-raboty/integrations))
3. Разместите виджет на сайте ([Инструкция](/russian/opisanie-raboty/razdel-vidzhet))

**Можно приступать к работе!**

{% hint style="info" %}
Ознакомьтесь как можно объединить виджеты Blinger.io и:

* [Freshdesk](/russian/faq-1/faq/po-kanalam/freshdesk#kak-obedinit-vidzhet-blinger-c-onlain-chatom-freshchat)
* [Zendesk](/russian/faq-1/faq/po-kanalam/zendesk#kak-obedinit-vidzhet-blinger-c-onlain-chatom-zendesk)

(ссылки кликабельны)
{% endhint %}

## Работа с использованием Blinger.io API?

Для настройки Blinger.io выполните следующие действия:

1. Подключите свои аккаунты каналов в раздел "Приложения" ([Инструкция](/russian/opisanie-raboty/channels/dobavlenie-kanalov))
2. Получите Blinger.io API Token у службы поддержки
3. Выполните интеграцию со сторонним решением, используя методы API из документации ([Инструкция](/russian/opisanie-raboty/api))
4. Разместите виджет на сайте ([Инструкция](/russian/opisanie-raboty/razdel-vidzhet))

{% hint style="warning" %}
Для входящих сообщений (от клиентов) используются Webhooks, а для исходящих сообщений (от операторов) используется метод: **`Send message`**
{% endhint %}


# Кейсы клиентов

## Белавиа поддерживает клиентов только в социальных сетях и мессенджерах

**Ситуация:** Авиакомпания имела проблемы со скоростью реагирования на запросы клиентов, обращающихся через онлайн-чат. Необработанное обращение клиента быстро превращалось в “потерянное обращение”, так как клиент покидал сайт компании из-за длительного ожидания ответа (золотая середина реакции на обращение через онлайн-чат составляет 2 минуты). Компания пошла на риск - отключила онлайн-чат и оставила для поддержки клиентов каналы (соцсети мессенджеры), несмотря на то, что перед отключением 50% от всего объема текстовых обращений поступали из онлайн-чата.

**Результат:** Объем текстовых обращений после отключения онлайн-чата не изменился - он просто перераспределился в иные каналы (социальные сети, мессенджеры). Таким образом, Белавия победила “потерянные обращения”, так как точка контакта с клиентом сместилась с сайта в социальные сети и мессенджеры. В случае работы через социальные сети и мессенджеры, клиент со 100%-ой вероятностью получит ответ, открываемость таких сообщений не менее 96%. Перевод поддержки в социальные каналы позволил снизить скорость реагирования на запросы клиентов, без потери удовлетворенности качеством обслуживания (золотая середина реакции на обращение через социальные сети и мессенджеры составляет 5-10 минут). В свою очередь, это позволило физически обрабатывать все поступающие обращения со 100%-ым результатом

## KupiVip экономит деньги

**Ситуация:** Проблемой интернет-магазина KupiVip (.ru, .by, .kz) была высокая стоимость содержания телефонии, которой пользовался контакт-центр для поддержки клиентов.

**Результат:** Компания для поддержки клиентов внедрила социальные сети и мессенджеры. По результатам 6 месяцев работы, 50% телефонного трафика перетекло в социальные каналы (соцсети и мессенджеры), что позволило приблизительно наполовину сократить расходы на телефонию.

## БСБ-Банк выстоял

**Ситуация:** БСБ-Банк летом 2017 года временно потерял лицензию НБ РБ на операции с физическими лицами, что вызвало панику среди клиентов, которые в свою очередь создали максимальную нагрузку на Контакт-центр Банка. В тот день в Контакт-центр трудно было дозвониться, клиенты находились в “очереди” (знаете, когда вам робот по телефону отвечает "Ваш звонок очень важен для нас. оставайтесь на линии), тем самым создавая еще большее волнение.&#x20;

**Результат:** Исходя из сложившейся ситуации (пиковая нагрузка Контакт-центра), некоторые клиенты выбрали альтернативный канал коммуникации - социальные каналы (в тот день банк решил также отключить онлайн-чат из-за возможного эффекта “потерянных обращений”). Такая тактика позволила равномерно распределить нагрузку, обрабатывать одномоментно оператору сразу обращений клиентов, обратившихся через эти каналы, и ответить всем клиентам, которых волновал вопрос безопасности их финансовых накоплений.&#x20;

## БелВЭБ уволил компанию по SMM

**Ситуация:** БелВЭБ до внедрения Blinger.io поддержку клиентов в социальных каналах самостоятельно не оказывал. Этим занималась сторонняя компания, которая оказывала им также SMM-услуги. От этого страдало качество консультаций по услугам банка (качество ответа и скорость).

**Результат:** Посредством решения Blinger.io, поддержка клиентов в данных каналах перешла в контакт-центр банка, что позволило соблюдать стандарты обслуживания клиентов, принятые банком, и, в конечном итоге, повысить удовлетворенность клиентов. Компания по SMM была “уволена”. Похожий кейс решен с Газпромбанком.

## Мультиязычная поддержка в RoboForex и Exness

**Ситуация:** Все форекс-брокеры щепетильно относятся к качеству поддержки клиентов и стараются всегда находится с ними в тесном контакте. Многие брокеры работают с клиентами по всему миру. И чтобы улучшить уровень обслуживания, некоторые принимают решение начать оказывать поддержку в социальных каналах. Основной задачей RoboForex и Exness было распределить обращения через мессенджеры на отдельные языковые группы операторов - английский, испанский, немецкий и китайский.

**Результат:** Гибкие настройки решения Blinger.io позволили в авто-режиме распределять обращения на конкретную языковую группу операторов, что позволило еще быстрее  обрабатывать вопросы клиентов.

## В Teztour офисы продаж = контакт-центр

**Ситуация:** Проблемой компании было отсутствие быстрой и эффективной маршрутизации клиента, приходящего из социальных каналов самой компании  Teztour, который хотел приобрести тур или уже приобрел, но имеет вопросы. Важно, что компания Teztour является туристическим оператором и самостоятельно не продает туры, только через своих агентов.&#x20;

**Результат:** Компания получила возможность подключить к Blinger.io все офисы продаж агентов, конвертировать каждое обращение из соц.сетей в лида и быстро маршрутизировать их на ближайший для клиента офис продаж. Второе преимущество - таким подходом, TezTour создал децентрализованный контакт-центр из агентских офисов продаж.

## МТБанк и 2 линии поддержки&#x20;

**Ситуация:** МТБанк один из первых в Беларуси начал использовать Blinger.io для поддержки клиентов через мессенджеры и соцсети. Изначально через эти каналы осуществлялись только консультационные услуги Контакт-центром банка (оформление банковских карт, кредитов, депозитов).

**Результат:** Через год работы с Blinger.io банк принял решение масштабировать сервис и создал на базе Blinger.io поддержкe клиентов полного цикла (front- и middle-офис). Т.е. 1-я линия - Контакт-центр банка, 2-я линия - передача его на офис продаж, решение вопросов действующих клиентов (например, технические вопросы).

## Яндекс.Такси внедрила омниканальность в Zendesk

**Ситуация:** Яндекс.Такси получает более 1000 обращений в день от водителей разной направленности. Каналом связи c компанией водители выбрали WhatsApp. Яндекс.Такси предоставил единый номер, по которому водители могли обращаться. Операторы службы поддержки обрабатывали их непосредственно в интерфейсе WhatsApp Web, что доставляло компании ряд неудобств: физически трудно обработать данные обращения одному оператору (WhatsApp Web можно авторизовать только на 1 устройстве), такие обращения трудно регламентировать под SLA.&#x20;

**Результат:** Компания обратилась к Blinger.io, так как у решения есть интеграции с WhatsApp и Zendesk Support - helpdesk-решение, используемое Яндекс.Такси. Компания смогла развернуть в Zendesk Support, где основным каналом коммуникации является  электронная почта, омниканальный модуль от Blinger.io, c помощью которого подключила номер WhatsApp для связи с водителями. Все обращения от них стали преобразовываться в привычные для операторов тикеты и обрабатываться по SLA, принятом в компании. По итогу, Яндекс.Такси смог подключить больше операторов на поддержку через WhatsApp и сделать работу с обращениями прозрачной.&#x20;

## СОВКОМБАНК поддерживают мобильных менеджеров через мессенджеры

**Ситуация:** Один из крупнейших банков России - СОВКОМБАНК - имел сложность работы с мобильными менеджерами. Высокая текучка данной группы сотрудников мешала решению проблемы низкого качества знаний продуктов банка.&#x20;

**Результат:** Банк выделил группу поддержки для решения вопросов, поступивших от данных менеджеров. Основным каналом коммуникации стал WhatsApp. Теперь мобильный менеджер СОВКОМБАНКа может в любое время обратиться в службу поддержки через единый номер WhatsApp, а операторы получают все обращения в единый интерфейс Blinger.io. Большой плюс такой коммуникации в том, что и операторы и менеджеры могут обмениваться между собой иными типами контента, что во многом упрощает коммуникацию. Ну и конечно недостаток уровня знаний продуктов у мобильных менеджеров компенсируется за счет квалифицированной службы  поддержки головного офиса банка.

## **Рекрутеры** Profi.ru нанимают сотрудников через мессенджеры&#x20;

**Ситуация:** Компания Profi.ru активно занимается поиском квалифицированных сотрудников для различных проектов. Ранее рекрутеры использовали телефон для прозвона, однако это отнимало много времени, в случае если кандидат поднимал трубку не с первого раза.

**Результат:** Компания подключила WhatsApp номер и активировала в Blinger.io возможность делать исходящие сообщения кандидатам с предложением вакансии. В таком случае, компания изменила бизнес-процесс: прозвон, в случае неответа, исходящее сообщение с номера Profi.ru со ссылками на дополнительные материалы, в случае ответа, кандидат переходит на другой этап, если кандидат не ответил делается повторная попытка. Иногда человеку лучше заранее отправить сообщение если номер незнаком, чтобы он знал по какому вопросу ему звонят.&#x20;


# Термины

**Компания** - лицо, которое регистрирует рабочее окружение, создавая аккаунт супер-администратора в Blinger.io, для использования решения в бизнес-процессах компании, например, поддерка клиентов.

**Супер-администратор** – аккаунт пользователя с полным, в границах своего окружения, доступом ко всем функциональным возможностям и настройкам Blinger.io; именно аккаунт супер-администратора добавляет операторов.

**Оператор** – аккаунт пользователя, предназначенный, в основном, для работы с обращениями клиентов.

**Роль** – совокупность полномочий, которые возможно предоставить аккаунту типа "Оператор" для расширения списка его функциональных возможностей.

**Клиент** – лицо, обратившееся в службу поддержки компании через социальную сеть, мессенджер, электронную почту или онлайн-чат, в результате чего было создано обращение в Blinger.io.

**Сообщение** – предложение, содержащее некоторый смысл, передаваемый клиентом оператору и обратно, и являющееся составным элементом обращения и диалога.&#x20;

**Обращение** – совокупность сообщений от клиента и оператора, которая в целом представляет завершенный диалог; в интерфейсе обращением принято считать период с момента нажатия "Начать диалог" и после нажатия на "В закрытые".

**Диалог** – совокупность обращений с одним клиентом, который обратился через какой-либо канал (социальная сеть, месенджер, электронная почта, онлайн-чат); в интерфейсе диалогом считается вся история переписки с клиентом в определенном канале в разделе "Диалоги".

**Канал** – общее понятие для социальной сети, мессенджера, электронной почты или онлайн-чата, с которыми выполнена интеграция в Blinger.io&#x20;

**Аккаунт канала** – страница, группа, бот-канал или номер, добавляемые в Blinger.io, например, подключается конкретный бот-канал в канале Skype&#x20;

**Группа операторов** – один и более операторов, объединенных по какому-либо признаку (языковой, географический, рабочая смена, компетенция и тд.)

**Виджет** – это javascript-приложение, которое выполняет переадресацию пользователя с веб-страницы, на которой размещен виджет, в аккаунт канала, добавленный в Blinger.io


# Регистрация и вход

## Общая информация

Чтобы начать пользоваться Blinger.io, необходимо пройти регистрацию. Для этого требуется имя, электронный адрес и номер телефона.

В Blinger.io существует 2 типа аккаунтов:

* **аккаунт "Супер-администратора"** - первый и основной аккаунт, в котором производятся все настройки Blinger.io, а также имеется возможность непосредственно работать с обращениями клиентов.&#x20;
* **аккаунт "Оператора"** - аккаунты создаваемые ([**Как добавить оператора?**](/russian/opisanie-raboty/razdel-operatory/upravlenie-operatorami#dobavit-operatorov)) супер-администратором и предназначены для непосредственной работы с обращениями пользователей. Также имеется возможность расширить полномочия данному типу аккаунта ([**Какие полномочия можно добавить Оператору?**](/russian/opisanie-raboty/razdel-operatory/upravlenie-rolyami#opisanie-polnomochii)).

{% hint style="warning" %}
Оператор приглашается в  Blinger.io супер-администратором, самостоятельной  регистрации аккаунта **нет**.&#x20;
{% endhint %}

{% hint style="info" %}
**Совет:**&#x20;

Если необходим аккаунт, который будет использоваться для управления (контроля, анализа) работой операторов, то предлагаем пользоваться аккаунтом "Супер-администратора", либо создать аккаунт "Оператора", расширив для этого аккаунта полномочия.&#x20;
{% endhint %}

## Зарегистрироваться в Blinger.io?

{% hint style="warning" %}
Инструкция актуальна только для регистрации аккаунтов типа "Супер-администратор"
{% endhint %}

Чтобы создать аккаунт супер-администратора необходимо пройти по ссылке: [**https://app.blinger.io/site/registration**](https://app.blinger.io/site/registration)

![](/files/-LnMyP48Vj9mvlDBG_M8)

Ввести необходимые для регистрации данные (имя, действующий email, контактный номер телефона),  согласиться с [**Условиями использования сервиса**](https://blinger.io/terms)**,** пройти проверку на "анти-бот" и нажать "Зарегистрироваться"

{% hint style="warning" %}
Правилами Blinger.io установлено, что к регистрации не принимаются email, которые начинаются на **info@**
{% endhint %}

После этого, на указанный в форме регистрации email придет письмо для завершения регистрации.&#x20;

![](/files/-LnN-wNF-i61kWdNhRF_)

Пройдите по ссылке указанной в письме, чтобы задать пароль для аккаунта супер-администратора и нажмите "Сохранить пароль"

![](/files/-LnN0dx1HWhfontywEND)

После успешного завершения регистрации, будет произведен автоматический первый вход в Blinger.io для последующей настройки

## Войти в Blinger.io?

{% hint style="info" %}
Инструкция актуальна для аккаунтов "Супер-администратора" и "Оператора"
{% endhint %}

Чтобы войти в свой аккаунт ("Супер-администратора" или "Оператора"), необходимо пройти по ссылке: [**https://app.blinger.io/site/login**](https://app.blinger.io/site/login) и ввести данные, которые использовались при регистрации (email и пароль)

![](/files/-LnN33Awshelk5BSBm1f)

## Забыли пароль аккаунта?

{% hint style="info" %}
Инструкция актуальна для аккаунтов "Супер-администратора" и "Оператора"
{% endhint %}

Чтобы восстановить пароль необходимо пройти по ссылке: [**https://app.blinger.io/site/forgot**](https://app.blinger.io/site/forgot) либо нажать "Забыли пароль?" на странице входа в аккаунт. В появившемся окне ввести email аккаунта и нажать "Получить инструкцию".

![](/files/-LnN53lU2CBid9PXOBkD)

Если email аккаунта введен корректно, то придет письмо со ссылкой, по которой необходимо пройти и задать новый пароль

{% hint style="info" %}
Запоминайте свои пароли :innocent:
{% endhint %}


# Раздел: Приложения

#### В разделе Приложения Blinger.io можно делать следующее:

* добавить аккаунты каналов, обращения из которых планируется обрабатывать в Blinger.io **-** [**перейти к описанию**](/russian/opisanie-raboty/channels/dobavlenie-kanalov)
* тегировать добавленные аккаунты каналов **- перейти к описанию**
* настроить закрепление аккаунтов каналов за конкретными группами операторов **-** [**перейти к описанию**](/russian/opisanie-raboty/channels/raspredelenie-po-kanalam)

![Рисунок - Раздел: Приложения](/files/-Llld25JnGF_pWDGYcIf)


# Добавление каналов

В разделе представлены пошаговые инструкции по добавлению каналов, с которыми Blinger.io имеет интеграции.&#x20;

{% hint style="warning" %}

#### Важно!

Добавлять аккаунты каналов в аккаунт Blinger.io может человек с правами **Супер-администратора.**
{% endhint %}

{% hint style="info" %}

#### Совет!

Внимательно выполняйте каждый шаг инструкций - это позволит вам **сэкономить время**.&#x20;
{% endhint %}


# Facebook

## Общая информация

#### Интеграция позволяет:

* **подключать Страницы** к Blinger.io (не личные аккаунты)
* **отвечать на сообщения** из Facebook Messenger подключенной Страницы
* **отвечать на комментарии** клиентов под публикациями, которые размещены на стене Страницы теми, кто имеет возможность управлять данной Страницей

{% hint style="warning" %}

#### **Перед началом интеграции с Facebook необходимо:**

* авторизоваться в Facebook под учетной записью, имеющей роли «Администратора», «Редактора», «Модератора» в подключаемой Странице
* проверить, что у подключаемой Страницы активирована в Настройках (раздел "Общие") функция «Обмен сообщениями»&#x20;
  {% endhint %}

## Подключить Facebook Messenger?

### Шаг 1. Открыть вкладку «Приложения» и нажать кнопку «Добавить»

![](/files/-LlqAvctzb5OCngjsdci)

### **Шаг 2.** Выбрать канал Facebook и нажать «Добавить Facebook»

![](/files/-Llqoz0Y5Ebedh4Dz_h0)

### **Шаг 3.** Нажать в появившемся окне «Начать»

![](/files/-Llqp3kHw5U22YaoBlMr)

{% hint style="info" %}
После того, как будет нажата кнопка "Начать", вы будете перенаправлены на страницу Facebook, где необходимо **разрешить доступ приложению** Blinger.io, чтобы выполнить поиск «Страниц», которыми вы можете управлять.

#### Шаг 1.

![](/files/-LlqpNS_IS8LW73V20Q6)

#### Шаг 2.

<img src="/files/-LlqpnKEl_RnkxGHFffX" alt="" data-size="original">

#### Шаг 3.

![](/files/-Llqq7u__jiaD6KNIpAe)
{% endhint %}

### **Шаг 4.** Выбрать необходимую Страницу для подключения и нажать "Добавить"&#x20;

![](/files/-LlqqVnA0_dBdcBNRWzB)

{% hint style="success" %}

### Интеграция завершена!

{% endhint %}

## **П**одключить Facebook Comments

### **Шаг 1.** Нажать «Изменить» в интеграции с Facebook

![](/files/-LlqqhyhAnz7oFLNYdDg)

### Шаг 2. Поставить галочку напротив от Enable и нажать «Сохранить»

![](/files/-Llqqt_VQqtf_XDzzfwA)

{% hint style="success" %}

### Интеграция завершена!

{% endhint %}


# WhatsApp

## Общая информация

Интеграция позволяет подключать как обычные аккаунты, так и WhatsApp Business аккаунты, и **не требует для подключения наличие доступа к WhatsApp Business API.**&#x20;

Интеграция с WhatsApp - это разработка Blinger.io, созданная по принципу «reverse engineering».&#x20;

{% hint style="info" %}

#### У вас есть доступ к WhatsApp Business API (прямой или опосредованный)?

Обратитесь в Службу поддержки Blinger.io, чтобы получить информацию о возможности подключения.&#x20;
{% endhint %}

## Подключить WhatsApp?

### **Шаг 1.** Открыть вкладку Приложения и нажать кнопку «Добавить»

![](/files/-LlqAvctzb5OCngjsdci)

### **Шаг 2.** Выбрать канал WhatsApp и нажать «Добавить WhatsApp»

![](/files/-LlqAm0EJh6kgyanYQ-3)

### **Шаг 3.** Нажать в появившемся окне «Добавить» для загрузки QR-кода

![](/files/-LlqBB-ZGCKUb4MBu84N)

### Шаг 4. Открыть на смартфоне меню сканирования QR-кода в приложении WhatsApp / WhatsApp Business

{% hint style="warning" %}
Приложение WhatsApp / WhatsApp Business должно быть заранее связано с номером телефона, который планируется использовать для подключения к Blinger.io&#x20;
{% endhint %}

#### Как это сделать в смартфоне?

{% tabs %}
{% tab title="iOS" %}
1\. Открыть раздел **«Настройки»** и нажать **«WhatsApp Web / Desktop»**

![](/files/-LB6_C2r-VD9d-TAD9lN)

2\. Перед сканированием необходимо нажать **«Выйти со всех компьютеров»**, после чего **«Сканировать QR-код»**

![](/files/-LBBKtSkvcF3pPhIIdDx)
{% endtab %}

{% tab title="Android" %}
1\. Зайти в меню приложения и выбрать пункт **«WhatsApp Web»**

![](/files/-LBBLWyTlNKx_N6EYq79)

2\. В появившемся окне нажмите **«Выйти со всех компьютеров»**, а потом **«+»**, чтобы включить камеру для сканирования QR-кода.

![](/files/-LB7eIdKfcZRt3idiynt)
{% endtab %}
{% endtabs %}

### Шаг 5. Отсканировать смартфоном сгенерированный QR-код

![](/files/-LlqJ_ZeQNEXMKtvJsO0)

{% hint style="success" %}

### Интеграция завершена!

{% endhint %}


# Telegram

## Общая информация

Интеграция позволяет подключать Telegram-ботов (не личные аккаунты). Telegram-боты - это не чат-боты, это специфическое название канала в Telegram, которые позволяют настроить канал коммуникации компании с клиентом.&#x20;

Инструкция составлена исходя из факта того, что Telegram-бот уже создан и его необходимо подключить к Blinger.io. Если Telegram-бот не создан, то предлагаем воспользоваться инструкцией: [**Как создать бота в Telegram?**](/russian/faq-1/faq/po-kanalam/telegram)&#x20;

## Подключить Telegram-бота?

### **Шаг 1.** Открыть вкладку Приложения и нажать кнопку «Добавить»

![](/files/-LlqAvctzb5OCngjsdci)

### **Шаг 2.** Выбрать канал Telegram Bot и нажать «Добавить Telegram бота»

![](/files/-LlqSk2EK_nT8-VyN1YC)

### **Шаг 3. Найти и открыть в Telegram бота** BotFather

![](/files/-LEtFvsMELLGknsBvdVc)

### **Шаг 4.** Ввести в строке сообщений BotFather значение `/mybots`

![](/files/-LEtGN1L_0Ov__-Itxqb)

### Шаг 5. Выбрать Telegram-бота, который необходимо подключить

![](/files/-LEtH3SHr2ivrohjhHKp)

### Шаг 6. Нажать кнопку «API Token»

![](/files/-LEtHFdJ2SOWOtcjFK8Q)

### **Шаг 7. Скопировать значение Token**

![](/files/-LEtK2wPUIHqDN0pyG89)

### **Шаг 8.** Вернуться в Blinger.io, вставить скопированный Token и нажать «Добавить»

![](/files/-LlqXCjFTsbScDeEE-nd)

{% hint style="success" %}

### **Интеграция завершена!**

{% endhint %}


# Viber

## Общая информация

Интеграция позволяет подключать Viber Bot Account (не личные аккаунты). Viber Bot Account - это не чат-боты, это специфическое название канала в Viber, которые позволяют настроить канал коммуникации компании с клиентом.&#x20;

Инструкция составлена исходя из факта того, что Viber Bot Account уже создан и его необходимо подключить к Blinger.io. Если Viber Bot Account не создан, то предлагаем воспользоваться инструкцией: [**Как создать Viber Bot Account?** ](/russian/faq-1/faq/po-kanalam/viber)

Ранее Viber Bot Account назывались Public Account'ами, но технология их подключения не изменилась.

## Подключить Viber Bot Account?

### **Шаг 1.** Открыть вкладку Приложения и нажать кнопку «Добавить»

![](/files/-LlqAvctzb5OCngjsdci)

### **Шаг 2.** Выбрать канал Viber и нажать «Добавить Viber»

![](/files/-LlqYOUxqRf4I_ULONpj)

### **Шаг 3.** Войти в Viber Admin Panel

**Ссылка на Viber Admin Panel:** <https://partners.viber.com/login>

Для входа необходимо ввести номер телефона, к которому привязан аккаунт Viber и нажать Login. После чего в приложении Viber на смартфоне отобразится сообщение с кодом, который необходимо ввести для входа в Viber Admin Panel.

![](/files/-LEy44NHlevKYgSdjqKq)

После чего в приложение от Viber придет 6-тизначный пароль, который надо ввести в течение 2 минут

![](/files/-LEy7XLvPdYS-GaY1moJ)

### **Шаг 4.** Нажать на раздел «Info» и скопировать значение Url

![](/files/-LEyE5LEwNk9RTPS7unj)

### **Шаг 5.** Перейти в Blinger.io и вставить в поле «Имя» скопированный Url&#x20;

![](/files/-LlqicZff4Ewy_hqbbi-)

### Шаг 6. Вернуться в Viber Admin Panel и скопировать значение Token

![](/files/-LEyJ9CQ-1s-X249JG4b)

### **Шаг 7.** Перейти в Blinger.io, вставить скопированный Token в поле «Auth key» и нажать «Добавить»

![](/files/-LlqiYLqdssgJg5FEqzr)

{% hint style="success" %}
**Интеграция завершена!**
{% endhint %}


# Twitter

## Общая информация

#### Интеграция позволяет:

* **отвечать на сообщения** клиентов
* **отвечать на комментарии** клиентов под твитами, которые были размещены в ленте подключенного аккаунта

## Подключить Twitter Messages?

### **Шаг 1.** Открыть вкладку «Приложения» и нажать кнопку «Добавить»

![](/files/-LlqAvctzb5OCngjsdci)

### **Шаг 2.** Выбрать канал Twitter и нажать «Добавить Twitter»

![](/files/-Llqm0-sifW5QHfqgjvb)

### **Шаг 3.** Нажать в появившемся окне «Начать»

![](/files/-LlqmEbnW2XVGfAKQikH)

{% hint style="info" %}
После того, как будет нажата кнопка "Начать", вы будете перенаправлены на страницу Twitter, где необходимо **разрешить доступ приложению** Blinger.io, чтобы выполнить поиск аккаунта, которым вы управляете.
{% endhint %}

### Шаг 4. Нажать «Авторизовать»

![](/files/-LEsQ0InuKcPKkCJLUyq)

... Twitter как канал добавлен в Blinger:

![](/files/-Llqn1Zq4DNVf_92wxzy)

### **Шаг 5.** Зайти в подключенный аккаунт Twitter, нажать "Еще" и выбрать пункт меню «Настройки и конфиденциальность»

![](/files/-LlqnPUosLGuG1i549ZC)

### **Шаг 6.** Перейти в раздел «Конфиденциальность и безопасность» и активировать опцию «Получать личные сообщения от любых пользователей»

![](/files/-Llqo-Eo_-d6lPQbGuia)

{% hint style="success" %}

### **Интеграция завершена!**

{% endhint %}

## Подключить Tweet Comments?

### **Шаг 1.** Нажать «Изменить» в интеграции с Twitter

![](/files/-LlqrqBrXxb1YdNAlAmC)

### Шаг 2. Активировать Enable и нажать «Сохранить»

![](/files/-LlqsJqx3IfLeyVPz8nj)

{% hint style="success" %}

### **Интеграция завершена!**

{% endhint %}


# WeChat

## Общая информация

Интеграция позволяет подключать аккаунты типа "Subscription" или "Service", которые должны иметь статус подтвержден или *verified*.

{% hint style="warning" %}
**Перед началом интеграции с WeChat необходимо:**

* проверить чтобы в разделе Interface Privilege в категории "Conversation Service",пункты графы "Interface" имели статусы "Obtained"
  {% endhint %}

## Подключить WeChat?

### **Шаг 1.** Открыть вкладку Приложения и нажать кнопку «Добавить»

![](/files/-LlqAvctzb5OCngjsdci)

### **Шаг 2.** Выбрать канал WhatsApp и нажать «Добавить WeChat»

![](/files/-Llvca17_fjxM-QVesk0)

### Шаг 3. Войдите в аккаунт WeChat

Перейти в раздел раздел Basic Configuration меню "Development"

![](/files/-Lf_6HqTJNgxBx6ZwaNT)

### Шаг 4. Сохраните значение **Developer ID (AppID)**

Скопируйте и сохраните значение **Developer ID (AppID)** в каком-нибудь документе, напр., Блокнот

![](/files/-Lf_5Z1deZRusBa01T0y)

### Шаг 5. Внесите в IP whitelist IP-адрес Blinger.io

Нажмите напротив IP whitelist кнопку *View*, далее *Modify* и внесите ip-адрес **82.202.218.185** и подтвердите изменения

![](/files/-Lf_9Njm9hIi1r_wjCU4)

{% hint style="warning" %}
Обязательно проверьте, что IP-адрес был внесен в список корректно. Для этого необходимо повторно нажать на кнопку *View и* убедится что IP-aдрес внесен.
{% endhint %}

### Шаг 6. Сохраните значение Developer Password (AppSecret)

Нажмите напротив Developer Password (AppSecret) кнопку *Reset*

![](/files/-Lf_C7d4nLnuB2_qPmo-)

Введите в поле Login password пароль от Wechat аккаунта, код с картинки и пройдите дальше&#x20;

![](/files/-LfdZtLSMEQD6PNmhX67)

Скопируйте и сохраните значение **AppSecret** в тот документ, в который ранее сохранили Developer ID (AppID) и нажмите на *Confirm and Next.*

![](/files/-Lfde6fzYBBtLI_eR2AU)

### Шаг 7. Сохраните QR-код официального аккаунта Wechat

Перейдите в раздел Account Details

![](/files/-Lf_PYwAMhhyG5lCfyu6)

Нажмите на указанный значок

![](/files/-Lf_SIv5a35kAu9I7zKD)

и скачайте файл с QR-кодом аккаунта любого размера

![](/files/-Lf_Sn3tyI9PUcGoXDO5)

### Шаг 8. Выполните интеграцию WeChat с Blinger.io&#x20;

Вставьте, ранее сохраненные значения **Developer ID (AppID)** и **AppSecret** в поля AppID и AppSecret соответственно, загрузите файл с QR-кодом аккаунта и нажмите *Добавить.*

![](/files/-Lf_OC0pqgGlf6SxpERs)

### Шаг 9. Настройте конфигурацию сервера WeChat

Нажмите *Change configuration*

![](/files/-Lf_FoX1t41bT6NdQhQl)

&#x20;Вернитесь в Blinger.io в раздел Приложения и нажмите *Изменить* в интеграции Wechat

![](/files/-Lf_GNlrzKd8wCaIfs_q)

Скопируйте значения **Webhook url** и **Webhook token**

![](/files/-Lf_Gj3t1sUAmsPxbjyx)

и вставьте их соответственно в поля **URL** и **Token**

![](/files/-Lf_HNR3WSLVciXBD0Li)

Далее, необходимо нажать *Random Generation* для генерации ключа, оставить активным параметр **Plaintext Mode** в меню Message Encryption Method и нажать *Submit.*

После того, как снова окажитесь в разделе Basic Configuration необходимо нажать кнопку *Enable* (*Примечание:* после нажатия отобразится кнопка *Disable*).

![](/files/-Lf_J0Z7A46nZGSK6M2X)

{% hint style="success" %}

### Интеграция завершена!

{% endhint %}

{% hint style="info" %}
**У работы интеграции с Wechat есть своя особенность.**&#x20;

После завершения всех работ по интеграции, обмен сообщениями начинает работать **спустя 30-60 минут.** Такая задержка связана с внутренними техническими процессами компании мессенджера WeChat.
{% endhint %}


# Вконтакте

## Общая информация

#### Интеграция позволяет:

* **подключать Сообщества / Группы** к Blinger.io (не личные аккаунты)
* **отвечать на сообщения**, отправляемые клиентами в Сообщество&#x20;
* **отвечать на комментарии** клиентов под публикациями, которые размещены **на стене Сообщества** теми, кто имеет возможность управлять данным Сообществом

{% hint style="warning" %}

#### **Перед началом интеграции с Вконтакте необходимо:**

* авторизоваться в Вконтакте под учетной записью, имеющей роль «Администратора» в подключаемом Сообществе / Группе
* проверить, что у подключаемого Сообщества **активирована функция «Написать сообщение»** (путь: Управление - Сообщения - Сообщения сообщества: Включены)
  {% endhint %}

## Подключить Диалоги?

### **Шаг 1.** Открыть вкладку Приложения и нажать кнопку «Добавить»

![](/files/-LlqAvctzb5OCngjsdci)

### **Шаг 2.** Выбрать канал VK и нажать «Добавить VK»

![](/files/-LlquFt8nHp4m2r4hL71)

### **Шаг 3.** Нажать в появившемся окне «Начать»

![](/files/-Llqv9iOaqyeDIEZyiMc)

### **Шаг 4.** Выбрать Сообщество, которое планируется подключить

![](/files/-LlqvLgo91l9M7VRWo48)

... нажать «Разрешить», для возможности подключения приложения Blinger.io

![](/files/-LEnP1f1s3Pb9XoJv6km)

... после этого , в Blinger.io появится статус об завершении интеграции. **Но интеграция не окончена!!!**

### **Шаг 5.** Нажать «Изменить» в интеграции с Вконтакте

![](/files/-LlqwVTaTkzytCzU3lwn)

### **Шаг 6.** Открыть Вконтакте и перейти в раздел «Управление» Сообщества, которое было подключено

![](/files/-LmKbSJ3-CVnFMMhDPHm)

### **Шаг 7.** Перейти в раздел «Работа с API», и переключиться на вкладку «СаllBack API»

![](/files/-LmKc36JUEqqJm3SmcTk)

### **Шаг 8.** Скопировать значение "Строка, которую должен вернуть сервер"

![](/files/-LmKdP6z1-GHj8yWZ-2W)

### **Шаг 9.** Вернуться в Blinger.io и вставить скопированное значение в поле "Webhook key" и нажать "Добавить"

{% hint style="info" %}
После этого будет сгенерирован Secret key (указан на рисунке), его необходимо скопировать
{% endhint %}

![](/files/-LmKe1oyvS8yoxVDjUsM)

### **Шаг 10.** Открыть Вконтакте, вставить Secret key в поле "Секретный ключ" и нажать "Сохранить"&#x20;

![](/files/-LmKeubNjY-zFsGlpeoQ)

### **Шаг 11. Заполнить поле "URL", установить версию API v.5.50 и нажать "Подтвердить"**

Значение для поле "URL": [**https://api.blinger.io/vk\_webhook**](https://api.blinger.ru/vk_webhook)

![](/files/-LmKfkzA2JKoY_qPhNUO)

### **Шаг 12.** Активировать во вкладке «Типы событий» пункты «Входящее сообщение»

![](/files/-LmKgr7-PlX5IFWq3ona)

{% hint style="success" %}

### **Интеграция завершена!**

{% endhint %}

## Подключить Комментарии?

### **Шаг 1.** Нажать «Изменить» в интеграции с Вконтакте

![](/files/-LmPY57WY99e1Am0263R)

### **Шаг 2.** Нажать в появившемся окне «Get access token»

{% hint style="warning" %}
При каждом нажатии на «Get access token», **токен** для работы с комментариями **будет обновляться**
{% endhint %}

![](/files/-LmPYGIgJKd0az5jkDA1)

### **Шаг 3.** Скопировать значение токена из адресной строки браузера

{% hint style="info" %}
Значение токена расположен между значениями `access_token=` и `&`
{% endhint %}

![](/files/-LEoImDS663UMF-zlvGp)

### **Шаг 4.** Вернуться в Blinger.io, вставить токен и нажать «Сохранить»

![](/files/-LmPYnStm2guQa0Zw1hU)

### **Шаг 5.** Зайти на главную страницу подключенного «Сообщества» и перейти в раздел «Управление»&#x20;

![](/files/-LmKbSJ3-CVnFMMhDPHm)

### **Шаг 6.** Открыть раздел «Работа с API», перейти во вкладку «СаllBack API»

![](/files/-LmKc36JUEqqJm3SmcTk)

### **Шаг 7.** Перейти во вкладку "Типы событий" и поставить галочку напротив поля "Новые" в блоке "Комментарии на стене"

![](/files/-LmPZVh1H0cvRcf4lZx5)

{% hint style="success" %}

### **Интеграция завершена!**

{% endhint %}


# Одноклассники

## Общая информация

#### Интеграция позволяет:

* **подключать Группы** к Blinger.io (не личные аккаунты)
* **отвечать на сообщения**, отправляемые клиентами в Группу&#x20;

{% hint style="warning" %}
**Перед началом интеграции с Одноклассники необходимо:**

* авторизоваться в Одноклассниках под учетной записью, имеющей роли «Администратора / Супермодератора / Модератора » в подключаемой Группе
* в настройках Группы (раздел: Сообщения) **установить в поле "Сообщения могут писать" значение "Гости и участники"**
* отправить абсолютно любое сообщение данной Группе из учетной записи, **не являющейся ее участником** до момента интеграции.
  {% endhint %}

## Подключить Одноклассники Группу?

### **Шаг 1.** Открыть вкладку Приложения и нажать кнопку «Добавить»

![](/files/-LlqAvctzb5OCngjsdci)

### **Шаг 2.** Выбрать канал Одноклассники и нажать «Добавить Одноклассники»

![](/files/-Llvl97XPNPofn5QvrRT)

### **Шаг 3.** Открыть Группу Одноклассники, которую планируется подключить, и перейти в «Настройки»

![](/files/-LlvldiELkYwTo7WDR5l)

### **Шаг 4.** Выбрать раздел «Сообщения» и нажать «Получить ключ доступа»

![](/files/-LlvmL1YYi6FzYicQtg_)

### **Шаг 5.**  Нажать «Получить новый ключ доступа» и скопировать сгенерированный ключ

![](/files/-Llvmb8-MZO95wrvY2nT)

### **Шаг 6.** Открыть Blinger.io и вставить ключ доступа в поле «Токен»&#x20;

![](/files/-LlvoKUUSUEbTNfY7jzX)

### **Шаг 7.** Перейти Одноклассники и скопировать значение ID Группы&#x20;

ID группы располагается между "'/group/" и "/messages". Также это значение можно скопировать в поле ID, если перейти в раздел "Основные"

![](/files/-LlvnSam3b-mlH4-c-oO)

### **Шаг 8.** Открыть Blinger.io, вставить ID в поле «Group name» и нажать «Добавить»&#x20;

![](/files/-LlvoPO7NOoZ4IzFwBRO)

{% hint style="success" %}

### Интеграция завершена!

{% endhint %}


# Skype

## Общая информация

Интеграция позволяет подключать Skype Bot'ов (не личные/обычные аккаунты). Skype Bot - это не чат-боты, это специфическое название канала в Skype, которые позволяют настроить канал коммуникации клиента с компанией.

Инструкция составлена исходя из факта того, что Skype Bot уже создан и его необходимо подключить к Blinger.io. Если Skype Bot не создан, то предлагаем воспользоваться инструкцией: [**Как создать Skype Bot?**](/russian/faq-1/faq/po-kanalam/skype)&#x20;

## Подключить Skype bot?

### **Шаг 1.** Открыть вкладку Приложения и нажать кнопку «Добавить»

![](/files/-LlqAvctzb5OCngjsdci)

### **Шаг 2.** Выбрать канал Skype и нажать «Добавить Skype-бота»

![](/files/-LlvtaXVqMUOMoF_stM8)

### **Шаг 3.**  Зайти в аккаунт Microsoft Azure **и** выбрать Skype  Bot, который  планируется подключить

{% hint style="info" %}
Если нет аккаунта на портале Microsoft Azure, то воспользуйтесь инструкцией: [**Как создать аккаунт Microsoft Azure?**](/russian/faq-1/faq/po-kanalam/skype#kak-sozdat-akkaunt-na-microsoft-azure)
{% endhint %}

Прямая ссылка на **Microsoft Azure:** <https://portal.azure.com/#home>

Выбрать конкретного Skype-бота можно найти в разделе "All resources".&#x20;

![](/files/-Lm4PF-SYsGMhm2_4c_5)

{% hint style="info" %}
Skype-bot всегда имеет тип: **Bot Channels Registration**
{% endhint %}

### **Шаг 4.** Изменить "Messaging endpoint" в разделе Settings

Указать Messaging endpoint: `https://api.blinger.ru/skype_webhook/`и нажать "Сохранить"

![](/files/-LEyUfSg5hGZWcUOCQFl)

### **Шаг 5.** Скопировать значение поля Microsoft App ID

![](/files/-Lm4U1V1ecU7X-LcuBKr)

### Шаг 6. Открыть Blinger.io и вставить Microsoft App ID в поле «Application id»

![](/files/-Lm4ULNaFHXJd0ej-mlj)

### **Шаг 7.** Скопировать значение поля Client secret

Нажать "Manage" в поле Microsoft App ID

![](/files/-Lm4UzNQPFjHDpS0LfgJ)

... удалить текущий Client secret

![](/files/-Lm4VCyvzMN3N7b1lJF7)

... создать новый Client secret путем нажатия на кнопку "New client secret"

![](/files/-Lm4VQdG6CTqzpNZCtJ6)

... скопировать значение **Сlient secret**

{% hint style="info" %}

* поле Description можно заполнить любым значением
* в поле Expires указать Never
  {% endhint %}

![](/files/-Lm4WIljv2Kqmx8jRY0q)

### Шаг 8. Открыть Blinger.io, вставить **Сlient secret** в поле «Application Secret» и нажмите "Добавить"

![](/files/-Lm4Won223Cz260pmhXZ)

### **Шаг 9.** Вернутся на портал Microsoft Azure, перейти в раздел Channels и добавить канал Skype

![](/files/-Lm4Y9W73_COEaY5lE1x)

### **Шаг 10.** Заполнить проблемы Publish в соответсвии с требованиями и нажать "Submit for Review"

{% hint style="info" %}
Заполнение раздела Publish необходимо, чтобы созданного Skype Bot можно было отыскать через строку поиска в приложении Skype.

Обратите внимание на поля, где необходимо указать ссылки на «Условия использования» и «Политику конфиденциальности», которым руководствуется ваш ресурс.&#x20;
{% endhint %}

![](/files/-Lm4acUvpTBbtgdlRFXD)

**По желанию:** для Skype Bot можно установить логотип - путь: Settings - Bot profile - Icon

![](/files/-Lm4bkKHpXr2jEgMrXhM)

{% hint style="success" %}

### **Интеграция завершена!**

{% endhint %}

{% hint style="info" %}
**У работы интеграции с Skype есть своя особенность.**&#x20;

После завершения всех работ по интеграции, обмен сообщениями начинает работать **спустя 5-15 минут.** Такая задержка связана с внутренними техническими процессами компании мессенджера Skype.
{% endhint %}


# Line

## Общая информация

Интеграция позволяет подключать Line Business Channels.

{% hint style="warning" %}

#### **Перед началом интеграции с Line необходимо:**

* установить на смартфон мобильное приложение Line и создать аккаунт

**Важно:** Новая версия Line в Appstore на территории РФ недоступен для скачивания
{% endhint %}

## Подключить Line?

### **Шаг 1.** Открыть вкладку Приложения и нажать кнопку «Добавить»

![](/files/-LlqAvctzb5OCngjsdci)

### **Шаг 2.** Выбрать канал Skype и нажать «Добавить Line»

![](/files/-Lm4pctr9e_HRuDccpFa)

### **Шаг 3.** Войти с свой аккаунт **LINE Business ID**

Прямая ссылка на **LINE Business ID**: [**https://account.line.biz/login**](https://account.line.biz/login)

Предлагается выбрать один из двух методов авторизации (выбран "Log in with Line Account")

![](/files/-Lm4vH-wsrCbkTgkM30n)

Регистрационные данные аккаунта **LINE Business ID** - логин (электронная почта) и пароль, которые использовались при регистрации аккаунта в мобильном приложении.&#x20;

![](/files/-Lm4w-LizbcT_gZQj6Te)

{% hint style="info" %}
Также можно воспользоваться методом входа по QR-коду
{% endhint %}

### **Шаг 4.** Перейти в раздел Accounts и выбрать тот, на базе которого будет добавляться канал для интеграции

![](/files/-Lm4worX2_6SlMP6O-Hb)

### Шаг 5. Скопировать Basic ID

{% hint style="info" %}
Значение скопировать необходимо без символа @
{% endhint %}

![](/files/-Lm4yz8Mt353qgXGsx63)

### Шаг 6. Вернуться в Blinger.io и вставить Basic ID в поле "Bot id"

![](/files/-Lm4zMY-85J25l_dAvdG)

### Шаг 7. Открыть раздел Messaging API и нажать [LINE Developers](https://developers.line.biz/en/)

![](/files/-Lm52WfKJu6mCpM9mqk1)

### Шаг 8. На портале LINE Developers выбрать Messaging API и далее нажать "Start"

![](/files/-Lm52ggAkq3oCbYumDBd)

![](/files/-Lm5310JMc3K2XxS-89C)

### Шаг 9. Выбрать уже существующую запись провайдера либо создать новую

![](/files/-Lm53K1AjdvcM4jooyvj)

### Шаг 10. Выбрать один из существующих каналов либо создать новый

![](/files/-Lm55OnYlT59n23dFP4T)

### Шаг 11. Скопировать Channel ID и Channel secret из вкладки Channel Settings

![](/files/-Lm57jU0pSMTWTcHkp8u)

### Шаг 12. Вернуться в Blinger.io и вставить Channel ID и Channel secret в поля "Client id" и "Channel secret" соответсвенно

![](/files/-Lm56icLkNOeXRkcQ5wx)

### Шаг 13. Указать Webhook URL

Для этого необходимо нажать "Edit" и вставить Webhook URL. После этого нужно подтвердить адрес - нажать "Verify"

{% hint style="warning" %}
В поле Webhook URL необходимо ввести адрес, который строится из двух частей:

1. **Адрес** - [`https://api.blinger.ru/line_webhook?channel_id=`](https://api.blinger.ru/line_webhook?channel_id=)
2. **Значение** - `Channel ID`

Примечание: После знака "=" необходимо вставить значение **Channel ID** (без пробелов и т.п.)
{% endhint %}

![](/files/-Lm58JfpyDzYk4D6xvUN)

### Шаг 14. Сгенерировать и скопировать Channel access token

![](/files/-Lm5701zhC1-H1pGZdZz)

### Шаг 15. Вернуться в Blinger.io и вставить Channel access token в поле "Channel access token" и нажать "Добавить"

![](/files/-Lm57P9MZveY4Xg0j4qc)

{% hint style="success" %}

### Интеграция завершена!

{% endhint %}


# Email

## Общая информация

Интеграция позволяет подключать почту различных сервисов (публичные и внутренние). Инструкция составлена с примерами подключения **Gmail, G Suite** и **Yandex.**&#x20;

Перед началом интеграции с электронной почтой, настройте пересылку писем.

## Как настроить пересылку?

{% hint style="warning" %}
**Настройка пересылки не является стоп-фактором** для перехода к следующем шагу настроек, то есть можно&#x20;
{% endhint %}

Пересылка писем должна быть настроена на **<forwarding@mail.blinger.io>**. Ниже расположены инструкции, как настроить пересылку в сервисах Gmail / G Suite и Yandex.

{% tabs %}
{% tab title="Gmail / G Suite" %}
Путь:

1. Открыть "Настройки"
2. Перейти в раздел "Пересылка и POP/IMAP"
3. В поле "Пересылка" указать Email для пересылки

![](/files/-Lm9mG_sJkVn2Of-UaD2)
{% endtab %}

{% tab title="Yandex" %}
Путь:

1. Открыть "Настройки"
2. Перейти в раздел "Правила обработки почты"
3. В разделе создать правило "Все письма пересылать по адресу:" и указать Email для пересылки

![](/files/-LExaU9yuyvi5LxyqnFb)
{% endtab %}
{% endtabs %}

{% hint style="info" %}
После настройки пересылки, необходимо сообщить Службе поддержки, что была выполнена данная настройка. Это необходимо для того, чтобы Blinger.io подтвердил на своей стороне возможность пересылки. \
P.S. В случае с Gmail, иногда не требуется подтверждение
{% endhint %}

## Как подключить Gmail?

Перейдите в раздел **Настройки** своего аккаунта в **Gmail**. Перейдите во вкладку **Пересылка и POP/IMAP** и активируйте **включить IMAP**&#x20;

![](/files/-M2cGYrVSMgB8uZrkM7-)

Далее, перейдите в **Google Account** (ссылка: <https://myaccount.google.com/security>). Во вкладке **Безопасность** найдите раздел **Ненадежные приложения, у которых есть доступ к аккаунту** и нажмите **Открыть доступ**

![](/files/-M2cgQosKJyqkhjkSqzE)

Откройте Blinger.io. Во вкладке **Приложения** нажмите кнопку **Добавить**, после чего найдите канал **Email** и нажмите **Добавить Email**

![](/files/-Lm9l2VLixUlay9hqavy)

заполните требуемые поля...&#x20;

![](/files/-M2cLNu5G4gOWUmwg3Fu)

| Поле                              | Значение                                          |
| --------------------------------- | ------------------------------------------------- |
| **Email** или **Email** **Login** | электронная почта, которую планируется подключать |
| **Host**                          | smtp.gmail.com                                    |
| **Port**                          | 587                                               |
| **Password**                      | пароль аккаунта электронной почты                 |
| **From name**                     | отображаемое имя отправителя                      |

... нажмите **Добавить.**

## **Как подключить G Suite?**

Откройте панель админа **G Suite** (адрес: <https://admin.google.com/>) и перейдите в раздел  **Security**.

В меню раздела выберите пункт **Less Secure Apps**, установите значение напротив **Allow users to manage their access to less secure apps** и нажмите **Save**.

![](/files/-M2cW8cnOfZwHIhsNibe)

Вернитесь в основное меню панели админа **G Suite** и откройте раздел **Apps**. Далее, перейдите в **G Suite** и выберите сервис **Gmail**.

![](/files/-M2cXiHHjrnj06h1hYZB)

Внизу списка выберите **Advanced Settings**

![](/files/-M2cYmUoqhqNOkC9FrDi)

В подразделе **Routing** нажмите **ADD** в пункте **SMTP relay service.** Задайте настройки, как на картинке ниже, и нажмите **Save**

![](/files/-M2c_5rmRItqsAhzS5gs)

Далее, перейдите в **Google Account** (ссылка: <https://myaccount.google.com/security>). Во вкладке **Безопасность** найдите раздел **Ненадежные приложения, у которых есть доступ к аккаунту** и нажмите **Открыть доступ**

![](/files/-M2cgQosKJyqkhjkSqzE)

Откройте Blinger.io. Во вкладке **Приложения** нажмите кнопку **Добавить**, после чего найдите канал **Email** и нажмите **Добавить Email**

![](/files/-Lm9l2VLixUlay9hqavy)

заполните требуемые поля...&#x20;

![](/files/-M2cLNu5G4gOWUmwg3Fu)

| Поле                              | Значение                                          |
| --------------------------------- | ------------------------------------------------- |
| **Email** или **Email** **Login** | электронная почта, которую планируется подключать |
| **Host**                          | smtp-relay.gmail.com                              |
| **Port**                          | 587                                               |
| **Password**                      | пароль аккаунта электронной почты                 |
| **From name**                     | отображаемое имя отправителя                      |

... нажмите **Добавить.**

## Как подключить Yandex?

Откройте аккаунт Yandex.Mail (адрес: <https://mail.yandex.by>) и перейдите в **Все Настройки > Почтовые программы**

![](https://lh3.googleusercontent.com/6vEXqNO8wwNsc6clJNFpXdSN2gETs6-GHF_ybYLVvqgbYDYrQBbjBQgm0L93VqeXmk9N_hbcEb8_-eooJ1Xen-m6bfQiXZbwJmPOcXTd-cx2UOP4ByYd8tUIU_kkhOP-IsIE0sxV)

Поставьте галочку на **С сервера imap.yandex.ru по протоколу IMAP** и после нажмите **Сохранить изменения**

![](https://lh6.googleusercontent.com/OC6jby18Qmx74orDI83RKbA7TFR_KLgJsJK3LDNArdKV87NBiw5UvhA4YgHE_ybmMZFCXrRc3yz2TiUGf56efh3CMGcZQtVpxePHiSmL_EZ6n95hP1lpzupZjO1oCzMsNuFU9VIV)

Откройте **профиль Яндекса** (адрес: <https://passport.yandex.by/profile>) и нажмите **Создать пароль приложения**

![](https://lh3.googleusercontent.com/JtoRbM3TvXM0mhchkKQuje_wVAjJm36ih7trRG-YJ_V9hK4l9q0YhvQKH-dpOhS4Eus6w9CK08JB0Q1X0T4dZGh9bOf9YM3wd2llN7wCeYKrkncvxRtpKrBcWdVhutaGIEWKYyZj)

Заполните поля как на картинке ниже и нажмите **Создать**

![](https://lh5.googleusercontent.com/o2FE2BFeAFzUCz1v59MvRcdmGlI58_-f38jrXt5mX-mtbWevkxL-luBpiyAdQIMGHVH8X28Buxx4SJf03zqJS4t4VIE1RqMqJiBIbX9HeCvvbZpaXcsWXS6kwS_sTWWOjsRgIkkD)

После этого появится окно с паролем

![](https://lh6.googleusercontent.com/grSz2XBshuvInCC1_IUjRiG60POIeEG_abnxQ9Z8XEULEgzvgtIinebUj9mwLmx5j92dnYJR2OJiupOER79yKqiu9gNlBwKL9rT5wtmgUM3w_M468dP0r1Q1LQwwNtpSfVtf7dAR)

Сохраните это значение.

Откройте Blinger.io. Во вкладке **Приложения** нажмите кнопку **Добавить**, после чего найдите канал **Email** и нажмите **Добавить Email**

![](/files/-Lm9l2VLixUlay9hqavy)

заполните требуемые поля...&#x20;

![](/files/-M2cLNu5G4gOWUmwg3Fu)

| Поле                              | Значение                                          |
| --------------------------------- | ------------------------------------------------- |
| **Email** или **Email** **Login** | электронная почта, которую планируется подключать |
| **Host**                          | smtp.yandex.ru                                    |
| **Port**                          | 587                                               |
| **Password**                      | пароль аккаунта электронной почты                 |
| **From name**                     | отображаемое имя отправителя                      |

... нажмите **Добавить.**

{% hint style="warning" %}
**Если интеграция не получилась**, попробуйте еще раз проверив корректность вводимых данных и соответсвие выполняемых шагов согласно инструкции
{% endhint %}


# LiveChat

Интеграция позволяет обмениваться личными сообщениями с посетителями сайта.

## Общая информация

Канал Livechat - это онлайн-чат от Blinger.io

## Подключить LiveChat?

### Шаг 1. Открыть вкладку «Приложения» и нажать кнопку «Добавить»

![](/files/-LlqAvctzb5OCngjsdci)

### **Шаг 2. Выбрать канал LiveChat и нажать** «Добавить **LiveChat**»

![](/files/-Lm4hZg0sfoRm3-i-U2l)

### Шаг 3. Нажать "Добавить"

![](/files/-Lm9BGsycNf4KnwoDYxt)

{% hint style="success" %}

### **Интеграция завершена!**

{% endhint %}

## Настроить Livechat для авторизованной зоны?

Данная функция позволяет передавать данные залогиненного аккаунта непосредственно в Blinger.io

### Шаг 1. **Получить Secret key**

Чтобы получить Secret key, необходимо зайти в раздел "Приложения", нажать "Изменить" в блоке Livechat и скопировать на странице настроек значение в поле Secret key&#x20;

{% hint style="warning" %}
Если поле **Secret key** пустое, тогда нужно удалить LiveChat и добавить заново
{% endhint %}

![](/files/-LoV7jQBkD300zJYh95r)

### Шаг 2. Разместить дополнительный код на странице виджета

Перед js-кодом Виджета разместить на этой же странице следующий код:

{% hint style="info" %}
Передавать можно любое количество параметров
{% endhint %}

```javascript
<script>
 var customBlingerConfig = {
   customLivechatFields: {
     your_custom_param_1: 123,
     your_custom_param_2: 'my value',
     your_custom_param_n: 999,
     sign: 'ff127a29530759df7752f6ffab2a78fd'
   }
 };
</script>
```

### Шаг 3. Вычислить значение параметра `sign`

Значение параметра `sign` зависит от значений, передаваемых параметров - это hash от значений параметров. Hash вычисляется на стороне вашего сервера и требуется для защиты передаваемых параметров от изменений третьих лиц.

Вычисляется следующим образом:

1. конкатенация всех значений передаваемых параметров + **Secret key**
2. вычисление MD5 hash от полученной строки

{% hint style="info" %}
**Пример:**

1. возьмем любые параметры, например, **`Rdr9ucDi19nixmpevci5EiOvlFVyXbCT`**
2. делаем конкатенацию значений параметров: **`“123my value999Rdr9ucDi19nixmpevci5EiOvlFVyXbCT”`**
3. вычисляем хеш: **`md5(“123my value999Rdr9ucDi19nixmpevci5EiOvlFVyXbCT”)`**
4. полученный хеш подставляем как значение **`sign: 'ff127a29530759df7752f6ffab2a78fd'`**
   {% endhint %}

### Шаг 4. Вычисление параметра на стороне Blinger.io

На стороне Blinger.io будет произведена аналогичная операция. После чего будет сопоставлен полученный hash с тем, который пришел с вашей стороны. При совпадении клиент будет помечен в Blinger.io значком <img src="/files/-LoVBzInCLRCLq3GtM7-" alt="" data-size="original"> . Пример ниже:&#x20;

![](/files/-LoVC8y8-gnMKdIHUhCV)

При нажатии на <img src="/files/-LoVBzInCLRCLq3GtM7-" alt="" data-size="original"> или аватар клиента, можно увидеть в таблице Сustom Fields значения параметров, которые добавляли на втором шаге.

![](/files/-LoVCjIbv3bH2qP2XSd0)


# Custom app

## Общая информация

#### Интеграция позволяет подключить:

* собственный (либо гибкий сторонний) онлайн-чат
* чат в мобильном приложении
* любой сторонний мессенджер (если нет в разделе "Приложения")&#x20;
* чат-ботов в мессенджерах по типу "Мессенджер - чат-бот - Blinger.io",&#x20;

для того чтобы обрабатывать обращения клиентов в Blinger.io, Zendesk, Intercom, Kayako или SalesForce.&#x20;

## Подключить Custom app?

### Шаг 1. Открыть вкладку «Приложения» и нажать кнопку «Добавить»

![](/files/-LlqAvctzb5OCngjsdci)

### Шаг 2. **Выбрать канал Custom app и нажать** «Добавить **Custom app**»

![](/files/-Lm9roVGkKfvYEJMBiQM)

### Шаг 3. Настроить добавление канала

| Поле                | Тип     | Описание                                 |
| ------------------- | ------- | ---------------------------------------- |
| **Name**\*          | varchar | Имя приложения                           |
| **Custom App Id\*** | varchar | Уникальный Id приложения                 |
| **Webhook URL\***   | varchar | URL для отправки сообщения из Blinger.io |

### Шаг 4. Настроить получение и отправку сообщений от end-user

{% hint style="info" %}
Сообщения приходят в **json-формате**
{% endhint %}

#### Получение сообщений от end-user

| **Поле**                  | **Тип** | **Описание**                                                                                                                                                    |
| ------------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **token\***               | varchar | <p>Авторизационный токен.</p><p>Передается в заголовке Authorization: Bearer</p><p>TOKEN</p><p>Генерируется при добавлении приложения из интерфейса Blinger</p> |
| **custom\_channel\_id\*** | varchar | Уникальное поле. Задается при добавлении приложения из интерфейса Blinger                                                                                       |
| **client\_id\***          | varchar | Id конечного пользователя                                                                                                                                       |
| **client\_name**          | varchar | ФИО конечного пользователя                                                                                                                                      |
| **client\_phone**         | varchar | Телефон конечного пользователя                                                                                                                                  |
| **info**                  | json    | Дополнительная информация о конечном пользователе                                                                                                               |
| **type\***                | varchar | <p>Тип сообщения:</p><ul><li>text</li><li>image</li><li>file</li></ul>                                                                                          |
| **data\***                | text    | Текст сообщения или ссылка на файл                                                                                                                              |
| **echo**                  | boolean | Эхо-сообщение, т.е. сообщение подтянутое из другого сервиса                                                                                                     |
| **echo\_outgoing**        | boolean | Исходящее эхо-сообщение                                                                                                                                         |

####

#### Отправка сообщений end-user

| **Поле**                | **Тип** | **Описание**                                                                                          |
| ----------------------- | ------- | ----------------------------------------------------------------------------------------------------- |
| **token**               | varchar | <p>Передается в заголовке Authorization: Bearer</p><p>TOKEN</p>                                       |
| **custom\_channel\_id** | varchar | <p>Уникальный custom\_channel\_id.</p><p>Задается при добавлении приложения из интерфейса Blinger</p> |
| **client\_id**          | varchar | Id конечного пользователя                                                                             |
| **type**                | varchar | <p>Тип сообщения:</p><ul><li>text</li><li>image</li><li>file</li></ul>                                |
| **data**                | text    | Текст сообщения или ссылка на файл                                                                    |

### **Шаг 5. Настроить webhooks**

Вебхуки для входящих и исходящих сообщений можно посмотреть на странице настроек приложения.

Пример:

![](/files/-LayY9rwYgT8OAdOYFvE)

{% hint style="success" %}

### **Интеграция завершена!**

{% endhint %}


# Тегирование канала

## Общая информация

Функция "Тегирование канала" необходима, если требуется, чтобы операторы различали из каких аккаунтов канала пришли клиенты, что позволит получить дополнительную аналитику.&#x20;

Примеры использования:

* компания имеет необходимость подключить несколько аккаунтов одного канала, например, 4 аккаунта WhatsApp и нужно понимать, какой клиент из какого канала пишет.

## Как настроить?

### Шаг 1. Во вкладке Приложения нажать "Изменить" в интеграции с одним из аккаунта канала

![](/files/-LmAG9MjnCPnRW4Lfw_x)

### Шаг 2. Ввести в поле "Теги" то название, которое необходимо задать данной интеграции

Чтобы удалить Тег необходимо нажать на "x".

![](/files/-LmAGNbg07hWaf56YkJE)

{% hint style="success" %}

### Функция настроена!

{% endhint %}


# Закрепление канала за группой

## Общая информация

Функция "Закрепление канала за группой" необходима, если требуется, чтобы обращения из определенных аккаунтов канала поступали в конкретные группы операторов.&#x20;

Примеры использования:

* необходимо развернуть омниканальную поддержку на разных проектах и у каждого проекта есть своя группа операторов
* развернуть мультиязычную поддержку (одна группа операторов - Европа, вторая - Китай) и на каждый регион необходимы свои каналы

## Как настроить?

### Шаг 1. Перейти в "Распределение по каналам" во вкладке Приложения

![](/files/-LW2gWF2VjU8VkjW9j-P)

### Шаг 2. Настроить функцию

#### Вариант 1. Если необходимо, чтобы диалог с клиентом возвращался в исходную группу, за которой закреплен канал, через который обратился клиент.

Выбрать те группы, которые необходимо привязать к аккаунту канала.

![](/files/-LW2iDX6BUB8Haj_T8gb)

Включить "Распределение закрытых диалогов в назначенные группы" и указать сколько должно пройти минимум времени (часов), чтобы новое обращение из закрепленного канала отобразилось в исходной группе

![](/files/-LmAEccnK7VfyXwhEeJ_)

Нажать "Сохранить"

#### Вариант 2. Если необходимо, чтобы диалог с клиентом после его закрытия оставался в этой группе&#x20;

Выбрать те группы, которые необходимо привязать к аккаунту канала.

![](/files/-LW2iDX6BUB8Haj_T8gb)

Перейти во вкладку "Авто распределение сообщений" раздела "Настройка", активировать функцию

![](/files/-LmyiX1WlB7tueBq1K3g)

&#x20;Нажать "Сохранить"

{% hint style="success" %}

### Функция настроена!

{% endhint %}

## Остались вопросы?&#x20;

Перейдите по ссылке

{% content-ref url="/pages/-LW33ZKTE\_KKXi9uKxiS" %}
[Привязка каналов к группам](/russian/faq-1/faq/o-funkciyakh/privyazka-kanalov-k-gruppam)
{% endcontent-ref %}


# Раздел: Интеграции

В разделе Интеграции возможно настроить интеграции с известными CRM/Helpdesk решениями.&#x20;

В настоящее время **Blinger.io поддерживает 7 интеграций**. Они позволяют в привычном для компании рабочем пространстве, будь то Zendesk Support или BPM'online, общаться с клиентами, которые предпочитают вместо традиционным каналам общения более современные: мессенджеры и социальные сети и при этом хранить всю информацию по клиенту в одном месте.&#x20;


# Freshdesk

## Общая информация

Интеграция позволяет прямо в интерфейсе Freshdesk обрабатывать сообщения из мессенджеров и социальных сетей. Каждое обращение конвертируется в "Тикет".&#x20;

{% hint style="info" %}
Blinger.io выступает исключительное в роли "транспорта", который доставляет сообщения клиентов в интерфейс Freshdesk. Тонкая настройка обработки обращений производятся в интерфейсе Freshdesk, Blinger.io никак не влияет на бизнес-процесс стандартной работы хелпдеска.
{% endhint %}

## Настроить интеграцию с Freshdesk?

### Шаг 1. Зайти в раздел Интеграции и нажать "Добавить интеграцию" напротив Freshdesk

![](/files/-LbYmCEpoxqguN5k8_a5)

### Шаг 2. Заполнить соответствующие поля и нажать "Add Freshdesk integration"

![](/files/-LbYmNfJkp290Q7QRkbQ)

{% hint style="info" %}

### Примечание

**Subdomain** - располагается в адресной строке открытого аккаунта Freshdesk.\
**Email и Password** - данные для авторизации в аккаунте Freshdesk.
{% endhint %}

{% hint style="warning" %}

### Важно

Если появилось **сообщение об ошибке** при попытке добавления интеграции, то необходимо проверить корректность данных авторизации и субдомена.
{% endhint %}

### Шаг 3. Перейти в меню "Admin" аккаунта Freshdesk и выбрать "**Automations**" в разделе "**Helpdesk Productivity"**

![](/files/-LkxIYUO2OO1GhT3zNAB)

### Шаг 4. Перейти во вкладку "Ticket updates" и нажать "New Rule", чтобы создать правило для работы с Blinger.io

![](/files/-LkxIksPS5oNTQBTbBfZ)

### Шаг 5. Заполнить необходимые поля и установить следующие значения и нажать "Save"

| Поле                                 | Комментарий                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Rule name**                        | **-** любое значение                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| **When an action performed by...**   | - значение "Agent" с тегом "Any"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| **Involves any of these events**     | - значение "Reply is sent"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| **On tickets with these properties** | - значение "Match ALL of the below"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| **Perform these actions**            | <p> - выполнить следующие действия:</p><ol><li>выбрать значение <em>Trigger webhook</em></li><li>указать <em>Request Type: POST</em></li><li>скопировать значение <em>Webhook URL</em> со страницы интеграции в аккаунте Blinger и вставить это значение в поле <em>Callback URL</em></li><li>указать значение <em>Encoding: JSON</em></li><li><p>отметить в поле <em>Content</em> значения<em>:</em> </p><ul><li><em>Ticket ID</em></li><li><em>Subject</em></li><li><em>Description</em></li><li><em>Tags</em></li><li><em>Last public comment</em></li><li><em>Status</em></li><li><em>Contact Unique External Id</em></li></ul></li></ol> |

![](/files/-LkxKe6j6ShiQ0hIzlOm)

![](/files/-LkxKs2vIg0z00DK7aZU)

![Value for Callback URL](/files/-LbcMI1UfT3Uc0N03cSw)

{% hint style="success" %}

### **Интеграция завершена!**

{% endhint %}


# Zendesk

## Общая информация

Интеграция позволяет прямо в интерфейсе **Zendesk Support** обрабатывать сообщения из мессенджеров и социальных сетей. Каждое обращение конвертируется в "Тикет".&#x20;

{% embed url="<https://www.youtube.com/watch?v=m2vIanMPl5w&t=7s>" %}

{% hint style="info" %}
Blinger.io выступает исключительное в роли "транспорта", который доставляет сообщения клиентов в интерфейс Zendesk Support. Тонкая настройка обработки обращений производятся в интерфейсе Zendesk Support, Blinger.io никак не влияет на бизнес-процесс стандартной работы хелпдеска.
{% endhint %}

## Настроить интеграцию с Zendesk?

### Шаг 1. Зайти в раздел Интеграции и нажать "Добавить интеграцию" напротив Zendesk

![](/files/-Lm9zAL-PbGiH3QjVQZE)

### Шаг 2. Зайти в аккаунт Zendesk, выбрать «Настройки» раздел «Аккаунт» и скопировать значение поля «Субдомен»

![](/files/-LFIAgvgqIopIFZZkKWf)

### Шаг 3. Открыть Blinger.io, вставить Субдомен нажать «Добавить интеграцию с Zendesk»

![](/files/-Lm9zXb_DvOLaf3xpgHU)

{% hint style="success" %}

### **Интеграция завершена!**

{% endhint %}


# Intercom

## Общая информация

Интеграция позволяет прямо в интерфейсе Intercom обрабатывать сообщения из мессенджеров и социальных сетей. Каждое обращение конвертируется в "Диалог".&#x20;

{% hint style="info" %}
Blinger.io выступает исключительное в роли "транспорта", который доставляет сообщения клиентов в интерфейс Intercom. Тонкая настройка обработки обращений производятся в интерфейсе Intercom, Blinger.io никак не влияет на бизнес-процесс стандартной работы хелпдеска.
{% endhint %}

## Настроить интеграцию с Intercom?

### Шаг 1. Зайти в раздел Интеграции и нажать "Добавить интеграцию" напротив Intercom

![](/files/-Lcf3eWlo2mUAaQZzbci)

### Шаг 2. Открыть аккаунт Intercom и перейти в «Settings»

![](/files/-LcezgT03hlIBb5X0KvD)

### Шаг 3. В разделе «Developers» выбрать «Developers tools»

{% hint style="info" %}
После нажатия на «Developers tools» произойдет переадресация на Intercom Developer Hub
{% endhint %}

![](/files/-LcewMu1o3jXba7H3DbW)

### Шаг 4. Нажать «New app» и задать любое имя для создаваемого приложения

![](/files/-LcewgCST2hqysSGdEJP)

### Шаг 5. Скопировать значение "Access token"

![](/files/-LcexmNFHhNPlZmLNTUO)

### Шаг 6. Перейти в Blinger.io, вставить "Access token" в одноименное поле

![](/files/-LmA-S-ZnnpsvVgH_Z79)

### Шаг 7. Вернуться в Intercom и скопировать значение App id

App id указан в адресной строке между `app/../`, как в примере на рисунке ниже

![](/files/-Lcf-S4uBi187xVhJdoq)

### Шаг 8. Перейти в Blinger.io, вставить "App id" в одноименное поле и нажать "Добавить интеграцию"

![](/files/-LFMEZecJDNpKZk5O3Ac)

### Шаг 9. После добавления интеграции, нажать кнопку "Изменить" в блоке интеграции с Intercom и скопировать значение "Webhook URL"

![](/files/-Lcf1PvnoAL_LfiD9b3L)

### Шаг 10. Настроить в Intercom Developers Hub "Webhook URL"

На странице Intercom Developers Hub в разделе Configure выбрать Webhooks. Вставить  "Webhook URL" в поле "Your request endpoint URL", в разделе Webhook Topics выбрать **`conversation.admin.replied`** и нажать "Save".

![](/files/-Lcf2ClzYAH81MZTQBVK)

{% hint style="warning" %}
Выбирайте в разделе "Basic information" версию API 2.2
{% endhint %}

{% hint style="success" %}

### **Интеграция завершена!**

{% endhint %}




---

[Next Page](/llms-full.txt/1)