How to Connect WhatsApp Business to Pipedrive: Step-by-Step Guide

The second thing that breaks budgets: on October 1, 2026, service messages become billable. Every reply your reps send inside the 24-hour window is free today. From October, Meta charges for them at the utility rate of the relevant market, with no volume discounts. Several markets also move onto standalone, higher-rate pricing on the same date.

At Brutal Marketing we connect WhatsApp to CRMs regularly, and in Pipedrive there are two forks in the road that determine both your budget and whether you can connect at all. We'll cover both: what to do when the native integration is available to you, and what to do when it isn't. Plus number migration, template moderation, and an honest calculation for 1,000 conversations a month.

The confusion starts with the names. People say "we connected WhatsApp to our CRM" while meaning three different things with three different sets of consequences.

WhatsApp Business App is the free phone app. One primary device, up to four linked ones, manual replies, a catalogue, quick replies. On its own it gives you no CRM integration.

WhatsApp Business Platform (Cloud API) is Meta's official business channel. This is what powers Pipedrive's native integration. Unlimited agents, templates, automation, delivery analytics.

Grey integrations hook up your number by emulating WhatsApp Web via a QR code. Cheap and fast, right up until the number gets blocked.

In our experience grey solutions survive a few months on average — exactly until your reps start sending outbound at volume. Then the number hits restrictions and the client asks us to rescue the database. Rescue is not always possible: conversations from an unofficial integration cannot be migrated into Cloud API.

Meta supports coexistence mode: the same number runs in the WhatsApp Business App on the phone and simultaneously in Pipedrive via Cloud API, with messages mirroring both ways. Pipedrive specifically recommends this setup for people who work from their phone.

What breaks in coexistence mode: group chats do not sync, and editing or unsending messages stops working. Walk your team through this before you connect, not after the first "why can't I delete a message anymore?"

This is the main fork, and it is exactly what most guides skip.

Road one — Pipedrive's native integration. Found under Tools and apps → WhatsApp. It talks directly to Cloud API, conversations land in the Sales Inbox and attach to deals and contacts, and templates and numbers are managed inside Pipedrive. Constraints: Growth plan or above, global admin permissions, and beta status — it is not available to every account.

Road two — a third-party provider (BSP) from the marketplace. Twilio, 360dialog, Wati, Gallabox, TimelinesAI and a dozen others. You install an app from the Pipedrive marketplace and conversations appear in a widget or as deal activities. Works on any plan, including Lite.

The rule of thumb we use: if the client is on Growth and the native integration has already rolled out to their account, we take it — fewer links in the chain and zero markup. If they are on Lite, or the integration has not arrived yet, we take a BSP but budget two line items instead of one.

You can check which road you are on in under a minute: open Tools and apps and look for a WhatsApp entry. If it is not there, only road two is available to you right now.

What follows covers road one in detail. If you are going with a provider, the sections on templates, the 24-hour window and pricing apply equally — only the connection steps will come from your BSP's interface.

Half of all failed setups are not technical problems — they are missing access. Gather everything up front.

1. Growth plan or above. Roughly $39 per user per month billed annually, $49 billed monthly. Pipedrive restructured its plans in 2025 along with the tier names, so check the current pricing page.
2. Global admin permissions in Pipedrive. Without them you cannot connect the account or manage numbers and templates.
3. A personal Facebook account with access to the business portfolio.
4. A Facebook Business Portfolio — Meta's central hub for business assets.
5. A WhatsApp Business Account (WABA) linked to that portfolio. Can be created during setup.
6. A phone number that can receive an SMS or a call. Meta rejects most virtual numbers from random services.
7. A payment method in Meta. The card must clear international payments. Without one, your first messages go out and then billing hits the payment threshold and the channel stops.

It is also worth settling your pipeline structure before you connect, because WhatsApp leads will start landing in the CRM within the first hour and they need a stage to land on.

This is a one-time setup and takes 15–30 minutes once your access is in order.

Step 1. Open the integration. In Pipedrive, go to Tools and apps → WhatsApp. If the entry is missing, the integration has not rolled out to your account yet or your plan is below Growth.

