Skip to content

Feature Overview

This page lists the customer-visible capabilities currently tracked in the Product Feature Catalog. Package availability is a default commercial configuration; your organization may also have role permissions, project settings, or organization-level overrides.

Summary

Capabilities By Area

Billing

FeatureStatusPackagesWhat it does
Transcript Only ModeAvailableAll packagesA project setting for teams that need call and chat transcripts without analysis. A call is transcribed, categorized and its speakers identified, and the transcript is indexed for search and the assistant; the analysis, criteria, script rules, Voice of Customer and deal state are not run. A minute of such a call costs a quarter of a minute (TRANSCRIPT_ONLY_MINUTE_FACTOR = 0.25): a 5:10 call is charged 1.30 minutes, from the plan’s included minutes, bonus minutes or the wallet alike, and a chat costs a quarter of the chat price. The mode is available on every plan, including pay-as-you-go. Switching it on does not change what was already charged, and switching it off returns the project to its previous automatic-analysis setting. The Analyze action on a record of the mode charges a full minute (the full chat price) on top of the share already charged — 1 + 0.25 in total, no credit for the first charge — with the price shown before it starts; it works in manual mode too. A CRM import estimate counts a quarter of a minute only when every project of the organization is in the mode, and a full minute otherwise, as an upper bound. The Uspacy embedded screen shows «Transcript only» for such a project and «Manual analysis» for a project whose automatic analysis is off without the mode. A record of the mode has no speaker roles in the Markdown export (the roles come from the analysis), so speaker labels stay as speaker_N unless the transcript cleanup renamed them.
Billing WorkspaceAvailableAll packagesSubscription, usage, credits, and billing controls inside the app.
Stripe Subscriptions And CheckoutAvailableAll packagesStripe checkout, customer portal, webhooks, subscription status, cancel/reactivate, and embedded billing safeguards.
Budgets, Credits, And Usage ChargesAvailableAll packagesThe organization owner (client role) sets a monthly budget limit and sees what remains of it. The limit raises alerts at fixed shares of it (50, 80, 95 and 100 %); a single charge that crosses several shares raises the highest one only. It refuses a bulk CRM import that would cross it, but does not stop ordinary call processing. The owner also buys prepaid credits through Stripe Checkout and can turn on automatic wallet top-ups (Enterprise is billed under its agreement instead). In prepaid mode each processed call or chat is charged against the included minutes first, then bonus minutes, then the wallet; in postpaid billing (Enterprise) calls and chats are charged at their flat rates. Per-minute and per-chat rates are set by Aelo; billing screens do not show customers provider costs or margin.
Cost TransparencyAvailableAll packagesWhat the organization owner (client role) is charged: wallet balance, the minutes and chats used in the selected period and what they cost, the per-minute and per-chat rates, and a ledger of charges, credits and bonus minutes. On billing screens, provider costs and margin are visible to Aelo only; only the organization owner opens the billing screens (budget alerts with spend and limit also reach administrators).

Core Pipeline

FeatureStatusPackagesWhat it does
Ingest, Transcribe, Analyze PipelineAvailableAll packagesCore record lifecycle from ingress through transcription, AI analysis, delivery, and side effects.
Analysis Verification And GroundingAvailableAll packagesSecond pass over a finished analysis before it is published: a safety verifier re-reads the transcript on every analysis, and a fact verifier joins it whenever the analysis carries something your CRM will act on — a card field this delivery will fill, or an agreement your settings put to work as a follow-up task or as a check that a promised call-back really happened. A field the delivery does not write — a Smart Process destination, autofill off, a field outside the autofill list, a low-confidence value — is not checked and is not written either. It keeps the claims whose quote can be located in the transcript (adding the quote and its timestamp as evidence) and withholds the ones that cannot be grounded instead of delivering them. A free-text field that states several facts is checked fact by fact: each fact needs its own quote, a statement that something was not agreed passes when nothing in the conversation says otherwise, though such a field is not written to the card, and one refuted fact removes the whole field; when the checked facts do not add up to the text of the field, it stays unconfirmed. When an analysis carries neither, there is nothing to guard, and the fact pass is skipped rather than spent on grading the wording of the report. A call whose category is ambiguous gets one extra adjudication pass. Free narrative is never rewritten: a high-impact statement stays in the analysis as drafted and gets an objection only when the transcript shows it is wrong — words that say otherwise, a unit or currency the speaker never said, a date the spoken words do not fix, or a different product or party; a statement the conversation simply never mentions gets no objection, because an absence cannot be shown with a quote. An unconfirmed claim that was meant for the CRM (a card field or an agreement) withholds only the card field updates: tasks are created from confirmed agreements, an unconfirmed agreement gets no task, and call-back checks and the deal state keep working. A safety signal, a role conflict, an ambiguous category, failed personal data minimisation or a verification that could not be completed withholds the whole automatic part — card field updates, follow-up tasks and the deal state; an objection to the wording of the report withholds nothing on its own. The report still reaches your CRM either way, carrying a note whenever something was withheld; that note, like the report email, the webhook and the record screen, names the facts in question. On the record screen the state sits as a badge beside the overall score: hovering shows the status and the reasons, clicking opens the individual statements — the wording the verifier objected to and the line from the conversation that shows the error (hidden only when it contained personal data that minimisation removed). The printed PDF always shows that breakdown expanded. Verification is not a setting you can switch off, and the verifier calls that run are charged to the organization budget alongside the analysis itself.
Stage-Aware Scoring — Deal Stage, Outcome & ProgressionAvailableNot included by defaultCaptures a Bitrix24 or Uspacy deal’s CRM pipeline/stage at analysis time (crm_stage_id/crm_pipeline_id/crm_stage_semantic/crm_stage_source) and grades the call against the scorecard bound to that stage — exact binding first, stage-phase semantic as fallback, category binding when neither matches. The stage phase comes from the CRM’s own marker (Bitrix24’s won/lost semantics; for Uspacy, only a funnel’s closing success/fail stage), else from the phase the customer chose for the stage on the Deal Stages tab, else is guessed by AI from the org’s pipeline and stage names (only the names are sent to the AI model, asked again only when a stage is added or renamed or an earlier attempt gave no answer) and stored as a guess (crm_stage_semantic_origin), marked as such on the Deal Stages tab and the Objections screen; changing a stage’s phase re-phases the calls already recorded there (their scores are not recalculated). On a recurring schedule it also syncs each linked Bitrix24 or Uspacy deal’s outcome (open/won/lost; for Uspacy from the funnel’s closing success/fail stage) to drive a deal-outcome funnel (call volume by won/lost, broken down by average quality score) and derives a per-call progression verdict (advanced/held/regressed) of the deal’s stage ~7 days after the call against its stage at the call, shown as a chip beside the call — for Bitrix24 from the deal’s stage history, for Uspacy (its portal keeps no stage history) from the stages Aelo itself saw the deal in on its scheduled sync (kept for 90 days after the deal was last seen there) — so a Uspacy call whose 7-day window ends at a time Aelo had not seen the deal at (e.g. before the feature was switched on, or in a gap between two syncs) gets no verdict. Deal-only in v1; a no-op for orgs without a Bitrix24 or Uspacy connection. Opt-in per org (flag default off). The stage badge is hidden on the Bitrix24 embedded surface; re-analysis rehydrates the stored at-call snapshot rather than re-capturing, so a record’s stage always reflects the moment of the call.

