Data Panda brings your Webex meeting, calling and device 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 IT, operations and sales teams use every day.
Webex is Cisco's unified-communications platform. It bundles Webex Meetings, Webex Calling, Webex Messaging, Webex Contact Center and the Webex Devices fleet (room kits, desk phones, headsets) into one client and one admin surface. The product sits inside Cisco's broader collaboration stack, with hooks into the network gear, identity and security tooling that already runs in the same building.
Most Webex shops are large, regulated or both. Banks, public administrations, hospitals, defence and education tenants pick it because it ships with on-prem and hybrid options, FedRAMP-authorised tiers, and a room-device line that mounts in halls Cisco salespeople measured ten years ago. Our connector pulls the activity surface that lives across that estate: meetings with hosts, durations and recurrence, participant join and leave times, call records, recording inventory, room-device usage and the user directory. That metadata answers the questions IT and finance keep asking on quarterly admin-portal exports. Which Webex licences are paid for and never used. Which conference rooms host two meetings a day and which ones host two a quarter. How recording storage is climbing now that hybrid meetings are the default. Those answers are worth a lot more in a warehouse next to headcount, real-estate and Microsoft 365 data than inside Control Hub.
Meetings, calls, recordings and room devices in one place, instead of three Control Hub exports nobody re-runs.
Let Webex activity metadata trigger the housekeeping the IT lead would otherwise do by hand in Control Hub.
Put Webex usage and Cisco network signals next to each other so the UC bill lines up with how the network gets used.
Small internal tools on Webex metadata for IT, facilities and finance audiences.
A list of concrete reports, automations and AI features we have built on Webex data. Pick the one that matches your situation.
Which Webex licences are we paying for and nobody uses?
Active versus provisioned Webex Suite seats per business unit and site, with last meeting, last call and last recording date attached. Finance and IT see which seats are sitting unused since the last reorganisation, instead of guessing from a Control Hub export pulled the morning of the renewal call.
Which meeting rooms still earn their Cisco kit?
Booked hours, real join activity and recording counts per room device and per building. Facilities and IT spot rooms whose Webex Room Kit hosts two calls a day and rooms whose kit hangs idle for a quarter, which sets the next move (relocate, downsize the spec, or pull the device) on numbers rather than walking the floor.
Are Webex and a parallel meetings tool both being paid for the same people?
Hybrid tenants where Webex runs alongside Microsoft Teams or Zoom show user-level overlap directly. The view names users active in both platforms in the same week, which lets IT and finance decide where a seat belongs and where the parallel licence can come off the next renewal.
Webex Suite spend per active user, per active room device and per active queue becomes a number you can compare across business units, instead of one line in the Cisco contract. Useful at renewal, when the Cisco account team wants to talk seat counts and you want to talk actual use.
External meeting hours per rep against pipeline and account activity. Sales leadership separates reps who carry their week with the right customers from reps whose calendar fills with internal Webex syncs.
Estate-wide topology in one view. IT runs licence reclaim, room-device audits and recording-retention reviews on data that refreshes with the rest of the warehouse, instead of on a one-off Control Hub export from last quarter.
External Webex meetings join back to the Salesforce account and opportunity using attendee emails and calendar metadata. Rep activity reports show actual customer-facing hours per deal stage, and managers see which opportunities close with three calls and which ones drag through twenty.
Upcoming and finished Webex meetings post to the relevant Slack channel with host, agenda link and participant count, so a hybrid Cisco-and-Slack tenant keeps meeting context where the team already chats. Useful when one business unit runs Webex for video while the rest of the company lives in Slack.
Webex meeting timestamps, hosts and participant counts sit next to the Gong transcript and deal-health score for the same call. Sales leadership reviews one row per conversation where time spent, who was on it and how it went are visible together, instead of toggling between Control Hub and Gong.
External Webex meetings match back to the HubSpot company and deal using attendee email and meeting timestamps. Marketing and sales see which deals are getting real video time after a campaign lands, and revenue reports show meeting hours per deal stage rather than calendar invite counts.
You keep the reporting tool you already have. We connect it to the warehouse where your Webex 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.
The connector stays at the metadata surface: meetings (host, topic, start, duration, recurrence), participants (join and leave times), Webex Calling records, recording inventory entries (with size and retention label) and the user directory. Recording media itself, transcripts and chat content are not part of the default pull, which keeps the warehouse focused on usage and licence reporting rather than conversation analysis. Conversation-level review is better handled in the system that already has consent and retention controls in place.
Webex spans cloud-only tenants, hybrid deployments that pair the cloud with on-prem services (Webex Hybrid Calling, Hybrid Calendar, Expressway), and FedRAMP-authorised cloud tiers used by US public-sector tenants. The connector reaches whatever surface your admin scope and credentials cover. For hybrid and government tenants we agree the scope up front, since some data lives in your own datacentre and some in the Cisco cloud, and the warehouse model has to reflect both.
We review your Webex setup and the systems around it. Together we pick the first thing worth building.