Experience Lion CRM — The King of WhatsApp CRM 7 Days Free Limited Access
→ Request Access

Pipedrive WhatsApp Integration: The Complete 2026 Guide

Pipedrive shipped native WhatsApp in June 2026 on Growth and above, still in beta. What it does, what it cannot do yet, and the real per-seat cost.

Almost everything currently ranking for this topic is out of date, and not by a little.

Search for a Pipedrive WhatsApp integration today and the top results will tell you, confidently and in plain words, that Pipedrive has no native WhatsApp integration and that you must buy a marketplace app. One of the guides sitting high on that results page was last updated in December 2023. It says there is no native integration, though there used to be one.

That was true when it was written. It is not true now. Pipedrive’s own support documentation, updated on 26 June 2026, describes a built-in WhatsApp integration that is live on the Growth plan and above. It also says something the marketing pages do not: the feature is still in beta, and it is not available to every customer yet.

So the honest answer to “does Pipedrive have WhatsApp” in 2026 is neither the yes on the feature page nor the no in the blog posts. It is: yes, on some accounts, on some plans, doing some of what you probably want.

This guide covers the part that decides whether the project works for you. Not the click path — Pipedrive documents that well enough. What matters is which of the three routes fits your team, the one capability the native beta does not have yet, and the pricing structure that turns a three-person WhatsApp requirement into a bill for every seat you own.

In this guide

What changed in June 2026

Pipedrive has been round this loop before, which is exactly why the web is so contradictory about it.

In May 2022 Pipedrive launched a Messaging Inbox with WhatsApp and Facebook Messenger among the channels. It did not last in the form people remember, which is why a guide written in late 2023 could accurately say there was no native integration but that one had existed. Anyone who tried it back then and gave up has a memory that is now three product generations stale.

The current integration is the second attempt and it is a different thing. It is built on the WhatsApp Business Platform rather than a light channel bridge, which means it needs a Meta Business Portfolio and a WhatsApp Business Account behind it. It gives you a shared inbox inside Pipedrive, lets an admin assign numbers to specific team members, and lets you build and store message templates in one place instead of in a separate vendor tool.

Two details from the support documentation matter more than any feature list. The integration requires the Growth plan or above. And it is described as a beta feature that is not available to all customers yet.

That second one has a practical consequence people keep tripping over. You can be on a qualifying plan, follow the instructions exactly, and simply not see the option, because your account has not been included in the rollout. That is not a misconfiguration and no amount of reconnecting Meta will fix it. Before you plan anything around this feature, open Pipedrive, go to your tools and apps settings, and confirm with your own eyes that the WhatsApp option is present on your account. Do that first. It takes a minute and it changes which of the three routes below you are actually choosing between.

It is also worth knowing that Pipedrive’s own two pages on this disagree. The support article names the Growth requirement and the beta status. The public feature page names neither, and says the integration is free if it is included with your plan. Neither page is lying, but the marketing page is the one that will make you think this is settled and universally available. It is not yet.

The three ways to put WhatsApp into Pipedrive

Every route you will be sold falls into one of three shapes, and they differ in who bills you, who owns the WhatsApp number, and what can be automated.

Route one: the native integration. WhatsApp conversations land in Pipedrive, tied to people and deals, handled by your reps in the tool they already have open. You connect your own WhatsApp Business Account, so Meta bills you directly for messages and Pipedrive does not sit in the middle of your message economics. Requires Growth or above and requires your account to be in the beta.

Route two: a marketplace app. Pipedrive’s marketplace has a shelf of WhatsApp apps, and several of them rank higher for this keyword than Pipedrive’s own documentation does. They vary enormously. Some sync a personal WhatsApp session into Pipedrive without the Business Platform at all. Others are full messaging platforms that treat Pipedrive as one of several CRMs they connect to. They charge their own subscription on top of Pipedrive, and some of them add a margin on every message.