Records

FeatureStatusPackagesWhat it does
Conversation Records WorkspaceAvailableAll packagesRecord list, record detail, audio access, transcript access, uploads, and per-record metadata views.
Record Reprocessing ControlsAvailableAll packagesCost estimation, re-analysis, media retry, and workflow-triggered record processing controls.
Automatic and Manual Analysis ModesAvailableAll packagesAn organization chooses between two modes. In automatic mode every new record is transcribed and analyzed on arrival. In manual mode records are accepted and listed but wait in awaiting_start without spending minutes, and an organization owner or admin starts the ones they want — a single record from its card, a selection from the records list, or the accumulated backlog, each with its price shown before the charge; every manual start — a single record, a selection or the backlog batch — re-prices the set on the server and does not start if the price has risen since it was shown (for example the included minutes ran out while the confirmation was open), or if the set now holds more records or more calls with no known duration than were priced, returning the new price instead; the backlog run starts exactly the batch that was shown, so records that arrive after the confirmation opened wait for the next run; if the price cannot be computed (billing unavailable) nothing starts and the reason is named; an organization billed under a contract (postpaid) sees the amount as charged under its contract rather than beyond its plan — one run takes at most 200 records and reports what remains, so a larger backlog is cleared by repeating the run. A manual start overrides both the organization-level gate and a project whose automatic analysis is switched off. New organizations begin in manual mode. CRM bulk import is available only in automatic mode; it does not queue records for a later manual start, so manual-mode organizations must switch to automatic before running one. The mode can be switched from the records-list banner or from organization settings. A paying organization that exhausts its included minutes AND its wallet balance is switched to manual mode by the system itself, with the reason and the moment recorded so the banner can tell an imposed pause from a chosen one; whichever records had already cleared the organization gate and were mid-pipeline when funds ran out land in awaiting_funds — there can be more than one at once, since the balance check applies per record passing through the gate, not just to a single record — while every record arriving after that — the pause’s main, ongoing outcome — is stopped by the organization gate itself and lands in awaiting_start instead. Both start the exact same way as any other pending record — individually, by selection, or through a backlog run under the same 200-record limit. A call is not held back by the minute charged while it is being processed: when that charge itself uses up the included minutes or empties the wallet, the analysis it has just paid for still runs to the end, and it is the next record that waits. A repeat analysis of a call charged on an earlier run gets no such exception. A record that ran out of funds only after it had already been transcribed keeps that transcript: starting it resumes from there instead of transcribing again, and because its minutes were already charged at transcription, it is quoted and charged nothing on that start. If that charge never went through and the call’s duration is known, the call is quoted and charged once on that start — by the duration of the conversation, or by the length of the recording when the conversation was not measured — and never again. When neither length is known, the start does not analyse the saved transcript: the call waits for its recording, like a call that arrived without one. Records that were already sitting in awaiting_funds from before this mode existed are startable the same way too — nothing already stalled there needs a separate fix. Topping up the balance does not clear the pause reason or switch the mode back to automatic by itself — only an explicit mode change from an organization owner or admin does either (turning automatic mode back on, or resubmitting manual), and until then processing stays manual with the pause still shown as the reason. What the reason SAYS does change once the organization can pay again — whether it topped up, was given bonus minutes, or simply reached a new billing cycle: the banner and the settings screen stop stating a shortage in the present tense and instead explain that the mode was taken automatically and that turning it back on is now the organization owner’s call. Organization settings show that explanation too, not only the records-list banner: an owner who opens settings directly would otherwise see a manual mode they never chose, with no hint why. A free-tier organization is never switched to manual mode for this: its included-minute grant resets with the calendar month, so running it out is a normal monthly event rather than an imposed pause, and processing resumes on its own once the new cycle starts.

Analytics

