Why did my Zendesk solved ticket count change?

The Zendesk help pages give 3 common reasons. The first to rule out: The solved count is built from each ticket's status being solved or closed, so a ticket counts only while it has one of those statuses.

What causes it?

  1. The solved count is built from each ticket's status being solved or closed, so a ticket counts only while it has one of those statuses.

    In the Zendesk help: IF ([Ticket status - Unsorted] = "Solved" OR [Ticket status - Unsorted] = "Closed") THEN [Ticket ID] ENDIF Metrics and attributes for Zendesk Support, read 2026-11-12.

  2. Where your plan lets you build Explore reports, a report placed on a dashboard follows the dashboard's filters, so the same report can show a different count there.

    In the Zendesk help: Any filters set inside of an individual report are overwritten by dashboard-level filters. Filtering Explore reports, read 2026-11-12.

  3. A this-year range starts on January 1, so early in the year it covers only a few weeks.

    In the Zendesk help: Year-based date ranges always begin on the first of the year, not 365 days in the past or future. Editing dates and date ranges, read 2026-11-12.

How do I check it myself?

  1. Check the filters on the report and on its dashboard, and remove them one at a time to see which changes the count.

    In the Zendesk help: Verify or remove your filters. Troubleshooting reporting and data discrepancies in Analytics, read 2026-11-12.

  2. Check the reopened tickets count for the same days to see whether solved tickets were reopened.

    In the Zendesk help: The number of tickets that were reopened after being solved. Doesn’t include tickets solved and reopened during the same update. Metrics and attributes for Zendesk Support, read 2026-11-12.

How does Zendesk work with Feder?

  • Connect Zendesk to Feder and it joins your Experience apps.
  • When you connect Zendesk, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.

Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.

See whether you can trust the numbers in Zendesk, one of your Experience apps. Feder only reads. It never changes anything in Zendesk.

Where do these answers come from?

Every cause and check on this page comes from the Zendesk help pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.

Know the day a number breaks, not the month after.