For details on how Record Collection and storage work, see PSTN Call Records - How it Works & Use Cases
This report presents PSTN usage by your users and shared devices, compiled from all available Call Detail Records (CDRs) in your Microsoft Teams Calling environment.
It provides a summary of user call activity and, as of version 10.3, offers insights on recommended plans for users while flagging those that can be adjusted to match these recommendations.
How Utilization is Calculated
- CDRs are calculated for Voice-Enabled Teams Accounts with an assigned phone pumber or Shared Calling Policy.
- Only the first leg of the call record is considered
Known Limitations
Because only the first leg of the call is considered (transfers from a queue or autoattendant to a user are not considered) there are some known limitations:
- Calls placed/received to/from the queue or auto-attendant are associated with the resource account.
- If the user has Shared Calling, only outbound calls are considered. Inbound calls are tabulated against the Resource account answering the call (Auto Attendant or Call Queue).
- All Shared Calling users will always show as having 0 incoming calls, given that incoming calls first route through an AA or Queue.
How Monthly Usage is Calculated
User must have a call older than 30 days for Monthly usage insights to be populated for UPNs with Enterprise Voice Enabled.
-
Example 1 - Oldest call from user is 120 days ago, total calls/minutes are divided by 4 to get monthly (30 day) average.*
-
Example 2 - User only has a call from last week. Monthly averages cannot be calculated.*
How Recommended Plans Are Calculated (version 10.3)
Note: Recommended Plans can only be provided when monthly usage is calculated.
- Accounts with a low amount of incoming calls and outgoing minutes should be on Shared Calling
- Accounts with a high amount of incoming calls (where a DID is warranted) but low amount of outgoing minutes should be on a Per Minute Plan
- Accounts with a high amount of incoming calls and high amount of outgoing minutes should be on a Bundle
Customizable Thresholds - Administrators can adjust the thresholds for the above calculations via the administration page.
How Rows Are Marked for Suggested Change (version 10.3)
Operator Connect & Direct Routing
With Operator Connect or Direct Routing Numbers, the platform does not have visibility into the type of plan assigned to the account, but we can still propose certain changes, namely:
-
Accounts with Shared Calling:
with low outgoing calls, high incoming should change to a Per Minute Plan with a dedicated DID(not possible until visibility into incoming calls becomes available)- with high outgoing calls should upgrade to a Bundle
-
Accounts with a dedicated number and low outgoing and low incoming downgrade to Shared Calling
Microsoft Calling Plans
-
When on Shared Calling Accounts:
With low outgoing calls, high incoming. Upgrade to a Per-Minute Plan (Pay-As-you-go) requiring a DID(not possible until visibility into incoming calls becomes available)- Woth high outgoing calls, high incoming. Upgrade to BUNDLED-MINUTES. (Calling Plan)
-
Pay-As-You-Go Accounts:
- with low outgoing and low incoming, downgrade to SHARED CALLING.
- wotj high outgoing, upgrade to BUNDLEED MINUTES
-
Accounts with Calling Plans:
- with low outgoing and high incoming, downgrade to PER-MINUTE
- with low outgoing and low incoming, downgrade to SHARED CALLING.
Notes
- This report is created by analyzing all assigned numbers in Teams and cross-referencing those numbers with any corresponding CDR related to calls made or received.
- The report stores calling data for the past 90 days.
Required Permission
This report requires the CallRecords.Read.All API permission. For more information consult the Roles and Permissions Required for ZPM documentation.