Step 2. Launch the setup assistant. "Get started" opens Pipedrive's step-by-step assistant. "Connect" takes you straight into Meta's flow. We recommend the assistant: it automates nothing and changes nothing in your account, but it checks off everything you need and stops you failing halfway through.

Step 3. Work through the assistant's three checks. It asks in sequence about your Facebook account, your Business Portfolio access, and your WhatsApp Business Account. At each step, if something is missing, it gives you instructions or a ready-made request message you can forward to a colleague or agency partner who controls the portfolio.

Step 4. Decide on the number at the WABA stage. The assistant offers to convert a personal number to a business number, or to use a new or existing one. Pipedrive recommends the native mobile app here because it supports coexistence. Important: converting an account can lose existing chats — back them up before this step.

Step 5. Close the assistant and click "Connect." Meta's connection flow opens.

Step 6. Select your Facebook Business Portfolio. If you do not have one, create it here with "Create a Business portfolio."

Step 7. In the second dropdown, select "Connect a WhatsApp Business App." This is the hardest step in the guide — detail below.

Step 8. On the next screen select "Use a new or existing WhatsApp number." Pipedrive recommends using an existing number. Enter it in the field.

Step 9. Verify the number with a code, if you are adding a new one.

Step 10. Review the data you will share with Pipedrive and click "Confirm." There will be a pause here — the connection is not instant. Wait for the final screen and click "Finish."

Step 11. Add a payment method in Meta Business Manager. Payments → Add payment method. Without it the channel runs until it hits the threshold, then stops.

Step 12. Assign numbers to your team. Tools and apps → WhatsApp → Numbers, the pencil icon next to the number, tick the users, "Save."

Step 13. Run a test. Message the work number from your personal one and check: did the conversation appear in the Sales Inbox, did it attach to the contact, was a deal created, did automation fire, did the owner get notified?

At the account selection step Meta shows three options. Only one is correct: "Connect a WhatsApp Business App." If you already use WhatsApp Business and pick either of the other two, the connection completes and then throws an error when you try to add the phone number. The error text does not explain why, so people start reconnecting everything from scratch.

The second half of the same trap: if the number previously lived on a third-party integration such as Twilio, your business portfolio already contains a WhatsApp account that integration created. Trying to reuse it with Pipedrive also produces an error. The fix is to create a new WhatsApp Business Account rather than reviving the old one.

In Pipedrive each user can be assigned to only one WhatsApp number at a time. Assign a rep to a second number and they are automatically removed from the first.

For a single-number team that is a non-issue. For a company with several business lines it is an architectural problem. If you run separate numbers for "sales" and "support" and a rep works across both, you either split people by function or consolidate onto one number with routing inside the CRM.

We usually recommend the latter: one number, clear routing internally. It is simpler for the customer when one company is talking to them, not three different numbers.

Without Meta business verification you operate under constraints: fewer numbers per portfolio and lower limits on business-initiated conversations.

New numbers start at 250 unique customers per day that you can message first. The limit then scales in tiers — 1,000, 10,000, 100,000, unlimited — based on volume and your number's quality rating. The rating is visible right in the Numbers section, next to the status.

Quality rating drops when users report or block you. Fall to "Low" and your limit freezes. Fall critically and the number gets cut off from broadcasting.

Practical takeaway: do not push the full database in the first two weeks. Start with a warm segment — everyone who messaged you in the last 90 days. They do not complain, the rating stays green, and the limit climbs on its own.

Three scenarios, three different sets of actions.

Scenario 1. The number is on a regular personal WhatsApp. The painful one. Pipedrive warns explicitly that converting an account can lose existing chats. Before converting: export a chat backup (Settings → Chats → Chat backup), record the key contacts in the CRM by import, and only then convert.

Scenario 2. The number is on the WhatsApp Business App. Good news: nothing needs deleting — the connection runs through coexistence mode. The number keeps working in the app while Pipedrive receives the same conversations.

