Skip to content

Bitrix24 Integration

Overview

Aelo integrates with Bitrix24 as an embedded application. Once installed, you can:

  • Access an Aelo dashboard directly inside Bitrix24
  • Open the Aelo tab in a deal, lead, contact or company card: the deal state and the conversations of that card — see The Aelo Tab in CRM Cards
  • Get analysis results on CRM cards (contacts, deals, leads, companies) in mapped fields (on the card itself or a Smart Process item) and, by default, as a comment in the card’s timeline
  • Automatically create Aelo records from Bitrix24 calls and chats
  • Push analysis results back to CRM fields
  • On Pro and higher plans (or during the Pro trial of a free organization), get the state of a deal or lead after each analysed conversation as a separate timeline comment, and create a CRM task from its next action — see Deals

Installing Aelo in Bitrix24

Owner Admin

  1. Open the Aelo app card in the Bitrix24 Marketplace.
  2. Click Install.
  3. Authorize Aelo to access your Bitrix24 account.
  4. Complete the onboarding flow within the embedded app.

Embedded Dashboard

After installation, Aelo appears as an application in your Bitrix24 left menu. The tab bar of the embedded app has the dashboard tabs and Records. Delivery to CRM cards is not a tab: it is set up in the Aelo web app (Analysis Setup → CRM Updates, see Delivery to CRM Cards).

Dashboard Tabs

The same dashboard as in the Aelo web app, with its filter panel (see Dashboard). Its tabs stand in the tab bar in place of Overview, the ones your role and access allow: Summary, Conversations, Sales, Quality, Team and Voice of Customer. A rep gets one tab, Mine. A tab that your plan does not include carries a lock and opens a plan screen. Voice of Customer is one of the six, so it is not drawn a second time; the card’s Report → opens its full report. When no tab can be offered (for example, an access without any section), Overview stands in their place and says why there is nothing to show.

The Company criteria card on the Quality tab is a report only in the embedded app: criteria are created and edited in the Aelo web app. The same goes for the built-in criteria: their answers appear in the call panel and its PDF and in the dashboard here (the Standard checks card), while pausing them or narrowing where they apply is done in the web app, in Analysis Setup → Criteria.

The Quality tab has the How objections are handled card. Report “Objections” → on it opens the Objections screen inside the app; ← Overview at the top brings you back to the dashboard.

Records Tab

The organization’s conversations, calls and chats (see Records). You can search the list and filter it by channel, call direction and call category, and hide missed calls. A row shows who the conversation was with, the rep, the category, the duration and the quality score — or, while the conversation is still being processed or if processing failed, its stage or a failure mark. Click a row to open the conversation’s analysis in the same tab; Back returns to the list.

Voice of Customer Tab

The same Voice of Customer view as in the web app, for owners, admins and supervisors. It is part of Pro and higher plans (and is open during the Pro trial of a free organization): on other plans the tab is still there: while the organization has demo data it shows that demo under a banner asking to turn to the account owner to change the plan, and without demo data it says so instead of showing data. Reps do not see this tab. In an organization with the new dashboard (a closed preview), Voice of Customer is one of the dashboard sections instead, and this separate tab is not shown.

The Aelo Tab in CRM Cards

Open a deal, lead, contact or company in Bitrix24 and choose the Aelo tab in the row of the card’s tabs (when the row is short of room, Bitrix24 moves it under More). Aelo registers the tab when the app is installed or the Bitrix24 source is reconnected under Data Sources, and removes it when the source is disconnected; the tab exists in Bitrix24 only.

  • Deal and lead — at the top, the deal-state card of this deal or lead: status and chance to close, what is happening and why, the next action with Create task in CRM, what to say next, commitments and objections, qualification and the history of states (see Deals); under it, the list of the card’s conversations. The Draft a message to the client button is there too. There is no deal queue and no Open in CRM link in the tab — you are already in the CRM.
  • Contact and company — the list of conversations only: contacts and companies have no deal state.
  • Conversations — calls and open-line chats in one list, newest first, 20 at a time (Show more loads the next page). A row shows the channel, the title, the rep, the duration, the quality score — or the processing stage while there is no score — and the time. Click a row, or a quote on the deal-state card, to open the conversation’s full report — analysis, transcript and audio — in the same tab; Back to conversations returns to the card and the list.
  • Refresh — an open tab does not update by itself: it keeps what it loaded until you click Refresh at the top of the tab, which asks the deal state, the card and the list of conversations again. If the refresh fails, the deal state and the conversations already on screen stay, marked that they may be out of date, with Try again.
  • A lead the deal grew from. When a deal continues the state of a lead (see Deals), its list also holds the conversations of that lead, each marked from lead #…; the card’s Continuation of lead #… link opens that lead in Bitrix24.

