Zendesk custom fields reporting: build reports that match your workflow
Standard Zendesk metrics tell you how fast your team responds and how many tickets arrive. Custom fields tell you what those tickets are about, who they affect, and why they matter to the business. If you have set up custom fields in Zendesk — product area, issue type, contract tier, revenue segment — but never built reports around them, you are sitting on the most operationally useful data in your instance and not using it.
This guide covers how to report on custom fields in Zendesk Explore, how to combine them with standard metrics for richer analysis, and what to do when the reports reveal problems worth fixing. For related context, see the support metrics dashboard hub.
Why custom field reporting matters
Every Zendesk instance ships with the same default fields: priority, type, status, group, assignee. These are useful for basic operations, but they do not capture your business context.
Custom fields fill that gap. Common examples:
- Product area: Which feature or product does this ticket relate to?
- Issue type: Bug, how-to, billing, account access, feature request.
- Customer tier: Enterprise, SMB, free, trial.
- Contract value or MRR range: Which tickets come from high-revenue accounts?
- Root cause: What actually caused the issue (shipping delay, integration failure, UI confusion)?
Without reports on these fields, your dashboards answer “how fast” and “how many” but not “about what” or “for whom.” The first set of questions is operational. The second set is strategic.
Prerequisites
Before building custom field reports, confirm:
-
Your custom fields are consistently used. Run a quick check: what percentage of tickets have the field populated? If fewer than 80% of relevant tickets have a value, fix the fill rate first. Reports on sparse data mislead more than they help. See tag coverage rate for a parallel concept.
-
Field values are clean. Dropdown fields are cleaner than free-text fields for reporting. If you are using free-text custom fields for categories, consider migrating to dropdowns so values are consistent.
-
You have Explore access. Custom field reporting requires Zendesk Explore on Professional or higher. The fields appear in the Tickets dataset under “Custom fields.”
How to report on custom fields in Zendesk Explore
Step 1: Find your custom fields in the dataset
In Zendesk Explore, open a new report using the Support: Tickets dataset. In the Rows panel, expand Ticket custom fields. You should see each custom field listed by its display name. If a field does not appear, it may not be reportable — check that it is a supported field type (dropdown, text, numeric, checkbox, date).
Step 2: Build a distribution report
Start with the simplest useful report: a breakdown of ticket volume by custom field value.
- Metric: COUNT(Tickets)
- Rows: Your custom field (e.g., Product Area)
- Filter: Date range (last 30 or 90 days)
This shows you how tickets distribute across categories. If 60% of your tickets land on one product area, that is where your ops investment should concentrate.
Step 3: Cross-reference with standard metrics
The real value comes from combining custom fields with the metrics you already track:
| Report | Metric | Rows | What it reveals |
|---|---|---|---|
| Resolution time by product | Median resolution time | Product area | Which products are hardest to resolve |
| FRT by customer tier | Median first reply time | Customer tier | Whether high-value customers get faster responses |
| CSAT by issue type | CSAT score | Issue type | Which issue categories drive dissatisfaction |
| Volume by root cause | COUNT(Tickets) | Root cause | Where to invest in prevention |
Each of these is a one-step extension of your existing reports. Add the custom field as a second row or filter, and you transform a generic metric into a business-specific insight.
Step 4: Build trend views
Static distributions are useful but limited. Add a time dimension:
- Metric: COUNT(Tickets)
- Rows: Your custom field
- Columns: Ticket created — Month
This shows whether a category is growing, shrinking, or stable. A ticket volume spike in “integration issues” after a product release tells engineering something specific. A flat line in “billing questions” tells finance their documentation is holding.
Step 5: Create a segment filter
For ongoing use, create a saved filter for each major custom field value. This lets you slice any dashboard by product area, customer tier, or issue type without rebuilding reports. In Explore, save the filter as a dashboard control so stakeholders can toggle between segments.
Combining custom fields for deeper analysis
Single-field breakdowns are a starting point. Cross-tabulations reveal patterns that single fields hide:
- Product area × customer tier: Do enterprise customers disproportionately file tickets about a specific product? That is a retention signal.
- Issue type × resolution time: Bugs may take longer to resolve than how-to questions, which is expected. But if billing issues take as long as bugs, something is broken in the billing workflow.
- Root cause × reopen rate: Tickets tagged “UI confusion” that get reopened frequently suggest the initial resolution is not addressing the actual problem. See customer reopen rate for what to track.
Keep cross-tabulations to two dimensions. Three or more dimensions create reports that are hard to read and easy to misinterpret.
Common mistakes
-
Reporting on fields with low fill rates. If only 40% of tickets have the custom field populated, your report represents less than half of reality. Fix the fill rate before trusting the distribution. Use Zendesk triggers or required fields to improve coverage.
-
Using free-text fields for categorical data. A free-text “product” field will produce dozens of variations (“Payments,” “payments,” “Payment Module,” “pay”). Switch to dropdowns for anything you plan to report on.
-
Ignoring “Other” or “None” categories. A large “Other” bucket usually means your field values do not cover enough categories. Review the underlying tickets to find what “Other” actually contains and add specific values.
-
Building reports without a question. “Show me tickets by product area” is a view, not an insight. Start with a question: “Which product area has the worst resolution time relative to its volume?” Then build the report to answer it.
-
Not connecting to outcomes. A beautiful chart of tickets by issue type is useless if nobody acts on it. Tie custom field reports to decisions: staffing allocation, product priorities, training focus, escalation rate reduction.
What to do when custom field data reveals a problem
Volume concentration
If one custom field value accounts for more than 40% of tickets, investigate:
- Is that expected based on product usage? If so, ensure staffing matches.
- Is there a systemic issue driving volume? A root cause analysis on that segment may reveal a fixable product or documentation problem.
- Should you build self-service content for that category? See self-service rate and help center analytics.
Resolution time outliers
If a specific category has median resolution time significantly above the team average:
- Check whether those tickets require specialized knowledge. If yes, ensure the right agents are assigned. See auto-assignment accuracy.
- Check whether those tickets are being escalated disproportionately. High escalation rate in one category suggests training or tooling gaps.
CSAT differences across segments
If CSAT varies significantly by custom field value, the low-scoring segments are where to focus. A team-wide CSAT of 85% may hide a 65% score for one product area — and that product area’s customers may be churning.
Making custom field reports part of your review
Add custom field breakdowns to your weekly support ops review. Specifically:
- Weekly: Glance at volume by top custom field to catch shifts early.
- Monthly: Review resolution time and CSAT by custom field to find emerging quality issues.
- Quarterly: Audit field values and fill rates. Add new values, retire unused ones, and validate that the taxonomy still reflects how your business operates.
Custom field reports are not a separate analytics track. They are a lens on the same metrics you already review — first response time, resolution time, CSAT, ticket volume — filtered by the dimensions that make those metrics actionable for your business.
FAQ
Which custom field types work in Zendesk Explore? Dropdown, text, numeric, checkbox, date, and regex fields all appear in the Tickets dataset. Multi-select fields have some limitations in Explore’s filtering. Lookup relationship fields may not be directly reportable — check Zendesk’s current documentation for your plan level.
How do I improve custom field fill rates? Make critical fields required on ticket forms. Use triggers to auto-populate fields based on tags, subject line patterns, or requestor organization. Add fill-rate monitoring to your weekly review so gaps get caught early.
Can I report on custom fields across multiple ticket forms? Yes, as long as the field exists on all relevant forms. If a field only appears on one form, the report will only include tickets submitted through that form. For cross-form analysis, use fields that are shared across forms.
What if my team does not use custom fields yet? Start with one high-impact field — typically product area or issue type. Add it as a required dropdown on your main ticket form. After 30 days, build your first distribution report. One well-used field provides more insight than five partially filled ones.