Currently, ticket status automation that reactivates tickets upon receiving new messages only works for Chat-sourced tickets. In many workflows, tickets are created via email but follow-up messages can come through Microsoft Teams, including from additional contacts. These Teams replies are correctly logged in the ticket but do not trigger status changes, leaving tickets in Planned or Waiting states and risking missed updates or SLA breaches. The requested feature is to extend the existing status update automation to all incoming message sources—such as email, Teams, and others—regardless of how the ticket was originally created. This would ensure that any new contact reply reactivates the ticket and updates its status appropriately for the service desk.