CRM integrations are connectors that link a CRM to your channels, payment services, telephony and accounting systems, so their data lands in a single customer record instead of five tabs. Each connector syncs both ways: a customer writes on Telegram and the message is already in the record, pays through Payme and the deal status updates with no manager. Three layers are critical in Uzbekistan: Instagram and Telegram as channels, the local Payme, Click, Uzcard and Humo payments that global CRMs usually lack, and accounting in 1C. In Zukko.AI these connectors are native and on every plan; if a service is missing from the catalogue, you connect it yourself through the open API and webhooks from the Business plan, or we build your own integration on the Enterprise plan by quote. All channels meet in one inbox where the AI employee (AI agent) replies, and your data stays yours, with export available at any time. Onboarding takes from 2 hours for a small business and up to 30 days for an enterprise.
Below: what a connector is in plain words, what you can connect, how native integrations differ from universal ones, and why this is critical in Uzbekistan.
What integrations are, in plain words
Every business already has its own set of tools: messengers, payment services, 1C, a till, telephony. Replacing all of it for the sake of a new system is expensive and painful. Integrations solve the problem differently: the AI-CRM becomes a layer on top of your stack and ties scattered tools into one system.
Each integration is a connector: it plugs an external service into the CRM with two-way sync.
- A customer writes on Telegram — the message and the contact are in the record immediately.
- A customer pays through Payme — the deal status updates with no manager involved.
- A document is posted in 1C — the data syncs in both directions.
- A call takes place — the recording, transcript and outcome land in the same record.
What you can connect
| Category | What connects |
|---|---|
| Channels | Telegram, Instagram, WhatsApp, Facebook, Viber, web chat |
| Payments | Payme, Click, Uzcard, Humo, international acquiring |
| Accounting and retail | 1C, point-of-sale and warehouse systems, HoReCa systems |
| Telephony | VoIP/SIP providers, SMS gateways |
| Work services | Calendars, documents and spreadsheets, email, corporate messengers |
| External CRMs and ERPs | Classic CRMs and accounting systems via the open API, from the Business plan |
The channels converge into one feed — how that works is described in the single inbox module. Telephony and call recording are covered under VoIP telephony.
What if the connector you need does not exist
If a service is not in the catalogue, from the Business plan you can connect it yourself through the open API and webhooks. We build your own integration on the Enterprise plan, by quote.
A word on lock-in: the data stays yours and export is available at any time. An integration should not turn into a lock on the door — it is a working connection that can be cut.
Native connectors or universal integration builders
There are two approaches on the market: a native connector inside the platform, and universal integration services (no-code “zaps” between apps). The difference shows up not in the demo but in the third month of use.
| Universal integration services | Native AI-CRM connectors | |
|---|---|---|
| How it works | Through an intermediate layer | Directly, inside the platform |
| Sync | Usually one-way | Two-way |
| Paying for volume | Operations billed separately | Included in the plan |
| Local UZ payments | Usually absent | Payme, Click, Uzcard, Humo |
| Who fixes a breakage | You or a contractor | The platform vendor |
Universal zaps are fine for rare, non-critical scenarios. Anything touching money, inbound enquiries and the customer base is safer on native connectors.
Why this matters in Uzbekistan
The main local wedge is the payment rails: Payme, Click, Uzcard, Humo. Global CRMs generally do not support them: the till lives separately and the deal in the CRM is closed by hand. The second wedge is channels: in Uzbekistan sales and support happen in Instagram and Telegram, not in email.
The third is local accounting: 1C, point-of-sale and warehouse systems. When all three layers are connected to one AI-CRM, the manager does not need five tabs open and the director does not need to reconcile reports from different systems.
How to connect: the order of work
- Map the stack. Which channels, payment services, telephony and accounting systems are already in use.
- Mark what is critical. What must sync both ways and what only needs to be read.
- Connect the ready-made connectors. Channels and payments are usually switched on at the start.
- Build what is missing. From the Business plan, connect the service yourself through the open API and webhooks; on the Enterprise plan we build your own integration by quote.
- Check permissions and logs. Who sees which data and where the change log is kept — see Security and data.
For a small business the whole path takes from 2 hours; for an enterprise environment with internal systems, up to 30 days.
Frequently asked questions
Can WhatsApp, Telegram and Instagram be connected to the CRM
Yes. Incoming chats and comments are gathered into a single inbox and attached to the customer record, together with calls.
Are local payments Payme, Click, Uzcard and Humo supported
Yes. Global CRMs usually do not cover local payment rails — for Uzbekistan that is a decisive difference.
What if the connector we need does not exist
From the Business plan you can connect the service yourself through the open API and webhooks. We build your own integration on the Enterprise plan, by quote.
Is there any vendor lock-in
No. The data stays yours and export is available at any time.
How long does connection take
For a small business, from 2 hours; for an enterprise with internal systems, up to 30 days.
Do we need a developer
Not for the ready-made connectors — those are set up in the interface. A developer may only be needed on the side of your own internal system.