Route three: a dedicated WhatsApp platform, with Pipedrive alongside or replaced. Here the conversation lives in a system built for WhatsApp — inbox, chatbot, broadcast, template management, a pipeline board driven by chat rather than by deals — and Pipedrive either receives the outcomes or stops being needed. This sounds like the vendor-serving answer and sometimes it is, but for a team whose sales conversations are ninety percent WhatsApp, running a deal-centric CRM as the primary system is genuinely the wrong shape. The section on whether you need Pipedrive at all works through when that is true.

The choice between these is usually presented as a feature comparison. It is not. It is decided almost entirely by one question, which is the next section.

What the native integration actually does

Stripped of marketing language, here is the working set.

You get a WhatsApp conversation view inside Pipedrive, with messages attached to the person record and visible in the deal context. A rep answering a customer does not switch tools and does not lose the history when a deal is handed over. That is the single biggest practical win, and for a lot of teams it is enough on its own.

You get team assignment. An admin connects a WhatsApp Business Account and assigns the numbers under it to users. This is how you avoid the situation where all customer chat lives on one salesperson’s personal handset and walks out of the door when they resign.

You get template management in the same place. Because Meta requires a pre-approved template to open a conversation with anyone who has not messaged you in the last twenty-four hours, template management is not an optional nicety — it is most of the operational work of running WhatsApp at scale. Having it inside the CRM rather than a separate vendor console is a real reduction in tool sprawl.

There is one structural limit worth planning around: a user connects one WhatsApp Business Account, and the numbers under that account are what an admin can then assign. Your WABA connection is bound to a person’s authorisation, not to the company in the abstract. Think about who that person is before you connect. Connecting it under the account of the founder who signs in twice a month, or under a rep who might leave, creates a small future problem that is annoying to unpick. Use an admin identity you will still control in two years.

And there is one thing not in the list above, which matters more than everything in it.

The automation gap, and why it decides your route

Pipedrive’s own WhatsApp feature page carries a short line that most readers skim past: automation features will be available soon.

Read that against what teams actually want from this project. When you ask a sales manager why they want WhatsApp in the CRM, the answer is almost never “so my reps can see chats in a nicer window”. It is: send the quote follow-up automatically three days after the deal moves to proposal. Message the customer when the deal is won. Fire a reminder sequence at the deals that have gone quiet. Those are automations triggered by CRM state, and they are precisely what the native beta does not do yet.

So the native integration, today, is an inbox. A good one, in the right place, solving a real problem. But it is a conversation-capture tool, not a sales-automation tool.

That single fact resolves the route decision more cleanly than any feature table:

  • If what you need is conversations captured against records, so history survives handover and nothing lives on a personal phone, the native integration is the right answer and you should not pay a third party for it.
  • If what you need is messages that fire off CRM events — stage changes, deal creation, win, dormancy — the native beta will not do it, and you need either a marketplace app that specialises in exactly that, or a platform built for WhatsApp automation.
  • If you need both, at volume, with chatbots and broadcast, you are looking at route three, and the honest comparison is against the platform cost rather than against the marketplace app.

This is also the answer to the question people keep asking on forums: if Pipedrive shipped native WhatsApp, why do all the marketplace apps still exist? Because the native integration has not shipped the part those apps sell. That will change, and when it does the marketplace economics change with it. Right now it has not.

If you are still working out what the underlying channel can and cannot do before you compare tools, WhatsApp CRM vs WhatsApp Business API separates the raw channel from the software people build on top of it, and it is the cheapest hour you can spend before signing anything.

The plan trap: WhatsApp needs Growth, and Pipedrive bills per seat

This is the part no comparison page will do for you, and on Pipedrive it is sharper than on most platforms.

WhatsApp requires the Growth plan or above. Pipedrive is priced per seat per month. Those two facts combine badly, because the plan is a property of the account, not of the individual user who needs the feature.

Work it through. Say you run a twelve-person sales team on Lite, which is fourteen dollars per seat per month on annual billing — about a hundred and sixty-eight dollars a month for the account. Three of your reps handle inbound WhatsApp and you want those conversations in the CRM.

