Scripts
Aelo’s Scripts feature lets you define structured sales scripts — step-by-step conversation guides that reps should follow. When linked to a project, Aelo measures how closely each conversation adheres to the script and includes the result in the quality analysis.
A sales script is an ordered sequence of steps that define the ideal conversation flow. Each step contains:
- Step name — a short label (e.g., “Opening”, “Needs Discovery”, “Product Pitch”)
- Step settings — Required Step (a missed required step lowers the score), Order Enforced (the step counts only if it came after the previous steps) and Weight (how much the step adds to the score)
- Phrases — what the rep is expected to say at this step. Each phrase is Required, Optional or Forbidden, and is matched Exact, Semantic (a paraphrase is accepted) or Regex
- Order — position in the conversation flow
A new organization gets six ready-made scripts. In a workspace created through sign-up they are provisioned with the organization; in one created from a CRM app they are created when the Owner completes the first sign-in to the app. Until that happens, they appear the first time an Owner or Admin opens Analysis Setup → Script rules. Four of the six are already bound to a call category and start working on their own:
| Script | Bound category |
|---|---|
| Sales Discovery | Product inquiry |
| Deal Closing | Purchase |
| Support Greeting | Support |
| Complaint Resolution | Complaint |
The other two — Sales Chat and Cold Call — are drafts: they carry no binding, because there is no call category that matches them (a sales chat is categorized as a product inquiry or a purchase, and a cold call is not a category at all). They are marked Not assigned in the list and stay unused until you bind them to a category or make one the default script of a project.
Every ready-made script is an ordinary script: edit its steps, rebind it, or delete it.
Ready-made scripts are written in the organization’s language. When an Owner or Admin changes that language in Settings, the ready-made scripts you have not touched are rewritten into the new language shortly after the change, in the background (not at the very moment you save) — the same scripts, not copies: their bindings, project assignments, step weights, required flags and criterion settings stay as they were, and the script’s version number goes up by one. Past evaluations keep their scores and step results exactly as recorded: the step names and criterion texts written into them stay in the old language, while the script’s name on an evaluation card is read from the script itself and appears in the new language. A script counts as untouched when none of its text was changed (name, description, step names and descriptions, criteria), its steps were not reordered, and no criterion was switched to another type or to exact-match or regular-expression matching (such a criterion’s text is a literal pattern, so it is never translated). A script that fails any of these conditions stays exactly as you left it, and so do scripts you created yourself. The translation never overwrites a change you saved before it writes: such a script stays as it is. If the language was changed by other means, or the ready-made scripts stay in the old language after a while, ask support to run the translation for your organization.

Owner Admin
- Open Analysis Setup in the main menu, go to the Script rules step and switch to its Script rules tab (the step opens on the Categories tab).
- Click New Script (Create First Script while the list is empty).
- Enter the Script Name and, if needed, the Script type and Description.
- Click Save Changes. The script is created and stays open in the editor, now with the Steps section (it does not exist before the first save). Instead of adding steps by hand you can use AI Script Parser: it builds steps and phrases from the text of a script, and they are created when you click Save Changes.
- Click Add Step. The step appears as “Step N”; click its name (or the pencil) to rename it, then press Enter or the tick.
- Expand a step with the arrow to the left of its number to set Required Step, Order Enforced and Weight, and to add phrases with Add Phrase.
- Change the order with the up and down arrows on a step; the new order is saved a moment after your last click.
- Changes to a step or a phrase apply as soon as you make them. A deleted step or phrase can be brought back with Undo for a few seconds. Save Changes saves only the fields of the script itself (name, type, description, the Active switch).


A step row shows its number, name, the Required and Ordered badges (when those are set), the number of phrases, and buttons to rename and delete the step.


Scoring is switched per project: Projects → Settings → Analysis & Quality → Enable rule-compliance scoring. It is on for a new project. While it is off, no script — assigned to the project or bound to a category — is checked in that project’s conversations; the Script rules step of Analysis Setup names the projects where it is off, with a link to the switch.
When a project has a script that applies and scoring is on, the AI evaluates how well each conversation follows the script:
- Overall adherence score (0–100%) — the weighted average of the step scores, over the steps that were owed. A step is scored by the weight of its required criteria that were met; a met optional criterion adds a bonus on top, capped at what the required ones earned, and an unmet optional criterion costs nothing. A step where a forbidden criterion was detected, or an order-enforced step performed out of place, scores 0. An optional step that never happened is left out of the average — and out of the step count beside it — rather than counted as a failure.
- Step-by-step breakdown — each step with a tick, the share of its required phrases that were met (for example 2/3) and its score; open a step to see the matched and missed phrases
- Missed required phrases — the mandatory criteria that were not met. Unmet optional criteria are not listed: they cost no score, so they are not a gap
The adherence score is shown in the record detail panel — inside the analysis, in the Script rules group (the “Script Adherence” card, with the score in its header).
The card shows three tiles — Steps Completed, Steps In Order (for example 5/7) and Order Score — and, if some steps came in the wrong place, a warning line for each (“expected position 2 → actual position 4”). Below are the step rows (a step the script did not owe in this conversation is marked “not required” and has no score), the Missed required phrases list and, at the bottom, the script name (with its version when it is above 1).