Who sees what

The tab shows only what the person can open in Aelo — the same boundary as the Records list:

  • Owner and Admin — every conversation of the card;
  • Supervisor — the conversations of their assigned projects and of the people under them in the org structure, and their own;
  • Rep — their own conversations and those of the people under them in the org structure.

The deal-state card is shown only when the conversation its state is built on is visible to the person. When nothing is visible, the tab says that conversations of this deal that you can access in Aelo will appear here; it never says how many conversations are hidden.

The deal-state card and your plan

The deal-state card is part of Pro and higher plans and is open during the Pro trial of a free organization. On a lower plan the tab says so in place of the card, and the list of conversations stays. When the feature is switched off for the organization, the tab asks you to contact your administrator. Until the first analysed conversation of the deal or lead, the tab says that the state appears after it.

Limits

  • One conversation, one card. A conversation is attached to the single CRM entity that Bitrix24 recorded the call or chat on. A call recorded on a contact is in the contact’s tab, not in the tab of a deal that contact belongs to.
  • One portal. A card’s number is the number on its own portal: the tab of deal #123 shows the conversations of deal #123 of that portal, not of another portal of the same organization.
  • A task created from the tab has no link to the Aelo app. Create task in CRM works as in the app — the title, the reason and the due date — but, unlike a task created in the Aelo app, it does not carry the link to the deal card in Aelo.
  • If the tab is missing, contact Aelo support: the tab is registered for the portal by the Aelo team. Until it is, the app works as before, without the tab.

Analysis Details

Results reach the CRM card through CRM delivery — in the fields you map (on the card itself or a Smart Process item) and, by default, as a comment in the card’s timeline (an optional note on the call or chat activity is off by default; see Delivery to CRM Cards); the full analysis of a conversation opens in the Aelo tab of the card or in the Aelo app from the Bitrix24 left menu.

For calls with audio, the analysis panel also shows a Voice metrics block — objective acoustic signals of how the call was delivered: speaking rate (words per minute), pauses, pitch variation, and voice stability. These are measurements of delivery, not transcript content; chats and audio-less records do not have them.

Automatic Record Creation

When configured, Aelo can automatically capture calls and chats from Bitrix24:

  1. A call is made or received in Bitrix24.
  2. Bitrix24 sends the recording to Aelo via webhook.
  3. Aelo transcribes and analyzes the recording — in Automatic mode right away (if the project’s Auto Analysis switch is on); in Manual mode, where a new organization starts, once an owner or admin starts it.
  4. Results are delivered back to the CRM entity card.

Setting Up Automatic Capture

  1. In Aelo, go to Data Sources and connect Bitrix24 — enter your domain and authorize access.
  2. Configure distribution rules (Analysis Setup → Distribution) to map CRM call/chat events to Aelo projects.
  3. Recording capture starts automatically once the source is connected (Data Sources).

Delivery to CRM Cards

Aelo can push analysis results to CRM entity fields:

Delivery Methods

MethodDescription
Custom FieldsChoose a CRM field for each analysis result in the table of the CRM Updates step
Smart ProcessesUse Bitrix24 Smart Processes for structured data
Report as a comment (on by default)Post the analysis report as a comment in the card’s timeline
Report as a note (off by default)Save the analysis report as a note on the call or chat activity

