Partners need the ability to schedule resources for a ticket that specifically targets the existing Assigned Resources, vs only the Ticket Owner. The Ticket Owner is fairly irrelevant. The ticket owner is often not the person responsible for moving the ticket forward -- the assigned resource is. Assigned resources can also change over the life of a ticket due to teamwork and handoffs, so the system needs to respect the current assigned resource(s) at the time the reminder fires, not a static owner. The current behavior ties to the ticket owner, which does not reflect real-world responsibility in many MSP workflows.

EX: The active assigned resource(s) are the target of scheduling the follow-up date/time on a Stale Ticket.

If Thread is already pulling and displaying the assigned resource in the Inbox UI, the data is clearly accessible. The gap is that other parts of Thread (like Super Magic, Reminder Agent, and Flows) don't leverage that same data point for targeting or automation.