Teams | Collaboration | Customer Service | Project Management

if you’ve ended up here, there’s a good chance your Salesforce dashboard isn’t keeping up with the pace of the team. Your numbers might look right eventually - just not when you actually need them. Pipeline moves. Deals change stages. Calls happen. Forecasts shift. But when your dashboard is out of date, people stop trusting it - then they stop using it.

Microsoft Teams is where many support teams coordinate work. But Zendesk doesn’t always surface the signals you need there - a problem if you’re in a conversation thread and there’s suddenly a spike in tickets, a string of negative CSAT ratings or anything else that needs urgent attention. In this guide, we’ll show how to send the right Zendesk notifications and KPI alerts into Microsoft Teams, so you and the rest of the team can react fast without turning your channels into noise.

If you’re here because you’ve got a fast-moving sales floor (or a support queue), and HubSpot dashboards aren’t keeping up… you’re not alone. HubSpot dashboards refresh, but not in real time - here’s what’s possible, and how to get a faster live view. HubSpot is brilliant for logging and managing the work.

If you’re weighing up whether to build your own KPI dashboard or buy one, the decision probably feels more complicated than it did a few years ago. Modern APIs are easier to work with. Charting libraries are more prolific and fancier. AI tools can generate working dashboards in minutes. On the surface, the case for building dashboards from scratch has never looked stronger. In practice, the trade-offs have not changed as much as the tools have.

If you’ve spent any time in Zendesk Explore, you have probably run into the same limitation as most support teams. The standard metrics are useful, but they only tell part of the story. Ticket volume, first reply time, resolution time, CSAT. They are a starting point, not the full picture. As soon as you want to dig into how your team is performing against SLAs, backlog, workload, or automation, you need something more tailored to how your support operation works.

Gamification is the practice of adding game-like mechanics such as points, badges, leaderboards and rewards to non-game activities in the attempt to influence behaviour. The term took off in the early 2010s when websites and apps started using the idea to drive engagement. Stack Overflow is a well-known example: simple gamification mechanics like upvotes and reputation scores helped steer behaviour and improve contribution quality. It wasn’t just “fun graphics” - it was a system.

If you lead a support team, you already have plenty of data. Seeing how many tickets are coming in, how long customers are waiting, and whether your team is hitting SLAs is pretty straightforward (especially when using Geckoboard to monitor Zendesk KPIs in real-time!). But what’s often not so obvious is where things are about to go wrong - which conversations are quietly becoming frustrating, which customers are at risk of churning, or where agents are under the most pressure right now.

MTD Training, a leadership and management training provider based in Coventry, had plenty of data but very little shared visibility. Important numbers lived in Salesforce, spreadsheets and handwritten notes. Only a few people could access them, and even then, different reports often gave different answers. For Chief Operating Officer Kelli Grinter, this created a real challenge.

In the Autumn of 2025 we brought together Zendesk customers, implementation partners and friends of Geckoboard for a focused discussion on how support teams are preparing for 2026. Across the fireside chat, guest talks and informal conversations, one theme kept coming up. Teams are moving away from traditional volume reporting and toward clearer, more meaningful visibility into what really shapes customer experience. Here is a breakdown of what we covered and the takeaways you can use right away.