In Kazakhstan, the first contact with a business almost always comes through a messenger: a customer messages on WhatsApp using a number found on 2GIS, drops a question into an Instagram direct message about an ad, or moves from advertising into Telegram. The problem is that these channels operate separately from the CRM. The sales rep responds from a personal phone, the conversation is invisible to management, and half of the inquiries simply get lost between shifts and over weekends. Below is a concrete blueprint for consolidating Instagram, WhatsApp, and Telegram into a single Bitrix24 pipeline via Wazzup, along with exactly what to configure so that no lead falls through the cracks.
Why Leads Genuinely Get Lost (It's Not That Reps Are Lazy)
Before automating anything, it is worth understanding the mechanics of these losses. In most companies, this is not about motivation but about a leaky process. The typical points of leakage are:
- Conversations live in the rep's personal WhatsApp: the employee leaves, and their clients leave with them, along with the entire history.
- Instagram direct messages are monitored by the SMM specialist rather than the sales team, so an inquiry is seen only several hours later or the next day.
- There is no record of the inquiry as an object: there is nothing to measure, and conversion rates and cost per lead by channel remain unclear.
- In the evening, on weekends, or during lunch, a customer writes and gets no reply for 3 to 6 hours, then moves on to a competitor who responded within 5 minutes.
- One number writes via both WhatsApp and Instagram, creating duplicates, and reps end up contacting the same client twice.
- There is no distribution: the inquiry lands in a shared chat, where it is either grabbed by everyone or picked up by no one.
What Wazzup Is and Why It's the Right Choice
Wazzup is a connector that brings WhatsApp, Instagram Direct, and Telegram straight into Bitrix24 Open Channels. The sales rep communicates not from a phone but inside the CRM record; the entire history is tied to the lead or deal and stays within the company even after an employee leaves. For Kazakhstan, this is a working standard: it supports local carrier numbers (Beeline, Tele2/Altel, Kcell), works with WhatsApp both via the QR code of a personal number and through the official WhatsApp Business API, and does not require reps to keep the client base in their own pockets.
A key point: Wazzup is not just another chat tool but a transport layer. All the logic, including auto-creation, distribution, auto-replies, and templates, is configured within Bitrix24 itself. That is why this combination should be treated as a single whole: channel plus CRM plus rules.
Step 1. Auto-Creating a Lead from Any Message
The first thing to enable is having every new inquiry automatically create a lead (or a deal, if you operate without a lead stage). This is configured in Bitrix24 Open Channels: the 'Automated actions' section, set to create a lead on the first message from a new contact.
- The source is set automatically: you can see whether the client came from Instagram, WhatsApp, or Telegram, which is the foundation for channel analytics.
- The name, avatar, and number/handle are pulled into the record, so the rep does not need to enter anything by hand.
- Enable automatic duplicate detection by phone number and contact linking: if a client previously wrote via WhatsApp and now arrives via direct message, the messages are merged into a single contact instead of spawning duplicates.
- If you already run a pipeline without leads, configure auto-creation of a deal in the appropriate first stage.
Step 2. Distribution Among Sales Reps
An inquiry with no owner is an inquiry that belongs to no one. In Open Channels, set up a distribution queue. There are three basic scenarios, and the choice depends on your team's structure:
- Evenly (round-robin): inquiries are handed to reps in turn. Suitable when the product is uniform and everyone sells the same thing.
- Strictly to the first available rep: whoever takes it first owns it. This is a strong incentive for speed, but it can overload your most active reps.
- By rules: a specific direction/city/language is routed to a specific rep. Relevant when, for example, corporate clients go to one rep and retail to another, or when a Kazakh-speaking operator is required.
Configure escalation separately: if a rep has not responded within N minutes, the inquiry is reassigned to the next rep or to a manager. In Bitrix24, this is done via timers in business processes or via automation rules at a given stage. That way, no 'forgotten' chats physically remain.
Step 3. Response Speed: Auto-Reply and SLA
The customer should not be left in silence, even if every rep is busy or it is currently 11 p.m. The minimum setup:
- An instant auto-reply to the first message: 'Hello! We have received your inquiry; a rep will respond within N minutes. If it is urgent, call +7 701 960 13 11.' It is sent automatically within seconds.
- After-hours hours: a separate auto-reply with an honest expectation: 'We work from 9:00 to 18:00 and will respond in the morning. Leave your question, and we will not lose it.' The lead is still created and waits for a rep.
- An SLA timer on response speed: you set a target, for example, 'first response within 10 minutes.' Bitrix24 highlights overdue chats and sends a notification to the manager.
- Notifications to the rep in the app/Telegram, so a new inquiry is visible immediately rather than only the next time the CRM is opened.
The rule is simple: the customer always gets a reaction within seconds, automated, and a human within minutes. Silence in a messenger equals a lost lead.
Step 4. Templates and Quick Replies
The speed of a live response rests on prepared answers. Build a library of templates for typical questions, so the rep inserts a reply in a single click straight from the record:
- Price list and terms, payment details (including Kaspi), and delivery options across Almaty and the regions.
- Answers to 'Is it in stock?', 'How much does it cost?', and 'Where are you located?', the most common first questions.
- Follow-up templates: 'You were interested in ...; is it still relevant?', for those who left to think it over.
- Account for language: keep parallel templates in Russian and Kazakh so there is no need to switch manually.
An important detail for WhatsApp: if you work through the official WhatsApp Business API, the first message to a customer outside the 24-hour window can only be sent using an approved template. This must be agreed in advance with Wazzup/Meta; otherwise, automated follow-ups and broadcasts will not go through. With a QR connection of a personal number this restriction does not apply, but there is a risk of being blocked for bulk sending, so for broadcasts the API is the more correct approach.
Step 5. Pipeline and Channel Analytics
Once everything is in a single pipeline, something that did not exist before appears: numbers. What to track after launch:
- The number of inquiries by channel: how many come from Instagram, how many from WhatsApp, and how many from Telegram, so you know where to invest the advertising budget.
- The average time to first response per rep: who is slowing the pipeline down.
- Conversion from inquiry to deal and to payment by channel: the real cost per lead, rather than 'it feels like Instagram is working.'
- The share of missed/unanswered inquiries, which should trend toward zero after escalation is configured.
It makes sense to reinforce this combination with IP telephony (Asterisk) and a 1C integration: then the call, the conversation, and the shipment all live in a single record, and payments are pulled in automatically. But that is the next stage; first, close the gap with messengers.
A One-Day Launch Checklist
- Connect WhatsApp, Instagram, and Telegram to Open Channels via Wazzup.
- Enable auto-creation of a lead/deal plus deduplication by phone number.
- Set up the distribution queue and timer-based escalation.
- Enable auto-replies (business and after hours) and an SLA on response speed.
- Upload a template library in two languages and get WABA templates approved for follow-ups.
- Set up notifications for reps and managers.
- After a week, pull the first analytics on channels and response time.
The core point of this entire setup: not a single message from a direct message or WhatsApp should remain in someone's personal phone or go unanswered. Once you have consolidated your channels into a shared Bitrix24 pipeline via Wazzup and added automation for responses and distribution, you stop losing leads for no reason at all, and for the first time you see the real numbers for each source.