FeatureStatusPackagesWhat it does
Analysis WorkspaceAvailableAll packagesAnalysis detail APIs and UI surfaced inside the Conversations screen: per-record analysis panel, quality metric columns and QA/sentiment filters in the records table, and re-analysis trigger. The standalone Analyses screen merged into Conversations (2026-07); /analyses redirects to /records.
Acoustic Voice MetricsAvailableAll packagesObjective voice-delivery signals for calls — speaking rate (wpm), pauses, pitch variation, and voice stability — computed by the acoustic service from the call audio and surfaced on the record analysis panel.
Analytics DashboardsAvailableAll packagesDashboard and analytics pages for call volume, quality, and performance views.
Call StatisticsAvailableAll packagesCall statistics page and API for call volume, trends, durations, and operational call metrics. The page counts calls only — chats are not in its total — unless it is opened from a dashboard card (its report link) whose channel filter is Chats or All channels: then it counts that channel, so its numbers are those of the card. Filters: period, projects. The missed share is missed inbound calls of all inbound calls, answered and missed; missed calls whose direction is unknown are shown apart and are not in the share.
Missed Calls AnalyticsAvailableAll packagesMissed-call analytics view for call outcomes, follow-up gaps, and operational monitoring: missed inbound calls, outbound calls the client did not answer, missed calls of unknown direction (apart, not in the share), the missed share of inbound calls and a table by rep. Counted on the server over every call of the period, within the records the viewer may open — not over the first 200 rows of a list. In Records the same split is on the badge of a call, in its card and in the filter: “Missed” (an inbound call nobody picked up), “Client No-Answer” (an outbound call the client did not answer) and “Missed, direction unknown”; choose the “Missed” category together with a Direction (Incoming, Outgoing or Direction unknown) to list each of them on its own. In Bitrix24, an outbound call under 15 seconds that Bitrix24 does not mark as missed is counted as “Short”, not as “Client No-Answer”. Filters: period, projects (the API takes projectIds); opened from a dashboard card, the page shows the window, projects and demo rule of that card.
Customer Questions and Decline ReasonsBetaPro, Business, Scale, EnterprisePart of the Voice of Customer section: what customers ask and why they decline, from the conversations analysed since collection started — there is no earlier history. Sales tab: frequent questions by subject (“in K of N conversations”, the change against the previous period and the three latest wordings), questions left without a full answer, and why customers decline (“in K of N declines”) with the declines broken down by the call number in the series, by rep (a rep gets a row only with at least 3 sales conversations in the period) and, with stage-based scorecard selection, by funnel stage. Site and content tab: frequent questions and first-minute questions — on a call, asked within the first 60 seconds; in a chat, asked before the rep’s first message — with an export of the tab and a draft FAQ for your website built on request (not stored, up to 10 drafts a day per organization and 5 per person). Every number opens the conversations behind it. Neither collecting the questions nor building the draft charges minutes.
Objections by ReasonAvailableAll packagesThe Quality tab lists the objection reasons of the period, most frequent first, with the number of conversations each came up in and the share the team handled, out of the conversations with an objection. Every objection is sorted into one reason from a closed list of 19 (price, not now, delivery and availability, needs approval, other, and so on), so one reason is counted together however customers phrase it. Counting unit is the conversation. Objections analyzed before the list existed are sorted through a stored mapping of past wordings; when none of the period’s objections matched a known reason, the card says how many conversations had one instead of reporting no objections. From the card, the Objections screen shows every objection of a period up to a quarter in two views: market (conversations and share per reason among conversations with a recognized objection, change against the previous period of the same length, customer wordings and quotes; deal stage at the time of the call and deal movement after it only where the CRM data exists for those conversations) and team (unhandled share, average handling score, reps who drop the reason most, from 3 conversations). Each reason shows up to three best-handled conversations with the rep replies that followed, taken from the transcript, and a quote opens its conversation with the quote highlighted. Filters: period, projects, call category.
Script Steps ReportAvailableAll packagesAn Analytics screen showing which steps of the sales script the team does not complete and which criteria they miss. It opens from the menu or from the Skipped Steps widget on the Quality tab, with the widget’s period and projects. For each script it lists the steps, the most often not completed first; every step shows the share of conversations where it was not completed next to the number of conversations that owed it (“143 of 150”), how many of those were partly done and how many fell short of exactly one criterion, and how many conversations did not need the step (an optional step that did not come up). A step nobody missed stays on the list with 0. “Not completed” means not every required criterion matched, the same as the tick on the record. A row opens into a breakdown by rep (reps with few conversations are one footnote, conversations without a rep are their own line) and by criterion, with the criteria that are almost never met marked so the wording can be checked before blaming people. An opened step links to the Records list filtered to the conversations where that step was not completed, with the report’s period and projects (no link for a step removed from the script, and none in the Bitrix24 app). The top of the page says how many of the analyzed records of the period were evaluated against a script, and marks a script whose rules changed inside the period. A permanent note explains that a step required in the script but conditional in meaning is counted as not completed when the condition did not occur, until steps can be marked as conditional. Supervisors see their own projects. Filters: period up to a quarter, projects.
Voice of CustomerAvailablePro, Business, Scale, EnterpriseOne section with what customers say across the conversations of a period up to a quarter, split by who acts on it. Sales: summary cards naming the top objection, decline reason, unanswered question and theme (the row heard in the most conversations, at least 5), then one section at a time — Objections (the Objections screen), Declines, Questions and Themes — each list showing its first five rows with the rest on request. Marketing: competitors named in conversations (merged through the client glossary, the same counts as the dashboard’s Voice of Customer tab), how they were spoken of and in what context; pricing, demand and trend signals; the needs customers named. Product and service: product feedback at every level from incident to praise, and supply and regulation signals. Site and content: summary cards naming the question asked most often, the top first-minute question and the theme whose conversations most often left a question without a full answer, then one section at a time — Frequent questions, First minute, Themes and FAQ draft (a draft FAQ for your website built on request), each list showing its first five rows. With no theme in the set, neither tab shows a themes section or card; the button next to the tabs reads “Set themes”. Customer questions and decline reasons, and conversation themes from the organization’s own set, are described in their own entries. On the Marketing and Product and service tabs every row reads “in K of N conversations” with the change against the previous period of the same length, opens to the most recent conversations behind it (up to 20), and says in words when fewer than 5 conversations stand behind it. Over time: every row of a block counted by a closed code or a merged name — objections, decline reasons, question subjects, themes, competitors, market signals and product feedback — carries a line of its share across the period, by day up to 31 days and by week beyond, with a gap where the period has no data rather than a zero; an open row shows the same as bars, where a bar narrows the row’s conversations to that day or week, and switches to the last 12 months by month within the organization’s retention, where a month offers to show the whole page for it. Objections have the line, and opened the same bars and last 12 months, in the Objections section of Sales, market view only — not on the separate Objections screen; there a bar narrows the objection’s customer quotes. Questions without an answer, first-minute questions and needs have no line. A summary card shows its row’s line once a block of the tab — its section or What changed — has loaded it for the period with the row on screen, loading none of its own (the team view of objections loads none), and drops it when its numbers come back changed while that block is closed, until the block is opened again; the unanswered-question, first-minute and theme-with-unanswered-questions cards have none. A What changed view — on Marketing and Product and service a switch above the blocks, on Sales always the last section, on Site and content while customer questions are on — lists the rows of all the tab’s blocks that carry a mark, strongest shift first; objection reasons are among them, marked grew, fell or new by the same rule against the conversations with a recognized objection (the share their row shows) — new only when no earlier period with recognized objections held the reason and no earlier period, the previous one included, held an objection that could not be sorted into a reason; never gone, as only reasons heard in the period are listed; the reason’s row in the Objections section of Sales is marked new by the same rule; a block whose count reached its limit is named instead of marked. Marks follow one rule on screen, in print and in the monthly email: grew or fell when both periods have at least 30 conversations, the larger at least 5 with the row, and the share moved by at least 3 percentage points and by at least half; new and gone only against earlier periods of the same length counted in full within retention. The lines come from a derived table of each analysis’s codes and normalised keys (no conversation text, deleted with the record), filled for the whole retention of the organizations that had the section in October 2026 (for a later one it starts about a week before it gets the section) and checked nightly; a line that is still loading or failed never holds back the rows’ numbers. Counting is by the closed fields of the analysis (feedback level, signal type, sentiment); free-text wordings are shown under each row, not grouped. Export, from one Export menu on every tab: a CSV of the tab, a printable report of the tab, and a list of customer wordings; on Sales these cover the Objections section — the objection reasons of the market view with their conversations, their share of the conversations with a recognized objection and the previous period, the customer quotes in the wordings, and in print the screen’s lines on conversations with objections and the unrecognized share — and, while customer questions and decline reasons are on, the Declines and Questions sections (decline reasons, questions without an answer, frequent questions); on Sales and Site and content, while conversation themes are on, the themes block too (not under a theme filter); the team view of objections and the decline breakdowns, which name reps, are not exported. A monthly Voice of Customer email summarises the same numbers, with the top question subjects and decline reasons as counts only; a person who holds a narrow analytics access grant (access.analytics_grants) with Voice of Customer aggregates receives it instead of the letter of their role, over the area of the grant, with the questions and declines lines only when the grant opens the text of records (a Group lead yes, an Analyst no); the email is sent on Pro and up by the plan of the organization, so below Pro it stops even while the grant is active. Filters: period, projects, call category and, with conversation themes on, one conversation theme (see the conversation themes entry).
Conversation ThemesBetaPro, Business, Scale, EnterpriseThe organization’s own set of conversation themes inside Voice of Customer — what a conversation is about (a model, leasing, delivery to regions), up to 30 in use, archived instead of deleted, separate from the call category and the subject of a question. New conversations get 1–3 themes from the set (or uncategorized) and an optional suggested new theme in the Voice of Customer step — the step that finds customer questions, so themes need customer questions and decline reasons switched on, and a conversation in which the step cannot tell which side is the customer gets no themes and is not counted; conversations analysed before the set had its first theme are not labelled afterwards. The Sales and Site and content tabs count them: each theme in K of N conversations (N — the conversations with themes assigned since the theme entered the set, returned from the archive or had its definition changed), the change against the previous period where the two are comparable, the share of conversations no theme fits, theme by call category, and per theme the average quality score and the declines among sales conversations (Sales) or the conversations with a question left without a full answer (Site and content); the themes block leaves in the tab’s CSV and print export, except under a theme filter, which does not narrow it; on Site and content without customer questions the export is the whole themes block, unlabelled by a theme. A theme picker next to the Themes button narrows the whole Voice of Customer page to the conversations of one theme: every block of every tab (Sales, Site and content, Marketing, Product and service), in the portal and in Bitrix24, counts only that theme’s conversations, the FAQ draft is built from their questions (the daily draft limit is shared, not split), the themes block itself keeps showing the whole set with the chosen theme highlighted, a line above the tab’s summary says «K of N conversations in the period» with a Clear button, and a theme set inside the previous period has no comparison with it; an export under a theme says so in its file name and printed heading. An empty set can start from a proposal: one model call over the organization’s last-90-days conversation topics and call categories (re-redacted; no minutes are charged) returns up to 25 themes (10–25 asked for, fewer kept after the checks) with conversation shares, which the owner or an administrator edits and approves. Once a week the suggested new themes of the last 30 days (re-redacted, at most 300 distinct phrases, one model call per organization, no minutes charged) are grouped into at most five candidates; a candidate reaching 10 conversations and 3 % of the period’s conversations, not repeating a call category or a question subject and not already in the set is shown to the owner and administrators with its counts and up to three example conversations, to accept into the set or reject (silent for 90 days).
Deal State SummaryAvailablePro, Business, Scale, EnterpriseA running state of every CRM deal or lead after each analysed conversation — status (at risk, needs attention, on track) with the chance to close, what changed, why, the next action with its due date and what to say at the next contact — recommended by the sales methodology of the deal’s pipeline. In Aelo: a deal queue (deals and leads in three buckets with counts and CRM amounts, the reason for the status, the chance to close, the next action, its due date and the rep; closed deals counted apart) and a deal card (the current state, the history of states, the deal’s conversations, «Open in CRM» and a one-click CRM task for the next action — in Uspacy a planned activity assigned to the deal’s or lead’s responsible employee, when Uspacy names one (otherwise Uspacy assigns it), only while the portal’s processing is active); Uspacy deals show no amount. On request the deal card also writes a draft message to the client from the current state — one short follow-up in the project’s analysis language, shown in Aelo to check, edit and copy, not stored and not sent to the CRM; it works on demo deals too and is limited to 60 drafts per user and 200 per organization in 24 hours. In Bitrix24: the Aelo tab of a deal or lead card shows the same deal card of that deal or lead (the state, the history, the one-click CRM task and the draft; no queue, no «Open in CRM») over a list of the card’s conversations — calls and open-line chats, each opening its full report — inside the viewer’s own access in Aelo; a deal’s list also holds the conversations of the lead it grew from, and a task created from the tab carries no link to the Aelo app. In the CRM: after each new state a separate comment in the timeline of that deal or lead (Bitrix24, Uspacy; only the organization’s active CRM, the one that receives call reports), only for conversations up to 7 days old, with its own organization switch in Analysis settings → CRM updates (on by default). The methodology is a setting of each pipeline (a Bitrix24 pipeline or a Uspacy funnel) on its own step, Analysis settings → Sales methodology, which the Deals screen also links to for an owner or an admin — a standard framework (BANT, SPIN, MEDDIC, Challenger, or BANT + SPIN by default) plus optional company rules (the product, approved answers to objection reasons, next-step rules and contact-pause norms per stage, prohibitions); methodologies belong to the CRM they were saved in — up to 100 pipelines of a connected CRM and up to 200 in all per CRM, those of pipelines since deleted in the CRM included (reset on the same step); with both Bitrix24 and Uspacy connected the step shows the Bitrix24 pipelines, and a Uspacy deal still follows its own funnel’s methodology; leads follow the default, and so does a deal whose pipeline cannot be read from the CRM. A deal converted from a lead (in Uspacy, the linked lead Uspacy marks as converted) continues the lead’s state as of the deal’s first conversation, and its card links to the lead for a viewer who can open the lead’s card. A new organization’s demo data includes demo deals (no CRM link, no CRM task). Aelo does not charge for the state or the draft.

