WhatsApp and amoCRM Integration: All Chats, Contacts and Deals Inside Your CRM

How do I connect WhatsApp to amoCRM?

Connect official WhatsApp (WABA) in WazzaBee, which takes 15 minutes, then in the "Connectors" section enter your amoCRM subdomain and click "Connect amoCRM". The amoCRM integration is included in the line subscription of $66 per month, no developer needed.

A manager quits and takes three hundred customer conversations with them on their phone. A request arrives in WhatsApp at nine in the evening, the manager sees it in the morning, and the customer has already bought from a competitor. Meanwhile amoCRM is in perfect order: pipelines, tasks, reports, except the actual sales are happening elsewhere, in chats the CRM cannot see. WhatsApp and amoCRM integration closes this gap: conversations land in amoCRM automatically, turn into contacts and deals, and stay with the company rather than on an employee's personal phone. Let's look at what this gives businesses in Kazakhstan and how to set it up through WazzaBee.

While WhatsApp lives separately from amoCRM, you pay for it every day

In Kazakhstan, WhatsApp is the main way customers reach a business. They won't call and won't send an email. Here is what happens when this channel is not connected to the CRM:

• Requests get lost silently. A request came in, but it is not in amoCRM, and nobody is responsible for it. No one sets a task, sends a reminder or asks "why didn't we close this sale?".

• The customer base belongs to the employee, not the company. Conversations, agreements, discounts, promises: all on someone else's phone. When the employee leaves, all of it leaves with them.

• Management can't see what customers are being promised. Response speed, tone, deal terms: all out of control. So is leaking the customer base to a competitor.

• Managers work in two windows. They copy the phone number, name and request details from the messenger into the deal card. That's minutes per customer, typos in numbers and frustration by the end of the day.

A separate problem is "grey" solutions: browser extensions, emulators, custom scripts on a personal number. They create the illusion of integration right up until the first number ban, and the entire chat history usually disappears along with the number. We covered the reasons for bans separately: why WhatsApp bans business numbers.

If a conversation with a customer is not in the CRM, for the business that conversation does not exist. Integration turns every chat into a company asset: it is linked to a deal, visible to management and stays after the manager leaves.

WazzaBee expert

What WhatsApp and amoCRM integration gives you

Once connected, WhatsApp becomes a working channel inside amoCRM. The manager doesn't open their phone or switch tabs: they work in the deal card, and the customer receives a regular WhatsApp message.

Feature	What it means in practice
Chat in the deal card	Incoming messages arrive in the native amoCRM chat, replies go out to WhatsApp. Everything in one window
Contacts are created automatically	WazzaBee looks up the number in contacts and, if not found, creates a card with the phone number and name from the messenger
Deal in the right pipeline	The inquiry lands in the right pipeline and stage. If you want to review inquiries first, choose "Incoming leads"
Files, photos and voice messages	A customer sent a photo of a breakdown or a voice message, and you can see and hear it right in amoCRM
Templates in the chat	Approved WhatsApp templates load into amoCRM: the manager picks the right one instead of copying text from notes
Salesbot step	The amoCRM bot sends a template at the right pipeline stage on its own and fills in data from the deal fields
WazzaBee section in the left menu	All lines and channels in one list, for those who prefer working with a list of conversations rather than cards
A team on one number	Several managers reply from one business number without passing a phone around
History stays with the company	Conversations are stored in amoCRM and in WazzaBee. An employee leaves, the chats stay

Which WhatsApp to connect to amoCRM

This decision matters more than the integration itself, because it determines whether your number survives to the end of the quarter.

Official WhatsApp Business API (WABA): the number is verified, linked to a business account and operates under Meta's rules. It is not banned simply for being automated, it handles high message volumes and lets you message customers first, using a template. It is the only option you can seriously build business processes on: we explained what WABA is and how to get it in our article on official WhatsApp for business in Kazakhstan.

Unofficial connection methods (the regular WhatsApp app linked to a service in violation of the rules) look cheaper. The price of that simplicity is risk: Meta bans such numbers, and a number can be banned at any moment, usually at the worst possible time. The customer base goes with it. For a company number we recommend official WABA only.

A special case: when WhatsApp Business is already running on the number and you don't want to give up the app. There is a shared mode for this: WhatsApp Coexistence lets you connect a number to a CRM without deleting the app: the phone keeps working, and conversations still land in amoCRM.

What it looks like in practice: three scenarios

1. Request at night, deal in the morning

A customer writes in WhatsApp at 23:40. WazzaBee passes the message to amoCRM: if the phone number is not in the database, it creates a contact and links a deal to it in the "Initial inquiries" pipeline at the first stage. In the morning the manager sees not a missed message on someone else's phone, but a card in their own pipeline, with the inquiry text and number.

2. The customer went quiet and the 24-hour window closed

WhatsApp allows free messaging for 24 hours after the customer's message. After that you can only write using an approved template. In amoCRM this doesn't turn into a quest: templates are visible right in the card chat, the manager picks the right one and sends it. How templates work and which scenarios are built on them is covered in our article on WhatsApp HSM templates. Also keep in mind the changes in service message pricing: templates are now billed under different rules.

