Skip to content
The Workflow Library
Get the full library

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

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: Service Hub Professional.

Company2 stepsUpdated for HubSpot seat pricing
OutcomeEvery 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 mapreporting-alerts-041
Associated ticket's last-modified date changes, or association changes leads to Rollup recalculates automatically. Rollup recalculates automatically leads to last_support_interaction_date reflects most recent ticket activity. Associated ticket's last-modified date changes, or association changes Rollup recalculates automatically last_support_interaction_date reflects most recent ticket activity
Associated ticket's last-modified date changes, or association changes leads to Rollup recalculates automatically. Rollup recalculates automatically leads to last_support_interaction_date reflects most recent ticket activity. Associated ticket's last-modified date changes, or association changes Rollup recalculates automatically last_support_interaction_date reflects most recent ticket activity

When to use it, when not to

Use it

  • Use it as a quick recency signal for account health, combined with a ticket volume counter such as reporting-alerts-040.
  • Use 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.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 2 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 · 2 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 · 2 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

The properties JSON creates the fields in one call. The workflow JSON documents the build.

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 Counter property: support tickets opened by a company (lifetime volume)Company2 steps Property: days since last marketing email open (engagement recency helper)Contact2 steps Stage-entry timestamp properties for pipeline velocity reportingDeal5 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