Review

FeatureStatusPackagesWhat it does
Analysis Annotations And ReviewsAvailableAll packagesHuman annotations and review status/feedback attached to individual analysis results.
Human Review QueueBetaNot included by defaultDurable queue for CRM automation blocked by analysis verification, with audited approve/reject decisions.

Integrations

FeatureStatusPackagesWhat it does
Direct Telephony SourcesAvailableAll packagesDirect source setup and ingestion for Streamtelecom and Binotel; Unitalk and Ringostat are in beta.
Data Source ManagementAvailableAll packagesSettings wizard and source-management API for available sources, active source, setup, connection test, and disconnect flows.
CRM Source ReconnectAvailableAll packagesOne-click rebind of a disconnected Bitrix24 or Uspacy source that is still installed in the portal, restoring the binding without a marketplace reinstall.
Hybrid Media SourcePartialAll packagesWhen a CRM is the record source but its call activity carries no recording file — only a text reference into the recording archive of the telephony operator — a telephony installation can be connected in an audio-only (media_only) role to supply it. A call id read directly out of the CRM activity is tried first; if none resolves, a telephony call index is matched by phone number, call time and duration. The index is fed by the live webhook for every call the operator reports as finished, and by a historical CDR pull for whatever the webhook never saw. An outcome of “nobody picked up” or “line busy” is what lets Aelo stop waiting and close the record with a named reason; so does a match that stays ambiguous after narrowing. Any other unanswered outcome cannot be told apart from one Aelo does not recognize yet, so the recording is still requested until the 24-hour ceiling.
Bitrix24 IntegrationAvailableAll packagesEmbedded Bitrix24 app, an Aelo tab in the deal, lead, contact and company cards, CRM data sync, and delivery paths back into Bitrix24. The tab’s «Refresh» button rereads the card’s conversations and, in a deal or lead card where the deal state is available, the deal state, without reloading the card.
Bitrix24 Smart Process SetupAvailableAll packagesEmbedded and organization-level Smart Process setup for storing and delivering analysis results in Bitrix24.
Uspacy IntegrationBetaAll packagesUspacy Calls Beta: the portal is connected by installing Aelo from the Uspacy Marketplace, calls arrive through the signed placement flow with their recording link, and the finished analysis comes back into Uspacy as a call note plus one comment on the linked entity. Aelo also reads the portal’s deal funnels with their stages and a deal’s current stage, so the Deal Stages tab, the sales methodology of each funnel, the deal state, stage capture and, with stage-based evaluation, deal outcomes and the per-call progression verdict work for Uspacy deals; for the deal state it also reads a deal’s linked leads, to continue the state of the lead the deal was converted from. The app’s page in Uspacy shows the connection status and, once the portal has an Aelo organization, a menu of large buttons — Records, Overview, Deals, Analysis Setup, AI assistant, Settings, Billing — that open those sections of the Aelo web app in a new tab, for that organization, behind the ordinary Aelo sign-in; Uspacy has no embedded Aelo app and no Aelo tab in its cards yet.
Support Chat IdentityAvailableAll packagesIdentifies a logged-in user to the operator side of the Bitrix24 support-chat widget embedded in the app, instead of the operator seeing an anonymous guest. Edge-api derives a salted hash (SUPPORT_CHAT_SALT) that the widget treats as external authentication, plus the user’s name, email, avatar, and role, and a custom-data block with organization name, subscription tier and status, organization id, and which surface (standalone app vs. Bitrix24 domain) the identity came from. One handler is mounted for both the Clerk-authenticated app and the Bitrix24 embedded session, so a user keeps one support history regardless of which surface they write from.
CRM ImportAvailableAll packagesBulk CRM import initiation, status, cancellation, history, and workflow trigger support.
CRM Fields Metadata CacheAvailableAll packagesCRM field metadata cache that powers provider-aware field selection in the inbound routing rule builder.
Public Upload APIAvailableStarter, Pro, Business, Scale, EnterpriseProgrammatic call upload and result retrieval via org-scoped API keys.

