How to Create a Service Desk Dashboard in Looker

Building a great service desk dashboard means you can finally stop guessing how your support team is truly performing. Instead of scattered data and manual reports, you get a clear, real-time view of everything that matters. This guide will walk you through building your own service desk dashboard in Looker, from picking the right metrics to creating your first visualizations.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Why A Looker Dashboard Is a Game-Changer for Your Service Desk

Ditching siloed analytics in tools like Jira Service Management or Zendesk for a centralized Looker dashboard isn't just about making prettier charts. It’s about unlocking real, operational benefits. In reality, most native reporting tools only show you a piece of the puzzle. A dedicated dashboard gives you the full picture.

• End Reactive Fire-Fighting: Instead of waiting for a high-priority ticket storm to discover a problem, a dashboard helps you spot negative trends in response times or ticket backlogs early.
• Boost Team Performance: You can objectively track metrics like first response time and tickets resolved per agent. This highlights top performers who can mentor others and identify those who might need extra support, all backed by data, not gut feelings.
• Improve Customer Experience: By monitoring Customer Satisfaction (CSAT) scores, SLA compliance, and First Contact Resolution (FCR), a dashboard provides a constant pulse on the quality of your service.
• Justify Resources: Need to make a case for hiring another support agent? A dashboard showing a rising ticket volume trend alongside a spiking backlog is hard evidence for management to ignore.

Choosing the Right Metrics for Your Dashboard

A common mistake is cramming every possible metric onto a single screen. This creates a cluttered, confusing dashboard that nobody uses. The goal is clarity, not complexity. Start by focusing on a handful of key metrics that answer specific business questions across a few core areas.

Ticket Volume & Trends

These metrics help you understand demand and plan for peak times.

• Created vs. Resolved Tickets: Visualized as a dual-line chart, this immediately shows if you’re keeping up with incoming demand or falling behind.
• Tickets by Channel: A simple bar chart showing ticket volume from sources like email, portal, phone, or chat helps you understand where to allocate resources.
• Ticket Inflow by Day/Hour: A heatmap is perfect for this. It can reveal predictable rushes (like Monday mornings), allowing you to schedule staff more effectively.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Team Performance & Efficiency

These metrics focus on how effectively your team is handling the workload.

• Average First Response Time (FRT): This is a crucial indicator of customer experience. Tracking this as a KPI, maybe with a gauge visualization against a target, shows how quickly customers get an initial acknowledgment.
• Average Resolution Time: This measures the entire lifecycle of a ticket, from creation to close. A line chart showing the trend over time can reveal a process improvement or a system issue.
• SLA Compliance Rate: A single, big number showing the percentage of tickets that met their Service Level Agreement (SLA) is a powerful, high-level metric for stakeholders.
• Tickets Resolved Per Agent: A simple table or bar chart helps you understand workload distribution and individual capacity.

Customer Satisfaction

This is where you measure the perceived quality of your support.

• Customer Satisfaction (CSAT) Score: Whether it's a 1-5 scale or a percentage, display this as a large number or a trendline to easily monitor customer happiness.
• First Contact Resolution (FCR) Rate: What percentage of issues are solved in a single interaction? Higher FCR means happier customers and a more efficient team.

Getting Your Data Ready for Looker

Looker doesn't store your data, it queries it where it lives, which is typically a cloud data warehouse like Google BigQuery, Snowflake, or Amazon Redshift. This means you need to first get your service desk data (from ServiceNow, Jira, Zendesk, etc.) into one of these systems.

This is usually done with an ETL (Extract, Transform, Load) tool like Fivetran or Stitch that automatically pulls data from your service desk app and loads it into your warehouse.

Once the data is in your warehouse, the real magic of Looker begins with its modeling layer, LookML. Your data team will write LookML code to define your business logic. In simple terms, this is where you tell Looker:

• The Relationships: How tables like tickets, users, and comments relate to each other.
• The Dimensions: The things you want to group by or filter on (e.g., ticket_status, agent_name, creation_date).
• The Measures: The calculations and aggregations you want to perform (e.g., count of tickets, average resolution time, SLA met percentage).

A well-structured LookML model is the foundation of your dashboard. It makes data exploration intuitive for non-technical users and ensures everyone in the company is using the same definitions for key metrics.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Step-by-Step: Building Your Dashboard in Looker

