Skip to content

Settings

Overview

The Settings page is organized into grouped sections accessible via a sidebar. Available sections depend on your role:

  • My Account (all roles) — Profile, Notifications
  • Organization (Owner, Admin) — Organization, Team & Access, Access Log, Service Status, Plan & Billing
  • Integrations (Owner, Admin) — Data Source; API Keys — Owner only
  • Compliance (Owner, Admin) — Compliance Settings, Consent Management, Data Subject Requests

Evaluation profiles, criteria, sales scripts, and record distribution are configured separately — in the Analysis Setup section of the main menu, not in Settings (see below).

The Settings sidebar: My account, Organization, Integrations and Compliance

My Profile

All roles

Manage your personal account settings:

  • First Name and Last Name — two separate fields; together they are how your name appears across the platform
  • Email — your account email (read-only). It is the primary address of your sign-in profile: change it under your avatar menu → “Manage account”. A new address becomes your account address once it is verified and made primary — the next time you open Aelo (Aelo checks the address at most once every five minutes, so right after the change it can take up to five minutes); from then on, the emails that go to your account address arrive there. If that address already belongs to another Aelo account (for example, an invitation is waiting for it), the account address stays as it was
  • Role — your role in the organization, shown as a badge; to change it, contact an administrator
  • Language — interface language only (English, Russian, Ukrainian, Spanish, Portuguese (Brazilian)); it does not change the language of call analysis
  • Theme — not here: switch Light/Dark with the sun or moon icon in the sidebar footer

Profile language setting

Notifications

All roles

The page is a column of cards: 1. What counts as an event (the alert rules), 2. Who receives it — by default (what each role gets before a person changes anything), 3. Where it arrives (your channels, below), Team channels by project, What you receive right now and, for the Owner and Admin, Aelo tips and news.

Configure your personal notification delivery channels:

ChannelConfiguration
In-appAlways enabled, and not a switch on this screen. Notifications appear in the bell icon.
EmailA switch, plus an optional Custom email field; leave it empty to use your account email.
WebhookA switch, plus the Webhook URL and an optional secret for the HMAC signature; Aelo sends the notification data to your URL with HTTP POST.
TelegramPress Connect Telegram, then Start in the chat that opens (or enter the 6-digit code the bot shows). Use Disconnect to remove it.
Bitrix24 Group ChatA switch and a Chat ID. Shown only while Bitrix24 is connected to the organization.

Email, webhook and Bitrix24 group chat are switches; Telegram is connected and disconnected on its own. Below the channels, Daily digest, Weekly Reports and Personal emails are separate switches, and a shared Notification Categories filter controls which event types are delivered across all enabled channels. Changes are kept with Save Channel Settings. Not every role is offered every channel: a role that only receives personal notices sees just the digests and, while coaching is on, the Personal emails switch. A notification in the app is deleted 180 days after it was created, together with every user’s status of it (delivered, read, archived).

Feedback on your conversation. When a supervisor, administrator or the account owner leaves feedback on one of your calls or chats — a coaching note, a note on the call, or a review with a comment — you get a notification in the app and an email. The email does not contain the comment itself: it says who left feedback and on which conversation, and its button opens that conversation; for a call, at the moment the feedback is about. The comment is read in the app. If the same person leaves several comments on one conversation within 30 minutes, you get one email, and the rest arrive in the app. The email is sent by default. It is a personal notification, in the Collaboration category, which every role sees in its notification categories while coaching is on; with coaching off, neither the category nor feedback on your conversations in the “What you receive right now” summary is shown. Every user, including a rep, can turn the email off with the “Personal emails” switch in notification settings; it does not depend on the general Email channel. If your account has no email address (an account created from Bitrix24 can have none), the email cannot arrive: the settings say so next to the switch and show where to enter your address, and the “What you receive right now” summary shows how feedback on your conversations reaches you. Unticking the Collaboration category turns the notification off entirely: nothing in the app, no email and no Bitrix24 notification. Personal notifications never go to a Bitrix24 group chat or to a webhook. If your Aelo account is linked to your user in your company’s Bitrix24 portal, you also get a Bitrix24 notification: it likewise says who left feedback and on which conversation, without the comment, and its link opens Aelo inside the portal on that conversation, a call at the moment the feedback is about. It follows the same 30-minute rule. The “Personal emails” switch does not stop it; unticking the Collaboration category does, and you can also mute it in Bitrix24’s own notification settings. This works only when coaching is turned on for your organization.

