Call reporting for Microsoft Teams, from inside your own tenant.
Connect Insights for Microsoft Teams shows how your calls went: who you missed, how your queues did and why a call sounded poor. Your call data never leaves your own Microsoft tenant.
Purple • Microsoft Teams telephony and contact center • 90+ countries • Dutch support
- Callers say they could not get through: The complaint arrives weeks later, by email. Teams does not show you which calls to people's own numbers went unanswered, or how long callers stood in a queue before they hung up.
- Nobody knows if that caller was rung back: A missed call sits in one colleague's head. There is no shared answer to who still owes a call back, so the same customer rings a third time.
- Teams forgets before the quarter is over: The Teams Queues app keeps call data for 45 days, so this quarter cannot be put beside the last one. And what it keeps is about queues, not about calls to someone's own number.
- Every screen opens with its finding in one sentence: The summary says how calling went before you have read a single figure, and puts the few things most worth acting on underneath, each one a link. Pick any period from one day to a year and it is set beside the same weeks before.
- Was every missed caller rung back, and how fast: Missed callers are sorted by how quickly they were rung back: within an hour, within eight hours, later, or never. The ones still waiting come first, and the departments where contact is lost sit next to them.
- Service level, waits and the callers who gave up: Per queue, with gave up, overflowed and timed out kept apart, because they are three different problems with three different fixes. Click a figure and the calls behind it open, worst first.
- Why the call sounded bad: the network, the headset or neither: Audio devices are compared across many calls rather than judged one call at a time, worst first. The network screen does the same for wired, wifi and mobile, and names the wifi adapter and driver that performs worst across your laptops.
- Call back: Within an hour, within eight hours, later or never. Callers still waiting come first.
- Queues: Service level, waits and callers who gave up, per queue. Gave up, overflowed and timed out are counted apart.
- Wallboard: A full screen board of today's queues for a TV or a second screen. It refreshes every minute and shows the time it was drawn. Counts only, no names.
- Roles: Administrators see everything, department managers their own department, queue managers their own queues on the queue screens and the wallboard. Sign-in uses your own Microsoft accounts.
From €149 per month. For up to 50 licensed Teams Phone users, with the queue reporting included. Purple sets it up with you. Connect Insights runs in your own Azure subscription, so the Azure bill is yours: roughly €40 a month. We put that in the quote rather than let you find it later.
Frequently asked questions
Can Purple see our call data?
No. Connect Insights runs in your own tenant, and the access Purple has through Azure Lighthouse cannot reach your data.
Is this employee monitoring?
No. It reports how calls went, never when someone worked or for how long. There is no screen, export or field for anyone's hours, which is why it suits a conversation with your works council.
What do we need?
Microsoft Teams Phone, an Azure subscription in your own tenant, and an administrator who can give consent. The Azure resources run on your own subscription.
Is it real time?
No, on purpose. A call usually appears about twenty minutes after it ends, which is when Microsoft publishes it. The wallboard shows today so far and refreshes every minute.
Who sees what?
Administrators see everything, department managers their own department, queue managers their own queues. A wallboard account sees only the wallboard, for the queues you chose.
What does it cost?
From €149 a month for up to 50 licensed Teams Phone users. On top of that you pay your own Azure, roughly €40 a month, because everything runs in your own subscription.
How far back does the history go?
History starts about 30 days before installation, which is Microsoft's limit, and grows from there. After that you choose how long it is kept.
How do updates work?
New releases reach your deployment by themselves. There is no maintenance on your side.
Which languages?
Dutch and English, on every screen, chosen per person.