Skip to content
sipbox

Cloud PBX integrations

A catalogue of what sipbox connects to today and what is being built. The status next to each item is honest: an integration counts as working only when it runs for a live customer — everything else is marked “in development” and does not pretend otherwise.

CRM

Bitrix24

Customer card on an incoming call, the call and its recording in the deal timeline, a flag for a failed attempt, routing by deal owner.

amoCRM

in development

Connector in development. We name no date until it runs for a live customer: a date that slips costs more than an honest “not yet”.

RetailCRM

in development

In development. Until then the link is built with webhooks — RetailCRM accepts inbound requests.

1C

in development

In development. Exchange with 1C is normally built by whoever maintains the configuration; from our side it needs webhooks.

For developers

Webhooks

Call events are sent to your endpoint over HTTP. This is how sipbox is wired to a system that has no ready-made connector.

REST API

in development

No public documented API yet. Settings are managed in the portal; outbound events are delivered by webhooks.

Messengers

Telegram

in development

Missed-call alerts into a chat are in development. Today alerts go by email and over webhooks.

Your system is not on the list

That is expected: we have two ready-made connectors and the market has hundreds of systems. The practical route is webhooks — sipbox posts call events to your endpoint and your system does whatever it needs with them. That is how in-house CRMs, ERPs and industry systems get connected. If you are unsure whether that route fits your case, write to us and we will work it out before onboarding rather than after.

Questions about integrations

Why are there only two working integrations?

Because we count an integration as working only when it runs for a live customer and we support it. A wall of ten logos, half of them “in beta”, looks more convincing but leads to people signing up for a connector that does not work. Bitrix24 and webhooks cover most of what people need; the rest is built on the same core as demand appears.

When will amoCRM, RetailCRM and 1C arrive?

We name no dates until the connector works for a live customer. A promised date that slips costs more than an honest “in development”. If a specific system is critical to your decision, say so in your request — it affects priority.

Can telephony be connected to an in-house system?

Yes, with webhooks. sipbox posts call events over HTTP to an endpoint you specify, and your system decides what to do: create a record, open a card, send an alert. It needs an endpoint reachable from the internet and a developer to handle the request.

Do integrations cost extra?

No. We charge for seats, not for connectors: integrations are included. Which capabilities come with which plan is in the comparison table on the pricing page.

What happens to the integration if we switch CRM?

The connector is reconfigured for the new system, while call history and recordings stay in sipbox: they live with us and export to your own storage rather than existing only inside the CRM. Changing CRM does not cost you the recordings.

Connect your own trunk

Tell us about your setup — we’ll estimate the savings at your volume and help configure your carrier’s trunk.

Request accessTalk to us