The Workflow Library

Library / Tickets and SLA / tickets-sla-019

Reopened ticket re-routes to original owner if still active, else pool

Tickets and SLATicketService Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A reopened ticket stays with the rep who already knows its history, unless that rep is no longer on the team, in which case it drops back into normal rotation instead of sitting assigned to someone who cannot act on it.

Workflow map Enrollment, branches and actions at a glance tickets-sla-019
flowchart TD
    A[Ticket reopens] --> B{Owner known and still on queue's team?}
    B -->|yes| C[Keep owner, notify them]
    B -->|no| D{Ticket queue value?}
    D -->|billing| E[Rotate to Billing pool]
    D -->|technical| F[Rotate to Technical pool]
    D -->|general| G[Rotate to General pool]
    E --> H[Notify new owner, reassigned]
    F --> H
    G --> H
    C --> I[Set routed date]
    H --> I
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it alongside tickets-sla-007 (auto-reopen on reply), as the piece that decides who actually owns the reopened conversation.
  • UseUse it whenever reps leave the team or move between queues, since a reopened ticket built to auto-assign back to "the same owner" quietly fails the day that owner is gone.
  • SkipDo not use it if your team is small enough that reassigning a reopened ticket is always a manual, deliberate choice; the branch logic here adds complexity that a two-person team does not need.
  • SkipDo not use it as a substitute for tickets-sla-007's reopen detection itself; this fiche assumes the ticket has already reopened and reacts to that.
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.4 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.8 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 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 tickets and sla 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.