Projects
A project is a workspace for the conversations of one team, line or sales direction. Every record belongs to one project, and the project decides how the record is processed: which channels are accepted, the language the report is written in, which call counts as short, the profile and script it is evaluated by, which supervisors see it and where its alerts go.
At sign-up Aelo creates the first project and makes it the organization’s default project. The Projects section of the sidebar is visible to the Owner, Admins and Supervisors; a Supervisor sees the projects assigned to them, and a person with narrow analytics access sees the projects that access opens. The list can be filtered by status.
The Owner, Admins and Supervisors can create a project: the Create Project button in Projects, or the Command Palette (Cmd+K / Ctrl+K). A person with narrow access to selected projects or departments cannot create a project: that takes organization-wide access. The Create New Project form:
- Project Name — required.
- Description — optional, see below.
- Channels — Phone Calls and Chats; at least one is required.
- Report language — Auto by default.
- Analysis profile and Script rules — optional: without them the organization’s profiles by category and scripts apply.
A Supervisor who creates a project becomes its admin and can change and archive that project just as an Admin can. The Owner and Admins change any project on its Project Settings page, opened by the settings button in the list. Changes on the Overview tab are saved with Save Settings.
The description is included in every AI analysis of this project’s conversations — just as the company description is included in the analysis of every project. Say what the line or team is, which customers it talks to and what a good conversation means for it: this helps evaluate conversations more accurately. It is changed on the Overview tab.
The Channel Processing tab switches calls and chats on and off for the project. Calls and chats from Bitrix24, telephony and Uspacy on a channel that is off are not processed at all — no transcription and no analysis — even if distribution sent the record to this project. The switch does not stop a file uploaded by hand or a record sent through the Public API: those are processed, and minutes are spent.
The create form saves the channel choice in the project itself, so in a new project both channels are marked Override, and changing a channel for the whole organization does not touch them. Reset returns a channel to the organization’s settings — it is then marked Inherited. A channel switched off for the whole organization cannot be switched on in a project: it is marked Org locked.
Both languages are set on the Overview tab:
- Report language — the language the AI writes summaries, insights and recommendations in. Auto writes in the language of the conversation. Quotes from the conversation always stay in the original language. The report language of all projects together is also shown in Common settings on the Analysis Setup overview.
- Recognition language — the language spoken in the recordings. If the project’s calls are in one language, set it; leave Auto when the language varies from call to call.
More on both in Analysis Setup.
The Overview tab sets the thresholds below which a conversation is not analyzed:
- Min Call Duration (sec) — 30 seconds by default. A shorter call is transcribed but not analyzed: the transcript is available on the record, without quality analysis or a script check. The comparison uses the speech duration when the recognition service reports it, and the recording length otherwise: a call that reaches an answering machine — 80 seconds of recording and 9 seconds of greeting — counts as short. A short call spends no minutes. A Bitrix24 call shorter than 15 seconds is marked short before transcription: it is neither transcribed nor analyzed.
- Min Chat Messages — 4 by default. Chats shorter than this, or with no rep reply, keep their transcript but are not analyzed.
Short calls can be hidden in the records list with the Hide short calls switch (see Conversations).
The status is set on the Overview tab:
| Status | New records | What is already there |
|---|---|---|
| Active | Accepted; whether they are processed right away depends on the organization’s analysis mode — Automatic or Manual (see Organization) — and on the project’s auto analysis switch | — |
| Paused | Not accepted: calls and chats from Bitrix24, telephony and Uspacy are skipped silently, and a file upload or a Public API request gets an error that says why | Records and analytics stay |
| Archived | Not accepted, as for a paused project | Records are kept |
A project can also be archived on the Danger Zone tab: Archive disables processing and keeps the records. An archived project is restored by setting its status back to Active or Paused.
If you archive the default project, the organization no longer has a default project, and restoring it does not make it the default again. Until you set another one, telephony and Uspacy calls go nowhere, and Bitrix24 records that match no rule are not accepted.
Only the Owner can Delete Project, and only an archived one: on the Danger Zone tab, Delete permanently deletes the project and all its data.
Which project a new record lands in depends on its source:
| Source | Project |
|---|---|
| Bitrix24 — calls and chats, imported ones included | The first distribution rule the record matches; if none matches, the default project |
| Telephony (Binotel, Ringostat, Stream Telecom, Unitalk) | Always the default project: distribution rules do not apply to these calls |
| Uspacy | Always the default project: distribution rules do not apply to these calls |
| Public API, file upload | The project named when the record is sent |
Telephony connected only as an audio source for Bitrix24 creates no records of its own: its calls become Bitrix24 records and go through the rules.
Rules for Bitrix24 are set on the project’s Distribution tab: conditions on record and CRM fields (channel, direction, duration, responsible user, department, deal, lead, contact or company fields, day of week and hour). Rules run in order, and the first rule a record matches decides; drag rules to reorder them within the project, and see and change the order across all projects in Analysis Setup → Distribution.
On the same tab:
- Fallback Project — Set as Default makes this project the default project: records that match no rule go here, and so do telephony and Uspacy calls. Only an active project can be made the default.
- Reject Unmatched Records — Bitrix24 records that match no rule are not accepted. While the organization has a default project, the switch is on Standby: such records go to the default project.
Both settings apply to the whole organization, so only the Owner changes them; a project’s distribution rules are changed by whoever can change the project.
The decision for each Bitrix24 record is shown in Analysis Setup → Distribution → Log. Telephony and Uspacy calls appear there only when they were skipped (for example, there is no default project or the channel is off), and Public API and file-upload records do not appear there at all (see Settings).
- Team — Supervisors of this project: a Supervisor opens calls — transcripts, recordings and analyses — in the projects assigned to them, plus the calls of anyone under them in the org structure (see Team Management).
- Analysis & Quality — the analysis profile, the script, auto analysis and Transcript only mode.
- Alert delivery — where this project’s alerts are delivered.