With a solid LookML model in place, building the dashboard becomes the fun part. It’s a creative process of asking questions of your data and visualizing the answers.

Step 1: Create a New Dashboard

From the folder where you want to save your dashboard, simply click the New button in the top right and select Dashboard. Give it a clear, descriptive name like "Service Desk - Weekly Performance."

Step 2: Add Your First Tile (Ticket Volume Over Time)

Every chart or number on a Looker dashboard is called a "Tile." You create Tiles from an "Explore." An Explore is a user-friendly starting point for querying a specific dataset defined in your LookML.

1. Navigate to your service desk Explore.
2. In the left-hand field picker, find your Tickets view.
3. Select a time dimension, like Created Date. You can automatically group this field by Week or Month.
4. Select a measure, like Ticket Count.
5. Click the Run button. Looker generates the data.
6. In the Visualization panel, choose the Line chart icon. You can customize axes names and colors.
7. Click the gear icon in the top right and select Save > To an existing dashboard, then choose the dashboard you just created. Your first Tile is live!

Step 3: Create an "SLA Compliance" KPI Tile

Key Performance Indicators (KPIs) work best when presented as big, bold numbers. This makes them easy to scan.

1. Start a new query from your Explore.
2. This time, select only one measure, like SLA Met Percentage. This should be a pre-defined calculation in your LookML that divides tickets meeting their SLA by the total number of tickets.
3. Run the query.
4. In the Visualization panel, choose Single Value. Looker will display the result as a large number.
5. Save this Tile to your dashboard.

Step 4: Visualize Agent Workload with a Bar Chart

Let's create a chart to see how many tickets each agent has resolved.

1. Begin another query in the Explore.
2. Choose a dimension, such as Assigned Agent Name.
3. Select a measure, like Resolved Ticket Count.
4. Run the query to see the data table.
5. Switch the visualization to a Bar chart.
6. Arrange axes and labels for clarity, and save the Tile to your dashboard.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Step 5: Add Interactive Filters

A static dashboard is useful, but an interactive one is truly powerful. Filters allow your users to slice and dice the data on their own.

1. While viewing your dashboard, click the three-dot menu icon in the top right and select Edit dashboard.
2. From the top menu, select Filters > Add Filter.
3. Let’s add a Date filter. Give it a title, choose the field to filter, and configure a default value (like "Last 30 Days").
4. In the Tiles To Update tab of the filter configuration, make sure you link the filter to the correct date field on each Tile you want it to affect. For some, it may be ticket close date, ticket open date, or ticket first reply date, etc.
5. Save your filter. Now, anyone viewing the dashboard can change the date range and all the linked tiles will update instantly.

Tips for a Dashboard That Actually Gets Used

Creating the dashboard is only half the battle. Now you need to make sure it's a go-to resource for your team.

• Start with questions, not tools. Before building, ask "what are the 3-5 biggest questions our team needs answered daily?" Then, build visualizations that answer precisely those questions.
• Tell a story. Arrange your tiles logically. Start with high-level KPIs at the top (like overall CSAT and SLA Compliance), then drill down into ticket trends, and finally, show individual performance metrics at the bottom.
• Keep it clean. A good dashboard has plenty of white space. Resist the urge to add "one more chart." If it's not essential, leave it out. You can always build a separate, more detailed dashboard for deep-dive analysis.
• Automate with scheduling. Use Looker's scheduling feature to email a PDF or a report with an embedded PNG of the dashboard to stakeholders every Monday morning. This keeps the data top-of-mind without them ever needing to log in.

Final Thoughts

Creating a service desk dashboard in Looker is a shift from wading through CSV files to having a clear, strategic overview of your entire support operation. By focusing on essential metrics and presenting them in an intuitive way, you empower your team to make smarter decisions, improve service quality, and prove their value to the entire organization.

Frankly, setting up data pipelines, writing LookML code, and mastering a complex tool like Looker can be time-consuming, especially for teams without a dedicated analyst. At Graphed , we thought this process should be easier. For our users, connecting data sources and creating a real-time service desk dashboard is as simple as describing what you want to see. Just ask a question like "Create a dashboard showing our ticket backlog trend next to our average resolution time for the last quarter" and the visualizations are built for you in seconds.