Outcome. Every 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.
flowchart TD
A[Associated ticket's last-modified date changes, or association changes] --> B[Rollup recalculates automatically]
B --> C[last_support_interaction_date reflects most recent ticket activity]

When to use it, when not to
- UseUse it as a quick recency signal for account health, combined with a ticket volume counter such as reporting-alerts-040.
- UseUse 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.
- SkipDo 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.
- SkipDo 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.
or the reporting and alerts 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.