Scenario 3. The number is with a third-party provider — Twilio, Wati, 360dialog or another CRM. Meta supports migration between providers if the number is registered, you have WABA access, and two-factor authentication is disabled for the duration. The number and approved templates carry over. Automations reset to zero and need rebuilding. And remember the old-WABA trap — create a new WhatsApp Business Account for Pipedrive.

The one rule of migration: do it in the quietest hour of the week. In the gap between disconnecting the old account and registering the number on Cloud API, inbound messages are not delivered — they simply vanish.

On disconnection specifically: if you disconnect WhatsApp from Pipedrive, new message syncing stops, but previously synced history stays in the account and becomes fully accessible again if you reconnect. That removes the biggest fear — "what if it doesn't work out and we lose everything."

Messaging a customer first — outside an open window — is only possible with an approved template. Every template goes through Meta review and gets a category, and that category drives the price directly.

Three categories:

• Utility — transactional: order confirmation, delivery status, appointment reminder, booking change. Cheap.
• Authentication — verification codes and one-time passwords. Cheap, with their own formatting rules.
• Marketing — everything else: promotions, discounts, re-engagement, announcements. The most expensive category, and it never gets volume discounts.

The line between utility and marketing is intent. "Your order #1024 has shipped" is utility. "Your order has shipped, and here's a promo code for your next one" is marketing — in the same sentence.

1. A variable at the very start or end of the text. {{1}}, welcome! gets rejected. Variables must be surrounded by text on both sides.
2. Two variables in a row. Meta reads {{1}} {{2}} as an attempt to bypass review.
3. An empty or meaningless sample value. If your example for {{1}} is "text", it will not pass. Use something real: "Elena", "#1024".
4. Category does not match content. Declared utility with a discount inside it means rejection, or automatic re-categorisation to marketing with a new price.
5. Promises and guarantees. "We guarantee 40% sales growth" is a red flag for reviewers.
6. Errors and markup. Stray characters, broken links, HTML tags, truncated text.

Example that gets rejected:
{{1}}, we have 50% off! Today only! Message {{2}}

Same meaning, this one passes:
Hello {{1}}. Until August 15 there's 50% off the "Foundations" online course. To reserve your spot, tap the button below. [Button: Reserve a spot]

The difference is not politeness, it is structure: the variable sits inside the text, the deadline is specific, the action is specific, and there is no cascade of exclamation marks.

Review usually takes anywhere from a few minutes to a day. Submit templates as a batch 2–3 days before a campaign launches, never on launch day.

Keep 5–8 base templates live for recurring scenarios: re-engagement, appointment reminder, order confirmation, review request, abandoned cart. In our projects, one well-written re-engagement template brings 8–14% of a database silent for 60+ days back into conversation.

In the native integration, templates are created and managed inside Pipedrive — but only a global admin can do it. Build that into your process: a rep cannot "just quickly add a template" themselves.

A customer messages you and a 24-hour customer service window opens. Inside it you can send anything, free-form, no templates required. Every new message from the customer resets the window.

Once the window closes, free-form messages stop being delivered. From that point it is templates only, and templates cost money.

Special case: if the customer arrived via a Click-to-WhatsApp ad or a button on your Facebook page, a free 72-hour window opens. Everything you send inside it, templates included, is not billed. For businesses driving paid traffic into WhatsApp, this is the cheapest communication channel in existence.

Today, agent replies inside the window are free. From October 1, 2026 Meta starts charging for service messages at a rate equal to the utility rate of the relevant market, with no volume discounts. Separately, dedicated pricing for the Meta Business Agent takes effect on August 1, 2026.

In practice: a conversation with 15 messages from your rep, which costs nothing today, becomes a paid line item from October. Exact figures for several markets were not published at the time of writing — Meta committed to releasing them by September 1, 2026.

In our experience, three quarters of lost WhatsApp leads are not a pricing problem — they are a response-time problem.