Notices about money. A low, critical or negative balance, a crossed budget threshold and a failed auto-recharge are service notices: they reach the account owner and administrators in the app and by email whatever the Email switch and the notification categories say. Leaving Email off or unticking Budget & Billing does not stop them, so whoever holds the money learns that a charge failed. The email goes to the address entered for the Email channel while that channel is on, otherwise to your account address, or to the address you entered if the account has none — without an account address, the Email channel keeps that field on screen even while Email is off. A line under the notification categories says the same: money notices arrive whatever the Email switch and the categories say. The footer of such an email says how to change its address: in the notification settings, or — when it goes to your account address because Email is off — by turning Email on there and entering the address. With Email on, the other notices of the categories you ticked arrive by email too. The account address is the primary address of your sign-in profile: once changed and verified there, it becomes the account address the next time you open Aelo, and these emails go to it (see My profile). The emails that 80 % of the plan’s included minutes are used and that analysis is paused go to the same address, and their footer says how to change it in the same way. The “What you receive right now” summary shows these notices on a line of their own and warns when your account has no email address for them to arrive at.

Notification channel settings

What you receive right now

Aelo tips and news

At the bottom of the same page, for the account owner and administrators — separate from everything above it. The alerts and digests above are about your own account and keep arriving either way. These emails are about how to use Aelo, new features and plans. Subscribing is entirely optional.

Subscribe or unsubscribe with one click; the choice takes effect immediately and applies to your address only, never to a colleague’s. If your account has no e-mail address — a CRM portal user has none until the account is linked — there is nothing to subscribe, and the block says so instead of offering it.

Organization

Owner Admin

Configure organization-level settings:

SettingDescription
Organization NameYour company or team name
IndustryFree text, up to 100 characters (for example, “Business automation & CRM”)
Company DescriptionYour company, products or services and target audience, up to 2,000 characters. It is included in every AI analysis across all projects to improve accuracy
TimezoneDefault timezone for reports and timestamps. An organization that has not chosen one uses Europe/Kyiv
First day of the weekWhere the week begins for everyone in the organization: the Week period of the Analytics report screens and their weekly series (the Criteria report, Voice of Customer trends), the best week and the week streak in My achievements on the Mine tab of the dashboard, and the weekly email digest, which arrives at 08:00 organization time on this day and covers the week that has just ended. Monday by default
LanguageLanguage of emails, notifications and report labels. Not the interface language, not the analysis language.
RegionEurope (EU), shown for information. It is not a choice you can change here

The form ends with read-only totals (accounts including invited ones, projects, creation date) and a Save organization button. Data retention, analysis mode and the AI assistant sit below it and are saved separately.

The AI assistant switch below the form (Pro and above) lets the organization owner turn the assistant off for everyone in the organization, and on again, without contacting us. Admins see its state but cannot change it. The switch is the organization’s own choice: if Aelo has switched the assistant off for the organization at the platform level (for example under the contract or compliance requirements), the switch is locked and says so — turning it on again is then a request to support. During the Pro trial the assistant has a smaller ceiling: 3 questions a minute, 15 an hour and 30 a day (paid plans: 10, 120 and 300); the quota the assistant shows counts against that ceiling.

Organization settings form

Analysis mode: Automatic or Manual

The AI assistant switch

Data retention

Owner Admin

The Data retention block below the organization form sets how many days Aelo keeps your organization’s data. Recordings, transcripts, analyses, supervisors’ coaching notes, coaching sessions, AI assistant questions and deal states older than that are permanently deleted.

  • Period — 1 to 365 days. While the field is empty the platform policy applies, and the block shows it: a number of days, or that nothing is deleted by age. Once your own period is saved, the block shows that instead; Use platform policy clears the field.
  • Who changes it. Only the organization owner changes the period. An Admin sees the current period and the explanation, but no field to change it.
  • Shortening needs a count and a confirmation. When the new period is shorter than the current one, Aelo first counts what it would delete and shows those numbers in a Shorten retention? dialog. The period applies only after Delete and apply. If the count fails, the period does not change. Lengthening the period, or shortening it without deleting anything, saves without asking.

