WhatsApp Outreach in B2B: What Section 7 UWG Allows

The channel everyone wants and almost no one is allowed to use

WhatsApp has the best delivery rates in German business communication. Messages get read, usually within minutes. That’s exactly why it comes up in every other multi-channel discussion — and exactly why it’s the most heavily regulated of the three common outbound channels.

The short answer up front: WhatsApp is not a first-contact channel in B2B. Not because it’s technically impossible, but because Section 7 UWG requires prior consent for electronic mail — which, by definition, isn’t present for a cold contact.

This article frames the legal situation and describes what practically remains. How the channel is used within a sequence once the legal requirements are met is covered in the overview article on WhatsApp B2B Outreach.

Two legal levels that get regularly confused

The most common mistake in practice: if you have the data lawfully, you may also write to them. That’s not correct. There are two separate checks.

Level 1 — Data processing (GDPR). Collecting, storing, and enriching contact data of business people is regularly possible in B2B without consent, via legitimate interest under Art. 6(1)(1)(f) GDPR. This requires a documented balancing of interests, traceable data origin, and a functioning objection process.

Level 2 — Promotional outreach (UWG). Whether you may reach out on a specific channel is governed by Section 7 UWG. And this provision is channel-dependent — with significant differences.

Channel	Requirement for first contact
Letter mail	Permitted as long as there’s no objection — the only channel that doesn’t require consent
Phone (B2B)	Presumed consent suffices if there’s a factual connection to the recipient’s role (Section 7(2) No. 1 UWG)
Email	Prior consent required (Section 7(2) No. 2 UWG); exception only via Section 7(3)
LinkedIn and professional networks	Generally treated like messengers — but a staged approach based on legitimate interests and the network’s terms of use is fundamentally possible
WhatsApp and SMS	Prior consent required; existing-customer privilege disputed

The table explains why a phone call in B2B is often the legally milder route than a WhatsApp message — a result that initially runs counter to most sales teams’ intuition.

Why WhatsApp falls under Section 7(2) No. 2 UWG

The provision speaks of “advertising using … electronic mail.” Messenger services are, per prevailing legal opinion, covered by this: they serve the same function as email — a message addressed to an individual recipient that lands in their personal inbox and claims attention there.

The degree of nuisance with WhatsApp is arguably even higher than with email, because the message arrives on a device most people also use privately, and because it triggers a push notification. That’s not an argument for milder treatment, but for stricter treatment.

The distinction from phone calls matters here: Section 7(2) No. 1 UWG allows presumed consent to suffice for B2B phone calls — it’s enough if the advertising has a factual connection to the recipient’s role and contact can reasonably be expected. This relaxation explicitly does not exist for electronic mail. Applying it to WhatsApp stretches the provision beyond its scope.

The existing-customer privilege and its open flank

Section 7(3) UWG permits direct marketing to existing customers without separate consent if four conditions are cumulatively met: the address was obtained in connection with the sale of goods or services, the marketing concerns the company’s own similar products, the customer has not objected, and they were clearly informed of their right to object both at collection and at every use.

The point of dispute lies in the first criterion. The provision names the “electronic mail address.” Whether a mobile number used for WhatsApp falls under that is not conclusively settled. There are good arguments for it — functionally, the number is the address — and equally good ones against, because the number is typically collected for phone calls, not messenger marketing.

For practice, that doesn’t mean “prohibited,” but “unresolved, and the sender carries the risk.” Anyone using WhatsApp systematically in existing-customer campaigns should not rely on Section 7(3), but on a channel-specific consent that explicitly names WhatsApp.

What practically remains

The channel therefore loses the role it’s often assigned in outbound — the breakthrough first-contact tool. What remains is the role as a continuation channel within an already-opened dialogue. Four scenarios hold up:

1. The contact switches channels themselves. They reply to an email with “feel free to message me on WhatsApp, +49…”. The initiative documented lies with the recipient.
2. Scheduling logistics after an initial conversation. The channel is agreed upon in the conversation and the agreement is recorded in the CRM.
3. Trade show and event contacts where the number was deliberately exchanged, with awareness of its purpose. A collected badge scan is not this.
4. Ongoing proposal or project phases where the customer has established the channel.

In all four cases, the decisive point isn’t the message, but the proof. Anyone who doesn’t document the consent with timestamp, wording, and source doesn’t have it in a dispute.

The operational consequence for sequences

Anyone building multi-channel sequences should therefore not model WhatsApp as step 1 or 2, but as a conditional step that only triggers if a consent flag is set on the contact. Technically, that’s a field check before sending; organizationally, it’s the point where a human checks the data basis once.

This is exactly where the difference between a clean and a risky setup lies: a system that sends WhatsApp messages from the same list as emails produces violations by the second. A system that couples the channel to a documented consent field can use it safely — just for far fewer contacts than the list provides.

That the check happens before sending, not after, is the whole point. More on this in the article on Human-in-the-Loop in AI Outbound.

Warning signs from vendors

If a tool or agency vendor advertises WhatsApp cold outreach as a feature, that’s not an innovation edge, it’s a liability risk being passed on to you. The sender of an unlawful marketing message is the advertising company — not the tool.

Specific phrasings you should question:

• “WhatsApp cold outreach, 100% GDPR-compliant” — the claim conflates the two legal levels and ignores the UWG entirely.
• “Legitimate interest also covers messengers” — that covers data processing, not the outreach itself.
• “You can always message existing customers via WhatsApp” — overstates an unresolved legal dispute as settled law.
• “We assume the legal risk” — check whether that’s contractually structured as an indemnity. Usually it isn’t.

Conclusion

WhatsApp is an excellent channel in B2B — used at the wrong point. For first contact, Section 7(2) No. 2 UWG requires prior consent, and the relaxation phone calls enjoy in B2B doesn’t exist here. The existing-customer privilege is unresolved for messengers and doesn’t support a systematic process.

What remains is a strong continuation channel for dialogues the contact themselves has moved there — provided the consent is documented and the sequence checks it before every send. Anyone who uses the channel this way gains response speed. Anyone who uses it as a shortcut into cold lists is buying a cease-and-desist letter.

This article is guidance for sales practice and does not replace legal advice for individual cases. Consult legal counsel for the specific design of consent language and processes.