The Workflow Library

Library / Reporting and alerts / reporting-alerts-008

Weekly Slack digest: ticket volume and CSAT average to service channel

Reporting and alertsTicketOperations Hub ProfessionalAdvanced~60 min to buildFull spec

Outcome. Once a week, the service channel gets one Slack message showing how many tickets were created, how many were closed, and the average CSAT score for the week, instead of pulling those numbers by hand from separate reports.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-008
flowchart TD
    A[Scheduled trigger: Monday 08:00] --> B[Custom code: count tickets created last 7 days]
    A --> C[Custom code: count tickets closed last 7 days]
    A --> D[Custom code: fetch CSAT feedback submissions last 7 days]
    D --> E{Any CSAT responses found?}
    E -->|yes| F[Compute average CSAT score]
    E -->|no| G[Note: no CSAT responses this week]
    B --> H[Format combined message]
    C --> H
    F --> H
    G --> H
    H --> I[POST message to Slack webhook]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when a service team wants a single weekly pulse-check number in Slack, combining volume and satisfaction in one glance.
  • UseUse it as a lightweight companion to a full service dashboard, not a replacement for one.
  • SkipDo not use it if the team already has a scheduled dashboard email covering the same metrics and does not need it in Slack specifically. See Variants for the native, no-code alternative.
  • SkipDo not use it if CSAT surveys are not enabled on the portal. Without survey data, this reduces to a ticket-volume-only digest, which is simpler to build with fewer moving parts; consider whether the added complexity here is worth it in that case.
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.5 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.1 numbered action
Known pitfallsTraps seen in production, each with what breaks and what to do instead.6 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, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
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.