CRM19 minJuly 10, 2026
CRM integration with Telegram, Instagram and your website: one funnel without lost leads
Robert MirovUpdated Jul 10, 2026
Integrating CRM (Customer Relationship Management — a system for tracking clients and deals) with your channels is not an “IT feature”. It is how you stop losing leads between Telegram, Instagram and the website. In Tashkent and across Uzbekistan the typical picture is: a client writes to a Telegram bot, repeats the question in Instagram Direct and submits a site form. Without one CRM (or without strict manual entry) you get three “new clients”, two managers reply to the same person, and the owner cannot see which channel produced payment. The goal of integration is simple: one contact — one card, every deal has a source (where the lead came from), an owner and a history. Below: architecture, connection order, webhook (automatic data push from a channel to your server), UTM, security, permissions, a test checklist, follow-up and soft timelines. No drama about “you will lose everything”, and no promise that “once connected, sales jump”. This complements CRM implementation and CRM for small business.
01Why connect channels to CRM: what breaks without it
Without channel links, CRM stays a “nice funnel” while leads live in private chats. Loss rarely looks like intentional ignore — usually it is everyday chaos.
A typical day without integration: morning message to the bot, afternoon Instagram Direct, evening site form lands in email, night call from a 2GIS number. Next morning some threads are forgotten, some are duplicated, and nobody writes the source.
| Before | After | |
|---|---|---|
| Three touches from one person = three “new” leads | One card, three activities in history | |
| Reply from a manager’s personal Instagram | Work channel + CRM record | |
| Site form to whoever’s inbox | Webhook → deal with `source=website` and UTM | |
| Owner report: “lots of messages somehow” | Report “source → lead → payment” | |
| Ads “work”, payments below expectation | Clear which channel makes money vs noise |
02Target architecture: one intake — one card
Base scheme for Uzbekistan businesses: Telegram bot, Instagram and site form land in one CRM. Card minimum: contact, request summary, source, owner, created time.
| Channel | What to pass to CRM | UZ note | |
|---|---|---|---|
| Telegram | Handle / `chat_id`, text, `source=telegram` | Most stable Bot API; often the main B2C channel | |
| Website | Name, phone (+998), UTM, `source=website` | Cleaner leads with phone validation | |
| Handle, text/dialog link, `source=instagram` | API harder; early manual SOP is fine | ||
| Call / 2GIS | Name, phone, `source=phone` or `maps` | Manual entry — but source is mandatory |
Principles without which integration is useless:
• deduplication (finding duplicates) by phone or Telegram ID — a repeat updates the card, it does not create a second “new client”
• notify the manager on Telegram when a lead is created
• source is filled automatically from the channel or by strict SOP — never “as it happens”
• history on the card: what was asked, what was answered, when to call back
If the system cannot answer “how many live deals now and where from” — it is not a working integration yet, just scattered chats next to a CRM login.
03Terms worth understanding before setup
Agree on words before connecting channels — otherwise the team and the vendor talk past each other.
• Lead — a potential client who showed interest (wrote, submitted a form, called).
• Deal / card — a CRM record with funnel stages (new → in progress → paid / lost).
• Source — channel label: `telegram`, `instagram`, `website`, `phone`, `referral`.
• Webhook — the channel POSTs to your endpoint (server URL) when a request appears.
• UTM — tags in ad links (`utm_source`, `utm_campaign`, etc.) to see not only “website” but which campaign.
• Deduplication — rule “same phone / chat_id = same card”.
• Endpoint — the URL that receives data from the bot, form or middleware.
| Term | Why the owner cares | |
|---|---|---|
| Source | See which channel brings payments, not only chats | |
| Webhook | Remove manual copy from chat to Excel | |
| UTM | Separate Google Ads from Instagram Ads inside “website” | |
| Dedupe | Avoid counting one person twice in ad reports |
Without these agreements, integration becomes “something was connected” and reports stay empty.
04In which order to connect channels
A calm order for most local businesses — not “everything at once”, but a chain you can verify.
1. Telegram — prove the full bot → CRM chain on a test number.
2. Website — form + UTM on the same webhook pattern and the same fields.
3. Instagram — official integration, middleware or a temporary manual SOP with tag `instagram`.
4. Calls / maps — manual entry with mandatory source if call volume is high.
| Stage | What you connect | Why this order | |
|---|---|---|---|
| 1 | Telegram → CRM | Stable API, familiar channel, easy to test | |
| 2 | Website → CRM | Same webhook template + UTM for ads | |
| 3 | API/SOP harder; does not block Telegram/site ads | ||
| 4 | Calls | Manual discipline after automation already works |
In Uzbekistan Telegram is often the main B2C channel: people write faster than they call. Once bot → CRM works, other channels follow the same field template. More on the bot — Telegram bot for business.
05Telegram → CRM: what to set up in practice
Telegram is usually the first and most useful channel to connect.
Setup minimum:
• a bot with a short quiz or form: service / product, city or district, budget or urgency, phone
• webhook → CRM endpoint with `source=telegram`
• auto-reply to the client: “request received, manager will contact within N hours” (N must be a real promise, not marketing)
• bind `chat_id` to the card — so you reply in the same thread and do not create duplicates
• manager push in work Telegram: name, summary, link to the card
What teams often forget:
• first-contact rule (CRM task within 15–60 minutes or the same workday)
• what to do if the client writes to a manager’s private chat — SOP: move to CRM or reply from the work account with a record
• test the “bad” path: bot down, CRM down, empty phone
| Before | After | |
|---|---|---|
| Client DMs the manager | Bot collects fields → CRM card | |
| “Someone will reply” | Push to a concrete owner | |
| Repeat message = new lead | `chat_id` / phone → same card | |
| No reply-time promise | Auto-reply with honest N hours |
When this chain is green, you can calmly add the website and ads — not the other way around.
06Website and UTM: cleaner leads from the form
The site form is the second most important intake, especially if you run Google Ads, Yandex or social ads to a landing page.
What to pass to CRM:
• name, phone with format validation (+998…)
• hidden UTM: at least `utm_source`, `utm_medium`, `utm_campaign`
• `source=website` (plus UTM in separate fields or a comment)
• page / service the form was submitted from
• time and form language if the site is bilingual
Webhook → JSON to the same endpoint template as Telegram. Do not invent a “special site integration” with different field names — managers will get lost.
| Field | Why | |
|---|---|---|
| Phone with validation | Less junk and fake leads | |
| UTM | Separate campaigns inside “website” | |
| Form page | See which offer worked | |
| source=website | One channel report |
A form with phone validation usually yields cleaner leads than cold Direct. If the form only emails someone — that is not CRM integration, it is delayed lead loss during a manager’s vacation.
07Instagram: Direct reality and honest options
Instagram Direct does not always have a direct, stable API for your stack. That is not a reason to ignore the channel — it is a reason to choose an honest mode for your current maturity.
Options:
1. Official Meta integrations (if available for your account type and CRM).
2. Middleware services that receive messages and POST a webhook to CRM.
3. Early on — SOP: manager enters Direct leads manually with tag `source=instagram` within N minutes.
Do not mix personal and work accounts — otherwise source is “unknown” and sales automation loses meaning. One work account, one SOP, one source.
| Approach | When it fits | Risk | |
|---|---|---|---|
| Manual SOP | Low Direct volume, disciplined team | People forget to enter CRM | |
| Middleware + webhook | Medium volume, need speed | Vendor dependency, token checks | |
| Official Meta integration | Stable volume, ready for setup | Longer rollout, Business permissions |
Owner rule: Direct without a CRM card = process breach, even if you “already replied nicely”. Otherwise Instagram reports will always undercount.
08Webhook, security and error handling
Integrations run on webhooks: the channel POSTs to your endpoint. Without security and a buffer, a lead can vanish silently — the worst case when ads are running.
Security minimum:
• secret token in the header — verify on the server (not in the URL “for convenience”)
• HTTPS on the endpoint
• timeout on outbound CRM API calls (guide: up to 30 seconds)
• error logging with time and failure type — without leaking internals to the client
• service API account, not a manager’s personal login
Retry queue: if CRM is down, store the payload (request body) and retry in 1–5 minutes several times. UZNEO bot projects include that buffer by default.
| Failure | What should happen | |
|---|---|---|
| CRM down for 2 minutes | Lead queued, then created | |
| Wrong token | Request rejected; log records the attempt | |
| Empty phone from site | Form validation; junk never reaches CRM | |
| Duplicate same chat_id | Card update, not a second lead |
If “integration exists” but leads disappear when CRM blips — it is a demo, not a finished stack.
09Source labels, permissions and report “through to payment”
Sources (minimum): `telegram`, `instagram`, `website`, `phone`, `referral`. Every deal must have a source — no exceptions. For the website, also store UTM.
Permissions:
• manager — own deals / group
• lead / supervisor — all deals + source report
• API token — service account, not a personal login
• audit log: who changed stage and when
Monthly, look not only at “source → lead”, but “source → payment” and loss reasons. Otherwise Telegram ads can look “successful” by chat count and weak by money.
| Role | What they see | Why | |
|---|---|---|---|
| Manager | Own cards, tasks | Focus on reply, not other people’s deals | |
| Supervisor | All + source summary | Manage channels and load | |
| Owner | Payments and losses by channel | Decide where to spend budget | |
| API / bot | Create and update leads | No “delete whole database” rights |
Permissions and source are not bureaucracy. They protect you from a month later when nobody remembers where paying clients came from.
10Soft timeline guides
Timing depends on CRM readiness, Meta accounts and custom work. Below is a guide for small and mid-size businesses in Uzbekistan — not an SLA and not a price list.
| Stage | Typical work | Soft guide | |
|---|---|---|---|
| Weeks 1–2 | Telegram → CRM, alerts, dedupe | Chain on a test number | |
| Weeks 2–3 | Site form + UTM | Same fields and webhook | |
| Weeks 3–4 | Instagram (API or SOP) | Source visible in reports | |
| Month 1 | Channel vs CRM loss check | UTM and rule fixes | |
| Month 2+ | Report tuning | “Source → payment” as habit |
If CRM is not implemented yet — funnel and discipline first, then channels. If channels already dump leads into chaos — Telegram and website first while simplifying the funnel. Full stages — CRM implementation.
11Pre-launch test checklist before ads
Walk every item on a real test number (+998), not “by eye in admin”.
☐ Telegram: message bot → CRM lead in under 2 minutes, correct `source`
☐ Website: form → lead with UTM, manager notified
☐ Instagram: test → automatic lead or manual entry per SOP with tag
☐ Dedupe: repeat same phone / chat_id → one card
☐ Owner assigned by rule (not empty)
☐ Manager Telegram push arrived with link/summary
☐ Source report shows channels separately
☐ Webhook errors logged; if CRM “falls”, lead is not lost (queue/retry)
☐ Client auto-reply sends and does not promise the impossible
☐ Permissions: manager does not see others’ deals if that was intended
After a green checklist you can point ads at one turnkey CRM. Before a green checklist, ads amplify chaos, not sales.
12Follow-up after launch and common mistakes
In month one check weekly:
• silent losses — channel lead count vs CRM
• UTM still valid after campaign and landing changes
• dedupe on repeat contacts
• replies have not drifted back to personal accounts
When you change CRM or add a channel, rerun the full checklist.
| Mistake | How it ends | Calmer path | |
|---|---|---|---|
| Connect everything at once | Nothing tested, people stop using it | Telegram → website → Instagram | |
| No source | Ads blind | Mandatory source, UTM on site | |
| No retry queue | Leads vanish on outage | Buffer + logs | |
| Personal accounts | History leaves with the employee | Work channels only | |
| Report leads only | Channel looks “top” | Watch payments and losses | |
| Ignore dedupe | Two managers on one client | Phone / chat_id |
Integration is a living process: campaigns change, people leave, Meta updates rules. Once a month — a short check, not “set and forget”.
Summary
One funnel from Telegram, Instagram and the website is basic sales hygiene in Uzbekistan, not an “advanced upgrade”. Calm order: bot and webhook → site form with UTM → Instagram as the process matures. One contact — one card, every deal has a source, every failure has a log and a retry — not silence. UZNEO designs these integrations — from a Telegram bot to a CRM system and sales automation. Write us — we will map your real channels and verify them with a checklist before you scale ads.
Automate sales and leads?
Bots, CRM and integrations for your business. Automation plan in 24h on Telegram.
Related services
More articles
8
CRM22 min
Best CRM for business in Uzbekistan
CRM17 min
CRM for small business: what it is and why it matters in practice
CRM19 min
CRM implementation: stages, timeline and typical mistakes
CRM18 min
AmoCRM, Bitrix24 or custom CRM: how to choose
Telegram bots14 min
Why a business needs a Telegram bot: what it gives you and when to wait
Telegram bots19 min
Telegram bot vs mobile app: what a business in Uzbekistan should choose
Telegram bots18 min
Telegram bot for leads and payments: how 24/7 intake works
Telegram bots17 min
