aisol/cases/teraline telecom
case · Teraline Telecom · b2b telecom · 2026

Six AI agents behind one growth strategy

How a licensed telecom operator brought sales, service and customer retention together into a single system — without replacing Bitrix24, IP telephony, billing or Service Desk.

250%ROI · year 1
×2funnel conversion
−40%customer churn
100%calls reviewed
6agents in production
client
Teraline Telecom
website
market
Corporate
telecom · KZ
stack
Bitrix24 · IP-PBX
Service Desk · Billing
Get a project like this from 6 weeks · fixed price
06 · agents

Six AI agents in production

Each handles its own task and is integrated with the existing systems.

0 min

Manual data entry in the CRM

Client records in Bitrix24 are filled in automatically after every call.

daily

A transparent funnel every morning

Conversion by stage, bottlenecks, deviations — with no manual report building.

proactive

Unhappy clients — before they leave

An alert reaches the manager before the client calls to cancel the contract.

market

Corporate telecom — a market where you cannot afford to lose a single client

Corporate telecom in Kazakhstan is a highly competitive market built on long-term contracts. Clients here are not buying a service — they are entrusting the provider with part of their infrastructure. Switching to a competitor is hard, but once a client has made that decision, winning them back is almost impossible.

Teraline Telecom operates exactly in this segment: data transmission, voice services and dedicated channels for corporate clients. Every contract is a long-term relationship with a high value and a high cost of error.

In a business like this, three things drive growth: the quality of acquiring new clients, the depth of work with the existing base, and the speed of the technical support response. The roll-out was built around these three areas.

before

The data was there — but it wasn't working

BOTTLENECK · BEFORE THE ROLL-OUT

The company already had a CRM and used it actively. But the data in it reflected the past, not the present: information was entered with delays, and analytics were built manually and took time. Management received a snapshot of sales not in real time, but on request.

Calls were recorded, but not analysed systematically. No one knew for certain whether managers followed the scripts, which objections came up most often, or at which stage of the funnel the most deals were lost. This was data that existed — but wasn't working.

Technical support looked much the same: requests were handled, but no one tracked the patterns of recurring problems in a systematic way. An unhappy client could raise the same issue several times before being flagged as a risk.

Handing clients over from active-sales managers to account managers happened through the CRM, but the depth of that handover depended on the individual. There was no single standard.

what we did

Six AI agents for six tasks

Instead of one large project, we broke the roll-out into concrete working modules — each handling a specific task and integrating with the existing systems without replacing them.

Sales · 3 agents

Acquiring new clients: control over managers' work, a transparent funnel, a standardised client handover.

1agent
sales · CRM

Call monitoring and automatic CRM entry

The AI agent began transcribing all inbound and outbound calls of the active-sales managers. Every call was automatically converted to text, after which the agent checked it on two fronts.

First — script compliance: did the manager go through all the required stages of the conversation, ask the right questions, and handle objections to the standard? Second — extracting client data: what matters to them when choosing a provider (price, speed, reliability, level of service), their current connection speed, their monthly spend, and whether they have problems with their current provider.

All of this data flowed automatically into the client record in Bitrix24 — in a structured form, in the right fields. The manager would finish the conversation and the record was already filled in. No manual entry, no delays, no lost details.

how it worksIP-PBX · APISpeech-to-TextLLM extractionBitrix24 custom fields
2agent
analytics · funnel

Daily sales-funnel analytics

The AI agent gathered data on all active deals and built a report for the head of sales every morning — without queries to managers and without manual assembly.

The report showed conversion at every stage of the funnel: reaching the decision maker → agreeing to a meeting → holding the meeting → sending the details → closing the deal and payment. For each stage it was clear how many deals moved forward, how many got stuck, and which managers were performing below the team average.

In addition, the agent analysed call transcripts: at which points in the conversation objections came up most often and how managers handled them. Managing sales stopped being based on gut feeling — now it is data that is updated every day.

how it worksBitrix24 APIfunnel cohortstranscript clusteringdaily digest
3agent
client handover · control

Client handover: active sales → account management

Every time a new client moved from an active-sales manager to an account manager, the AI agent began tracking the quality of that handover against a specific checklist.

Did the account manager get to know the client personally? Did they find out what matters to the client in working with a provider — not from the record, but in a live conversation? Did they identify what could be offered as an add-on and when that would be appropriate? Did they set themselves a task with a reminder?

