Daily
Get a daily Zendesk ticket report
Each morning you see how many tickets came in and got solved yesterday, and what's still open by priority.
- Runs
- Daily
- Apps
- Zendesk
- AI
- Not needed
- Access
- read
Send this to your assistant
Create a ClickRuntime automation: every weekday at 8am, email me yesterday's Zendesk tickets created and solved, plus how many are open now by priority.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Support managers are asked the same questions every day. How many tickets came in yesterday? How many did we solve? How many are still waiting? Zendesk Explore can answer them, but someone has to open it, set the date range and read the chart, and on a busy Monday that step is skipped. Without a daily number, a slow slide in solved tickets goes unnoticed until the backlog is double.
Each morning, three counts are pulled from Zendesk: tickets created yesterday, tickets solved yesterday and tickets still open right now. They arrive in one email, and the figures are saved so each report can show the trend against earlier days. The whole thing reads like a one-glance dashboard, delivered to your inbox.
A good fit for small teams that do not have an analyst building dashboards.
What you get out of it
The backlog trend is visible daily
Created, solved and open arrive together each morning, so you see within seconds whether the team is keeping up. If created beats solved three days in a row, the open count is about to climb.
Staffing decisions with numbers
A week of daily counts shows your peak days and your quiet ones. That supports a request for another agent, or a decision to move people between queues, with numbers behind it rather than a hunch.
No more opening a dashboard
The report arrives where you already look, so leaders who never open Zendesk Explore still get the figures that matter. The step of logging in, setting dates and reading a chart disappears.
Shared understanding across the team
Forwarding the same email to leadership and to the team means everyone talks about the same numbers. Arguments about whose spreadsheet is right fade, and the weekly meeting starts from shared facts.
Incidents are visible the next morning
A sudden jump in new tickets is usually the first sign of an outage or a bad release. Even if nobody noticed during the day, the next morning's count points straight at it.
A record for performance reviews
Saved emails show how created, solved and open counts moved over weeks. When someone asks whether the team improved after a process change or a hire, you answer with dated figures instead of opinions.
How it works
What happens, step by step
Every morning, ClickRuntime counts the Zendesk tickets created and solved yesterday.
It also counts the tickets open right now, split by priority.
You get one email with those numbers, and it keeps them so you can see the trend over time.
Before it runs live
- Connect Zendesk
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Run it at a different time, more or less often, or only on weekdays
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Zendesk steps into one automation
Under the hood
The code that runs this automation
from datetime import date, timedelta
from clickruntime import on_trigger, http, credentials, notify
ZD = "https://yourcompany.zendesk.com/api/v2"
AGENT_EMAIL = "you@yourcompany.com"
def zd(method, path, **kw):
r = http.request(method, f"{ZD}{path}", auth=(f"{AGENT_EMAIL}/token", credentials.secret("ZENDESK_API_TOKEN")), **kw)
r.raise_for_status()
return r.json() if r.content else None
def count(query):
return zd("GET", "/search/count.json", params={"query": query})["count"]
@on_trigger
def run(event):
y = (date.today() - timedelta(days=1)).isoformat()
created = count(f"type:ticket created:{y}")
solved = count(f"type:ticket solved:{y}")
by_priority = {p: count(f"type:ticket status<solved priority:{p}") for p in ("urgent", "high", "normal", "low")}
lines = [f"Created yesterday: {created}", f"Solved yesterday: {solved}", "Open now:"]
lines += [f" {p}: {n}" for p, n in by_priority.items()]
notify.email_me(f"Zendesk {y}: {created} in, {solved} solved", "\n".join(lines))
return {"created": created, "solved": solved}FAQ
Common questions
Are the counts in my time zone?
Does open include on-hold and pending tickets?
Can the report be split by group or brand?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Get a morning list of tickets open for over 3 days
Each morning you see which tickets have been waiting too long, grouped by assignee.
See how it worksSolve pending tickets after 2 weeks of silence
Tickets waiting on a customer who never replied are solved automatically, and you get the list.
See how it worksNudge customers on pending tickets
Customers who haven't replied in 3 days get one polite reminder on their ticket.
See how it worksKeep exploring
Set up “Get a daily Zendesk ticket report” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.