Outcome. An account that suddenly opens several support tickets in a short window gets flagged to the account owner as at-risk, instead of the volume only showing up later in a monthly report.
Workflow map
Enrollment, branches and actions at a glance
renewal-expansion-013
flowchart TD
A[Ticket created, associated company] --> B[Increment Open Tickets Last 30 Days]
C[Ticket closed] --> D[Decrement Open Tickets Last 30 Days]
B --> E{Count >= 3 and not yet flagged?}
D --> E
E -->|yes| F[Set Ticket Spike Flagged = true]
F --> G[Create task for owner]
G --> H[Notify owner and CSM]
E -->|no| I[No action]
When to use it, when not to
- UseUse it once ticket volume per account is visible as a running number on the company record, not just as individual ticket records with no rollup.
- UseUse it as one input into a broader risk picture; pair it with renewal-expansion-004's churn risk score if usage and NPS data are also available.
- SkipDo not use it for accounts where a high ticket count is expected and healthy, such as an onboarding phase with planned check-ins; exclude those with the suppression list below.
- SkipDo not use it if ticket volume genuinely cannot be tracked per company in this portal (tickets not consistently associated to companies); fix that association gap first.
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.3 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 renewal and expansion 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.