Data retention below the organization form

Team & Access

Owner Admin

Manage your team in one section with these tabs:

  • Members — current team members, their roles, and pending access requests
  • Invitations — invitations you have sent and their status
  • Org structure (Owner) — departments, their heads and members; see Team

See Team for the full guide to roles and permissions.

Access Log

Owner Admin

Who changed whose access in the organization, and when — newest first. Each entry names what happened, the person it was about, the change itself (for example, the role before and after, or the analytics access preset) and who made it. Filter by type:

  • Members and roles — a member added or removed, a role changed, accounts merged, a link to a CRM account changed
  • Analytics access — analytics access granted, changed or revoked, and a member removed together with their analytics access
  • Projects — project assignments changed
  • Org structure — departments, their members and heads changed, including an import from the CRM

A person is shown by name only while they are a member of the organization: someone who has left appears as Former member, a change made by the Aelo platform team as Aelo (platform), and a change Aelo made by itself (for example, analytics access revoked because its department was removed) as Aelo (automatically). A change that moved several people at once — a project’s supervisors, a CRM user sync, an org-structure import — lists who was affected. Moving a department under another one lists as affected the heads of the departments above it who gained or lost sight of its records. When two accounts of one person are merged, events from before the merge name them by the remaining account. Events are kept for 365 days.

This is not the routing log in Analysis Setup → Distribution → Log, which lists decisions about incoming records.

The Access log with its filters

Service Status

Owner Admin

Settings → Organization → Service status shows how your organization’s own conversations move through processing: what is in the queue now, what was processed over the period, and what stopped and why. You see it without asking support.

The figures cover the whole organization, so the section answers only for a user who sees all of it — a user whose access is limited to part of the organization gets no figures. Demo records are not counted. Switch the period between 7 days to now and 30 days to now — a rolling window up to this moment, unlike the full days of the dashboard; the screen shows when it was last updated.

  • Analysis mode — Automatic or Manual, read-only here. When the system switched the organization to manual because funds ran out, the block says so and since when. Topping up does not switch the mode back by itself — see Settings → Organization.
  • Queue now — how many records are in processing, split by status (Received, Waiting for the recording, Waiting for the chat to close, Transcribing, Transcribed, Analyzing, Analyzed, Sending to CRM), and how long ago the oldest of them arrived. The queue is “now” and does not depend on the period.
  • Received in the period — how many records arrived in the period (Received) and, of those, how many are Done and how many Stopped. It counts records by when they arrived; the stopped blocks below count by when a record stopped, so a record that arrived earlier and stopped in the period is in them but not in this count.
  • Processing stages — how many runs each stage had (Transcription, Analysis, Sending to CRM, Orchestration) and how long a run took on average.
  • Stage failures — how many runs of each stage failed (“3 of 120”) and the reason of the last failure.
  • Records stopped in the period, by source — Bitrix24, Uspacy or other sources.
  • Records stopped in the period, latest — the ten most recent: when, which record (click to open it in Records), its project and the Reason, with a Retry button on every row.

A stopped record is shown by its reason, never by the technical text of the failure: No recording in the CRM, The recording did not arrive in time, The audio file could not be downloaded, Transcription failed, Analysis failed, Sending to the CRM failed or A failure on our side. The Overview and Errors tabs use the same reasons. They belong to the Admin dashboard: a role dashboard that only the platform owner opens now, for an organization in the admin console (the Organization View is the default there); an organization’s admin gets the new dashboard whatever the platform owner’s switch. The technical text is shown to the platform owner only.

Retry queues the record for processing again. If the organization is in manual mode, or automatic analysis is switched off in the record’s project, the record is not run — it waits to be started, and the message says so. A record of a Uspacy installation whose processing is paused or withdrawn is not retried at all: the message says the recording is stored but not analysed until processing of its source is resumed.

Numbers only read. Every action is a separate button that opens its own screen: Start waiting records (Records), Change analysis mode (Organization), Import from CRM (Data Source → Import), Access requests (Team & Access). Monthly budget and Top up balance (Plan & Billing) appear only for a user with billing rights — the Owner.

