Tariffs, procedures and licence conditions, answered with the page.

The sentence we hear

“Which package rule applies to this customer's complaint, and what is the escalation step?”

The problem

Tariff rules, package terms, complaint procedures and escalation steps sit in a knowledge base that lags the product team by weeks, plus email and the memory of senior agents. Agents answer differently, handling time grows, and the regulator's complaint rules add deadlines nobody can quote.

What changes

• Tariff rules, package terms, procedures and the complaint policy are loaded with their dates, and old versions are retired.
• Agents ask the way the customer spoke, in Bangla, English or both, and get the rule with the page.
• Questions the documents do not answer are logged, which shows the product and policy teams where the gaps are.
• No subscriber record is loaded; the answer is about the rule, and the agent reads the account in the billing system as before.

What stays with a person

The care supervisor confirms any answer that changes what a customer is told or refunded, and the quality team reviews the log weekly.

The result

The same current rule behind every call, with fewer questions to the senior on the floor.

Draws on

The sentence we hear

“Half our calls are balance, package and coverage questions that a person should not have to take.”

The problem

Routine questions fill the queue, and most chat tools were built for English first. The second SI pattern, chat and voice in Bangla, is built only after the knowledge base has passed its test, and it hands over to a person whenever it should.

What changes

• A chat channel, then a voice line, answers in Bangla from the same tested knowledge base, including Bangla typed in Latin letters.
• Anything that needs the customer's account is handed to an agent with the conversation so far.
• Each channel is scored on the Bangla test bench before it goes live, and re-tested every month under managed SI operations.
• The log shows what customers asked that the rules could not answer.

What stays with a person

The head of customer care owns the handover rules and signs the pass mark for each channel.

The result

Routine questions answered at any hour, in Bangla, with a person one step away.

Draws on

The sentence we hear

“The night shift needs the change procedure for this node, and the engineer who wrote it is asleep.”

The problem

Runbooks, vendor manuals, change procedures, site access rules and incident playbooks sit across wikis, PDFs and vendor portals, in English for a shift that speaks Bangla. A wrong step at 2 am is a service outage, and the post-incident review starts with the question of which procedure was being followed.

What changes

• Runbooks, vendor manuals and change procedures are loaded by version, with access limited to the operations roles that may open them.
• A shift engineer asks in Bangla or English and gets the procedure, its page and its version.
• The server gets a penetration test by a certified testing firm before it joins the operations network.
• The log shows which procedure was in force when a change was made, which the post-incident review can read.

What stays with a person

The shift lead approves every change before it is made, as the change process already requires.

The result

The current procedure with its page on every shift, from a server that works when the internet does not.

Draws on

The sentence we hear

“Which BTRC directive changed the rule on this, and what does our licence say?”

The problem

Licence conditions, BTRC directives, tariff approvals, interconnection terms and past filings run to thousands of pages, and a new licensing policy in 2025 changed the licence categories. The regulatory team answers questions from the board, legal and finance by searching email and memory, and a wrong citation in a filing is expensive.

What changes

• Licences, directives, approvals and past filings are loaded with their dates and numbers.
• Staff ask in Bangla or English and get the directive number, the clause and the page.
• Superseded directives are marked, not deleted, so the answer shows which one is current.
• Access is limited to the regulatory, legal and finance roles that may open the files.

What stays with a person

The head of regulatory affairs confirms every citation before it goes into a filing or a board paper.

The result

The directive, the clause and the page behind every regulatory answer.

Draws on

The sentence we hear

“Every new client abroad sends a security questionnaire, and our engineers stop building to answer it.”

The problem

A technology or platform firm answers security questionnaires from export clients, supports its product from documents that lag each release, and holds user data under the Personal Data Protection Act 2026. The answers to the questionnaire exist in policies, the last penetration test report and past replies, but the engineers who know them are the ones who should be building.

What changes

• Security policies, the last test report, past questionnaires and product documents are loaded, with access by role.
• Bahlul SI drafts an answer to each question and names the policy or report page it came from; where none exists, it says so.
• A penetration test by a certified testing firm gives the evidence the questionnaire asks for, scoped per system.
• The same index answers the support team's product questions, with the release version on each answer.

What stays with a person

The CTO or head of security approves every answer to a client, and the data readiness package decides what user data SI may ever read.

The result

Questionnaires drafted from evidence, engineers back on the product, and a test report to attach.

Draws on