Skip to content

Dashboard

Overview

The Dashboard is your landing page after login. It opens from the Overview menu item, and the page title is Dashboard (My work for a rep). It has the same layout for everyone and shows what your role and access allow:

  • Owners, administrators and supervisors get six tabs: Summary, Conversations, Sales, Quality, Team and Voice of Customer. A supervisor sees only the projects they are assigned to.
  • Reps get one tab, Mine, with their own results — see Mine.
  • A narrow access (for example Analyst or Group lead) decides which tabs and blocks a person sees — see What you see depends on your access.

In the Bitrix24 app the six tabs replace the Overview tab — see Bitrix24.

Every block is a card, and every card shows the same things: the number, what it rests on (select What the number is made of), the period, the time the data was read, and the change against the previous period of the same length. A card that has no data says so, a card that failed to load offers Try again (a failed read is never shown as 0), and a card that you cannot have is not shown at all. Cards lead on to the full reports (Report →) and to the screens where the thing is fixed (Alerts →, Review queue →, Coaching →).

The tab tells what it is for. Each tab starts with a first layer of three to four cards, and the rest is grouped into sections you reach with the chips under the tab’s name.

Weeks. The dashboard’s periods are whole days (see Filters). The weekly email digest and the best week and the week streak in My achievements on Mine start the week on your organization’s first day of the week — Monday unless it is changed in Settings. The digest and My achievements cut the week at midnight in the organization’s time zone. The Coaching activity block on Team is not tied to this setting either: it always looks at the last 7 days. After the first day is changed, the next weekly email covers the new calendar week, so the days between the old and the new week may fall out of the weekly emails once.

Filters

One filter panel sits above the tabs and applies to all of them. The tab and every filter are kept in the page address, so a link, Back and a reload bring you to the same screen.

  • Period — the last 7 full days (the default), the last 30 full days, the last full quarter, or custom dates (at most 366 days). A full day is one that has ended: today is not in the period.
  • Comparison — with the previous period of the same length (the default) or no comparison.
  • Projects — one or several. With none selected you see all the projects you may see: all of the organization for an owner, only your own projects for a supervisor.
  • Departments — for a Group lead the panel says which departments the view covers, for example All of your 2 departments. It is a scope, not a filter.
  • Channel — calls, chats or both. It applies to Conversations and to the Summary figures built from it (analysed and coverage, the share of missed calls, the conversations received per section, Latest conversations); Quality, Team, Sales and Voice of Customer count every channel, and a quality or voice number shown next to filtered figures says so.
  • Demo data — show or hide the sample data of a new organization.

Summary

The first tab answers “how are we doing and where to look”.

  • Conversation quality — the average quality score of the period (0–100) with its change.
  • Analyzed — how many conversations were analysed, out of those that could be analysed and out of all received.
  • Open alerts — alerts not yet acknowledged or resolved right now (the period does not apply), with a link to Alerts.
  • Highlights of the period — a few theses in plain words: the quality score, the share of missed inbound calls, how little of what could be analysed was analysed, and the competitor named in most conversations. If nothing stands out, it says so; if some data could not be read, it names what is missing.
  • By section — one line per section you have: how many came in, the score, the reps rated and those who need help, the deals, the conversations with business analytics.
  • Analysis completeness — a warning when only a small share of what could be analysed has been analysed, with the reasons for the rest.
  • Latest conversations — the most recent conversations of the same scope, each opening in Records. It is shown to those who may read conversations.

Conversations

How many conversations came in, where each of them is, and when the load peaks. The Channel filter applies here.

  • Received and processed — every conversation that came in during the period, by where it is now. Each one is in exactly one group, so the groups add up to the number received: analysed, waiting to be started (manual analysis mode, insufficient balance, or a Uspacy portal whose processing is paused or withdrawn), too short to analyse, no conversation recorded (for example, the CRM has no recording of the call), still in progress, a processing error, and missed calls as a group of their own; conversations that fit none of these are shown as Other statuses. A group opens its records for those who may read them. Coverage is analysed out of what could be analysed: the received less the missed and the too short.
  • Missed Calls — the share of missed inbound calls, out of all inbound calls, missed or not. Missed calls whose direction is unknown are counted apart and are not in the share. The change against the previous period is in percentage points (pp). The card also splits out the missed outbound calls — the ones the customer did not answer — and opens each part’s records; the Missed calls report uses the same definition. In Bitrix24, an outbound call under 15 seconds that Bitrix24 does not mark as missed is counted as too short to analyse, not as a missed one.
  • Conversations over time — a bar per day, with the daily average, the busiest day and the days without conversations. A day with none is a zero, not a gap.
  • Conversation categories, Channels and directions and Conversations by project — the structure of what came in.
  • Load by hour and Day × hour — when conversations come in, in your time zone (the card names it).