A block that could not be loaded says Could not load this block. instead of showing a zero; if the whole screen fails, it says so and offers Retry. For a user whose access is limited to some projects the screen does not fail: it says that the service status covers the whole organization and is not shown to them, and offers no Retry.

Service status: actions, analysis mode, the queue and the period's figures

Plan & Billing

Owner

Manage subscription and billing (tab by tab in detail on the Plan & Billing page):

  • Current pricing plan details
  • Weekly usage summary (per-minute billing)
  • Balance and charges history
  • Low balance notifications
  • Each figure names its window: Minutes left now is what remains at this moment, Minutes used this plan cycle counts from the start of your plan’s billing cycle, and the monthly budget (Budget left this month) counts per calendar month (UTC) and resets on the 1st. Remaining minutes and remaining budget do not follow the period selector on the usage tab.

Pro trial

A free (pay-as-you-go) organization gets every Pro feature for 14 days, once per organization: the trial is never repeated. Starter and the other paid plans do not get it.

  • Start. With your organization’s next analysed call or chat. Demo records, the re-analysis of an already analysed record and Aelo’s own service checks do not start it.
  • What opens. The organization is treated as Pro wherever Aelo decides what is locked: Voice of Customer (including customer questions, decline reasons and conversation themes), the AI assistant, deal state (including the sales methodology step, the CRM task and the draft message), narrow analytics access grants, public API keys (normally Starter and above) and the Pro dashboards and analytics.
  • What does not change. The 100 included minutes a month, the price per minute (6.5¢) and the criteria limit of your real plan.
  • AI assistant. A smaller ceiling than on paid plans: 3 questions a minute, 15 an hour and 30 a day (paid plans: 10, 120 and 300). The quota the assistant shows counts against the trial ceiling.
  • While it runs. A banner on every screen of the web app and of the Bitrix24 embedded screens (except the Aelo tab of a CRM card): “Pro trial: 14 days left”, “Pro features are open until {date}.” The menu items the trial opens carry the label “Pro · trial”. The monthly Voice of Customer email is sent, and the deal-state comment is posted to the deal or lead timeline in your Bitrix24 or Uspacy.
  • Before it starts. A locked Pro screen shows a note that 14 days of Pro features start with your next analysis.
  • After it ends. Right at the end time shown in the banner, with no delay. Data already produced stays stored, but the Pro screens are locked again with the note “The trial ended on {date}”. New conversations no longer get Pro processing: no new customer questions, decline reasons or themes, no new deal states and no new deal-state comments in the CRM (comments already posted stay there). Analytics access grants already assigned stay in force and can be revoked, but new ones cannot be given. Public API keys are refused again: a new key cannot be created (403 with a message to change the plan), and a request with an existing key gets 403 tier_not_eligible. The AI assistant is locked.

To keep Pro features after the trial, the account owner changes the plan in Plan & Billing.

Analysis Setup

Owner Admin