Checks in the report. When your organization has built-in criteria, the report has a ☑️ CRITERIA block with one line per built-in criterion that has an answer for this analysis: the criterion’s name and yes, no or unsure. “Yes” means that what the name says happened, so for “Broke personal data rules” it is a violation. When “Rep used profanity” triggered, the block adds up to five of the rep’s quotes with their time. For these checks the block replaces the older lines about the recording disclaimer, mandatory phrases and profanity; older lines come only from analyses made before the change, and only for a check whose criterion has no answer for that analysis. A check you paused, or one outside the criterion’s scope, has no line at all. Only built-in criteria appear in the block, not your own. The customer’s profanity is no longer sent to the CRM: the profanity line shows only the rep’s words.

In the Aelo app inside Bitrix24, the Create fields button in Settings creates Aelo’s own fields (quality score, sale probability, summary and the others) on deals, leads, contacts and companies alike, because a conversation’s results are written to whichever of those cards it is linked to. Bitrix24 silently skips a field that a card type does not have, so create the fields before relying on delivery.

The CRM Updates Step

Open Analysis Setup → CRM Updates. The step is laid out top to bottom:

  1. Delivery destination — two cards: CRM card (results are written to the fields of the card itself) and Smart Process (results are written to a Smart Process item). This is also where you create the Smart Process, repair its fields and recreate it. The choice of destination is saved at once.
  2. Which results to write to card fields — the field table when delivery writes to the CRM card; when it writes to a Smart Process, the table Which results to write to smart process fields takes its place (see below).
  3. What else to do in the CRM — one list of switches.
  4. The save panel at the bottom of the step.

The connection status is not in the step: it is on the Connection tab of Data Sources. The Sync CRM Users button is not in the step either: it is under Settings → Team → Org Structure, next to Import from CRM (see Team).

Which Results to Write to Card Fields

A table with three columns: Aelo result, Field in CRM and Field type. It has 15 rows in three groups:

GroupAelo resultWhat is written
Conversation outcomeSummaryAI-generated summary
Quality ScoreOverall QA score (0–100)
Sale ProbabilityPredicted sale probability (%)
SentimentCustomer sentiment: positive, neutral or negative; when the analysis did not score it, the field is not written
TranscriptFull call or chat transcript
Skill scores, 0–100GreetingGreeting and opening of the conversation
Needs DiscoveryHow the customer’s needs were explored
Objection HandlingHow objections were addressed
ClosingClosing techniques used
PolitenessThe rep’s politeness
ClarityClarity of speech and explanations
CRMCompleteness of the data collected for the CRM
Compliance, yes / noRecording DisclaimerYes or no from a built-in criterion (see below)
TCPA ComplianceYes or no from a built-in criterion (see below)
Data PrivacyYes or no from a built-in criterion (see below)
  • Choosing a field turns the row on. Pick a field in the dropdown and the result starts being written. Don’t write turns the row off. To turn the row back on, pick the field again.
  • Aelo default field. The Aelo default field (UF_CRM_AICA_…) option is offered only for five results — Transcript, Summary, Quality Score, Sale Probability and Sentiment: the Create fields button in the Aelo app inside Bitrix24 creates these fields (and a Keywords field, which delivery does not write). For the other results, choose your own fields.
  • One field for every card type. You do not choose a field separately for deals, leads, contacts and companies: delivery writes to the card the conversation is linked to. The table warns per card type: No such field on: lead — that card type has no such field; Field of the wrong type on: … — compliance results need a yes/no field, and delivery does not write to a field of another type; Fields not loaded for: … with a Refresh button — the field list of that card type has not been loaded. Above the table you see when the portal’s fields were last refreshed: Portal fields updated …. Bitrix24 silently skips a value for a field the card does not have.
  • Only these 15 results. Only they are written to fields. Keywords and the other results that used to have switches (closing technique, relevance, completeness and accuracy of content, empathy, rapport, sentiment change, clarity and professionalism of speech, filler words) are no longer offered in this step — delivery never wrote them to fields.
  • Scores are the ones on the record page. The seven rows of the group write the call’s component score with the same name as on the record page — the same as delivery to a Smart Process. When a component was not scored in this call, the field is not written.
  • Delivery to a Smart Process. The results go to the Aelo fields created together with the Smart Process, so the field cannot be chosen: the table has 11 rows — the summary, quality score, sale probability, sentiment and the seven component scores of the call, named as on the record page (Greeting, Needs Discovery, Objection Handling, Closing, Politeness, Clarity, CRM); the transcript and the compliance results have no such field — and the Field in CRM column offers Aelo smart process field or Don’t write. Delivery writes only the rows switched on: by default the summary, quality score and sale probability; the sentiment and the component scores are written once you switch them on. A row switched off is not written, and the value an earlier delivery left in the field stays. Switching a row only turns its writing on or off; the fields you chose for the CRM card stay as they were.

