Overview
Heyou integrates with WhatsApp to extend your organization's relationship graph beyond LinkedIn and your CRM. With your permission, Heyou reads the activity of your WhatsApp conversations — who is talking to whom, when, and how often — and translates that activity into relationship signals that inform your team's outreach. Message content is never read.
The integration runs through the Heyou browser extension while you are signed into WhatsApp Web. It is opt-in at both the organization and the individual level, and can be turned off at any time.
Scope
This article covers:
What Heyou reads — and what it does not
Heyou reads:
The list of your WhatsApp contacts, as WhatsApp exposes them to your session (name, phone number)
The list of your WhatsApp conversations, individual and group
Message timestamps — when a message was sent, and by which participant in the conversation
Heyou never reads:
Message text, in any conversation
Photos, videos, voice notes, documents, or any attached media
Status updates or presence information
Message reactions or read receipts beyond the timestamp of the underlying message
Data protection
WhatsApp data is treated as sensitive personal data throughout the Heyou platform. Every stage of processing is governed by controls that meet the same standard as the rest of your Heyou environment.
Sealed in transit. Every batch of WhatsApp data leaving your browser is sealed for the specific service that will receive it. Any request that arrives unsealed is rejected at the boundary.
Encrypted at rest. Contact identifiers, phone numbers, and conversation identifiers are stored under authenticated encryption. Each Heyou environment uses a distinct key; keys are not shared across environments.
Tenant isolation. Your data is scoped to your organization and never mixes with any other customer's data. The tenant boundary is enforced at every query, at the source.
Minimized in observability. Contact identifiers are excluded from the logs, metrics, and alerts our engineering team sees. When an integration issue occurs, the diagnostic signal is preserved without exposing personal data.
Access and consent
The WhatsApp integration is active only when both of the following are true:
Your organization has been provisioned for the WhatsApp module by your Heyou point of contact.
You have granted the Heyou extension permission for
web.whatsapp.comin your browser, and you are signed into WhatsApp Web in that browser.
Removing either permission suspends the integration immediately. Data already ingested is retained under the retention terms of your Heyou agreement and can be removed on request.
How this benefits your team
Sales development representatives discover the warmest introduction path into a target account. LinkedIn describes the network of the possible; WhatsApp reflects the network of the recently active.
Account executives convert cold outreach into referenced introductions by identifying which colleague already maintains an active thread with a decision-maker.
Revenue leaders gain organization-wide relationship coverage without requiring individual representatives to log every conversation in the CRM.
Sales operations receive relationship data that meets enterprise privacy and security expectations: metadata only, encrypted end to end, tenant-scoped, dual opt-in, and revocable.
Getting started
WhatsApp is an opt-in module available to eligible Heyou organizations. If your organization is provisioned for it, the WhatsApp step appears in your Heyou onboarding — this is where you grant the browser permission and confirm your WhatsApp Web session. If the step is not visible in your workspace, your Heyou point of contact can confirm eligibility.
Recent enhancements
The most recent additions to this module. New entries are added by Heyou's release process.
July 2026 — The WhatsApp onboarding step was added to the standard Heyou onboarding flow for eligible organizations, with a hardened token channel between the browser and the Heyou service. Integration reliability was strengthened, with dedicated failure telemetry that preserves diagnostic signal without exposing personal data.
July 2026 — The end-to-end data protection layer was completed for WhatsApp data: sealed transport from browser to service, authenticated at-rest encryption of contact identifiers in the database, and reinforced separation so WhatsApp incidents cannot affect your LinkedIn integration.
Early July 2026 — WhatsApp was added as a Heyou data source. Chat overviews and message timing — metadata only — began flowing into your organization's relationship graph.
If you have a question about this integration or the data it uses, reply to any Heyou email or open the in-product chat. Our team responds to every message.