Compliance

FeatureStatusPackagesWhat it does
Customer-Configurable Data RetentionAvailableAll packagesOrganization owner may shorten the retention window to any value from 1 to 365 days, previewed against what it would delete — records, coaching notes, coaching sessions, AI assistant questions and deal states — before it takes effect; absent means the platform level applies.
Incident ManagementAvailableAll packagesIncident CRUD, resolution, and breach-notification workflow tied to records and analyses.
Consent ManagementAvailableAll packagesConsent status, grant/withdraw events, embedded consent gate, organization compliance confirmation, and a notice to every member while intake is blocked — by an unconfirmed compliance setup or by a CRM whose call processing is not authorized.
Data Subject RequestsPartialAll packagesDSR request list/create/approve/reject/delete flow, with execution still requiring manual handling.
Call Compliance ResultsAvailableAll packagesOrg-level pass-rates on the Quality tab of the dashboard (the Standard checks card) for three per-call checks — call recording disclosed, the TCPA checklist on outbound sales calls (company identified, purpose stated, opt-out offered) and personal-data handling — counted from the answers of the matching built-in criteria, and from the AI analysis for calls without such an answer; a check Aelo has paused is marked under the card. Calls analyzed earlier without such an answer are counted from the stored AI analysis; newer analyses carry no compliance section.

Automation

FeatureStatusPackagesWhat it does
Inbound Routing RulesAvailableAll packagesOrganization-level JSONLogic rules and fallback settings that route incoming records to the right project.
AlertsAvailableAll packagesBusiness and system alert rules, events, and resolution flow. A triggered alert’s recipients are resolved from each org role’s default plus each user’s personal category subscription (RBAC-gated); above an org-configurable severity threshold (critical/high by default) it delivers instantly through the recipient’s own opt-in channels (email, personal Telegram, personal webhook), otherwise it is held for the daily digest. A rule condition can read the organization’s own call criteria (triggered, score or list value), built-in criteria included — the gallery templates on call recording disclosure and on the rep’s profanity are built on them, and a rule on a paused criterion does not fire; an answer counts only when it is applicable, confident, given for this processing of the conversation and for the criterion’s current wording — otherwise the rule does not fire. For such a condition the in-app alert card shows the criterion’s own quote from the answer that raised the alert, to people who can open that call and its criteria, with its time in the call when that moment is known; without a quote the card says ‘No quote: event not found’ when what the criterion looks for was not found, or ‘Quote unavailable’ when that answer is gone or has no usable quote; notifications never carry it. For a rule on the attention flag the card shows the moment of the conversation the flag rests on — time, speaker, label and quote — when the analysis has pinned the flag to one moment and found its quote in the conversation, to people who can open that call; notifications never carry it either. Independently, a project-level team channel — a Telegram group, the org’s own connected Bitrix24 group chat, or an org-configured webhook — can receive a reduced alert summary (rule, severity, call category, record link) with no transcript quote or caller name/phone.
AI AssistantAvailablePro, Business, Scale, EnterpriseGrounded questions and answers about a call, about a CRM deal, lead, contact or company across its calls and chats, or about the analysed calls and chats you can see — narrowed by period, project, rep, type, category or customer — with quotes from the transcripts and playable timecodes.

