Skip to content
  • There are no suggestions because the search field is empty.

Ticket | Auto Reopen Inactive Tickets (3d / 7d)

Use the Auto Reopen Inactive Tickets (3d / 7d workflow

Goal

Prevent tickets from remaining indefinitely in waiting statuses by:

  • Reopening after 3 days of inactivity

  • Reopening again after 7 days if still waiting

  • Tracking how many times the system reopens a ticket

  • Providing visibility into recently or repeatedly reopened cases

This replaces multiple legacy Freshdesk time-based automations with one HubSpot-native workflow.

Waiting statuses covered

The workflow applies when the ticket status is:

  • Pending

  • Waiting on customer

  • Waiting on third party

  • On hold

All statuses are handled in a single workflow using delays and re-checks (no separate per-status timers).

Properties

Ticket Reopen Count

  • Type: Number

  • Purpose: Tracks how many times the system has automatically reopened the ticket

  • Can be used for reporting, views, and escalation logic

Last System Ticket Reopen Date

  • Type: Date & time

  • Stores the timestamp of the most recent automatic reopen

  • Used for triage views, reporting, and troubleshooting

  • Allows the team to quickly identify tickets the system reopened vs. manually reopened

Reopened Stalled/Inactive Ticket

  • Type: Single checkbox

  • Set to Yes when this workflow automatically reopens the ticket

  • Used as a flag on the ticket record to show the above two properties in the side bar

  • Only reflects reopens from this workflow (not all system or manual reopens)

Enrollment

Trigger

Ticket status is any of:

  • Pending

  • Waiting on customer

  • Waiting on third party

  • On hold

Re-enrollment

Enabled on:

  • Status

Rationale:

  • When a ticket moves back into a waiting status, the timer restarts automatically

Workflow configuration

3-day checkpoint

  1. Delay 3 days

  2. Branch: Status is still any waiting status

If YES:

  • Set Status → Open

  • Format data → Ticket Reopen Count + 1

  • Edit record → Ticket Reopen Count = outcome of Format data

  • Edit record → Last System Ticket Reopen Date = use date action completes

If NO:

  • End

7-day checkpoint

(continues from the 3-day YES path)

  1. Delay 4 days (total = 7 days)

  2. Branch: Status is still any waiting status

If YES:

  • Set Status → Open

  • Format data → Ticket Reopen Count + 1

  • Edit record → Ticket Reopen Count = outcome of Format data

  • Edit record → Last System Ticket Reopen Date = use date action completes

If NO:

  • End

Record visibility

To make workflow-driven reopens immediately visible to team leads, these properties are displayed together on the ticket record:

  • Ticket Reopen Count

  • Last System Ticket Reopen Date

These are shown in a dedicated sidebar card titled “Inactive Ticket Reopens” near the top of the ticket that only shows if the ticket has a yes value in "Reopened Stalled/Inactive Ticket"

This provides:

  • At-a-glance identification of tickets reopened by inactivity logic

  • A quick severity indicator (reopen count)

  • Timestamp of the most recent automatic reopen

This card only reflects this workflow’s activity and does not represent all system or manual reopens.

Why this design

Single workflow

Replaces multiple Freshdesk automations with one centralized process.

Uses:

  • Delay

  • Branch

  • Format data

  • Edit record

No custom code required.

Deterministic timing

Delays are based on time in workflow, not “hours since” fields.

Clean reporting

Numeric counter and timestamp enable filtering, dashboards, and escalations.

Future enhancements (optional)

The Last System Ticket Reopen Date property provides visibility into when the system — not an agent — reopened a ticket.

This is primarily used for:

  • Daily triage views (tickets reopened overnight)

  • Identifying recently aged or stalled conversations

  • Troubleshooting “why did this ticket reopen?”

  • Reporting on reopen trends over time

Without this property, system-driven reopen events are indistinguishable from manual status changes.

Possible additions:

  • Escalate when Ticket Reopen Count ≥ 2

  • SLA or aging analysis using Last System Ticket Reopen Date

  • Dashboard reporting on reopen trends