1. First reply within 5 minutes. In Pipedrive this is handled by automation: create an activity for the owner on a new inbound message, plus a notification.
2. A trigger at hour 20 of the window. Workflow automation assigns a task or sends a short clarifying message if the conversation is still open and the customer has gone quiet. Their reply resets the window.
3. A task for the rep at hour 23. A human touch, on deals that justify it.
4. After the window closes, one re-engagement template. Not spam. Relevant to the deal stage. Not three in a row.
5. Check where the conversation started. From an ad means 72 hours, not 24.

Note that Pipedrive's automation builder is available from the Growth plan specifically. That is another argument for the native road — the plan that unlocks the integration also unlocks the automation to run it properly.

Two facts break every older calculation.

Fact one. On July 1, 2025 Meta dropped 24-hour conversation-based billing and moved to per-delivered-template-message pricing. Every "cost per conversation" calculator is now obsolete. You pay only for delivery.

Fact two. Price depends on the recipient's country, not on where your business is registered.

In Pipedrive's native integration you pay Meta directly from a linked card on a threshold model. Going through a provider adds a third line — their subscription and, usually, a per-message markup.

A typical month for a service business: 1,000 conversations, 600 customer-initiated and 400 initiated by you. A team of 5 users.

The Meta rates above are planning estimates for a mid-cost European region; the rate card is revised quarterly, so check the current one before signing off a budget. Several markets move to standalone, higher-rate pricing on October 1, 2026 — build in headroom.

Note the proportion: in Pipedrive the subscription costs 15–20 times more than the messages themselves. Optimising the Meta invoice only makes sense once you are sending tens of thousands of templates. For everyone else the real question is not "how do we save on messages" but "how many seats do we have in the CRM and do all of them genuinely need Growth."

Scenario A. Service business (dental, auto repair, salon). 80% inbound; outbound is appointment reminders, i.e. utility. The Meta invoice is negligible. Your real cost is the CRM subscription.

Scenario B. E-commerce with broadcasts. 2,000 marketing templates a month across the database. At $0.05 that is $100 for the broadcast alone. Here every percentage point of segment relevance converts directly into money.

Scenario C. Paid-traffic business. All communication starts from Click-to-WhatsApp, so 72 hours are free. The Meta invoice is near zero and the real cost is your ad budget.

We do not sell channels or CRMs people do not need, so let us be direct.

The integration is in beta. At the time of writing Pipedrive states the feature is not available to all customers. That means two things: the WhatsApp entry may simply not be in your menu, and the feature set will keep changing. Plan on the interface looking different in a few months.

The plan threshold. Growth and above. For an eight-person team that is $312/month for the CRM alone. If WhatsApp is your only reason to move up to Growth, price out the BSP-on-Lite alternative — sometimes it works out cheaper, sometimes not, depending on seat count.

One user, one number. A constraint to design your team around, not to configure your way out of.

WhatsApp penetration varies enormously by market. In some countries it is how business is simply done; in others it sits behind Telegram, Viber or SMS for domestic audiences. Where WhatsApp delivers most: export and cross-border sales, tourism and relocation, diaspora-facing businesses, and B2B with Latin America, India, the Middle East and Southern Europe.

Payments. Meta charges a card that clears international payments — worth closing with finance before connecting, not when the channel stops at the payment threshold.

Rules change faster than guides get written. The pricing model has changed twice in the last eighteen months, and a third change is already scheduled for October. Building a process that depends on one channel is risky; building it in a CRM, where a channel is just a swappable source, is sensible.

If you are still choosing a system, we have the same walkthrough for a CRM where the native integration is available from the entry-level plan: how to connect WhatsApp Business to Kommo — the budget maths comes out very differently there.

We at Brutal Marketing will select the best CRM program for you to use in your business. We will be happy to tell you about the program's capabilities and show you which settings will exactly help you achieve the desired financial results.

We handle the whole chain: checking whether the native integration is available to you, selecting a provider if it is not, registering the WABA, running Meta verification, migrating the number without losing conversations, getting templates approved, and configuring automation around your pipeline.

Get Pipedrive implemented with WhatsApp — on a free consultation we'll review your case, price out both roads, and tell you honestly which one works better for you.