Compliance Status on the card is three fields you map yourself — Recording Disclaimer, TCPA Compliance and Data Privacy — to Bitrix24 fields of the yes/no type (Create fields does not create them; a field of another type is not written). Each gets 1 (passed) or 0 (failed) from the answer of its built-in criterion for this analysis: “Disclosed call recording”, “Met TCPA requirements” and “Broke personal data rules” (for data privacy, “passed” means the answer was no). A check paused by you or by Aelo (see built-in criteria), one outside the criterion’s scope or not applicable to the call, and an “unsure” answer leave the field unwritten. For an analysis made before the change, the field comes from the older compliance assessment; in an organization without built-in criteria, new analyses leave it unwritten. Like the scores, a filled field shows the verdict of the most recent call that has one: a call that leaves the field unwritten does not clear an earlier verdict.

Compliance Status is an AI assessment, not legal advice. For new calls it reflects the answers of the built-in criteria (recording disclaimer, TCPA requirements, data privacy); calls analysed before the change keep the AI’s older evaluation of the transcript. The dashboard shows the pass rate too, on the Standard checks card of the Quality tab. It is counted from the answers of the built-in criteria “Disclosed call recording”, “Met TCPA requirements” and “Broke personal data rules” (for data privacy, “passed” means no violation), and, for calls analysed before the change that have no such answer, from the older compliance assessment — a call with neither is not counted (no assessed calls → an empty state, never a fabricated 100%). A check that Aelo has paused is marked under the card. It is not a legal determination — confirm regulatory compliance with qualified counsel.

What Else to Do in the CRM

One list of switches:

  • Deal state comment — on plans that include the deal state: after each analysed conversation of a deal or lead, a separate comment is added to the CRM timeline (see Deals).
  • Report as a comment — the analysis report as a comment in the card’s timeline (on by default).
  • Report as a note — the analysis report as a note on the call or chat activity (off by default).
  • Transcript on the call — attaches the transcript to the call record.
  • Activities from agreements — schedules a call or task on the card from the agreements made in the conversation.
  • Fill empty fields — fills empty deal or lead fields with values from the conversation; when the switch is on, you choose the fields to fill per card type under the row. Not offered when delivery goes to a Smart Process: auto-fill works only in the CRM card.

Saving Changes

There is one panel at the bottom of the step: Unsaved changes: N, Discard and Save changes. If you leave the page with unsaved changes, Aelo asks you to confirm. When you change fields or actions, saving is blocked until at least one field or action is on (the deal state comment does not count, and Fill empty fields counts only with a field chosen): “Choose at least one field or action other than the deal-state comment”. With delivery to a Smart Process, only the rows of its table count.

Fields That Already Hold a Value

Before writing, Aelo reads the card’s current field values and field definitions. Per field:

  • An empty field receives the new value.
  • A filled text field (summary, transcript) keeps its content, and the new value is added below it.
  • The score fields (quality score, sale probability, sentiment, the seven component scores and the three compliance fields) show the most recent call’s analysis. Calls are ordered by when they happened — the call time reported by the source, or the time Aelo received the call if the source reports none — not by when their analysis is delivered: an analysis replaces the score on the card only if its call is at least as recent as the call whose score is there. An older call analysed or re-delivered later (a replay, a re-analysis, a retry) leaves the score of a more recent one in place, and its other fields are still written. Two deliveries to the same card write their scores one at a time: one that arrives while another is writing is retried shortly after, as is a delivery that arrives while Aelo cannot reach the record of this order (one that keeps failing this way ends as Delivery Failed). A score is never written out of order or silently dropped for that reason. Aelo remembers which call’s score is on a card for 30 days after the score was last written; after that, the next delivered analysis sets the score. One limit: if that record cannot be updated right after a score was written and the delivery’s own record of the write is lost with it, an older call delivered afterwards may replace that score.
  • Values extracted from the conversation (optional auto-fill) go only into fields that are empty, never over an existing value.
  • Any other filled field that is not text is left untouched.