You cannot buy WhatsApp for three people. You move the account to Growth at thirty-nine dollars per seat, and you pay it on all twelve seats. Your bill goes from a hundred and sixty-eight to four hundred and sixty-eight dollars a month. That is an extra three thousand six hundred dollars a year, and roughly three quarters of the increase is being paid on behalf of people who will never send a WhatsApp message.

The message costs, which is what everyone budgets for, are not the expensive part of this project. The tier upgrade is.

This is the same trap the whole category runs, in different clothing each time. On Odoo it is an edition wall — WhatsApp is Enterprise-only and Enterprise is priced across the entire database. On Salesforce it arrives as an add-on layered onto an already substantial per-user cost. On HubSpot it sits behind a marketing tier with its own contact-based pricing. On the ecommerce side it wears different clothes again — an app subscription plus a per-message markup on Shopify, and your own hosting and scheduler bill on WooCommerce. Pipedrive’s version is the cleanest to calculate and the easiest to underestimate, because thirty-nine dollars sounds small until you multiply it by every seat you own.

Three things make the sum come out better:

Check what else the tier buys you. If Growth includes reporting, automations or product features you were about to buy elsewhere, the upgrade may be justified on its own merits and WhatsApp is a bonus. Do that comparison honestly rather than attributing the whole increase to WhatsApp — and equally, do not let a sales conversation attribute none of it.

Count seats before you commit. Many teams carry seats for people who log in monthly. Auditing and removing four dormant seats before a tier upgrade saves more than any WhatsApp app you could buy.

Price the alternative properly. If only three people need WhatsApp, a dedicated WhatsApp tool priced per user for those three, with your team staying on Lite, is frequently the cheaper structure — and it usually brings the automation the native beta lacks. That is not an argument against Pipedrive. It is an argument against paying a company-wide tier premium to solve a three-person problem.

Pipedrive renamed its plans, and the web has not caught up

A short section, because it will save you an hour of confusion.

Pipedrive retired its old five-tier naming — Essential, Advanced, Professional, Power, Enterprise — and now sells four tiers: Lite, Growth, Premium and Ultimate. On annual billing they run fourteen, thirty-nine, fifty-nine and seventy-nine dollars per seat per month. On monthly billing the same four are twenty-four, forty-nine, seventy-nine and ninety-nine.

Most pricing guides indexed today still use the old names and the old numbers. So does a good deal of Pipedrive’s own long-tail content and a lot of the comparison content written about it. If you are reading that WhatsApp needs a particular plan and the plan named is not one of the four above, you are reading something written before the rename and you should not trust its numbers either.

Two practical points. First, Growth is the second tier, one step above entry — not the mid-high tier the name suggests to anyone who remembers the old ladder. Second, the gap between annual and monthly billing is ten dollars per seat per month on the lower tiers and twenty on the upper ones, which on a twelve-seat account is well over a thousand dollars a year for the flexibility of monthly billing. Decide that deliberately rather than by default.

Before you start: what you need ready

Gather these before you touch the integration. Every one of them is a place where a setup stalls for a day because the right person was not in the room.

A Facebook account and a Meta Business Portfolio. Not a personal profile used as a business page. A real Business Portfolio, with a person who has admin rights on it and who will still be reachable next week.

A WhatsApp Business Account. This is a Meta object, distinct from the WhatsApp Business app on someone’s phone. Confusing these two is the most common false start in this entire project.

Global admin permissions in Pipedrive. The setup cannot be completed by a regular user. If your Pipedrive admin is a founder who is travelling, book the twenty minutes now.

A phone number you have decided about. New or existing, but decided. See the number section — this is the one choice that is genuinely hard to reverse.

Your business verification status. Meta’s business verification is a separate process with its own document requirements and its own queue. It is not always required to start testing, but it gates messaging limits and the green tick later. If you know you will want the verified badge, read the green tick guide before you start rather than after you are rejected. For the full approval path, the Meta WABA approval playbook covers the sequence and the usual rejection reasons.

