Unified Inbox for WhatsApp, Instagram and Telegram with AI: How to Get Every Chat Into One Window
By Марк Ингер, CEO at Pleep
A unified inbox is not "one more tab". It solves one specific problem: the same person reaches you by three different routes — an enquiry in Direct, a WhatsApp question a week later, a call on Thursday — and every channel greets them as a stranger. Below is how to get WhatsApp, Instagram and Telegram into a single window where AI handles the routine, anything hard goes to a human together with its context, and — just as importantly — what the platforms themselves will not let you do.
One fork in the road first, because this is where most bad decisions start. A "unified inbox" and a "single AI agent" are not the same thing, and getting them confused costs different amounts of money.
A unified inbox and a single AI agent are not the same thing
An inbox unifies what your team sees. An agent unifies what your automation knows. With a separate bot per channel you maintain the same prices and the same terms several times over, and the customer starts from zero whenever they switch channels. With a single agent you fix things once and the fix applies everywhere.
Here is the honest picture of what actually becomes shared and what stays separate. Omnichannel does not mean Instagram, Telegram and WhatsApp suddenly hand you one universal customer identifier.
| Layer | What becomes shared | Where the boundary stays |
|---|---|---|
| Knowledge base | One set of prices, rules and instructions answers in every channel | Messaging rules differ per platform |
| Team inbox | WhatsApp, Instagram and Telegram threads sit in one working window | Each platform keeps its own thread and its own identifier |
| Contact linking | A shared phone number or CRM record can merge one customer's activity | An identical handle does not prove it is the same person |
| Conversation context | The team sees the linked history before continuing | Automatic memory cannot be promised until the contact is matched |
| Human handover | The operator takes the live thread together with its transcript | The channel's reply window and permissions still apply |
The practical gain is one source of truth and one working window — not a pretence that Meta and Telegram issue a universal customer ID.
What each channel brings into the inbox, and what it forbids
An honest omnichannel setup is defined by platform policy, not by the checkbox list on a pricing page.
| Channel | What lands in the inbox | Platform limit |
|---|---|---|
| WhatsApp Business API | Inbound messages, replies, broadcasts using approved templates | Free-form replies are allowed for 24 hours after the customer's message; outside that window only a pre-approved template |
| Instagram Direct | Direct messages, story replies, comment automation | Requires a business or creator account connected through Meta; the customer must write first; a comment allows one private reply within seven days |
| Telegram | Direct messages and a bot | The bot replies without limits once a person starts the chat — the freest channel, and the least useful for people who have not written to you yet |
| Voice calls | Outbound calls and the outcome recorded in the same thread | You need a reason to call: campaigns run against your own lists of people who asked to be contacted |
| Website widget | Conversations from site visitors | Continuing in WhatsApp works only if the visitor left a phone number |
Two conclusions follow. First, first-response speed is a commercial decision rather than good manners, because outside WhatsApp's 24-hour window a free-form reply is simply not possible. Second, any service promising unlimited mass sending on WhatsApp is describing an unofficial route. Sender reputation is shared across the account: blocks and complaints cut your own limits.
Why three channels fall apart when handled manually
It is rarely the first message that breaks. It is the second one — in a different channel, from a person nobody recognised as the same customer.
- Traffic does not arrive during office hours: Instagram and WhatsApp peak in the evening.
- Comments, Direct, WhatsApp, Telegram and the site widget are five separate streams. Manually, you cover whichever one is currently open.
- Without a shared inbox the same person becomes two records and gets two different answers. From the outside that looks like a company that does not know its own prices.
- Handovers drop the thread: a manager picks the conversation up in another tool and the customer explains everything again. That repetition is where people quietly leave, and no report shows it.
- When channels live in different tools there is no single funnel. You end up with message counters per channel and no answer to the only question that matters: at which stage is money being lost.
How this gets set up: five steps
1. Start with the channel that already carries the most conversations
Usually WhatsApp. Channels connect one at a time, and adding the next one does not require rebuilding anything — you configure one agent rather than four bots. WhatsApp needs a suitable business number and access to Meta Business; coexistence mode lets you keep the WhatsApp Business app working on the phone, though availability and verification still depend on Meta.
2. Load the knowledge base once
Point the agent at your website or upload the price list, delivery terms and answers to frequent questions. Everything the agent is expected to answer has to exist as a document. The agent answers from those sources and says it will check rather than inventing a number.
3. Describe who gets which chats
Routing is described in plain words: which topics go to which team member. If no description matches, the chat stays unassigned — that is visible in the filters, and those chats need working through rather than trusting to a queue.
4. Test the flow with a test lead in every channel
Write from a test account into each connected channel. Confirm the conversation appeared under the right agent, the reply is visible to the customer, and the assignee and stage are correct. If a CRM is connected, check the created record separately. A send error has to be fixed before resending, not treated as delivered because the message appeared in the feed once.
5. Read the first conversations
Correct tone and gaps in plain words, with no prompt engineering. The correction applies to every channel at once because there is one agent. With separate bots the same correction is four edits, and one is always forgotten.
How human takeover works
The operator types a reply straight into the chat — and at that moment the AI goes quiet on that lead, so the customer immediately sees a human. Bringing the agent back takes one click, and it continues with the full context of what was said.
Around that sit the working details that decide whether a team actually uses the inbox. Conversations filter by channel, funnel stage, AI-or-operator mode and assignee, so a manager works their own queue instead of the whole company's correspondence. If you run several WhatsApp numbers, you can pick the one you need. Access is granted by role: managers see chats and analytics, operators reply, admins manage everything. And one limit worth knowing in advance: a shared inbox does not override the messenger's own rules — operator mode does not bypass a channel's reply window.
Where the lead lands: funnel and CRM
Every conversation carries a stage: new, qualified, proposal sent, closed. The agent reads that stage as context and shapes its answer around it, while the team sees the same board and can drag a card by hand.
For many B2C teams the built-in funnel is enough. If you are keeping your own CRM, amoCRM and Bitrix24 connect natively, with no middle layer: the agent creates the lead, moves the deal, attaches the transcript and reads deal fields back, so its answer accounts for the current stage. CRM writing belongs to the Business plan — worth factoring into the budget. Altegio and Google Calendar close out appointment booking, MoySklad covers stock, and with the Kaspi integration connected the agent issues an invoice against the customer's phone number, the customer pays it in the Kaspi app, and the agent receives the payment status.
Pleep's built-in funnel and an external CRM are different systems: having one does not mean the other is already connected. The step-by-step setup is covered separately in how to connect amoCRM and Bitrix24 to an AI agent. If Instagram is your main channel, start with the comment-to-Direct guide.
What a unified inbox costs in Pleep
| Plan | What is included | Price |
|---|---|---|
| Light | One messenger, voice agent and WhatsApp calls, website chat widget | 42,380 KZT/mo ($81.50) at 1,500 messages |
| Business | Everything in Light, up to three messengers, broadcasts and automatic follow-ups, amoCRM and Bitrix24, Google Calendar and Altegio, MoySklad | 68,380 KZT/mo ($131.50) at the same volume |
| Enterprise | From 25,000 messages or 5,000 minutes a month, custom integrations, contractual SLA | On request |
| Pay for results | No subscription: a share of revenue or a fixed fee per key action | Rate set against your average order value, agreed individually |
How the price is built: plan base plus a message package, with the same per-message rate on every plan. One operator seat is included; each additional seat costs $15 a month (7,800 KZT at a rate of 520). Voice is billed separately at 50 KZT per minute in tenge or $0.12 per minute in dollars — two independent prices, not a currency conversion. Quarterly billing takes 10% off, and Meta's message fees sit on top. The trial is 7 days, with no card.
Every plan includes the built-in CRM, Instagram comment automation, Kaspi invoices from the conversation, MCP servers and your own APIs, detailed analytics, and answers restricted to your knowledge base. There are three public plans — Light, Business and Enterprise — plus the pay-for-results model; there is no "Pro" plan in the public price list. Current terms and a calculator for your own volume are on the pricing page, and the full connection list on the integrations page.
Who else gets named in this category, and where they are stronger
These products are not interchangeable, and the important distinction is between an aggregator and an agent. Some of the services below are better than us at what they were built for.
- CareHub (carehub.kz) — a Kazakhstan platform with a unified inbox and an AI agent. Per their own site: the entry plan is 19,900 KZT/mo (shared inbox, WhatsApp via QR, AI agent), official WABA broadcasts start on the Business plan at 54,900 KZT/mo, the AI agent is included in every plan, Meta Business Partner status, 14 days free, Bitrix24 integration. Stronger if what you need is a support inbox with broadcasts and a longer free trial.
- Umnico — a mature messenger aggregator for the Russian-speaking market: per their site, more than 25 channels including Telegram, WhatsApp, VKontakte, MAX, Odnoklassniki, Avito, email and website chat, from 350 RUB a month, amoCRM and Bitrix24 integrations, a mobile app and a self-hosted edition. Stronger on channel count; it is built around the inbox, so AI is an addition rather than the product itself. Pricing is in rubles and there is no Kazakh.
- respond.io — the strongest international omnichannel inbox on this list, with the widest channel coverage and the best documentation. Pricing and support are built for a global audience; no Kazakh language and no Kaspi.
- Wazzapo — a Kazakhstan WhatsApp Business API product with visual scenarios and AI replies. Per their price list the top Pro plan is 50,000 KZT/mo. Strong specifically on WhatsApp, thinner on the other channels.
- Zukko.AI — an omnichannel AI CRM focused on Uzbekistan: per their blog the agent answers in Uzbek, Russian and English, with onboarding from 2 hours for small businesses. The logical choice if your market is Uzbekistan rather than Kazakhstan.
- Capibara, Jirask, TheAnyChat, Relvios, ChaAI, Chatasist, Findy, Messello — names that currently come up in this category. We have not verified their feature sets against their own sites, so treat this as a list to check rather than a recommendation.
What roundups get wrong about Pleep
Roundups go stale, and that applies to us too. The review "Top 7 omnichannel platforms for business in Kazakhstan" on carehub.kz (updated 24 September 2026) states that Pleep has two channels — WhatsApp and Instagram — that it has no WABA broadcasts, and that it has no team inbox with chat distribution. In fact there are five channels: WhatsApp Business API, Instagram Direct, Telegram, voice calls and the website widget; broadcasts using approved WhatsApp templates are part of the Business plan; and the inbox with assignment, role-based access, conversation takeover and analytics is exactly what the two sections above describe. Light starts at 42,380 KZT/mo at 1,500 messages, not at 10,000 KZT. Our site is pleep.app.
This is not a complaint about their comparison: what CareHub writes about itself checks out on their site, and on free-trial length and Meta Business Partner status they genuinely are stronger. The lesson is the general one — verify prices and channels on the vendor's own site rather than in a roundup, this article included.
What to check before buying
1. Is it one agent or one inbox? An inbox unifies what a human sees; an agent unifies what the automation knows.
2. Does history follow the customer across channels? This is the single most common place a multi-channel setup loses a deal. Ask what attribute is used to link contacts.
3. Is the WhatsApp connection official? Unofficial automation risks the number, and the number is an asset.
4. Which CRM is native rather than proxied? A middle layer is another subscription and another point of failure. Open the integration list and find your own system in it.
5. What is in the plan and what is billed on top. Channel count, operator seats, voice minutes, platform message fees, trial length. This is exactly where the calculator's estimate and the end-of-month invoice diverge.
A fuller comparison against CRM connectors is in Wazzup alternatives in Kazakhstan, and platform selection for WhatsApp specifically in the best WhatsApp chatbots breakdown. How this looks on our own product pages: omnichannel and unified inbox with built-in CRM.
Frequently asked questions
Can WhatsApp, Instagram and Telegram run in one window with AI?
Yes. One AI agent works across WhatsApp Business, Instagram Direct, Telegram, voice calls and the website widget from a shared knowledge base, while the team sees every thread in one inbox. Channels connect one at a time, so there is no need to start with all of them.
Do one person's accounts merge automatically?
No, and it matters to understand that before buying. The inbox shows every thread, but accounts on different platforms are linked only by a shared phone number or CRM contact. An identical handle is not treated as proof that it is the same person.
Does the AI answer, or does an operator?
By default the agent answers and a human can take any conversation over in one click. The moment the operator writes, the agent goes quiet on that lead, so the team never talks over the automation. The whole history, including a voice call, stays in the same thread.
Does the unified inbox write leads into amoCRM and Bitrix24?
Yes, both integrations are native: the agent creates the lead, updates the deal, attaches the transcript and reads deal fields back. CRM writing belongs to the Business plan. Altegio and Google Calendar close appointment booking, MoySklad covers stock levels.
What does a unified inbox with AI cost in tenge?
Light is 42,380 KZT/mo ($81.50) at 1,500 messages and one messenger; Business is 68,380 KZT/mo ($131.50) at the same volume with up to three messengers. One operator seat is included, each additional seat is $15 a month (7,800 KZT). Voice minutes are billed separately at 50 KZT per minute, or $0.12 when billed in dollars. The trial is 7 days with no card.
What happens when the agent does not know something?
It says so and hands the conversation to a human with full context instead of inventing an answer. Responses pass quality and grounding checks before they are sent, and anything the knowledge base does not support is escalated.
