Asterisk ↔ CRM · an Adminz solution
The connector listens to your PBX and files conversations into Bitrix24: the card on an incoming call, the outcome and the recording on the deal. It physically holds no control rights — not “we are careful”, but the PBX refusing an attempt to dial. Everything on your server; minutes stay with your carrier.
The product is under development. What is built and what is not is spelled out below.
Why us
There are two modes and you choose. In observation the connector reads events and nothing else: an attempt to dial is refused by the PBX itself — not by agreement, by permissions; check it yourself with one command. Dialling from the card is a separate right you enable deliberately; it is not built yet, and when it is, enabling it or staying on observation remains your decision.
Your clients’ numbers, call recordings and correspondence stay with you. We are not a cloud and not a middleman: the connector sits on your own machine next to the PBX. For a bank, a leasing firm or a clinic this is not an advantage but a condition of entry.
The subscription is per installation. Hire five more people in sales and the invoice is the same. Where you pay per seat, doubling the team doubles the bill.
Adminz runs networks, servers and telephony in Tashkent. If your infrastructure is already with us, that is one contractor and one phone number instead of two — and no “that is the telephony people, not us” conversation.
What we do not have: installations of this product. We are looking for the first ones and do them ourselves — terms for first clients are discussed separately and in your favour.
Why this does not exist yet
Carriers ship a browser softphone — but only for their own lines and their own minutes. Integrators connect Asterisk to a CRM — but you still talk into a handset. Bitrix24 documents that an ordinary application cannot carry the audio in the browser; the ones who get around it brought their own telephony. For someone else’s Asterisk, nobody does it.
Your PBX stays yours. Your trunk, your number, recordings on your server. We do not sit between you and your carrier, and we take no margin on minutes.
What it does
A client calls and the right manager gets their card, deals and history. An unknown number creates a lead by itself, so no call is lost.
The number in the card is a link. Click, and the PBX connects the call — nothing to type, no digit to get wrong.
A headset and the CRM tab. No desk phone, no client software to install and configure on every machine.
When the call ends, the deal gets duration, outcome and the recording your own PBX already makes. Settling “what did we promise them” takes nobody’s time.
What separates this from a quick hookup
Connecting a PBX to a CRM is not the hard part. Making the sales team trust what the card shows is. We know these places first-hand: some from our earlier connector that ran on a client’s portal, some from our own mistakes in the neighbouring product.
| How it shows up | What we do instead |
|---|---|
| Ten “missed calls” from one person | A call is identified by its call id, not by channel: one call, one record, however many phones rang |
| An outgoing call is filed as incoming | Direction comes from where the call arrived, not from the channel name — the administrator chooses that name |
| “Client 101 is calling” — that is a colleague down the hall | Internal conversations never reach the CRM |
| The call is credited to the wrong person | The call is credited to whoever answered: in a ring group that is whoever got there first, and otherwise the per-manager report misstates who is working |
| “Four minutes on the call” when it was forty seconds | Duration is counted from the answer, so “how long we talked” does not become “how long they waited” |
All five are closed by design and by tests, not by whoever edits the code remembering them. Verified against a fake PBX and a fake portal; on your installation we have yet to see it together.
What sits where
How it is built
The connector listens to your PBX and talks to the CRM over its own API. Audio goes from the manager’s browser straight to your PBX, not through us: call events pass through us, the conversation does not.
So the rollout holds no surprises
The two halves of the product ask for different things, and blurring that would be dishonest: the CRM link installs on almost any PBX, while talking in the browser has conditions no amount of goodwill gets around. If something is missing, you hear it before the invoice, not after.
Money
The subscription is per installation. Hire three more people in sales and the invoice does not move. Minutes you pay your carrier directly; we do not resell them.
We name the price for a first installation in conversation: it depends on the work your PBX needs, not on how many managers you have.
Where it stands
Next
If you run Asterisk with Bitrix24 or amoCRM and your managers still dial from a desk phone, write or call. We install the first ones ourselves and listen to what gets in the way: this is better built against your PBX than against our idea of it.