Skip to content
The Workflow Library
Get the full library

Ticket reopen counter property (recidivism tracking for reporting)

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Ticket4 stepsUpdated for HubSpot seat pricing
OutcomeEvery ticket carries an accurate count of how many times it has been reopened, giving the service team a reporting property to spot recurring-issue tickets instead of reading the timeline by hand.
Workflow mapreporting-alerts-005
Ticket stage changes Closed to Open leads to Custom code: read reopen_count, add 1, write back. Custom code: read reopen_count, add 1, write back leads to reopen_count >= 3?. reopen_count >= 3? leads to yes: Create review task for ticket owner; no: Exit. yes no Ticket stage changes Closed to Open Custom code: read reopen_count, add 1, write back reopen_count >= 3? Create review task for ticket owner Exit
Ticket stage changes Closed to Open leads to Custom code: read reopen_count, add 1, write back. Custom code: read reopen_count, add 1, write back leads to reopen_count >= 3?. reopen_count >= 3? leads to yes: Create review task for ticket owner; no: Exit. yes no Ticket stage changes Closed to Open Custom code: read reopen_count, add 1, write back reopen_count >= 3? Create review task for ticket owner Exit

When to use it, when not to

Use it

  • Use it when reporting needs a genuine count, not just a yes/no, of reopen events per ticket, for example to segment "reopened 3+ times" tickets for root-cause review.
  • Use it as an input to a broader recidivism report or dashboard grouped by product area or ticket category.
Read more on when to use itShow less

Skip it

  • Do not use it if a simple yes/no "has this ticket ever been reopened" flag is enough. That version is buildable natively with no custom code; see Variants.
  • Do not confuse this with SLA or escalation handling of reopened tickets. What happens operationally when a ticket reopens belongs to the tickets-sla category. This fiche only produces the reporting number.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 4 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 4 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Reporting and alerts spec

Not the workflow you needed?

More in Reporting and alerts

50 specs in this section

See all 50 This category, 39 EUR
FreeSlack alert: deal marked Closed Won (revenue milestone notification)Deal4 steps Anomaly alert: email bounce rate spike after a sendContact3 steps Stage-entry timestamp properties for pipeline velocity reportingDeal5 steps Timeline note logging on critical property change (audit visibility)Deal2 steps

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library