The cards lead on to the Call Statistics and Missed Calls reports.

Sales

Pro and up Beta

How the deals that had a conversation in the period end. The tab is a beta: its calculations may still change. The tab is available on Pro and up; on a lower plan it shows a plan screen instead of numbers. While an organization has only demo data, the tab shows the demo deals so you can see how it works.

  • Deal outcomes — the deals with at least one conversation in the period: won, lost, open, or outcome unknown (Aelo has no outcome from the CRM yet). The outcome is the deal’s current stage in the CRM at the last sync, not “closed in the period”, so there is no comparison with the previous period. The four rows add up to the number of deals.
  • CRM freshness — how fresh and complete the CRM data behind the tab is: the last outcome sync, the deals with no outcome yet, and how many calls are tied to a deal, a lead or to nothing.
  • Outcome × average score — the average quality score of the period’s conversations by the deal’s outcome, shown from 5 scored conversations.
  • CRM stage × share advanced — the share of conversations after which the deal moved to a later stage within 7 days, by the stage it was at during the conversation. The check runs 7 days after the call, so the most recent calls are still waiting for it.
  • Contact number per deal — which contact of the deal’s whole life fell in the period.

Outcomes and stage movement need stage-aware scoring to be on and a CRM that reports outcomes (Bitrix24). The tab shows a co-occurrence, not a cause: a number next to an outcome does not mean the conversation decided it. There are no amounts on this tab.

Quality

How conversations go and what to review. It leads with the Conversation quality block.

  • Conversation quality — the average quality score over the period’s scored conversations, how many were scored out of those analysed, and the change against the previous period. A conversation without a score is not counted as zero: when nothing was scored, the block says so instead of showing 0. Select the number to see whose conversations were counted: the whole organization or the selected projects for an owner, the supervisor’s own projects for a supervisor.
  • By day of arrival — one bar per day of the period, by the day the conversation reached Aelo (not the day of the call); a day without scored conversations stays an empty place. Select a bar to see that day on its own.
  • Open records — opens Records with exactly the conversations behind the number or the day: the same period, scored only, the same projects. A supervisor with no project selected and more than 40 projects sees why the list cannot be opened instead of a wider list. Inside the Bitrix24 app, Records opens in the web version, in a new tab.
  • Needs review — the conversations with an AI attention flag or a score below 60, with a link to the Review queue.
  • Skills that dropped and Skills — the two skills that fell most against the previous period, and every skill with its score, the number of rated conversations and the change (a skill needs at least 5 rated conversations in the period, and in both periods for a change), next to your company’s target when there is one.
  • Script adherence and Missed script steps — the script steps the team most often does not complete, each with its share and the number of conversations it comes from. A step counts as not completed when not every required criterion matched, so half-done steps are in it too; conversations that did not need the step are not counted. Report “Script Steps” → opens the Script steps screen: all steps of every script, who misses them and which criteria are behind it. The link is there for a period of up to 93 days; inside the Bitrix24 app it opens the web app in a new window.
  • How objections are handled — the objection reasons your team most often leaves unhandled. Every objection is sorted into one reason from a fixed list (price, not now, delivery and availability, and so on), so one reason is counted together however customers phrase it. Counts are conversations: “unhandled in 12 of 20 conversations”. A reason the team handled in every conversation stays on the list with 0 % unhandled, so you can see it came up and was dealt with. The share that could not be recognized is shown at the bottom of the card. Report “Objections” → opens the Objections screen: every objection customers raised, how often and in their words, and the team’s best answers. The card is shown to those whose access includes Voice of Customer figures.
  • Standard checks — the share of calls that passed each standard check in the period: Recording disclaimer, TCPA checklist and Data privacy. The shares are counted from the answers of the matching built-in criteria — “Disclosed call recording”, “Met TCPA requirements” and “Broke personal data rules” — and, for calls analysed before the criteria that have no answer from one, from the older analysis field (the recording disclaimer counts there only when a compliance assessment is present). For data privacy, “passed” means no violation was found. Calls where the check was not applicable or the model was unsure are left out of the share. If a check is paused by Aelo, the card says so: new calls are not evaluated by that check, and any share shown covers earlier calls. The card reads only the most recent calls and says so (“Most recent calls only.”) when there are more. It is an AI assessment, not a legal determination.
  • Feedback on analysis quality — how users rated the analysis: the number of ratings and the share rated low (2 stars or fewer).
  • Attention Score — a card with the method only. The calculation is not final yet, so it shows no number.
  • Company criteria — every criterion of your organization with its value: for a yes/no criterion the share, for a score its average, for a choice its answers. Each shows what it looks for (it triggers when something is found or when it is missing) and how its calls divide: evaluated, no answer (the model could not answer with confidence) and not applicable; not evaluated is an upper bound (some calls are still processing, the criterion was paused, or its step did not run). A paused criterion, an archived one and a change of wording in the period are marked. Open in the report opens the criteria report at that criterion.