Owner Admin Supervisor
The Script Steps screen (Analytics → Script Steps, titled Script adherence by step) shows which steps of a script the team does not complete, and which criteria are behind it. It follows the scripts switch: the menu item is there while scripts are on. It also opens from Report “Script Steps” → on the Missed script steps card of the dashboard’s Quality tab, with the card’s period and projects (for a period of up to 93 days; the card has no link for a longer one). Filters: period (up to a quarter) and projects. A supervisor sees their own projects.
- Coverage — the top of the page says how many of the period’s analyzed records were evaluated against a script (“Evaluated 150 of 400 analyzed records”). Only evaluated conversations are in the numbers below it: the shares describe them, not every conversation of the period.
- Steps — each script has its own block with its steps, the most often not completed first. A row reads, for example, “95% not completed · 143 of 150 conversations”: the step was due in 150 conversations and was not completed in 143. Under it: how many of those were partly done, how many were short of exactly one criterion, and not needed: N — conversations where an optional step did not come up; those are not in the share. A step nobody missed stays on the list with 0%. Where the step was due in fewer than 5 conversations, the row is marked few conversations: the share is not reliable.
- What “not completed” means — not every required criterion of the step matched, the same as the tick on the record. A step can be not completed and still score 60: it was partly done. That is why “partly done” always stands next to the main number.
- Open a row — a breakdown by rep (reps with few conversations are one footnote; conversations without a rep are a line of their own) and by criterion: in how many conversations it was not met, how many times it was the only one missing, and a mark almost never met where it is not met in at least 90% of 20 or more conversations. Such a mark is a question about the wording — can it be satisfied at all? — before it is a question about people. The rep is the one the conversation is assigned to now.
- Conversations where this step was not completed — a link in the open row opens the list of records where the step was not completed, with the same period and projects as the screen. There is no link for a step removed from the script, for a deleted script, or in the Bitrix24 app.
- Rules changed — when conversations of the period were evaluated under different versions of a script’s rules, the script shows the date the first changed version was first used to evaluate a conversation (not the date of the edit, and not necessarily a date inside the period); conversations under every version are counted together.
- Conditional steps — a step that is required in the script but conditional in meaning (“if the customer…”) is counted as not completed when the condition did not occur. The screen says so in a permanent note. Mark such steps optional in the script: while they do not come up, they stay out of the share.


Owner Admin
Beyond linking a script to a single project, you can bind a script directly to a call category at the organization level. Aelo automatically detects the category of every call (Purchase, Support, Complaint, etc.), so a category-bound script applies automatically to every matching conversation across your projects — no per-project link required.
- 10 call categories: Product Inquiry, Purchase, Scheduling, Support, Billing, Onboarding, Complaint, Cancellation, Follow-up, Other.
- Chats: resolve to their own category’s binding — same as calls.
- Missed and short calls are not analyzed, so no script resolves for them. The same applies to a chat with no rep reply, or with fewer real messages than the project’s Min Chat Messages setting (4 by default).
Each category can have at most one bound script per organization — trying to bind a script to a category that’s already taken is rejected; unbind (or rebind) the other script first.
When a record is analyzed in a project with rule-compliance scoring on, the script used for adherence scoring is selected in this order:
- Project script — the script assigned to the project below. A project’s script wins over a category binding on its own, and there is no pin for scripts.
- Category-bound script — the org script bound to the detected call category, used when the project has no script of its own.
- No script — if none of the above resolve, adherence scoring is skipped for that conversation.
Assigning, changing, or removing a category binding happens only in the matrix: Analysis Setup → Script rules → Categories tab. Each row of the matrix is a category with its current bound script (or “Project default script rules” if unbound):
- Assign — pick a script for the category.
- Reassign — picking a different script for a category that already has one moves the binding: the previous script is unbound first, then the new one takes the row. Nothing is rejected, and the script that lost the binding keeps its steps and phrases.

The script editor itself shows the Bound category field read-only, with a link back to the matrix (“Binding is changed on the “Categories” tab”).

Each category still allows only one active bound script per organization.
- Go to Projects > select a project > Settings.
- Open the Analysis & Quality tab and find the Script rules block.
- Select a script in Active script rules.
- Save.
All new analyses in that project will include script adherence scoring, as long as Enable rule-compliance scoring is on in the same tab. A script assigned to a project takes priority over an org category binding: assigning a script to a project is a deliberate choice, so bindings apply to projects that have no script of their own.

- Edit — modify steps, phrases, or ordering
- Duplicate — create a copy for a new variant
- Delete — permanently remove a script
| Feature | Owner | Admin | Supervisor | Rep |
|---|---|---|---|---|
| View scripts | ✅ | ✅ | ✅ | ❌ |
| Create/edit scripts | ✅ | ✅ | ❌ | ❌ |
| Delete scripts | ✅ | ✅ | ❌ | ❌ |
| View adherence results | ✅ | ✅ | ✅ | ❌ |
| View steps report | ✅ | ✅ | ✅ (own projects) | ❌ |
| Link scripts to projects | ✅ | ✅ | ❌ | ❌ |
- Keep scripts concise — 5 to 10 steps is ideal for most sales processes.
- Use required phrases sparingly — focus on compliance-critical phrases (e.g., disclaimers, legal terms).
- Create different scripts for different sales scenarios (cold call vs. follow-up vs. upsell).
- Review adherence trends to identify which script steps reps consistently miss.
- Update scripts regularly based on what works — use high-scoring conversations as reference.