Bitrix24
Your Lalexi conversations inside the Bitrix24 chat: a client's message arrives in an open line, the reply written there reaches the client, and every message lands in the CRM card's history.
If your managers work in Bitrix24 and would rather not leave it, the conversation can come to them. A client's message from any Lalexi channel appears in the chat of an open line in your portal, a reply written there reaches the client through the same channel, and everything your team writes in Lalexi shows up in the portal as a reply from the manager. Bitrix creates the contact card and the deal itself, from the phone number.
Only conversations whose contact has a phone number are passed on: Bitrix finds its CRM card by the number, and a conversation without one has nowhere to land. That leaves Avito, Cian, email, web chat and group chats in Lalexi only.
What you need
- an application in your portal. This is an ordinary Bitrix24 local
application, created by a portal administrator:
Applications → For developers → Other → Local application; - administrator rights in Lalexi — only an administrator can attach a portal to a workspace.
Step 1. The application in the portal
Create a local application and fill in our addresses:
| Field in the application | Value |
|---|---|
| Installation handler path | https://api.lalexi.com/bitrix24/install |
| Application handler path | https://api.lalexi.com/bitrix24/app |
Leave "uses API only" and the box saying the application finishes its own installation switched off: our page finishes the installation.
Application rights: imopenlines, imconnector, im, crm, placement.
Without them the portal refuses to create the line or to write to the card, and
you will see the reason in words on the integrations page.
Step 2. Installation
Install the application in the portal. Our page opens and sends you to Lalexi, to Settings → Integrations. No new workspace is created: you attach the portal to the one you already work in.
Step 3. Attaching it to a workspace
On Settings → Integrations a block named Attach a portal appears with the name of your portal. Press Attach to this workspace.
If the portal asked for its own keys, the same page has Application ID and Application secret — the person who created the application in the portal has them. The keys are stored encrypted and are never shown again. Every portal has its own pair: connecting a second portal changes nothing about the first.
After that, go back to the portal's tab — it refreshes itself. In Bitrix you will find an open line, tabs on the contact and deal cards, and an entry in the left menu.
What you can set
On the card of an attached portal:
- Send first from — the channel a message leaves through when a manager writes to a client there has been no conversation with yet. It can stay at "starting a conversation from the portal is not allowed";
- Write the reply under the name of whoever typed it — see "Authorship" below;
- Add every message to the CRM card's history — an entry in the card's feed for each message. If the feed is only meant as a log, this can be switched off;
- Enabled — stops the traffic without erasing the binding or the keys;
- Detach — removes the subscription in the portal and erases the keys.
The state of the binding is shown there too: Working, Failing, Needs reinstalling, Off or Waiting to be attached. If the portal refused something, the reason is written next to it.
Authorship
A reply written in the portal is recorded in Lalexi under the name of whoever typed it — provided that manager's email matches a member of your workspace. If it does not match, the reply is recorded under the name of the person who attached the portal.
We do not create Lalexi members for the sake of a byline: those are paid seats. If one person has different emails in the portal and in Lalexi, that is settled by a setting on the binding rather than by a new member — write to support.
What does not happen
- Statuses are not synchronised. Resolve a conversation in Bitrix and it stays open in Lalexi, and the other way round; the assignee is not passed on either. If the team works in the portal, open conversations will pile up in Lalexi;
- replies from the portal are your outgoing messages, and they count towards the workspace's message limit;
- writing first from a CRM card and the conversation on a card's tab are not available yet.
If something did not arrive
- a conversation whose contact has no phone number will not reach the portal — that is expected;
- Failing on the integrations page: the reason the portal gave is written next to it. Most often it is a right that was not granted, or an open line that was deleted;
- Needs reinstalling: the portal revoked the keys. Install the application in the portal again — the binding and its settings survive.