The criteria report

The criteria report is a screen of its own: Analytics → Criteria Report, available while criteria are on. It shows every criterion with how it answered over the period; open one to see it by day or week, the distribution of its answers and a table by rep. An answer in the distribution, a number in the table by rep and, for yes/no and score criteria, a bar of the trend open the calls behind them. A row is one person: a CRM id and the Aelo account of the same rep are one row, and the same id in two CRM portals is two rows (marked with their portal when the names match). The number in a row combined from several ids, or one whose id also belongs to another row, is plain text, not a link. Supervisors see only the projects they are assigned to.

The list of criteria in the Criteria Report

One criterion opened: answers by week, their distribution and the table by rep

Team

Who is doing fine and who needs help. A supervisor’s figures cover only their own projects. With no project selected in the filter, that means all of their projects — never the whole organization. A supervisor with no assigned projects sees a note saying so. The supervisor’s daily and weekly email digest counts the same projects (a person with a narrow access sees what the access allows and receives a digest built for that access); the daily one also lists the objection reasons the team left unhandled the day before (see Objections). The digest names the top rep and the rep at risk by the rules of the Team tab, one row per person: only a rep with at least 5 scored conversations in the period is rated, and a rep is at risk when their score is below 70. The top rep is the highest-scored rated rep who is not at risk; the rep at risk is the first one the tab lists under needs help — the lowest score, and on a tie the one with more talk time. With nobody at risk the letter has no at-risk line, and a rep at risk is never named top. The score is rounded as on the tab, and namesakes from different CRM portals carry the portal’s name. It covers its own period, so the names can differ from the screen.

  • Reps — a table with each rep’s score, the number of rated conversations and the change against the previous period. A table of scores, not standings: no ranks, no medals. A row is one person: a CRM id linked to a rep’s Aelo account is one row with that account, with the calls and score combined and the account’s name. Without such a link each CRM portal keeps its own row, so the same id in two portals is two rows. A rep with fewer than 5 rated conversations has “few ratings” instead of a score and is in none of the rules below.
  • Who needs help — rated reps with a score below 70, with a link to Coaching.
  • Improving — reps who rose by 3 points or more against the previous period, rated in both.
  • Rep score distribution — how many reps fall into each score range (90–100, 80–89, 70–79, 60–69, below 60). An empty range is a zero, not a gap.
  • Rep workload — conversations and time on calls per rep, the top of the list by time on calls.
  • Coaching activity — shown while Coaching is on. Four rows: Notes sent, 7 days; Follow-ups pending now — scheduled coaching sessions dated from the start of the last 7 days on, upcoming ones included; Average response time — in minutes below an hour, otherwise in hours; from booking a session to the date of the held session, over sessions with the “Completed” status booked in the last 7 days (none — “No completed sessions in the last 7 days”); Notes sent, all time. The block does not follow the dashboard’s period and filters — only the demo data setting — and leads to the Coaching screen.

Select a name in the Reps table to open two blocks about that person:

  • Rep’s frequent dips — the three most frequent dips for the period: the scoring criteria most often marked for improvement in their analysed conversations. Each dip shows how many of the person’s analysed conversations it occurred in (“in 3 of 7”) and up to two examples; an example with a quote expands it, and each one opens the conversation. Examples are shown to those who may read conversations and their quotes. Select the name again to clear the choice. When two rows share a name, the row of a rep with no Aelo account shows their CRM portal after it (Ivan · portal.bitrix24.ru), so you can tell whose calls it holds. The period can be up to 93 days; for a longer one the block asks for a shorter one. A supervisor counts only the conversations in the projects they are assigned to, so their figures for a person who also works elsewhere can be smaller than the ones the person sees in Mine.
  • After feedback — how that person’s score per criterion changed after the supervisor’s latest feedback: the average over the 10 scored conversations before it and the 10 from it onward, with the number of conversations (n) on each side. Feedback is a coaching note about the person, a note on their conversation other than a correction, or a review comment — left by someone other than the person (feedback from Aelo staff does not count). A criterion shows the change in points only when both sides have at least 3 scored conversations; otherwise its row says “too few”. If there has been no feedback yet, fewer than 3 scored conversations since it, or no criterion with 3 on both sides, the block says so instead of a table. The conversations are counted from the feedback date, not over the selected period; the selected projects and the demo data setting still apply. A supervisor counts only the conversations in their projects.

A viewer whose access does not include rep scores sees the table of reps as unavailable, and the names open nothing.

Voice of Customer

Pro and up