3. The pipeline messages the customer on its own

The deal moved to the "Invoice sent" stage: amoCRM Salesbot runs the WazzaBee step and sends the customer a template with the amount and payment due date, filled in from the deal fields. If it isn't delivered, the bot follows the "failure" branch and sets a task for the manager to call. Zero manual work, and the customer gets the message in the channel they open every day.

How to connect WhatsApp to amoCRM: step by step

The steps and button names below match the amoCRM connection guide in our documentation. The integration must be connected by an amoCRM account administrator: a regular employee will not be able to do it.

1. Sign up for WazzaBee. An account takes a minute to create, and a line comes with a 7-day trial: you can test the integration on your real requests.

2. Connect official WhatsApp. In the "Communication lines" section, click "Add line", choose WhatsApp and the WABA (Official API) type, then "Log in with Facebook" and complete registration in the Meta window. It takes 15 minutes. The number must not be in use by the regular WhatsApp app, or connect it via Coexistence. Details in the WABA guide.

3. Link with amoCRM. Open "Connectors", click the amoCRM card and in the "amoCRM subdomain" field enter your account name: for the address mycompany.amocrm.ru it is mycompany. Click "Connect amoCRM" and grant access to the WazzaBee app. You will be returned to the dashboard with the message "amoCRM connected!". No tokens, no code, no manual webhooks.

4. Set up the rules. For the line, turn on "Enable for amoCRM". In the "When a new customer contacts you" block, choose "Deal" or "Incoming leads", the pipeline and, for a deal, the initial stage. Then choose who is responsible: "First to reply becomes responsible" or "Round-robin distribution". Click "Save": the message "Chat channel connected" will appear.

5. Test it. Write to your business number from your personal phone and watch the contact, the "Request from messenger" deal and the chat appear in amoCRM. Reply from the card, and the message arrives in WhatsApp. If the contact already has an open deal, the conversation will continue in it.

6. Widget and templates. In amoCRM open Settings → Integrations, install the WazzaBee app and in the "Your amoCRM domain" field enter mycompany.amocrm.ru without https://. "WazzaBee Chats" will appear in the left menu. To make WhatsApp templates appear in the card chat, click "Sync templates" in the dashboard and refresh the amoCRM page with F5.

From there you can keep building: create Salesbot scenarios with the "WazzaBee: send WABA template" step and add other channels.

How do I send a WhatsApp broadcast through amoCRM?

A mass broadcast to your base is launched in the WazzaBee dashboard, in the "Broadcasts" section, while from amoCRM the template is sent by Salesbot: the "WazzaBee: send WABA template" step fires at the right pipeline stage and fills in data from the deal fields. Each broadcast message costs $0.086 and is deducted from the line balance.

How to launch a broadcast to your base in the dashboard:

1. On the broadcasts page, click "New".

2. Choose a WhatsApp line and click "Next".

3. Choose an approved template and an audience.

4. Specify what to insert into the template: name, phone number or a column from the file.

5. Click "Create campaign", then "Launch". The line balance must be at least $0.22.

All steps with screenshots are in the broadcast guide, and how to build a base without losing your number is explained in the article "WhatsApp broadcasts to your own base".

How much does WhatsApp and amoCRM integration cost?

The amoCRM integration is included in the official WhatsApp line subscription: $68 per month, line connection $0. Messages are paid separately: Meta charges for them under its own rules, and the money is deducted from the line balance in tenge.

Item	Cost
WABA line connection	$0
Line subscription	$68 per month
amoCRM integration	Included in the subscription
Broadcast (marketing template)	$0.086 per message
Order or booking notification	$0.0286 per message
Reply within the 24-hour window	First 1000 per month per number at the minimum price, then $0.0286
Incoming message	$0.0021

The subscription also includes a dashboard with chats, a team chat, the owner and 3 employees (then $6.64 per seat), broadcasts to your base (messages themselves are paid), Bitrix24 integration, a public API and webhooks. We covered how WhatsApp Business API pricing works in a separate article.

Not just WhatsApp

Customers don't come from just one messenger, and there is no point keeping half the conversations in the CRM and half on a manager's personal phone. Through WazzaBee you can connect to amoCRM:

• Telegram: a bot or a personal account.

• Instagram Direct and Facebook Messenger: messages land in the same pipelines.

• OLX.kz: listing conversations come into the CRM instead of staying in the personal account. More in our article on OLX and CRM integration.

Part of your team works in Bitrix24 rather than amoCRM? It connects the same way: WhatsApp and Bitrix24 integration. A general overview of channels and CRMs is in our article on CRM and messenger integration.

Where to start

WhatsApp and amoCRM integration is needed for one thing: to stop losing money at the junction between the messenger and the CRM. Every request becomes a card, every conversation part of the customer's history, every agreement the property of the company.

Try it on your own requests during the 7-day trial: create a WazzaBee account, connect your number and link it to amoCRM. If something doesn't work, contact support: we'll help with the setup and make sure requests reach your pipeline.