WhatsApp that closes. Not just answers.
An AI seller on the official WhatsApp Business API: answers in seconds around the clock, qualifies the lead, handles objections, books, sends a payment link and writes the result into your CRM. Russian and Kazakh.
What the agent does in WhatsApp.
Answers in seconds, at any hour
Every incoming message gets a real answer about price, availability and terms, read from your knowledge base, instead of a promise that somebody will call back tomorrow.
Qualifies before a human is involved
The agent asks the three to seven questions your team always asks, records the answers and passes on a lead that is already understood.
Handles the standard objections
Expensive, I will think about it, I found it cheaper. These get an answer grounded in your own positioning rather than silence until a manager is free.
Issues an invoice from the chat
With Kaspi connected, the agent issues an invoice using the customer's phone number. The customer pays in the Kaspi app, and Pleep receives the payment status and continues the WhatsApp conversation.
Broadcasts on approved templates
Outbound campaigns to your own opted-in lists run on templates, with per-campaign delivery analytics, and replies come back to the same agent instead of into a void.
Hands over with the full history
When a person is needed, the operator picks up the same thread with everything already said. The agent goes quiet on that conversation rather than talking over your team.
Official API or a phone with a QR code.
WhatsApp automation splits in two long before you compare features. One route is sanctioned by Meta. The other signs in as you, and the thing it risks is the number your customers already have.
| Unofficial QR automation | Official WhatsApp Business API | |
|---|---|---|
| How it connects | Scans a QR code from your phone | A verified business and a registered number |
| What is at risk | The number, and every chat history on it | Nothing beyond normal policy compliance |
| Outbound messaging | Sends until the number is flagged | Templates approved in advance |
| Survives WhatsApp updates | Breaks when the app changes | Versioned and documented |
| Multiple operators on one number | Fragile or unsupported | Built in |
| Business profile and display name | Not available | Available after business verification |
| Green verified badge | Not available | A separate Meta decision, never guaranteed |
| Broadcast analytics | Guesswork | Delivery and read data per campaign |
| If the number is lost | The history goes with it | The number is registered to your business |
The real price of the cheap route is not the subscription. It is the working number, which is usually the single most valuable asset a small sales team owns.
The WhatsApp rules that shape everything.
These are not formalities. They decide what any WhatsApp tool can do for you, and most comparison pages never mention them.
The 24 hour window
Once a customer writes, you can reply freely for 24 hours. After that a template approved in advance is required. This is why a fast first answer is a commercial decision, not a nicety.
Templates for anything you start
Any message you initiate outside the window has to be a pre-approved template. Campaign copy therefore has to be planned, not improvised the morning it goes out.
Consent is required
Marketing messages go only to people who agreed to receive them. Bought lists are how numbers get blocked, and no vendor can protect you from that choice.
The number carries a quality rating
Blocks and complaints lower it, and a lowered rating cuts how much you can send. Relevance is not only good manners here, it directly sets your sending capacity.
One number, many operators
On the official API several people and the agent can work the same number at once without anyone logging out. On a phone with a QR code the number belongs to whoever holds the device, which is why handover there is always fragile.
Business verification gates the profile
The company name, the description and the catalogue depend on verification through Meta. It is worth starting early because it is the slowest step and it is what makes the number look like a business rather than an unknown caller. The green badge is a separate decision by Meta and nobody can promise it, so treat verification as unlocking the profile only.
Where WhatsApp leaks money without automation.
WhatsApp is the main sales channel in this market, and it is usually the least managed one. The leak is rarely a missing feature, it is time of day.
Evenings and weekends
A large share of enquiries arrive when nobody is on shift. By the morning the customer has already written to two competitors.
Answered but not sold
Manual replies tend to answer the question and stop. Nobody qualifies, nobody follows up, and the conversation quietly ends after two messages.
Nothing reaches the CRM
Conversations stay in the app, so there is no pipeline, no follow-up list and no way to see where deals die.
Follow-up never happens
Most deals here need a second and a third touch. Manually, the second touch depends on somebody remembering, so the leads that needed one nudge are the ones that quietly close with a competitor.
One phone, one person
When WhatsApp runs on a physical handset, the channel belongs to whoever holds it. Holidays, sick days and staff turnover all become outages, and the history walks out of the door with the device.
How it goes live.
Connect the number
A WhatsApp Business number and a business that can be verified. This is the longest step, and doing it properly is what buys the official channel.
Load prices and policies
Point it at your site or upload documents. Pleep builds the knowledge base and a first sales script in about five minutes, with no prompt engineering.
Turn it on and read the transcripts
Correct anything off in plain language. The fix sticks, and it applies to Instagram, Telegram and voice too, because it is the same agent.
WhatsApp is where it closes, rarely where it starts.
Leads usually arrive from an Instagram post, an ad or a call and finish in WhatsApp. Splitting those across tools splits the context with them.
Instagram feeds WhatsApp
A comment becomes a Direct message, then the customer sends a number. The same agent picks it up in WhatsApp already knowing what was discussed.
Voice reopens stalled chats
For larger or silent leads the agent can call, then continue in WhatsApp afterwards, with the call and the chat in one history.
One knowledge base behind all of it
Prices change in one place. Every channel starts answering the new number the same day, with no flow to edit per channel.
Advertising lands in WhatsApp
Click-to-WhatsApp campaigns drop a stranger straight into the chat, usually outside working hours. Whether that spend converts is decided by what happens in the first minute of that conversation.
The site widget continues here
A visitor who starts on the website and leaves a number is picked up in WhatsApp by the same agent, already knowing what was asked, so nobody has to open with what can I help you with.
Where the result lands.
WhatsApp conversations that stay inside WhatsApp produce work nobody acts on. These are the systems the agent writes into.
amoCRM and Bitrix24, natively
Lead created, deal moved, transcript attached, custom fields filled. The agent also reads the deal stage back, so a customer mid-pipeline does not get the same opening message as a stranger.
Booking, stock and payment
Altegio and Google Calendar write the appointment, MoySklad answers availability, and connected Kaspi lets the agent issue an invoice using the customer's phone number. Payment takes place in the Kaspi app, and its status returns to Pleep.
Your own systems
Public API, webhooks, custom API tools and MCP servers let the agent look up an order or a delivery status mid-conversation. Confirm API permissions and integration scope for your account.
How this compares to other WhatsApp tools in Kazakhstan.
The category mixes three different products: API providers, CRM connectors and AI sellers. Several tools below are better than Pleep at the job they were built for.
- Wazzup
- The regional default for putting WhatsApp inside amoCRM or Bitrix24, and very good at it. A connector rather than an AI seller: it delivers messages to your managers, it does not sell for them.
- Wazzapo
- Kazakhstan-focused WhatsApp Business API with visual workflows and AI replies. A direct competitor on WhatsApp specifically and a strong one on this channel.
- Umnico
- A messenger aggregator with a long integration list and a mature inbox. Built aggregator-first, so AI selling is an addition.
- Kommo
- A CRM with WhatsApp built in, global rather than local. Good if you want the CRM and the channel from one vendor.
- respond.io
- The strongest international omnichannel platform here, with excellent documentation. Priced for a global audience, with no Kazakh focus and no Kaspi.
- WATI
- WhatsApp only, strong on templates, broadcasts and team inbox. A narrow tool that does its narrow job well.
- 360dialog
- A Business Solution Provider that sells the API access itself. You still need something on top to actually answer customers.
- Pleep
- An AI sales agent on the official API: qualifies, handles objections, books, issues invoices through connected Kaspi for payment in the Kaspi app, writes to amoCRM and Bitrix24 natively, and covers Instagram, Telegram and voice on the same brain. Russian and Kazakh as first-class languages.
| Question to ask | Why it decides the outcome |
|---|---|
| Official API or QR automation? | The unofficial route risks the number, and the number is the asset |
| Does it sell or only deliver messages? | A connector puts the message in front of a manager, an agent answers it |
| What happens at 22:00? | Most enquiries here arrive outside working hours |
| Can it take payment in the chat? | Moving to an invoice by email is where conversion drops |
| Which CRM is native, not via middleware? | Middleware is one more subscription and one more failure point |
| How is the Kazakh on your own script? | Feature tables claim it more often than live demos deliver it |
| Does the same agent cover Instagram and calls? | Splitting channels across vendors splits the customer history |
What it costs.
Two separate bills are worth keeping straight: the platform, and what Meta charges for WhatsApp conversations.
Subscription by volume
A plan base plus a per-message rate; the message rate is identical on every tier. Light with 1,500 messages is about $81.50 for one messenger. The first seat is included, with additional seats at $15 per month (7,800 KZT at 520 KZT/USD). CRM write-back is on Business; confirm custom API requirements for your account. The homepage calculator prices messages and voice; additional seats are billed separately.
Meta charges separately
WhatsApp conversation fees are set by Meta and depend on country and category. Any provider passing them on is normal, and any provider hiding them is worth a second look.
Or a share of revenue
There is a programme where you pay a percentage of closed deals instead of a subscription, calibrated to average order value and conversion.
What actually drives the bill
Volume is messages, not conversations, so a chatty agent costs more than a precise one. This is another reason answer quality is a cost question and not only a conversion question: an agent that resolves a question in four messages is cheaper than one that takes twelve to say the same thing.
What you need to start.
The paperwork is the slow part. The knowledge base is the part that decides whether the agent is any good.
A number and the right connection method
Choose the connection method first. Coexistence keeps the phone app working for a supported WhatsApp Business number. Direct Cloud API has different requirements; do not delete an existing account before checking the method you will use.
A business that can be verified
Verification through Meta needs the usual company details. It is worth doing early because it gates the profile and the green tick.
Your prices in writing
A price list, delivery terms and the answers you already send by hand. Without them the agent will correctly say it does not know.
A list with real consent, if you plan to send first
Inbound answering needs no list at all. Broadcasts do, and the list has to be people who agreed to hear from you. A bought database is the fastest way to lose the number, and that is a decision no platform can undo for you.
A decision about what the agent must never do
Discounts it cannot offer, promises it cannot make, questions that always go to a human. Writing these down before go-live takes ten minutes and it is the difference between an agent you trust with real customers and one somebody has to supervise.
Frequently Asked Questions
You need a WhatsApp Business number, access to the official WhatsApp Business API and a platform that answers on top of it. With Pleep you connect the number, point it at your site or upload a price list, and it builds a knowledge base and a first sales script in about five minutes. There is no flow to draw and no prompt to engineer.
After a customer writes to you, you may reply with free-form messages for 24 hours. To start a conversation outside that window you need a message template approved in advance. This is the main reason a fast first answer matters: the window opens when the customer writes, not when someone notices.
On the official WhatsApp Business API the number is registered rather than borrowed, so normal automated answering does not put it at risk. The real risks are sending to people who did not consent and collecting complaints, which lowers the number quality rating and cuts how much you can send.
Yes, to your own opted-in lists, using approved templates, with per-campaign delivery analytics. Replies come back to the same agent, so a broadcast turns into conversations rather than into unanswered messages.
Both are native. The agent creates the lead, updates the deal and attaches the transcript. Altegio and Google Calendar handle booking, MoySklad handles stock, and custom APIs or MCP servers can be called as tools.
Russian and Kazakh both, as first-class languages. Most international WhatsApp tools are weak here, and it shows up as customers not replying rather than as an error message.
With Kaspi connected, the agent issues an invoice using the customer's phone number. The customer pays in the Kaspi app, and Pleep receives the payment status and continues the conversation. Other gateways are discussed separately.
An operator opens the same thread with the whole history and continues. The agent stops answering that conversation, so your team is never talking over the automation.
There are two bills. The platform, where Pleep starts at about 42,380 tenge a month including 1,500 messages on the entry plan, and Meta fees for chargeable delivered messages, which depend on country and message category and are billed on top by whoever provides your API access. Any comparison that shows only one of those two numbers is incomplete.
For a supported WhatsApp Business number, Meta coexistence keeps the phone app working while Pleep handles messages through the API. Availability is checked during connection; this is not a promise for every personal WhatsApp account. Direct Cloud API is a separate connection mode with different number-migration requirements. Do not delete a working account in advance: choose the connection method and check its requirements first.
Answer the next WhatsApp message in seconds.
Connect the number and let the agent qualify, answer and close while your team sleeps.