A written answer to “what are we sending”. Templates need categorising as marketing, utility or authentication, and that categorisation determines what each message costs. Guessing here is the single most expensive small mistake in WhatsApp projects.

Setting up the native integration

The click path is short and Pipedrive documents it. What follows is the order that avoids rework, with the failure points called out.

One: confirm the feature exists on your account. Settings, then tools and apps. If WhatsApp is not offered and you are on Growth or above, you are not in the beta yet. Stop here and pick route two or three rather than waiting — there is no published date.

Two: connect from Pipedrive, signed in as a global admin. The flow hands you to Meta to authorise the Business Portfolio and WhatsApp Business Account. Do this signed into the Meta account that actually owns the Business Portfolio. Half of all failed connections are somebody authorising with the wrong Facebook login.

Three: attach the phone number. New numbers are provisioned in the flow. An existing number has to be released from wherever it currently lives first — including from the WhatsApp Business app on a phone, if that is where it is.

Four: assign numbers to users. As admin, decide who is answering. Do this before you tell anyone the integration is live, otherwise the first inbound message arrives in a shared void and someone answers it from their own phone out of habit.

Five: build templates and get them approved. Approval is usually quick but not instant, and rejections are common on first attempt for vague, promotional-sounding utility templates. Submit them a few days before you need them. Categorise honestly — miscategorising marketing as utility to save money gets templates rejected or recategorised by Meta and costs you more time than the saving is worth.

Six: send a real test to a real handset. Not to a colleague sitting next to you who already messaged you today, because that conversation is inside the twenty-four hour window and will send freely, proving nothing. Test the case that matters: a template message to somebody who has never contacted you. That is the path that exercises approval, categorisation and billing at once.

Seven: write down what happens when a rep leaves. Which numbers are assigned to them, who reassigns, who holds the Meta admin. Ten minutes now, and it is the difference between a smooth handover and a locked account later.

Choosing a marketplace app instead

If you are not in the beta, or you need the automation, the marketplace is where you will end up. The apps there are not comparable to each other and the listings do not make the differences obvious. Four questions separate them.

Does it use the WhatsApp Business Platform, or a personal WhatsApp session? Several popular tools work by syncing a logged-in WhatsApp session rather than by connecting an official Business Account. They are genuinely easier to set up, need no Meta approval, and work with the number already on your phone. They also operate outside the official platform, which means no green tick, no template system, and exposure to account restrictions if your sending pattern looks automated. That is a legitimate trade for a small team doing conversational selling. It is a bad trade for anyone sending volume — bulk WhatsApp messages without getting banned covers what actually triggers restrictions.

Who is billed for messages? Ask directly: do I connect my own WhatsApp Business Account and get billed by Meta, or do messages route through the vendor’s account? Your own account is the answer you want. Where the vendor sits in the middle, there is usually a per-message margin, and it scales with your volume in a way a subscription does not.

What triggers a message? This is the whole reason you are looking at an app rather than the native integration, so get specific. Can it fire on a deal moving to a named stage? On a deal being created, won, lost, or untouched for N days? Can a sequence stop automatically when the customer replies? A tool that can only send on manual click has not solved your problem.

What happens to conversation history when you leave? Some apps hold the conversation and write a summary to Pipedrive. Others write full history to the record. The second survives you cancelling the app. The first does not, and you find out at the worst moment.

If you are comparing named tools rather than categories, the whitelabel WhatsApp CRM comparison for India lays out the market, and there are direct breakdowns of the ones you are most likely to be quoted: Wati, Interakt, Gallabox, Rasayel, Callbell and Kommo. Several of those appear on the first page for this exact keyword, which is worth knowing when you are reading their comparison pages.

What this actually costs in 2026

Four bills, and they are not the same size as people expect.

