All templates

Daily Support Queue Digest

Every morning, WebRun opens your Zendesk queue, counts open and breached tickets by team and priority, identifies the five oldest unresolved tickets, and posts a structured digest to your #support Slack channel before the first agent logs on.

Runs on WebRun · Strict Lockdown policy
Every day at 7:30 AM WebRunorchestrates each step
1 Zendesk scan the open queue
2 Slack post the morning digest
In short

How can I send my support team a daily queue digest automatically?

Every morning, WebRun opens your Zendesk queue, counts open and breached tickets by team and priority, identifies the five oldest unresolved tickets, and posts a structured digest to your Slack #support channel — so every agent starts the day knowing exactly where to focus.

  • Team starts every day with a clear picture of open and breached tickets
  • Oldest unresolved tickets surfaced before they become complaints
  • No manual report building — digest lands in Slack before anyone logs on

Built for support team leads · customer service managers · SaaS companies · e-commerce support teams

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order — in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.zendesk.com in a real browser with your saved login — no setup, no API keys.

  2. 1
    Zendesk — scan the open queue
    zendesk.com
    WebRun in Zendesk: scan the open queue
    WebRun opens Zendesk to scan the open queue.
    • Open the Views section and load all open tickets grouped by priority
    • Count tickets by status: Open, Pending, On-hold, and SLA Breached
    • Pull the five oldest open tickets with their subject, customer, and days open
    • Note any tickets that breached an SLA overnight

    Done when Queue counts, oldest tickets, and SLA breaches are all captured.

  3. 2
    Slack — post the morning digest
    slack.com
    WebRun in Slack: post the morning digest
    WebRun opens Slack to post the morning digest.
    • Format a digest: total open count, breakdown by priority, and a list of the five oldest tickets
    • Highlight SLA-breached tickets in bold so the team can act first
    • Post to #support with a direct link to the Zendesk queue view

    Done when The digest is posted in Slack before the team's start time.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.zendesk.com
ScheduleRuns automatically on this cadence
Every day at 7:30 AM
DeliveryHow each run's result reaches you
Queue digest · Slack
OutputWhat each run produces — A structured daily digest: open ticket counts by priority, top 5 oldest tickets, and overnight SLA breaches.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment — WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Can I change the digest time?

Yes — set whatever start-of-day time suits your team in the plan and WebRun will deliver the digest before they log on.

What if the queue is empty?

It posts a short 'All clear' message so the team knows WebRun ran and there is nothing urgent to act on.

Can we get a digest for each team separately?

Yes — configure a view per team in Zendesk and WebRun can send each team their own digest to their own Slack channel.

Put this on autopilot.

Turn it on in minutes — or have our team set it up for you.