When end users send multiple short chat messages in quick succession, each message triggers a separate "customer updated" notification email to ticket resources and the ticket owner. This results in notification spam for MSP technicians. Partners are requesting a native Thread setting to batch or throttle these chat-triggered notifications -- for example, grouping messages sent within a short time window into a single notification, or adding a cooldown period between notification triggers for chat-originated updates. This would bring chat notification behavior more in line with the experience of email-based client updates.