Evaluation profiles, criteria, sales scripts, and record-to-project distribution no longer live in Settings — they’re configured in a separate Analysis Setup section of the main menu (/analysis-setup). The overview opens with how many steps are configured, each step marked as configured, needing attention, or running on defaults — or as not checked, when its state could not be read (the overview then offers to check again). Below it is the path a record takes: from the source through Distribution → Categories and Profiles → Criteria → Script rules → Sales methodology → CRM Updates to the result. Every step already works on its defaults; open the one you want to change. On a step screen, a compact strip of numbered steps leads to the neighbouring steps and back to the overview.

  • Distribution — which project a new record lands in. Distribution rules apply only to Bitrix24 calls and chats, imported ones included; how the project is chosen for other sources is in Projects. The step screen has a Rules tab (auto-assignment conditions, plus the fallback project) and a Log tab (per-record decisions — useful for debugging the Bitrix24 integration; an entry is kept for 90 days, and one for a call or chat still waiting to be processed until it is).
  • Categories and Profiles — the binding matrix that assigns evaluation profiles and scripts to record categories, plus Profiles and Deal Stages tabs. See Evaluation Profiles for the full guide.
  • Criteria — questions asked of every conversation (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 quote. The Owner creates and edits them; an Admin sees the list read-only. Beside them sit the built-in criteria worded by Aelo, which do not count toward your plan’s limit. See Criteria for the full guide.
  • Script rules — sales scripts and adherence scoring. See Scripts for the full guide.
  • Sales methodology — on Pro and higher plans, which include the deal state: the sales methodology of each CRM pipeline (a standard framework plus optional company rules) that the advice on a deal follows; the Deals screen links here too. The Owner edits it; an Admin sees it read-only. See Deals for the full guide.
  • CRM Updates — Bitrix24 and Uspacy organizations. For Bitrix24: the delivery destination, the field table for analysis results and the “What else to do in the CRM” list. For Uspacy the step exists on any plan: the “Report as a comment” and “Report as a note” rows and, on Pro and higher plans, which include the deal state, also “Deal state comment”. Changes are saved with one panel at the bottom of the step. On the overview, the step is marked “delivery goes to another CRM” when Aelo delivers analysis results to a CRM other than this source — the step’s settings then write nothing — and “needs attention” when the delivery CRM is disconnected; if the plan check could not be read, the step is marked not checked rather than shown as on. The connection status is not in the step but on the “Connection” tab of the “Data Source” section. See Bitrix24 Integration for the full guide.
  • Report language — the language the AI writes the analysis in (summary, insights, recommendations). Auto (default) writes in the language of the conversation; otherwise pick English, Russian, Ukrainian, Spanish, or Portuguese (Brazilian). Quotes from the conversation are never translated. Configured per project, in the Common settings section of the Analysis Setup overview.
  • Recognition language — the language spoken in the recordings. Auto (default) detects it per recording, and detection is not free: on a benchmark of 20 real Ukrainian calls it labelled two of them Bulgarian, and the hint changes the recognised text itself, not only the language label. Set the language whenever the project’s calls are in one language; leave Auto when the language varies from call to call. Lives in the project’s own settings, on the Overview tab, next to the report language (see Projects).

Language codes follow ISO-639-1 (en, uk, el); languages without a two-letter code use ISO-639-3 (yue, fil, cmn, ast, nso). Recognition supports 90+ languages — the language is picked from that list in the project’s settings.

Analysis Setup: how many steps are configured

Report language by project

Transcript only mode

For a project whose calls and chats you need as text, without analysis. Turn it on in the project’s settings, on the Analysis & Quality tab: the Transcript only switch sits under Automatic analysis after transcription. It applies at once — it does not wait for Save — and it is available on every plan, Pay as you go included. While it is on, the automatic-analysis switch is locked; your choice is kept and comes back when you switch the mode off.

  • What runs. A call is transcribed, categorized and its speakers are identified; the transcript is indexed, so search and the AI assistant still find it. A chat is categorized the same way.
  • What does not run. The analysis (summary, scores, insights), criteria, script rules, Voice of Customer and deal state. The record is marked “Transcript without analysis”.
  • Price. A call minute counts as 0.25 of a minute: a call of 5:10 draws 1.30 minutes instead of 5.2. The reduced minutes come from your included minutes, bonus minutes or wallet, in the same order as any other minutes, and are rounded up to 0.01 per record. A chat costs a quarter of the chat price.
  • Analyze later. Open the record and click Analyze, or select records and click Analyze transcripts (owner or admin; it works in manual mode too). The analysis is charged as a full minute (the full chat price) on top of the quarter already charged — 1.25 minutes for every minute of the call (6.5 for the 5:10 call above), with no credit for the first charge. The price is shown before anything starts, and a start that would cost more than shown does not run. Re-analyze of such a record, and Retry of one that finished, are refused with a pointer to Analyze, so the minutes are not spent twice by accident; Retry of a record that failed runs it again without analysis.
  • Switching the mode. Switching it on or off changes the price of what comes next only: records already charged keep their charge. Switching it off returns the project to its previous automatic-analysis setting.
  • CRM import. The price estimate before an import counts a quarter of a minute only when every project of the organization is in this mode; otherwise it shows the full minute as an upper bound, and the actual charge can be lower.
  • Export. Export to MD works as for any record (see Conversations). The speaker roles come from the analysis, which such a record does not have: if the transcript cleanup did not name the speakers, the labels stay generic (speaker_0, speaker_1). Aelo sets no limit on the number of records in one file: the transcripts are loaded in your browser, five at a time, so a very large selection takes a while.
  • Uspacy. The Aelo screen in Uspacy says “Transcript only” for such a project, and “Manual analysis” for a project whose automatic analysis is off without the mode.

Data Source

Owner Admin

Connect your telephony or CRM system in one section with two tabs:

Connection

With no source connected, the tab opens the Connect data source screen, which groups the sources by how they connect:

  • Telephony — webhook + API key: Stream Telecom, Binotel, Unitalk (beta), Ringostat (beta).
  • CRM — OAuth, app in your account: Bitrix24.
  • Direct upload — Public API (calls uploaded programmatically with an API key; keys are issued by the account owner and managed in Settings) and My system isn’t listed (tell us your stack and we estimate a connector).

How you connect depends on the source:

  1. Bitrix24 — the card opens the Aelo app page in the Bitrix24 Marketplace in a new tab. You install the app in your portal; there is no domain or credentials form in Aelo.
  2. Telephony — enter the credentials the vendor needs (Stream Telecom: username, password and API key; Binotel: key and secret; Unitalk and Ringostat: API key) and press Continue. Aelo then tests the connection, shows how to set up Real-time call capture, and offers to import existing records (Import records now or skip).

Once a source is connected, the tab shows it with an Active badge, its domain (for a CRM) and the connection date, with Change and Disconnect buttons.

Import Records

Import existing calls and chats for a date range you choose (From date to To date; some sources cap how many days one import can span) to pre-populate Aelo projects with conversation history. A cost estimate is shown before the import starts. Bulk import exists only for sources that support it; for the others, such as the Public API, the tab says so — records arrive as you send them.

Which analysis results land in which CRM fields is configured separately — in Analysis Setup → CRM Updates (see above); the field table there exists only when Bitrix24 is connected.

Data Source connection screen

Compliance

Owner Admin

Consent and data-subject tooling for regulated teams:

  • Compliance Settings — a screen titled Compliance: the organization’s recording approach, jurisdiction and legal basis; changes are saved automatically. At the bottom is the Compliance Confirmation block: until the owner or an admin clicks Acknowledge controller responsibility, recording processing is paused
  • Consent Management — the organization’s confirmation of recording processing and its audit trail, with Withdraw (where intake does not depend on this confirmation, withdrawing it on its own does not stop intake of recordings, and the screen says so beside the button); below it, a separate read-only record of the Terms and Privacy Policy acceptance by the account’s users and their marketing-email choice — account evidence, not participant consent. For a connected Uspacy portal the section also holds the Uspacy organization processing card: Pause, Withdraw instruction and Reauthorize processing
  • Calls are not being received — a notice on every screen while Aelo takes no new records: the consent setup is not confirmed, or a CRM’s call processing is not authorized (for Uspacy, for example, after processing was paused or withdrawn). Everyone in the organization sees which CRM stopped and who can fix it; the account owner or an administrator gets a link straight to Consent Management. If the app was removed from the portal and Aelo lost its access, the notice says so and asks to install the app again first. A removed app is not reported while another CRM of the organization still brings records
  • Data Subject Requests — a register of GDPR data subject requests. New Request records a request: its type (access, erasure, rectification or objection) and the subject identifier (email, phone, name or external ID). A new request is Pending; the Approve and Reject buttons move it to Approved or Rejected. Aelo neither searches for, exports nor deletes data for a request — an approved request is carried out by hand, together with Aelo support

Compliance Settings: recording and notification approach, jurisdiction and legal basis

Consent Management: the organization's consent confirmation

Data Subject Requests

Access by Role

SectionOwnerAdminSupervisorRep
Profile✅✅✅✅
Notifications✅✅✅✅
Organization✅✅❌❌
Team & Access✅✅❌❌
Access Log✅✅❌❌
Service Status✅✅❌❌
Plan & Billing✅❌❌❌
Analysis Setup✅✅❌❌
Data Source✅✅❌❌
Compliance✅✅❌❌

Tips & Best Practices

  • Set your timezone correctly — it affects all timestamps in reports and alerts.
  • Configure notification channels early — don’t miss critical alerts.
  • Test CRM integration thoroughly before connecting the source on production projects — capture starts automatically once it is.
  • Review Analysis Setup → Distribution → Log periodically to ensure distribution rules work as expected.