How do you connect WhatsApp to Facebook for a business?

The phrase covers three distinct jobs and the setups have almost nothing in common, so the first useful step is deciding which one is actually wanted. The first is putting a WhatsApp contact option on a Facebook Page so visitors can start a chat. The second is running ads that open a WhatsApp conversation when tapped. The third is handling WhatsApp messages and Facebook messages in one place so nothing is missed. Businesses frequently ask for the first, need the third, and are sold the second.

What all three share is the account structure underneath. A business asset — a Page, an ad account, a WhatsApp account — has to be owned by a business account in Meta's system rather than by a personal profile, and the assets have to sit under the same one. Most of the difficulty people hit is here rather than in any particular feature: the Page is owned personally, or by an agency's business account nobody can now contact, or two business accounts exist because someone created a second one while troubleshooting. Sorting ownership out first turns the rest into configuration.

The second recurring obstacle is the phone number. A number can be attached to a personal WhatsApp account, a WhatsApp Business app account on a phone, or the business platform used by software integrations, and it cannot be in more than one of these at once. Moving a number between them is possible and it is a migration, not a toggle — with consequences for message history and for which device can use it. The practical implication is that the number the business advertises is usually already in the wrong place, and deciding which model you want before migrating avoids doing it twice.

That choice comes down to how many people need to answer. The app on a phone suits a business where one or two people handle messages and nothing needs to connect to other software. The platform used by integrations suits a business that needs several people answering, messages appearing alongside other channels, or automation attached — and it introduces message-based charges and an approval process for message templates used to start conversations outside an open window. That template and window mechanic is the part most businesses discover late: outbound messages beyond an active conversation are constrained, deliberately, and a plan that assumed free outbound messaging has to be redesigned.

Click-to-chat advertising is the piece that most often justifies the whole exercise, because it converts an ad click directly into a conversation rather than into a form. It also changes what arrives: conversations start with no context and often outside working hours, so the value depends entirely on something answering promptly. Businesses that turn these ads on without a monitored inbox and an immediate acknowledgement generate conversations that go cold, and conclude the channel does not work when what failed was the coverage.

One caution about instructions generally, including recent ones: the menu paths in these products change often, and step lists go out of date faster than the concepts do. What stays stable is the structure — one business account owning both assets, one number in one account model, templates and windows constraining outbound messages, and an inbox somebody watches. If a step list does not match what you see, the current documentation from Meta is the authority, and the structural checks above are what tell you whether the problem is a moved menu or a genuine ownership issue.