The agent analysed calls and CRM activity over the first month after the handover. If any checklist item was not completed, the manager received an alert the same day, rather than learning about it a month later at a planning meeting.

how it worksCRM triggerchecklist scoringLLM topic detectionmanager alerts
Account management & retention · 2 agents

Working with the existing base: proactive contact, detecting dissatisfaction, and upselling.

4agent
existing base · retention

Monitoring work with the existing client base

The fourth agent worked with clients who were already connected — those who had been in the base for a long time and who are easy to stop paying attention to.

For each client the agent checked: was there a planned contact this month, are the problems from past requests closed, and are there signs of hidden dissatisfaction — situations where the client mentioned something in a conversation but never filed a formal request.

At the same time, the agent analysed upsell potential: it looked at the structure of consumed services, compared it with similar clients, and highlighted who could logically be offered what — with a concrete rationale, not just a "potential here" flag.

how it worksCRM + billing APIconsumption analysissilent-issue detectionweekly priority list
5agent
support · sentiment

Request analytics and detection of unhappy clients

The fifth agent worked in the contact centre. It analysed all support calls and correspondence: it transcribed conversations, identified the topic of each request and the overall tone — whether the client was satisfied, neutral or frustrated.

On this basis the agent did two things. First, it classified requests by problem type: no connection, low speed, a billing question, a quality complaint. This produced accurate statistics on the real reasons for requests, rather than the categories an operator picked manually. Second, it built a list of clients with a high level of dissatisfaction: those who raised the same problem several times or in whose conversations the agent detected rising frustration.

Working from this list, account managers made a proactive call — without waiting for the client to call themselves intending to cancel the contract.

how it workscall-center + chatstreaming STTLLM classificationsentimentCRM hand-off
Technical support · 1 agent

Helping operators during the conversation with the client — resolving routine questions faster and escalating complex ones.

6agent
operator · assistant

An AI assistant for support operators

The sixth agent worked not on the outside but on the inside — helping the operators themselves during the conversation with the client.

From internal documentation, technical regulations and the accumulated history of requests, the agent built a knowledge base. When an operator received a call, the agent identified the topic of the request in real time and suggested a ready answer or a sequence of actions — right in the operator's interface, while the conversation was still going on.

Routine questions — equipment setup, explaining a bill, standard technical issues — the first-line operator began resolving on their own, without handing off to a senior specialist. At the same time, complex cases were escalated faster: the agent helped the operator recognise that a question was non-standard right at the start of the conversation.

how it worksindexed knowledge baseService Desk pluginrealtime topic detectionRAG suggestions
what changed

First results — within the first month

The first thing noticed straight away was that morning planning meetings became shorter and more substantive. Instead of "how are things going with client X?", the conversation started with data: here is the funnel, here is the bottleneck, here are the managers below average at this stage.

A few weeks after the call analysis went live, it became clear exactly where conversion was being lost: most deals got stuck after the proposal was sent. The transcripts revealed the specific cause — managers were not agreeing on the next step right at the end of the conversation. The script was adjusted. Conversion at that stage went up.

In technical support, a list appeared of clients who had raised the same problem several times. A proactive call campaign was launched for them. Some of those who were already considering switching providers stayed.

results in numbers

What the business gained

Six metrics by which management measures the effect of the pilot — all collected automatically from Bitrix24, the IP-PBX and Service Desk, with no manual surveys.

250%
Project ROIover the first year
×2
Conversion growthacross the sales funnel
×3
Faster onboardingof a new manager
−40%
Lower churnof the client base
100%
Of calls reviewedwas 3% · manually
10 h
Saved per weekof the head of sales' time

What stays with the company

Six qualitative changes that keep delivering value after the pilot ends.

1

The sales funnel is transparent in real time — the manager sees every stage every day without manual reports.

2

Client records in the CRM are filled in automatically after every call — the data is up to date with no delays.

3

Sales-script compliance is checked on every call — without manually listening to recordings.

4

Client handovers between teams are standardised and monitored automatically against a checklist.

5

Unhappy clients are identified proactively — before they initiate the cancellation of a contract themselves.

6

Support operators resolve routine questions without escalating to senior specialists.

client view
Before the roll-out we knew the data was there — but we couldn't work with it in real time. Now I see the funnel every morning, I know where each manager is stalling, and I get alerts about clients who might leave — before they call intending to cancel the contract. This is a different level of management.
— HEAD OF SALES · TERALINE TELECOM

Want the same?

Tell us about your company — we'll start with a free process review and show you where AI will deliver the most impact.