Bill one: Pipedrive seats. Growth at thirty-nine dollars per seat per month annually, or forty-nine monthly, across every seat on the account. On a twelve-seat team that is four hundred and sixty-eight dollars a month annually billed. If you are upgrading from Lite purely for WhatsApp, the marginal cost is three hundred a month — three thousand six hundred a year. This is almost always the largest line and it is the one nobody puts in the business case.

Bill two: the app, if you need one. Zero on the native route. On the marketplace route, typically a per-user or per-inbox monthly subscription, and it stacks on top of Pipedrive rather than replacing any of it. A dedicated platform is also a subscription, but it may replace enough of Pipedrive’s role for the comparison to be fairer than it looks.

Bill three: Meta’s message charges. Unavoidable on any official route because Meta charges it, not the software. Pipedrive’s own documentation puts template messages at roughly one to ten US cents each, varying by category and by the recipient’s country. In India specifically the rates are approximately eighty-six paise per marketing message and around eleven and a half paise for utility and authentication, before eighteen percent GST. Service messages inside the twenty-four hour window after a customer writes to you are free.

The ratio there is the number to internalise: marketing costs roughly seven and a half times utility. Getting template categories right on day one is worth more than any negotiation you will have with a software vendor. And any cost estimate you read on a US or European blog can be several times wrong for your market in either direction, so do not budget from someone else’s currency.

Bill four: markup, if you allowed one. On the native route Meta bills you directly and there is no margin. On the marketplace route it depends entirely on the answer to the billing question above. This line is invisible at low volume and becomes the largest software cost at high volume, which is exactly why it is worth asking about before you sign rather than after.

Put it together for a twelve-seat Indian team on the native route, upgrading from Lite, sending eight thousand utility and two thousand marketing messages a month. The Pipedrive increase is about twenty-six thousand rupees a month. The Meta bill is roughly nine hundred rupees for utility and seventeen hundred for marketing, call it three thousand including tax. The software costs nearly nine times the messaging.

That ratio is the finding. Every guide on this topic optimises the message bill. The decision that moves your total by an order of magnitude is which seats sit on which tier. If that lands badly for you, the Lion CRM pricing page shows what the per-user cost looks like when WhatsApp is the product rather than a tier feature, which is the comparison worth doing before you upgrade twelve seats.

The phone number decision you cannot undo

Short section, disproportionate consequences.

A number registered to a WhatsApp Business Account cannot simultaneously be used in the consumer WhatsApp app or the WhatsApp Business app. Moving your existing business number onto the platform means it leaves the phone it currently lives on, and whoever has been answering it there stops being able to.

That is fine if it is a genuine company line. It is a problem if the number your customers know is a salesperson’s handset that also carries their personal chats, which in Indian SMBs it very often is.

Three options, in the order most teams should consider them:

Use the existing business number. Best for recognition and continuity, provided it is genuinely a company asset and you can take it off the handset it is on. Do this on a quiet day, not mid-campaign.

Provision a new number. Cleanest technically, and the right answer if the current number is personal or shared. The cost is that customers have to learn it, so plan a few weeks of forwarding and signature changes. Nobody regrets this as much as they expect to.

Keep both. The existing handset number for the conversations that already live there, a new platform number for automation and inbound. More moving parts, but it is the pragmatic answer when one salesperson’s relationships are the business.

Whichever you choose, decide before you start the connection flow. Reversing it is not impossible but it involves releasing a number from a WABA and waiting, and it always happens at the worst time.

What none of these routes will do for you

Worth saying plainly, because these come up as surprises about three weeks in.

None of them let you message whoever you like. Meta’s twenty-four hour window is a platform rule, not a software limitation. Outside it you need an approved template, and marketing templates need opt-in. No integration removes this and any vendor implying otherwise is describing something that will get your number restricted.

None of them fix bad list hygiene. Sending approved templates to people who did not opt in produces blocks, and blocks lower your quality rating, which lowers your messaging limits. The platform does the punishing, so switching software does not undo it.

The native route does not do automation yet. Covered above, but it belongs on this list because it is the most common misread of the June announcement.