UI

FeatureStatusPackagesWhat it does
Command PaletteAvailableAll packagesKeyboard-driven navigation entrypoint in the application sidebar.
Dark ModeAvailableAll packagesApplication theme mode support.
What’s New Release Pop-upAvailableAll packagesOne-time release notice shown at sign-in after a new version ships, in the app and inside the CRM placement.
UI AnimationsAvailableAll packagesMotion and transition layer for the application shell.

Notifications

FeatureStatusPackagesWhat it does
In-App NotificationsAvailableAll packagesNotification bell and dropdown for user-visible events.
Notification Channel PreferencesAvailableAll packagesPer-user notification channel settings (email, Telegram, webhook) and per-category subscriptions for external delivery. A personal subscription overrides the org’s per-role default; the org’s RBAC matrix still gates which categories a role may see at all. Telegram is connected with a one-click, one-time link to Aelo’s own platform bot — no chat ID or bot token entry. Org admins additionally set per-role category defaults in a role × category matrix.

Reporting

FeatureStatusPackagesWhat it does
Email DigestsAvailableAll packagesScheduled organization owner/admin/supervisor/rep digest emails backed by queues, templates, and unsubscribe tokens. Includes an alerts section — an aggregate rule/severity/count table for alerts below the instant-delivery severity threshold — shown only to roles whose RBAC-allowed categories include quality_alerts; the table has no per-record detail, so it never carries a caller’s name or phone number. The daily digest covers the 24 hours before it is sent; the weekly digest goes out at 08:00 in the organization’s time zone on its first day of the week (settings.organization_week_start, Monday by default) and covers the calendar week that has just ended, trending against the week before. The owner’s, admin’s and supervisor’s digests report the quality change in whole points — the rounded score minus the rounded previous score, as the unified dashboard shows it — not as a percentage; the rep’s digest reports My score and its change as the rep’s Mine tab shows them: the score of their own conversations as a whole number, and the change in whole points; their place in the team follows the Mine tab’s rule too: only reps with at least 5 scored conversations in the period are ranked and counted, and a rep with fewer gets no place line. The supervisor’s digest names the top rep and the rep at risk by the Team tab’s rules: only reps with at least 5 scored conversations in the period are rated, at risk is below 70, and a rep at risk is never named top rep. Delivery resolves per person: an organization-wide daily/weekly default (settable by a role holding organization.update; on when never configured) that each member may override for themselves, plus the unsubscribe link every digest carries. The daily digest of an organization owner (the whole organization) and a supervisor (their own projects) lists up to five objection reasons the team left unhandled the previous local day — reason names and calls unhandled out of calls where it came up, counted by the Objections screen’s code, never a customer quote or wording — with an org-tagged link to that screen on that day; it also gives the share of objections that could not be recognized, as the screen does, so it is absent only when nothing was left unhandled or the count could not be made. A member who holds an active narrow access grant (Settings → Team → Access) receives a digest built for the grant instead of the letter of their role: over the area of the grant (the whole organization, its projects, or the people of its departments) and only the sections its capabilities open — never records, quotes or audio, and rep names only with rep scores and ranking; nothing is sent when the sections the access opens have nothing to report for the period, and a rep holding a Group lead grant receives the department letter instead of their personal digest. The monthly Voice of Customer email follows the plan of the organization (Pro and up), while the daily and weekly digests keep arriving after a downgrade as long as the grant is active; revoking the grant returns the letters of the role.
Dashboard Quality BlockAvailableAll packagesThe first block of the unified dashboard: the average quality score over the scored conversations of the period, how many were scored and how many were not, the change against the previous period of the same length, and the score day by day. Every number opens what it rests on and, wherever the Records list can take its scope, the very conversations it was computed from — a supervisor with no project selected and more than 40 projects is told why instead. Supervisors see their own projects, reps their own conversations.
Unified DashboardAvailableAll packagesThe new dashboard of six tabs — Summary, Conversations, Sales, Quality, Team and Voice of Customer — with one filter panel (period, comparison with the previous period of the same length, projects, channel, demo data) kept in the address; a group lead sees which departments its view covers, as a scope, not a filter. Every block is a card with its number, its base, its period, the time the data was read and the change against the previous period, and states of its own; a block or tab the viewer has no capability for is not shown. Conversations: how many came in and where each is in its life cycle (missed calls a group of their own), coverage of what could be analysed, the missed-call share of inbound calls with an unknown direction counted apart, by day, structure by category, channel and direction and project, and the load by hour and weekday × hour in the viewer’s zone; each number explains what it rests on, and a life-cycle group opens its records for a viewer who may read them. Summary: the quality score of the period with its change, how many conversations were analysed, the open signals right now, a few theses of the period (quality, missed calls, analysis completeness, the most named competitor), one line per section the viewer has, a warning when little of what could be analysed has been analysed, and the latest conversations. Sales (Pro and up, shown locked below it): the deals with a conversation in the period and how they end — won, lost, open or outcome unknown — as the deal stands in the CRM, the average score by outcome, the share of conversations after which the deal moved to a later stage within 7 days and how fresh the CRM data is; aggregates only, a co-occurrence and never a cause. Team: a table of reps with their score, rated conversations and change (a rep with fewer than five rated conversations has no score), who needs help (a score below 70), who is improving (up three points or more), the distribution of scores, the workload by time on calls and, while Coaching is on, the notes and follow-ups of the last 7 days; a viewer with aggregates only sees no names and withheld small counts. Voice of Customer (Pro and up, as the Voice of Customer section): competitors, serious feedback, purchase barriers, market signals, conversation themes, needs, customer question subjects and decline reasons — labels and counts of the viewer’s scope, each with its own base, the change in percentage points, «few data» under five conversations, at most five rows and how many more, and a link to the section’s report; no client’s words; an export of the tab as a table of those labels and counts, read anew on the click, with the period, the scope and the demo setting (the customers’ wordings stay in the report’s export). Every chart of days and hours — conversations and the score by day, the load by hour and weekday × hour — has a table twin behind a «Table» button with the same numbers. Quality’s company criteria card lists every criterion — flag, score and choice — with its value, what a flag looks for, its calls as evaluated, unsure and not applicable, not evaluated as an upper bound, paused, archived and a wording changed in the period, and opens the criteria report on its own screen (/analytics/criteria) at that criterion. In Team, a name in the Reps table opens that person’s three most frequent dips for the period — the period’s top issues by scoring metric narrowed to the person, «in N of M» of their analysed conversations, with examples that open the conversations; periods up to 93 days. The same name opens «After feedback»: the person’s score per criterion over the 10 scored conversations before the supervisor’s latest feedback (a coaching note, a note on the call other than a correction, a review comment) and the 10 from it onward, n on both sides, the change shown where both sides have at least 3, and in words when there has been no feedback, too few conversations since, or too few before it. The channel filter applies to Conversations; Quality counts every channel and says so. Organization owners, administrators, supervisors and access-grant holders get it on /dashboard and in Bitrix24, where the six tabs replace the Overview. A rep gets their own view in the same shell, one tab «Mine»: their quality score with the change against the previous period, the skills to work on, its place among the colleagues with at least five scored calls (shown once it has five itself), its skills against the team, its frequent dips (the same block, counted the same way), its score after its latest feedback (the same block; demo notes are not its feedback), its personal bests and its supervisor’s notes. The platform owner keeps its dashboard, and so does an owner looking through a rep’s eyes.
Public Website And Product DocsAvailableAll packagesAstro marketing/legal site and Starlight customer-facing documentation under localized docs routes.
FeatureStatusPackagesWhat it does
Global SearchAvailableAll packagesSearch API and command-palette/search surfaces for finding product entities from the app shell. Includes search by meaning across calls and chats; how its search vectors are processed and kept is set out in the Privacy Policy and the DPA.

