We currently face a limitation in tracking ticket ratings timestamps. While conversation ratings are provided through webhook events, ticket ratings are not, forcing us to use the ticket closing date as a fallback. This creates inaccurate data when tickets are rated after their closure. This appears to be an oversight as this functionality is already available for conversations

This limitation affects our ability to:

• Accurately track CSAT metrics over time

• Report precise customer satisfaction data

• Maintain data integrity when tickets are reopened

• Provide reliable analytics to our customer service teams

We propose adding new webhook events for ticket ratings, similar to the existing conversation rating events. These events should include the same information as the conversation_rating_event. This also means we need a ticket_rating_updated_event when a ticket rating is modified.

This would enable:

1. Accurate CSAT reporting by actual rating date
2. Better tracking of customer feedback patterns
3. Improved analytics for service quality metrics
4. More reliable historical data for customer satisfaction trends

Have you any idea if it’s possible to add ?