The Workflow Library

Library / Reporting and alerts / reporting-alerts-034

Weekly digest: ticket volume by pipeline/queue to service leadership

Reporting and alertsTicketService Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. Once a week, service leadership gets an email showing how many tickets were created in the past week, broken down by pipeline (queue), so volume trends are visible without opening the Tickets tool.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-034
flowchart TD
    A[Weekly schedule: Monday 08:00] --> B[Report renders: ticket count by pipeline, last 7 days]
    B --> C[Sorted by count, highest first]
    C --> D[Email sent to service leadership distribution list]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it on a portal running more than one ticket pipeline (for example a general support queue and a separate enterprise or escalations queue), where leadership wants a volume comparison across them.
  • UseUse it as a lightweight weekly check-in that complements, not replaces, a live dashboard for day-to-day queue management.
  • SkipDo not use it on a single-pipeline portal. A single number in a weekly email adds less value than a live dashboard tile leadership can check anytime.
  • SkipDo not use it as an SLA or response-time report. This fiche counts ticket volume only; pair it with reporting-alerts-016 or a dedicated SLA report for response and resolution timing.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.2 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the reporting and alerts pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.