For an online store in Kazakhstan, orders come in from everywhere: the website, Instagram Direct, WhatsApp, the Kaspi store, phone calls, and Telegram. As long as managers keep all of this in their heads, in Excel spreadsheets, and in scattered chats, 15-30% of inquiries are lost: a customer messages you on Direct, gets no reply within an hour, and moves on to a competitor. Bitrix24 solves not "record-keeping for its own sake" but a specific challenge: consolidate every channel into a single pipeline, prevent any lead from slipping through, and extract repeat sales from the customer base you have already built. Below is how this works technically and what can actually be configured for a Kazakhstani business.
The Problem: Orders in Six Places and Zero Analytics
A typical store handling 200-500 orders per month works like this: the website sends inquiries to an email inbox, an SMM specialist runs Instagram from a phone, a separate person processes Kaspi orders in the Kaspi dashboard, calls go to a mobile number, and delivery is coordinated with the courier over WhatsApp. No one knows the real conversion rate by channel, which customers cost more to acquire, or why revenue dropped. When a manager leaves, their contact base leaves with them.
Bitrix24 closes this gap through a unified CRM, where every order is a deal with a source, an amount, a status, and a conversation history. The goal of the first week of implementation is to make it physically impossible for any lead from any channel to bypass the CRM.
Step 1. Orders from Every Channel in One Pipeline
The core tool is Bitrix24 Open Channels plus the Wazzup connector. In Kazakhstan, Wazzup is the de facto standard for connecting WhatsApp (including the WhatsApp Business API), Instagram Direct and comments, and Telegram. All conversations land in a single chat inside the CRM, are linked to a contact, and a deal can be created from a conversation in one click.
- Website - the order form and cart via CRM forms or the online store module; an inquiry immediately becomes a deal complete with UTM tags.
- WhatsApp / Instagram / Telegram - through Wazzup, the conversation history is stored permanently in the customer record rather than on the manager's phone.
- Calls - IP telephony on Asterisk: an incoming call pops up the customer record, and missed calls automatically become tasks or deals.
- Kaspi - orders from the Kaspi store are pulled in via integration, so Kaspi does not remain a blind spot outside the CRM.
- Email and 2GIS / the callback form - these are also set up as sources feeding into the same pipeline.
Step 2. Integration with the Website and 1C - So You Never Enter Orders by Hand
If the website runs on 1C-Bitrix, the online store connects to the CRM natively: a website order equals a deal, the cart equals line items, and statuses sync in both directions. For sites on other CMS platforms (Tilda, WordPress, OpenCart), you use CRM forms, a widget, or integration via the REST API and webhooks.
Integration with 1C is a critical part for Kazakhstan, because inventory accounting, invoices, and tax reporting all live in 1C (Small Business Management or Accounting for Kazakhstan). Two-way exchange eliminates double entry:
- Products and stock levels are exported from 1C into the Bitrix24 catalog, so a manager can see whether an item is in stock without calling the warehouse.
- Prices and discounts are pulled from 1C, so the CRM never holds outdated price lists.
- A closed deal automatically creates an order or sales document in 1C, so accounting does not need to re-enter the data manually.
- The payment status from 1C is returned to the deal, so the manager can see whether the money has come through or not.
The exchange is configured through the standard 1C-Bitrix exchange module or via REST. Here it is essential to lock down the key reference fields up front (SKU, the counterparty's IIN/BIN); otherwise items and customers will be duplicated - this is the most common pain point of such integrations.
Step 3. Order Statuses and Delivery - Automatic Customer Notifications
A customer in Kazakhstan expects to be notified through the same channel they wrote in - usually WhatsApp. In Bitrix24 this is handled by automation rules at the deal stages: when an order moves to the relevant status, a message is sent automatically.
- "Order received" - the customer gets confirmation with the contents and amount right away, without waiting for a manager.
- "Paid" - payment confirmation (Kaspi, Halyk, card, cash to the courier).
- "Handed to delivery" - a message with a tracking number or the courier's contact; integrations with Kaspi Delivery, CDEK, Kazpost, and local courier services.
- "Delivered" - closing the deal and an automatic request for a review or NPS.
- Any status can be duplicated to Telegram/SMS if the customer came from there.
The pipeline stages are configured around the real journey of your specific store, not around an abstract template. For an online store, 6-8 stages are usually enough: New -> Confirmed -> Awaiting Payment -> Paid -> Picked -> In Delivery -> Delivered -> Closed. Each stage is a point where you can attach an automation rule, a check, or a notification.
Step 4. Abandoned Carts and Incomplete Orders - Money Lying on the Floor
An abandoned cart in Kazakhstan is not only an unfinished payment on the website. More often it is a conversation on Instagram or WhatsApp where the customer asked for a price and then vanished. Bitrix24 catches both scenarios.
- Website: an unfinished order becomes a deal at the "Abandoned cart" stage, and after 1-3 hours a reminder message is automatically sent to the customer, with a promo code if needed.
- Chats: if there is no reply from the customer on a deal for N hours, an automation rule assigns the manager a "follow up" task or sends a tactful reminder itself.
- Response-time SLA: if a new inquiry is not answered within 15-30 minutes, the deal is escalated to a supervisor - this is precisely where the most revenue is lost.
- Segmentation of incomplete orders: what is abandoned most often, at what amount, in which channel - this is visible in reports and points to where the fix is needed.
Recovering even 10% of abandoned carts and stalled conversations pays back a CRM implementation faster than any advertising - these are customers you have already paid to acquire.
Step 5. Repeat Sales: the Core Economics of an Online Store
Acquiring a new customer in Kazakhstan through targeted ads and Kaspi commissions grows more expensive every season. A repeat sale into your existing base costs many times less, but without a CRM that base simply does not exist as an asset. In Bitrix24, every completed order stays in the customer record along with their purchase history - and that turns into revenue:
- Behavioral segments: those who bought a specific category, those who have not purchased in 90 days, those with an above-average order value - each segment gets its own WhatsApp campaign.
- Automated scenarios: X days after buying a consumable - a reminder to reorder; ahead of the season - a special offer to last year's buyers.
- RFM analytics: you can see which customers are about to "go dormant" and win them back with a targeted promotion before they leave.
- Upsells: an automation rule prompts the manager with complementary products based on the order history.
How Much It Costs and Where to Start
Bitrix24 Cloud comes in three plans: Basic suits a launch with a single pipeline, Standard fits a team with several channels and automation, and Professional is for when you need end-to-end analytics, CRM marketing, and many users. If you have a heavy 1C integration, custom development, or requirements to store data on your own server, you go with the on-premise (self-hosted) edition. Wazzup, Asterisk IP telephony, and the 1C exchange are paid for separately from the Bitrix24 license.
A sensible implementation sequence for an online store: first bring all channels into a single pipeline and get response times under control, then connect the website and 1C, then automate statuses and delivery, and only after that switch on abandoned carts and repeat-sales scenarios. Trying to launch everything at once is a common mistake that undermines adoption among managers.
The key principle: a CRM pays off not through features but through discipline in the flow of leads. First, make sure nothing gets lost; then make the customer base work for repeat sales. For a store in Kazakhstan with a volume of 150 or more orders per month, this is usually a matter of weeks until the first tangible revenue growth.