None of them make WhatsApp a broadcast channel. It is a permission channel that happens to have very high open rates. Teams that treat it as cheap SMS get a short spike and then a restricted number.

None of them replace someone answering. WhatsApp’s advantage is that people reply, which means somebody has to be there. A team that could not keep up with email will not keep up with a channel where the expectation is minutes. If that is the real constraint, WhatsApp auto reply and a WhatsApp AI chatbot are the honest answers, not a CRM integration.

Do you actually need Pipedrive for this?

An uncomfortable question that is worth ten minutes, especially given the per-seat maths above.

Pipedrive is a deal-centric CRM. Its model is that a deal moves along a pipeline, and everything else is context attached to that deal. It is very good at that, which is why teams with a considered sales cycle, multiple stakeholders and a forecast to produce, like it.

Now describe a different business. Inbound enquiries arrive on WhatsApp. Someone answers within minutes. A quote is sent as an image. The customer says yes or goes quiet. There is no proposal stage, no forecast meeting, nothing to nurture over a quarter. That is most of Indian SMB retail, services, coaching, clinics and real-estate brokerage.

For that shape, the deal record is administrative overhead. The pipeline that matters is the conversation list — who has replied, who has gone quiet, who needs chasing today. That is a WhatsApp kanban board, and it is a fundamentally different object from a deal pipeline even though both are columns on a screen. Teams in this shape end up doing double entry: real work in WhatsApp, then a second pass creating deals so the CRM is not empty. The CRM becomes a reporting obligation instead of a tool.

If that description fits, the right move is not to integrate WhatsApp into Pipedrive. It is to run the sales process where the sales process already happens, with a WhatsApp CRM Chrome extension that puts pipeline, tags, notes and follow-up sequences directly into the interface your team already has open all day. No tier upgrade across twelve seats, no double entry, and scheduled messages that fire without waiting for a beta to ship automation.

The test is simple. Count the deals in your pipeline this month that had a stage other than “new” and “won”. If that number is small, you do not have a pipeline problem that a CRM tier upgrade solves. You have a conversation-volume problem, and it wants a different tool.

If you do have a real multi-stage pipeline — genuine qualification, several stakeholders, a forecast someone reads — keep Pipedrive and put WhatsApp into it. That is what the native integration is for, and it is a good fit for exactly that team.

The whitelabel route: selling this to clients

If you are an agency or consultant reading this because a client asked, there is a different opportunity in it.

The work you are being asked to do — Meta Business Portfolio, WABA, number decision, template approval, categorisation, connecting it to a CRM — is the same work every time. You will do it once for this client and be paid once. Meanwhile the client pays a platform subscription every month forever, and none of that recurring revenue is yours.

The alternative is to sell the platform under your own brand. You take the recurring revenue, the client gets a tool with your name on it, and the setup expertise you were going to give away once becomes the reason they stay. What a whitelabel WhatsApp CRM is explains the model, and how to start a whitelabel WhatsApp CRM business covers the practical first steps.

The economics decide whether it is worth it, so look at them before the branding: pricing models for whitelabel clients, reseller margins, and the build versus buy question if you are tempted to construct this yourself on the Cloud API. If you are already advising clients on CRM choices, the agency playbook covers positioning it inside an existing service line, and finding whitelabel clients covers the demand side. For retention, which is where the model lives or dies, reducing client churn is the one to read.

Common problems and how to fix them

The WhatsApp option does not appear in Pipedrive. Check your plan is Growth or above, and check you are a global admin. If both are true, you are not in the beta rollout. There is no setting that fixes this and no published date — choose another route rather than wait.

The Meta connection fails or connects the wrong business. You are almost certainly authorising with a Facebook login that is not an admin of the Business Portfolio. Sign out fully, sign in as the correct admin, retry.

The number will not attach. It is still registered somewhere — most often the WhatsApp Business app on somebody’s phone. It has to be released there first, and the release is not instant.

Templates keep getting rejected. Usually category, not content. A message that promotes, offers, or invites the customer to buy is marketing, even if it reads like an update. Submitting it as utility gets it rejected or silently recategorised. Write it as what it is.

