Data Panda brings your WhatsApp Business conversation metadata together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your support, marketing and operations teams use every day.
WhatsApp was founded in February 2009 by Jan Koum and Brian Acton, both former Yahoo engineers, and was acquired by Facebook on 19 February 2014 for roughly 19.3 billion dollars, the largest venture-backed acquisition at that point. End-to-end encryption on the Signal Protocol rolled out across all conversations on 5 April 2016. The consumer app passed three billion monthly users in 2025 and became the dominant messenger across the EU, Latin America and the Indian subcontinent.
The business side started in January 2018 with the small-business WhatsApp Business app, then expanded in May 2022 with the Cloud API, today branded as the WhatsApp Business Platform. That platform is what mid-market and enterprise teams plug into through Business Solution Providers like Twilio, MessageBird (Bird) and 360dialog. Pricing runs per conversation, in four categories (marketing, utility, authentication and service), with rates that vary by country. The platform also enforces a 24-hour customer service window: outside that window the only outbound message you can send is a pre-approved template, in one of the three paid categories. None of that scope is visible inside the BSP console at the level the CFO or the support lead wants it.
Volume, category mix and per-country cost per conversation in one place, instead of an export the BSP only sends once a month.
Let WhatsApp events trigger work in the systems where the answer needs to land.
Put conversation topology behind AI that helps route, classify and forecast, on the metadata layer rather than message bodies by default.
Small internal tools on WhatsApp metadata for support, marketing and finance teams.
A list of concrete reports, automations and AI features we have built on WhatsApp Business data. Pick the one that matches your situation.
What is WhatsApp costing us this month, by country and by category?
Per-conversation cost split across marketing, utility, authentication and service categories, broken out per country and per sending business unit. Finance and the channel owner see the bill before the BSP invoice arrives, so the conversation about category mix and country spread happens with numbers, not with the BSP rep's monthly recap.
Which conversations are about to fall out of the 24-hour service window?
Open conversations with the time remaining before the free-form service window closes, grouped by team and by customer tier. Support leads see which threads need a reply or a pre-approved template before the channel locks them out, instead of finding out the next morning that a customer was left hanging.
Do our marketing sends have a verifiable opt-in behind them?
Marketable contacts joined to the opt-in event, with the source, timestamp and channel of consent. Marketing leadership sees which segments have a clean opt-in basis before pressing send, which is also the question DPO and legal want answered before a WhatsApp marketing template ever ships.
Channel cost reconciled against BSP invoices. Cost per conversation and category mix become numbers you can challenge per country, instead of accepting a single line in the SaaS-spend deck.
Conversations linked to accounts and opportunities. Sales sees which prospects engaged after a marketing template, which ones replied within the service window, and which ones never opted in to begin with.
Support and marketing-ops in one view. The team sees first-response time, service-window risk and template-approval health on data that refreshes with the rest of the warehouse, not on a CSV the BSP exports once a month.
Lifecycle-stage changes and list memberships in HubSpot trigger the right WhatsApp template send through your BSP, with consent and country-of-residence checks applied first. Marketing reaches contacts on the channel they open most, and the per-conversation cost lands back on the HubSpot contact so campaign reporting includes the WhatsApp leg.
New WhatsApp threads create or update Zendesk tickets with customer tier, language and service-window deadline attached, and stage changes flow back so the agent sees one timeline. Support leads catch the conversations approaching the 24-hour edge before the channel locks the team out, and reply time stops being a separate KPI from the rest of the helpdesk.
Order-status, back-in-stock and abandoned-cart segments in Klaviyo trigger the right WhatsApp template through your BSP, with the message classed as utility or marketing per Meta's category rules. Ecommerce sees opens and clicks land back on the Klaviyo profile, and per-conversation cost is part of the campaign ROI from day one.
Brevo lists and automation steps fan out across email and WhatsApp templates, with the channel choice driven by opt-in coverage and the per-conversation cost in the destination country. The marketing team picks WhatsApp where the open rate justifies it and email where it does not, on numbers from the warehouse rather than a gut call.
These are the 1 tables we currently pull from WhatsApp Business into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your WhatsApp Business data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
By default we pull conversation metadata: conversation id, category (marketing, utility, authentication, service), template name, sender number, recipient country, status, timestamps and cost where the BSP exposes it. Message body content stays out of the default scope, which keeps the warehouse well clear of the most sensitive part of the channel. Pulling message text is technically possible through the BSP API but needs an explicit privacy and retention conversation first, and is not how we recommend most customers start.
WhatsApp Business almost always sits behind a Business Solution Provider, and the connector pulls from that BSP rather than from Meta directly. That means the available fields and the freshness depend partly on what your BSP exposes through its own API, which we map into a consistent shape on our side. If you switch BSP later, the warehouse model stays the same and only the source connector changes.
We review your WhatsApp Business setup and the systems around it. Together we pick the first thing worth building.