The pairing closes the gap between what a meeting decided and what actually shows up in the system of record. ProtocolExpert records the meeting — on site in a site office or on a shop floor, off-site, or in any video conferencing tool — and transcribes it with its own speech engine, without sending audio to outside services. What comes out is a transcript, a short summary, and a list of action items with owners and dates. Those items then land in Bitrix24 as tasks linked to a project, a site, or a deal. If your meetings happen in one place and execution control lives in another, that is the situation this addresses.

Recording and transcribing a meeting is roughly half the job. The other half is manual: write it up, format it, send it around. A week later nobody can say how many action items from the minutes were closed, how many are overdue, or who was supposed to do what. The minutes exist on paper. The work does not exist at all.

The second layer is distribution. In a manufacturing or construction company, meetings do not happen in one conference room. There is the morning coordination call on site, the off-site meeting with a contractor, the weekly project review by video, the dispute call with a supplier. For all of it to flow into one control system, recording has to work wh ere the conversation happens, not wh ere the conference room microphone is bolted to the table.

Bitrix24 inside an enterprise perimeter is not just CRM. Tasks, projects, smart processes, access rights, and business logic all live there. ProtocolExpert, on its side, returns the structured output of a meeting: transcript, summary, action items, audio.

The integration works at the data level: the meeting output is parsed into action items, and each one arrives in the portal as a task with an owner, a due date, and a link back to the source. On the portal side that means REST calls, webhooks, business processes, and robots — the specific set depends on your Bitrix24 edition and your permissions.

What a first phase typically needs to produce:

• project review → tasks inside a Bitrix24 project, with deadline and creator;

• contractor or supplier call → the minutes file and a comment on the record;

• site coordination call → the work checklist for the shift;

• executive meeting → a summary of action items by department head.

ROOT CODE handles both sides of the work: custom development and integrations for large enterprises with distributed infrastructure, and the products in the Expert ecosystem. Company data as of 2026: operating since 2021, 135+ specialists, 90+ projects. The ecosystem products are listed in the national software registry.

Four conditions separate these industries from office-based sales or support.

Noise and terminology. Recording happens in a site office, on a shop floor, next to an open opening. The speech is full of abbreviations, axis numbers, concrete grades, and assembly names that a general-purpose model has never seen. The output quality depends on the dictionary for that specific plant. A custom dictionary is configured for your terminology — the model is further trained on the customers own material, including minutes from previous periods, process sheets, and site registers.

Connectivity on site. Recording has to survive poor connectivity or none at all. ProtocolExpert runs offline: audio is stored locally, and processing starts as soon as a connection appears.

Shift work and contractors. Some meeting participants have no account in the portal: a contractor, a construction inspector, a driver, a supplier representative. Someone has to enter the decisions that concern them into the system, and that rule is written down in advance. Otherwise half the action items stay outside any control loop.

Closed perimeter. Minutes contain prices, deadlines, claims, and personal data. In manufacturing and oil and gas, that is data which does not leave the perimeter. ProtocolExpert is deployed inside the customers own environment; audio and transcribed text never leave your infrastructure.

A pilot runs on one project and one meeting type, not across the whole company. The standard path has three stages.

Diagnostics (1–2 weeks). We take recordings of real meetings — three to five of them, anonymised — and run them through ProtocolExpert. We look at where recognition trips over your terminology, how many action items are extracted correctly, and how many need a human edit. We build the dictionary: the list of sites, participants, abbreviations, and job titles. We design the Bitrix24 exchange: which tasks are created, in which project, with which default due date.

Pilot (1 month). We connect one meeting type — usually the weekly project review or the site coordination call. Everything extracted automatically passes through a human before it reaches the portal. We keep a counter: how many action items went through without an edit, how many needed a clarification, how many were rewritten from scratch.

Rollout. If the accuracy is acceptable, we extend to other sites and meeting types. The base rules stay; only the terminology dictionary and the participant list change.

An honest section on limits is the first thing a decision-maker checks.

Nobody owns the meeting process, so action items still get rewritten by hand after the automatic pass and half of them get thrown away. Then you have sped up a step that should not exist.

Bitrix24 is not where execution actually lives: tasks are assigned in a messenger, and the portal is maintained for reporting. The integration will produce one more list that nobody opens.

There is no appetite for changing the process: who records an action item, at what moment, who approves the wording before it goes to the portal.

Contractors are expected to start working inside the customers system on their own.

What we will need from you:

• a person who owns the execution of action items, rather than the presence of a file in a folder;

• mapping rules: meeting type → which tasks are created, in which project, with which default deadline;

• source data for the dictionary and normalisation: sites, counterparties, job titles, internal abbreviations;

• access and roles: who may create tasks, who sees the minutes for a given site, how rights are split between locations;

• a decision on wh ere audio and transcripts are stored: wh ere, for how long, who has access.

We have dozens of sites and every meeting is different. Who configures the templates? The base set is built once and then replicated across sites. What differs per location is the terminology dictionary and the participant list, not the whole logic. Each additional site takes about a day of work, not a month.

Does meeting audio go to your side? The work happens inside the customers environment. Audio, transcripts, and extracted action items are stored on your infrastructure. We configure the exchange with the portal; we do not see the content.

Some sites have poor connectivity. Will a recording be lost? ProtocolExpert runs offline: the recording is stored locally and processing starts once a connection appears. If the link drops mid-meeting, the recording continues locally to the end and is then sent for transcription.

If recognition gets it wrong, who is responsible for a task that was never meant to exist? An action item counts as recorded once a person has seen it. The system prepares a draft; responsibility for the wording stays with whoever runs the meeting. The same rule settles the argument with an assignee who understood it differently.

What will my people have to do? Start the recording, review the list of action items before it goes to the portal, close tasks as usual. Reviewing one set of minutes takes 3–5 minutes on average, against 20–30 minutes of manual write-up.

Bring two things: one recording of a real meeting — anonymised, 20–30 minutes, ideally from a site or a shop floor — and access to a test project in your Bitrix24. We will work through that recording and show you what its action items look like as portal tasks, with owners, deadlines, and a link to the source. One session is enough to see wh ere recognition trips over your terminology, and wh ere nothing needs fixing in the first place.