One exception: if that read of the current values fails (for example, the portal is unreachable at that moment), Aelo cannot tell which fields are filled. Values extracted from the conversation are then discarded entirely, while the fields you designated for Aelo’s own output are written directly and may replace what was in them.

Onboarding within Bitrix24

When you open Aelo from Bitrix24 for the first time, the app puts a few screens in front of the dashboard. They come in a fixed order, and each one appears only if it applies to you; a screen with nothing to do for you is skipped:

  1. Terms & Privacy — shown to everyone who has not accepted yet. It also comes back once for the portal administrator who installed the app, if they accepted earlier as an ordinary member and the organization still has no owner (for example, after a reinstall). Tick the Terms of Service and the Privacy Policy and click Accept and Continue. If Aelo knows your email address, an optional marketing-emails checkbox is also shown. If the organization has no owner yet and you are the portal administrator who installed the app, you are first asked whether you represent the company (I represent this company) or are setting the app up for a client (I am setting it up for a client). A company representative becomes the owner and accepts the Terms and the Data Processing Agreement (DPA) on behalf of the organization. Someone setting it up for a client is given the Admin role where possible and accepts the Terms personally; the company’s portal administrator then reinstalls the app in the portal, opens Aelo, and accepts on the organization’s behalf, which makes them the owner. Anyone else is not asked this question and accepts the Terms personally.
  2. Request Access — shown only if you still have no role in the organization. This is rare: a new portal user normally gets the Rep role as soon as they accept the terms. Click Send Access Request; the screen then reads Awaiting Approval until an administrator decides, and Check Status re-reads the answer. If the request is declined, send a new one with Request Access Again. If it was approved but your account is not ready yet, the screen reads Access Approved: wait a minute and click Check Status. The person who became the owner in the previous step does not see this screen.
  3. Compliance settings — shown only to the organization owner, until they confirm. The owner selects the recording/notification approach, jurisdiction, and legal basis. If the organization does not rely on call-participant consent, it can select Other lawful basis and then choose the applicable legal basis separately. For a basis defined outside the listed categories, select Other basis under applicable law; the choices are not limited to GDPR terminology. The owner acknowledges the organization’s responsibility, as controller, to determine and document that basis and to provide notices or obtain consent where applicable law requires it. A language switcher is available on this screen. Until confirmation, Aelo does not process recordings, and everyone else in the organization sees a permanent banner naming the owner. These settings record the organization’s choice; Aelo does not determine which legal basis applies.
  4. Let’s tailor Aelo to you — a short questionnaire, shown once and only to the owner of a fresh installation. You enter the company name and choose your role, team size, and industry. The industry tailors the demo data on the dashboard; the role and team size are recorded with the organization. If the organization is still named after the portal address followed by (Bitrix24), the company name you enter replaces it; an organization with any other name keeps its name.

Projects, distribution, and field mapping are not part of this flow: set them up afterwards (see Setting Up Automatic Capture and Delivery to CRM Cards).

Access by Role

FeatureOwnerAdminSupervisorRep
Install app✅✅❌❌
View embedded dashboard✅✅✅✅
Configure CRM integration✅✅❌❌
Choose fields for analysis results✅✅❌❌

Tips & Best Practices

  • Test delivery first — always verify the chosen fields with a test record; capture starts automatically as soon as the source is connected.
  • Keep the timeline comment on for quick visibility — reps see the analysis report directly in the card’s timeline. It is on by default; the note on the call or chat activity is off by default, and turning it on duplicates the report.
  • Map quality score to a custom CRM field for filtering and reporting within Bitrix24; on the card it shows the most recent call’s analysis.
  • Set up distribution rules carefully (Analysis Setup → Distribution) — map different Bitrix24 lines or departments to different Aelo projects for appropriate evaluation profiles.
  • Review delivery errors in the Aelo web app: in Records, filter by Status Delivery Failed — common issues include expired Bitrix24 tokens or fields the card does not have.