Skip to content
Thirdlane

Platform Analytics

Platform Analytics is a fleet-wide reporting suite for multi-tenant systems. It shows usage across organizations you are allowed to manage: busy tenants, trunk and area-code breakdowns, capacity and seat meters, quiet or inactive tenants, and growth trends.

Open it from Reports > Platform Analytics (system / global / admin roles on multi-tenant installs). It is not shown on single-tenant systems; use Organization Analytics for one organization.

Typical questions

  • Which organizations generate the most traffic in this period?
  • How is inbound vs outbound traffic distributed across the fleet?
  • Which trunks or area codes carry the load?
  • Which tenants are quiet or under-using seats?

Links from busy-tenant rows can open that organization’s CDR Call List for a closer look.

The sections

Fleet Overview is the summary across every organization in your scope, with inbound and outbound totals.

Busy Tenants ranks organizations by call volume with the inbound and outbound split. Clicking an organization opens its call detail records.

Inbound vs Outbound shows the direction mix per organization. Inbound is identified by a DID being present on the call leg.

By Trunk covers named trunks only, and comes with the caveat below.

By Area Code groups outbound calls by North American area code across the fleet.

Traffic Heatmap is fleet traffic presented the way a single organization sees its own: daily, by hour, by weekday, and as a heatmap.

Capacity and Seats compares seat allocation against actual extension counts and feature flags - the section for finding organizations paying for more than they use, or quietly outgrowing what they bought.

Resource Meters reports transcription, recording AI and messaging volumes. These are usage meters, not rated billing.

Quiet Tenants lists organizations with no calls at all in the period. Worth checking before a renewal conversation, and worth checking after a migration, since a newly silent organization is sometimes a broken one rather than an idle one.

Growth Trends shows daily call totals per organization, reading from rollups where they are populated and falling back to live records otherwise.

Why By Trunk often shows no inbound

Inbound calls are attributed to a trunk only when the trunk is tagged on the call record, which normally happens when the DID is associated with that trunk. That association is optional and is missing on many older installations, so the inbound column can read zero even though the carrier trunk plainly carried the calls.

The fix is to associate DIDs with their trunk, which can be done in bulk from DIDs > Batch Update > Set Trunk. Do not simply assign every DID to the only trunk you can see: on multi-tenant and provider systems that is frequently wrong, and it produces confidently incorrect reporting rather than obviously empty reporting.

Access

Only administrators with platform-level access see this menu item. Data is limited to tenants the signed-in admin is allowed to manage.