What customers say, across the conversations of the period. The tab is available on Pro and up, like the Voice of Customer section; on a lower plan it shows a plan screen. Every card names its base — how many conversations it is counted from — and leads on to the matching report.

  • Competitors, Serious feedback, Purchase barriers, Market signals, What customers talk about, Product and service, Customer needs, Customer questions and content gaps and Why customers decline — labels and counts of your scope. A row is marked up or down against the previous period only when its share moved noticeably (by at least 3 percentage points and by half again, with 30 or more conversations in both periods); Purchase barriers has no comparison. Each card shows “not enough data” when it rests on fewer than 5 conversations, at most five rows and how many more there are. There are no customers’ words on the tab: only labels and counts.
  • Export — the whole tab as a table of those labels and counts, read anew on the click, with the period, the scope and the demo setting in the file. Customer wordings are exported from the report.

When the scan of a very large period is cut, the card says the data is incomplete instead of showing an empty list. Competitor names are merged through your competitor glossary — see Voice of Customer.

Mine

Rep

The rep’s own view: one tab with the numbers about your own conversations only.

  • My score and My progress — your average quality score with the change against the previous period, and how many of your conversations were scored. When nothing was scored in the period, the tab says so — it is not a score of zero. Your daily and weekly email digest reports My score the same way: the whole number and the change in whole points, for the digest’s own period.
  • What to improve — the skills below the focus line in your scored conversations, with your score and the target. The tips come from templates, not from a personal AI answer.
  • My position — your place among the colleagues with at least 5 scored conversations in the period, shown once you have 5 yourself.
  • My skills and the team — your score per skill next to the team average. The team average shows no names and nobody else’s scores.
  • My frequent dips — the same block a supervisor sees for you in Team, counted the same way, over your own conversations.
  • My score by day — one bar per day of the period.
  • My achievements — your best conversation, best week and the streak of weeks scoring 80 and above, over the last 26 weeks (not the dashboard’s period).
  • After feedback — the same block as in Team, for the latest feedback to you.
  • Personal coaching and Supervisor notes — shown while Coaching is on. Personal coaching lists your own coaching meetings in the selected period: the date, who held it, the status (scheduled, completed or cancelled) and the meeting’s text; the latest five are listed (“Showing N of M”). Only meetings where you are the person being coached appear, and the period ends at the start of today, so today’s and upcoming meetings do not show until the period has moved past them. Projects, channels and the demo setting do not apply to meetings. Supervisor notes shows the notes your supervisor left for you, all time.

Charts as tables

Every chart of days and hours — conversations by day, the quality score by day, the load by hour and day × hour — has a Table button under it. It opens the same numbers as a table, which is easier to compare and to read with a screen reader. The chart stays as it is; the table is closed until you open it.

What you see depends on your access

The dashboard offers a block only to someone who may have what is behind it; the server enforces the same rules on every read. A tab with no block you may see is not offered.

  • By default, the role decides: an owner and an administrator see the whole organization, a supervisor their own projects, a rep only Mine.
  • A narrow access replaces what the role shows for analytics. An Analyst sees aggregates only: the figures of each tab, with no rep names or scores, no conversations and no quotes (the Reps table, Latest conversations, record links and examples are not shown, and small counts are withheld), and the cards do not lead to the reports (Report →) or to the Alerts screen. A Group lead sees everything about the departments they lead — including reps and conversations — and the panel names those departments.
  • Pro and up tabs (Sales, Voice of Customer) are marked, not hidden: on a lower plan the tab opens a plan screen that says what it contains.

The platform owner’s organization view in the admin console and the page of a single rep keep their own screens.

Onboarding State

First-time users see the Onboarding Checklist alongside the dashboard. The checklist guides you through initial setup steps specific to your role. The checklist sits in a panel on the right of the dashboard; the arrow button collapses it into a tab at the edge of the screen. Once all steps are completed, it collapses into that tab by itself after a couple of seconds, and you can reopen it from there. It disappears for good only when you press the X button (“Hide Getting Started permanently”).

See Getting Started for checklist details.

Onboarding checklist

Access by Role

FeatureOwnerAdminSupervisorRep
Summary, Conversations, Quality tabs✅✅✅ (own projects)❌
Sales, Voice of Customer tabs (Pro and up)✅✅✅ (own projects)❌
Team tab: reps, who needs help, dips, score after feedback✅✅✅ (own projects)❌
Mine tab❌❌❌✅ (own)
Latest conversations and links to records✅✅✅ (own projects)❌
Onboarding checklist—✅✅✅

Spending and the budget are no longer on the dashboard: they are in Settings → Organization → Plan & Billing and Service Status. A narrow access changes this table for the person who holds it.

Tips & Best Practices

  • Start with Summary and follow its theses and the By section line to the tab that explains them.
  • Select What the number is made of before acting on a number: it names the base and the rule.
  • Supervisors: start with Who needs help in Team and open the rep’s name to see their dips and what changed after your feedback.
  • Switch the comparison off when you only need the figures of one period, and use the table under a chart to compare days exactly.