# Mandatory Ticket Categorization & Status Update on First Reply **URL:** \ **Category:** Tickets & Conversations\ **Tags:** professional\ **Created:** [March 12, 2025, 4:20pm UTC](https://community.hubspot.com/t/mandatory-ticket-categorization-status-update-on-first-reply/127833 "2025-03-12T16:20:26Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![AChapoux](https://avatars.discourse-cdn.com/v4/letter/a/b5e925/32.png) [@AChapoux](https://community.hubspot.com/u/AChapoux)\ **Post date:** [March 12, 2025, 4:20pm UTC](https://community.hubspot.com/t/mandatory-ticket-categorization-status-update-on-first-reply/127833/1 "2025-03-12T16:20:26Z")
Hello HubSpot Community, I’m used to support and conversation tools that require agents to categorize a ticket and update its status upon sending the first reply to the customer. This ensures that tickets are properly classified and don’t remain unupdated or stuck in an incorrect status. In HubSpot, I’ve noticed that agents can reply to conversations without being required to update the associated ticket, which sometimes leads to tickets being left unclassified or in the wrong status. This creates issues with tracking and reporting. Is there a way to make ticket categorization and status updates mandatory upon the first agent response in HubSpot? If not, are there any workarounds to enforce this behavior? (I don’t really want to use tasks to remind agents). Thanks in advance for your help! ---
**Author:** ![PamCotton](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/pamcotton/32/47916_2.png) [@PamCotton](https://community.hubspot.com/u/PamCotton)\ **Post date:** [March 12, 2025, 10:05pm UTC](https://community.hubspot.com/t/mandatory-ticket-categorization-status-update-on-first-reply/127833/2 "2025-03-12T22:05:46Z")
Hey @AChapoux, thank you for posting in our Community! In HubSpot, there isn’t a built-in way to make ticket categorization and status updates mandatory on the first agent response. However, you can enforce this behavior by setting up automated workflows. For example, you can create a workflow that triggers when a ticket is replied to for the first time and sends a reminder to update the ticket status or categorize it properly. Another option is using custom properties for categorization, which can help agents quickly classify tickets during the conversation. To our top experts, @Brenner and @RSchweighart do you have any other recommendations for @AChapoux matter? Thank you, Pam ---
**Author:** ![AChapoux](https://avatars.discourse-cdn.com/v4/letter/a/b5e925/32.png) [@AChapoux](https://community.hubspot.com/u/AChapoux)\ **Post date:** [March 13, 2025, 5:13pm UTC](https://community.hubspot.com/t/mandatory-ticket-categorization-status-update-on-first-reply/127833/3 "2025-03-13T17:13:35Z")
Thanks for your reply Pam! We already use custom properties for categorization, and our main goal is to ensure those properties are updated when the first reply is sent. Since they already have assigned tasks and reminders for other purposes, adding more reminders might be excessive. ---
**Author:** ![tverdokhlib1](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tverdokhlib1/32/58857_2.png) [@tverdokhlib1](https://community.hubspot.com/u/tverdokhlib1)\ **Post date:** [March 13, 2025, 12:44pm UTC](https://community.hubspot.com/t/mandatory-ticket-categorization-status-update-on-first-reply/127833/4 "2025-03-13T12:44:31Z")
@AChapoux, have you turned on this Ticket Automation (Settings - OBjects - Tickets - Pipelines - Automate)? Thus, the tickets will go to another status when an agent replies first. ![Знімок екрана 2025-03-13 о 14.40.49.jpg](https://d2qpr2jzcazej7.cloudfront.net/original/3X/6/b/6b9c02dd468cdb11f3dbf6f14e74dc18ec73b280.jpeg) ---
**Author:** ![AChapoux](https://avatars.discourse-cdn.com/v4/letter/a/b5e925/32.png) [@AChapoux](https://community.hubspot.com/u/AChapoux)\ **Post date:** [March 13, 2025, 5:10pm UTC](https://community.hubspot.com/t/mandatory-ticket-categorization-status-update-on-first-reply/127833/5 "2025-03-13T17:10:21Z")
Thanks Anton. We have 3 status when we reply so we can’t really use this automation I believe. It’s either : Solution sent Waiting for precision (waiting on contact) Waiting for Internal team (waiting on us) ---
**Author:** ![RSchweighart](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rschweighart/32/28924_2.png) [@RSchweighart](https://community.hubspot.com/u/RSchweighart)\ **Post date:** [March 13, 2025, 8:57pm UTC](https://community.hubspot.com/t/mandatory-ticket-categorization-status-update-on-first-reply/127833/6 "2025-03-13T20:57:48Z")
Hi @AChapoux, You can make properties required upon moving of statuses. ![RSchweighart_0-1741899051386.jpg](https://d2qpr2jzcazej7.cloudfront.net/original/2X/4/4268327ee44d1f155742e2f6a3d6cc7df093d1b5.jpeg) ![RSchweighart_1-1741899150056.jpg](https://d2qpr2jzcazej7.cloudfront.net/original/3X/0/8/08f42d5c897919b585d6647e01743618cad6bbaa.jpeg) It won’t prompt upon reply, but it will prompt when a user updates the ticket status to the one with conditional status properties set up. ![GIF Recording 2025-03-13 at 1.55.38 PM.gif](https://d2qpr2jzcazej7.cloudfront.net/original/3X/5/e/5e2cee5a95449c9699ef3c56509e94bcf78540ee.gif) I hope this is the solution. All the Best, _ **Ryan Schweighart** _ Whole Hart Impact, LLC [whimpact.co](https://www.whimpact.co?utm_source=hubspot&utm_medium=community_post) _I help organizations use HubSpot and Zapier._ ---
**Author:** ![Brenner](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/brenner/32/13741_2.png) [@Brenner](https://community.hubspot.com/u/Brenner)\ **Post date:** [March 19, 2025, 12:38pm UTC](https://community.hubspot.com/t/mandatory-ticket-categorization-status-update-on-first-reply/127833/7 "2025-03-19T12:38:05Z")
Hey folks! @AChapoux amazing question. All replies here are perfect to solve your necessities. But, I’d like to give another one tips: you can set an automation to find all tickets that have first reply is “know” and don’t have your properties filled out. After that, you have 2 ways: \> create a stage to complete all information to categorize your tickets; \> apply these conditions in a report, to track with your team each ticket that isn’t completed.