Messages send but nothing appears against the deal. On the native route, check the person record has the number in the format Meta returns, country code included. Records where the number lives in a custom field rather than the phone field are the usual cause.

Delivery rates fall over a few weeks. That is a quality-rating decline, and it comes from blocks and reports rather than from anything in the software. Cut marketing volume, tighten who you are sending to, and let it recover before pushing again.

Everything works but nobody uses it. The most common outcome, and the least technical. Reps keep answering on their own handsets because it is faster and nobody told them the number moved. Assign numbers, turn off the old route, and say so out loud. This is a rollout problem, not a product problem.

A 14-day rollout plan

Days one and two. Check whether the feature is on your account at all. Decide the route. Count your seats and calculate the real tier cost before anything else, because that number may change the decision.

Days three and four. Meta Business Portfolio and WhatsApp Business Account sorted, with the right admin identity. Number decision made and, if you are moving an existing one, scheduled.

Days five and six. Connect. Assign numbers to the two or three people who will handle the first wave. Do not roll it out to everyone yet.

Days seven and eight. Write six templates, not twenty. Categorise honestly. Submit and expect at least one rejection.

Days nine and ten. Test with real recipients outside the twenty-four hour window. Confirm messages land against the right person and deal.

Days eleven and twelve. Run it live with the small group. Watch for the double-entry behaviour — if reps are still answering on personal phones, find out why now rather than in month three.

Days thirteen and fourteen. Review. Volume, response times, template rejections, and whether the deals actually reflect the conversations. Then decide whether to widen access or whether the conversation-first route fits your team better than you thought on day one.

Frequently asked questions

Does Pipedrive have a native WhatsApp integration in 2026?
Yes. Pipedrive’s support documentation, updated 26 June 2026, describes a built-in WhatsApp integration available on the Growth plan and above. It is still described as a beta feature and is not available to all customers yet, so check your own account before planning around it. Most guides currently ranking for this topic were written before this shipped and still say no native integration exists.

Which Pipedrive plan do I need for WhatsApp?
Growth or above. Growth is the second of Pipedrive’s four current tiers — Lite, Growth, Premium, Ultimate — at thirty-nine dollars per seat per month on annual billing, or forty-nine billed monthly. Because Pipedrive charges per seat and the plan applies to the whole account, upgrading for WhatsApp means paying the higher rate on every seat, not only the people who use it.

Can I use WhatsApp with Pipedrive on the Lite plan?
Not natively. Your options are a marketplace app that works on any plan, or a dedicated WhatsApp tool used alongside Pipedrive. For a small number of WhatsApp users, either is usually cheaper than upgrading every seat on the account to Growth.

Does the Pipedrive WhatsApp integration do automation?
Not yet. Pipedrive’s own feature page says automation features are coming soon. Today the native integration gives you a shared inbox, number assignment and template management. If you need messages to fire on a deal moving stage, being won, or going quiet, you need a marketplace app or a dedicated WhatsApp platform.

What does it cost to send WhatsApp messages from Pipedrive?
Meta bills you, not Pipedrive. Pipedrive’s documentation puts template messages at roughly one to ten US cents, varying by category and recipient country. In India that is approximately eighty-six paise per marketing message and about eleven and a half paise for utility and authentication, before eighteen percent GST. Replies within twenty-four hours of a customer messaging you are free. On most accounts the Pipedrive tier increase costs several times more than the messages.

Can I use my existing WhatsApp Business number?
Yes, but it has to be released from wherever it currently is, including the WhatsApp Business app on a phone, and it cannot be used there afterwards. If the number is a salesperson’s handset carrying personal chats, provisioning a new number is usually the better call.

Do I need a marketplace app if Pipedrive has native WhatsApp now?
Only if you need something the native integration does not do — automation being the main one — or if your account is not in the beta. If you want conversations captured against people and deals and nothing more, the native route does that without a second subscription.

Become a Reseller