Top tips for Geckoboard-Zendesk power users

Learn about best practices for displaying your Zendesk data.

June 23, 2026

Set goals for your number visualizations

Geckoboard can visualize your progress toward targets or goals (up or down). If you have a clear target for your support metrics (e.g., reducing “First response time” to 2h from the current 4h average), you can include this on your number visualizations.

Embed your dashboard into Zendesk to boost visibility

One of the great things about Geckoboard is that it helps you create better visibility for your metrics. So, if your support team spends most of their time in Zendesk, it makes sense to embed your Geckoboard dashboard inside the Zendesk platform, where even more agents will see it more often.

This can be achieved using Zendesk’s iFrame app and Geckoboard’s Share links. To set up the iFrame app, provide the items below:

1. A title for your dashboard
2. The iFrame URL of your dashboard (insert your sharing link here)
3. An abbreviation to display in Zendesk (we recommend GB for Geckoboard)

Monitor time spent working on tickets

If you'd like to monitor time spent working on tickets, you can use the Zendesk Time Tracking app and custom fields.

Once set up, you can select Total time spent or Time spent last update as metrics, then add filters to get the desired granularity.

Use Drilldown to investigate the data behind your widgets

To see what's driving your metrics, use Drilldown and access Source data for all your Zendesk visualizations (except tables).

For example, if your CSAT has just gone down, you can zoom in to find out the tickets that caused the change.

Use the Geckoboard MCP to explore your Zendesk data with AI

The Geckoboard MCP connector gives compatible AI tools such as Claude and ChatGPT access to the Zendesk data (and other data sources) you've connected to Geckoboard. Once it's set up, you can ask your AI assistant to investigate changes in a metric, run custom calculations, or build tools of your own, all backed by Geckoboard's reliable data.

Here are some suggestions:

• Investigate metric changes: ask your assistant to dig into a change you've spotted, for example, "Use the Geckoboard MCP to investigate why my First reply time in Zendesk has increased recently."
• Calculate custom metrics: compute Zendesk metrics beyond the built-in offering, such as ratios between two values.
• Build your own mini-tools: set up something like a morning brief that surfaces any metrics worth a closer look since yesterday.
• Create hyper-personalized dashboards: build completely custom dashboards, using any visualizations and styles you want, all backed by Geckoboard's trusted, reliable metrics.

To set this up, read our guide on getting started with the Geckoboard MCP.

Display your team status

If you are using Omnichannel Routing, you can create a view of your teams' status using the Agent status metrics in the Zendesk Support data source.

Display Zendesk Messaging metrics

Using the Zendesk Support data source, you can create a wide range of metrics from Messaging with two different methods.

If you'd like to display real-time queue monitoring metrics, select the Messaging option from the Display field of a Zendesk Support widget, then select your preferred metric.

Alternatively, if you're interested in channel performance metrics, select any of the ticket metrics, then apply a filter to target only the Native messaging channel.

Compare historical metrics to see how their relationship evolves

When tracking historical data, it is often handy to compare the behavior of different metrics over a rolling time period.

For example, if you have a line chart for monitoring ticket creation over the past 14 days, you can put that into context by comparing it against the number of tickets solved in the same time period.

The most commonly compared metrics include:

• Created tickets vs. Solved tickets
• First reply time vs. First resolution time
• Number of SLA tickets breached vs. Number of SLA targets achieved

Get alerted if tickets ever get caught in back-and-forths

Your customers don't want long email chains any more than you do. Make those friction points visible, and you can finally address them.

Use this approach to achieve faster resolution times, higher satisfaction scores and spot patterns that help you prevent back-and-forth from happening in the first place.

Get alerted if a customer ever waits too long for a reply

Improve key support KPIs such as Average wait time proactively through this approach.

Create triggers in Zendesk to keep track of specific metrics

Want to visualize a metric that Geckoboard doesn’t support? It’s very possible that you can still achieve this through the use of tags and triggers.

Using Triggers, you can tag tickets in Zendesk when certain conditions are met. You can then use Geckoboard to visualize metrics related to your tagged tickets.

For example, with Geckoard, you can keep track of the one-touch resolution rate. But what if you want to know the absolute number of one-touch tickets (instead of the ratio)? Creating a couple of triggers in your Zendesk instance allows you to monitor the volume of tickets solved in one interaction.

Other useful examples include creating triggers to:

• Keep track of tickets received in a specific inbox
• Monitor tickets in a custom status