Docs refreshed for Astervis v1 — now covering AI call analytics. What’s new
Astervis Docsv1.0
User Guide

User Guide

Everything you do day-to-day in the Astervis dashboard.

This guide walks through the Astervis dashboard the way you'll actually use it — section by section, with the bits that matter to operators, supervisors and admins called out as you go. If you're new, start at the bottom with First steps after logging in; if you already know your way around, the cards below jump straight to the section you need.

Astervis runs entirely on your own server. Every call record and recording from your PBX is replicated into a local TimescaleDB store, and the dashboard reads from that — so what you see is your real call history, not a sample.

Where to go

User roles

What you can see and do depends on your role. Astervis ships three built-in roles, and the dashboard renders a different view for each — there's no "hidden admin menu" an operator can stumble into.

Full access. Admins manage everything: employees and their roles, work schedules, integrations (Bitrix24, amoCRM, Open Lines), the phone blacklist, QA rubrics, AI agents, and all system settings. The whole dashboard and every report is visible.

Roles are backed by RBAC — granular permissions (like blacklist.manage or qa.*) grouped into roles. An admin can fine-tune who can do what; the three roles above are the sensible defaults most teams start with.

The dashboard

The dashboard is your home screen. It's a grid of widgets drawn from the analytics built on top of your replicated CDR data — call volume (incoming, outgoing, combined), missed and lost calls, operator performance, average wait time, trunk load, and sales pulled from your CRM deals. There are heatmaps and hourly breakdowns where they help.

The widget set is role-aware: an operator's dashboard shows their own numbers, a supervisor's shows the whole team. You arrange the widgets you care about and leave the rest.

By design, analytics widgets show numeric values only — no currency symbols or codes. A "sales" figure is a count or an average, not a billed amount.

Calls & transcripts

The Calls section is the searchable table of your entire call history. Filter by date range, operator, direction, trunk or queue to find what you're after, then open any call to see its detail view.

If AI analysis is enabled and the call had a recording, the detail view is where the real value shows up:

  • the full transcript, with each turn labelled agent or customer, in the original language;
  • a 2–3 sentence summary (written in Russian regardless of call language);
  • sentiment (positive / neutral / negative) and a category (sales / support / complaint / inquiry / followup / other);
  • a QA score with the reasons and quotes behind it;
  • detected topics, key quotes and recommended next actions.

Analysis runs automatically after a call finishes — its status moves pending → processing → completed, so a fresh call may show "processing" for a moment before the transcript appears.

Need the raw data elsewhere? Export the filtered CDR view to Excel straight from the Calls table.

AI insights

This is the headline of Astervis. Beyond per-call transcripts and QA scores, the AI layer gives you:

A few things worth knowing as a day-to-day user:

  • QA Analytics (/qa-analytics) gives supervisors the average score, a distribution, a per-operator table with per-criterion breakdowns, and auto-detected anomalies (operators trending low, QA drops, complaint spikes).
  • The AI Assistant answers questions in natural language — it generates a read-only SQL query against your analytics, optionally searches transcripts, and returns a summary plus a suggested chart you can save.
  • Insights land in an inbox you can mark seen, acknowledged, resolved or snoozed — and they can be delivered to Telegram.

AI is optional and metered, gated by a separate AI license tier. When it's on, the audio of a finished call is sent to Google Gemini on Vertex AI for analysis — nothing else leaves your server. The analytics platform works fully without AI. See AI & privacy for exactly what's sent.

Operators

The Operators (employees) section is where admins set up the team. Each employee maps to the PBX extension that appears in your call records, which is what ties a call to a person across every report. Here you also manage positions (with a visual canvas for org structure) and assign each person a role.

Getting this right early pays off: leaderboards, the per-operator QA table and coaching insights all key off these assignments.

Reports

Reports are the deeper analytics behind the dashboard widgets. Expect:

  • Operator performance and leaderboards (with movement over time);
  • Trunk comparison, heatmaps and load distribution;
  • Wait-time and missed/lost-call breakdowns with drill-downs;
  • Sales from CRM deals — deal counts, average sale price, top incoming numbers;
  • raw CDR access with Excel export.

Supervisors and admins see the full catalogue; operators see the reports scoped to their own work.

Schedules

Define your team's work shifts under Schedules, then track actual time against them. The schedule report (/work_schedules/report) shows who worked when versus their planned shift, which is what you'll use for attendance and late-arrival review. Pair it with the operator assignments so the report knows who's who.

Blacklist

Block unwanted callers at the PBX itself. Add a number under Settings → Blacklist, and Astervis pushes it into Asterisk (via AMI into the astdb, with an ARI hangup fallback) so the call is stopped before it reaches an operator. The list supports CSV import and export, and phone numbers are normalised for Uzbek formats (+998 / 998 / 8).

Managing the blacklist requires the blacklist.manage permission, so it's an admin (or specifically granted) action.

First steps after logging in

If this is your first time in the dashboard, here's a sensible order to get oriented.

Look at your dashboard

Take in the home screen and the widgets on it. This is the live picture of your call centre — get comfortable reading call volume, missed calls and operator activity here first.

Confirm your team is set up

Admins: open Operators and make sure every person is linked to the right PBX extension and has the correct role. Everything downstream — reports, QA, coaching — depends on this.

Open a few calls

Go to Calls & transcripts, filter to today, and open a call. If AI is on, read a transcript and its QA score to see what the analysis gives you.

Set up schedules

Define your work shifts so the schedule report can track time and attendance.

Explore the AI layer

Try the AI assistant with a question like "how many missed calls yesterday?", and skim QA scoring to see the rubric templates you can adopt.

Stuck? Use the search at the top of the sidebar to jump to any feature, or check the FAQ for common questions.

Last updated on

On this page