Coaching

FeatureStatusPackagesWhat it does
Call Quality By RepAvailableAll packagesPer-rep call quality scores and trends, the individual rep view, and the APIs behind them. Presentation is a table of scores, not standings: no ranks, no medals.
Coaching WorkspaceAvailableAll packagesSupervisor coaching notes, 1:1 coaching sessions, coaching stats, and AI-generated coaching insights. When a supervisor, admin or client leaves feedback on a rep’s call - a coaching note, a note on the call, or the overall comment added to a review that had none - the rep is notified in the app and by email (their personal notices, the Collaboration category: the email can be turned off with their own switch «Personal emails», and unticking the category in their notification categories turns the whole notification off, the Bitrix24 one included), and a rep linked to a Bitrix24 portal user also gets a Bitrix24 notification in that portal; each links to the call at the moment the feedback is about (the Bitrix24 one opens Aelo inside the portal), and neither the email nor the portal notification carries feedback text. The rep’s notes card links straight to the call.
ScriptsAvailableAll packagesSales script library, script parsing, project-script assignment, step/phrase management, adherence scoring, and org-level category bindings that auto-select a script per detected call category.

Settings

FeatureStatusPackagesWhat it does
Project Pinned Analysis ConfigAvailableAll packagesPer-project opt-out from org category-bound auto-selection: pin the project’s own prompt profile so every analysis in that project uses it regardless of the detected call category. Scripts have no pin — a project’s own script already outranks the binding (#702, #707).
Project Quality Criteria WeightsAvailableAll packagesPer-project weight (0–10) of each of the six quality criteria in the call’s quality score. By default every criterion counts equally (the plain average of the criteria rated in the call); a project with its own weights scores every call — the card, the call list, every dashboard aggregate and rep rating, the public API, routing and alert rules, digests and the CRM score field — with one weighted formula.
Organization First Day of the WeekAvailableAll packagesOrganization setting for the first day of the week (Monday through Sunday; Monday when never set, so existing organizations see no change), changed in organization settings by a role holding organization.update (client, admin). For every member it decides where a week begins: the Week period of the report screens, its navigation, label and return to the current week; the best week and the week streak in My achievements on the dashboard’s Mine tab, and the weekly series of the Criteria report and Voice of Customer trends; and the weekly email digest, which goes out at 08:00 in the organization’s time zone on that day and reports the calendar week that has just ended, trending against the week before.
Settings: Service StatusAvailableAll packagesSettings → Organization → Service status (#1341): how the organization’s own records move through processing, readable by the client and admin roles without contacting support. It shows the analysis mode (Automatic or Manual, read-only, with the system pause reason and moment), the queue now by status with the age of the oldest waiting record, processed / completed / stopped counts for a 7- or 30-day period, stage runs with average time, failures by stage with the last reason, stopped records by source (Bitrix24, Uspacy, other), and the ten latest stopped records with a per-row Retry button. A stopped record reaches the customer as a reason (no recording in the CRM, the recording did not arrive in time, the audio could not be downloaded, transcription / analysis / CRM delivery failed, a failure on our side), never as the raw pipeline text; that text goes to the platform owner only. The figures are the whole organization’s, so a reader whose access is narrower than the organization (a supervisor, a rep, a project-scoped grant) is refused with 403, and demo records are left out. Numbers only read: every action is a separate button on its own screen — start waiting records (Records), change the mode (Organization), import (Data Source → Import), access requests (Team & Access), and the monthly budget and top-up (Plan & Billing) only for a role with billing rights. A block whose data failed to load says so instead of showing a zero.
Settings: Access LogAvailableAll packagesSettings → Organization → Access log: who changed whose access in the organization, and when — member added or removed, role changed, project assignment, org structure, CRM account link, accounts merged, analytics access granted, changed or revoked. Newest first, with «show more», filtered by kind of event (members and roles, analytics access, projects, org structure). Visible to whoever sees the team list (client, admin), for the selected organization only. Each entry shows the action, the person it was about, the role before and after or the analytics preset, and who made the change; a person is named only while a member of the organization — the same name the team list shows — otherwise «former member»; Aelo staff outside the organization appear as «Aelo (platform)», and a change the system made (access withdrawn because its department or project went away) as «Aelo (automatically)». A change of several people (a project’s supervisor list, a CRM user sync, an org-structure import, a department head) names up to ten of them, with the total. Events are kept for 365 days. Not the routing log of Analysis Setup → Distribution, which lists how incoming records were routed.
Projects WorkspaceAvailableAll packagesProject list/create/detail/settings, project lifecycle actions, project stats, and project-scoped configuration.

Data

FeatureStatusPackagesWhat it does
ExportAvailableAll packagesExport controls for charts, analytics, and customer data views.

Prompting

FeatureStatusPackagesWhat it does
Prompt BuilderAvailableAll packagesPrompt profile editor and prompt preview tools. Profiles are organization-scoped; the preview may additionally be scoped to a project, and then it applies exactly what the runtime reads out of that project — the analysis language, the project’s name and description.
Custom Call CriteriaAvailableAll packagesQuestions asked of every conversation — did something happen (yes or no), a 0–100 score, or one of your answer options. An answer that points at something in the conversation comes with a verbatim quote. Answers appear in the call panel and the PDF report, filter the call list, feed the Company criteria card of the dashboard’s Quality tab and the criteria report and can be a field of an alert rule, whose in-app card then shows the quote of the criterion. Every plan includes them, up to its criteria limit; the built-in criteria worded by Aelo sit beside them outside that limit. Criteria are created and edited in the web app, and a new one can start from a ready-made template or from a description in your own words that the AI turns into a draft — either only fills in the form, and the wording is then changed freely; the check on recent calls lets you mark answers as wrong and get a suggested edit of the wording to accept or reject; in the embedded Bitrix24 app the answers appear in the call panel and the PDF report of a call, and the Company criteria card is a report only. Demo data comes with two demo criteria and sample answers on the demo conversations (demo data loaded before they were added has none) — shown only with the results, outside the criteria limit, and removed with the demo data. The demo conversations also carry answers of the switched-on built-in criteria of your organization; the built-in criteria themselves belong to the organization and stay when the demo data is removed.
Built-in Call CriteriaAvailableAll packagesEight criteria worded by Aelo — company named, next contact agreed, recording disclosed, satisfaction guarantee, rep profanity, a forbidden word from the organization’s own list (#2784), TCPA compliance on outbound sales calls and a data-privacy violation — that sit beside an organization’s own criteria in Analysis Setup → Criteria, outside the plan’s criteria limit. Their wording is fixed — the forbidden-words criterion takes the organization’s list of up to 100 words, and stays paused while the list is empty; the owner pauses them and narrows their scope within the limits Aelo set. Their answers feed the attention flag, the CRM report, the mapped Bitrix24 card fields Recording Disclaimer, TCPA Compliance and Data Privacy (1 passed, 0 failed), the dashboard’s Standard checks card, the call panel and PDF, the records filter and the alert gallery, and they are the only place the said / not said checks happen: the main analysis and the analysis profile no longer carry mandatory phrases, profanity, the recording disclaimer or the compliance block (a new organization gets them from code defaults — company named, next contact agreed and satisfaction guarantee for product-inquiry, purchase, scheduling and follow-up calls, rep profanity for all calls, recording disclosed paused until the customer turns it on). The data-privacy criterion (calls, organizations with a concrete jurisdiction) is active: its wording counts asking for card secrets and naming the customer’s data after the person who answered said they ordered nothing, not an ordinary order call to the customer. The satisfaction guarantee is active as well (#3137): it applies only when the customer asks about a return or exchange, says they may return the item, directly states a fear or doubt that it will not suit them, or the rep offers a return or exchange on their own in case it does not suit — choosing a size or fit and every other call answer not applicable, not “not said”; no built-in is paused by Aelo.

Access

FeatureStatusPackagesWhat it does
Team Members And InvitationsAvailableAll packagesUser, team, membership, invitation, role visibility, and invitation-acceptance workflows.
Embedded Access RequestsAvailableAll packagesBitrix24 embedded-user access request flow and platform/admin approval surfaces.
Org-Hierarchy SupervisionAvailableAll packagesA department head sees the records handled by everyone under them in the org tree — imported from a CRM or, for an organization without an import, built by hand — in addition to (not instead of) their assigned projects — for the record list, search, and every detail surface (card, transcript, analysis). Subordinates count whether or not they have an Aelo account: employees the import keeps as pending members (no account to link to) are matched by their CRM identity, qualified by the record’s own provider. The head still needs an account, because access is granted to a person. Demo data loaded from October 2026 on comes with a sample tree — a demo company with Sales and Customer support — whose demo employees are matched to their demo calls; removing the demo data removes it.
Narrow Analytics Access GrantsAvailablePro, Business, Scale, EnterpriseAn owner (client role) or an admin gives a supervisor or a rep an analytics grant that replaces what their role shows for analytics, and revokes it. Two presets: «Analyst» — aggregates over the whole organization or over chosen projects — and «Group lead» — aggregates, team scores, records and evidence (transcripts, audio) of chosen departments. A grant can be narrower or wider than the role: a Group lead grant lets a rep read colleagues’ records in those departments, an Analyst grant on the whole organization lets a supervisor without projects see organization-wide aggregates. In Settings → Team, an «Access» column shows each member’s grant; an owner or an admin assigns, replaces or revokes it there, or invites a new member with limited access in one step. While a grant is active the person sees analytics only as the grant allows; their role, project assignments and billing stay as they were, but an action on a project — editing, archiving or deleting it, its scripts, supervisors, alert channels, routing and delivery rules — goes through only for a project the grant covers (any project of a whole-organization Analyst grant, the chosen projects of a project-scoped one, none for a Group lead grant, whose scope is departments), and creating a project only with a whole-organization Analyst grant; reading a project’s scripts, routing and delivery rules stops at the same boundary — a project outside it is refused, and the lists show only the projects the grant covers; revoking returns them to the role. Deleting a project or a department — including a department an org-structure import drops — takes it out of every grant that names it at once: the grant keeps the projects or departments left, and a grant left with none is revoked, returning the person to their role. A Group lead also opens the page of an employee of those departments who has no Aelo account yet, as long as the organization has only ever connected that CRM through one portal. A grant rides only on a supervisor or a rep: changing such a person to owner or admin is refused until the grant is revoked. Every assignment and revoke is recorded in the audit log right after it is saved, which an owner or an admin reads in Settings → Organization → Access log; the entry is written separately from the change (best effort): if writing it fails, the change still takes effect without an entry, and the failure is kept in Aelo’s error log. A person who holds a grant receives the daily and weekly email digest and the monthly Voice of Customer email built for the grant instead of the letter of their role (see the Email Digests entry).

Onboarding

FeatureStatusPackagesWhat it does
SaaS Onboarding WizardAvailableAll packagesSaaS onboarding, quick context collection, compliance setup gate, first-login redirect, and preview flow.
Embedded Bitrix24 OnboardingAvailableAll packagesEmbedded auth/session, install/onboard status, embedded consent gate, Smart Process step, and embedded dashboard entry.