The Workflow Library

Library / Reporting and alerts / reporting-alerts-041

Property: date of last support interaction per company (recency helper)

Reporting and alertsCompanyService Hub ProfessionalSimple~20 min to buildFull spec

Outcome. Every company record shows the date of its most recent ticket activity, so a rep or CS manager can tell how recently an account engaged support without opening the tickets list and sorting by date.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-041
flowchart TD
    A[Associated ticket's last-modified date changes, or association changes] --> B[Rollup recalculates automatically]
    B --> C[last_support_interaction_date reflects most recent ticket activity]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it as a quick recency signal for account health, combined with a ticket volume counter such as reporting-alerts-040.
  • UseUse it to spot accounts that have gone quiet on support, which can mean either a healthy, low-friction account or a disengaged one, worth a manual check either way.
  • SkipDo not use it if the portal's ticket-to-company association is inconsistent. A recency property built on incomplete associations is misleading, showing "no recent interaction" simply because tickets were never linked.
  • SkipDo not treat "recent" alone as a health signal without context; a company with one urgent open ticket yesterday is not automatically healthier than one with no tickets in six months.
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.2 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.