# Reminder workflow **URL:** \ **Category:** Tips, Tricks & Best Practices\ **Tags:** professional\ **Created:** [October 14, 2022, 9:14pm UTC](https://community.hubspot.com/t/reminder-workflow/67199 "2022-10-14T21:14:17Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\ **Post date:** [October 15, 2022, 5:10am UTC](https://community.hubspot.com/t/reminder-workflow/67199/2 "2022-10-15T05:10:59Z")
Hi @Kirekchiev, Thanks for sharing so much detail! Regarding your first workflow: It looks like this workflow contains both the ‘request received’ and ‘your ticket is about to be closed due to inactivity’ email. However, I wouldn’t set it up like that. The first email (if it is purely a ‘request received’ email) should be sent immediately, regardless of the _Last activity date_, that you’re checking in the branch before. The second email should be handled by another workflow. Here you don’t even have to check for the Last activity date. You can enroll tickets that are in ‘Waiting on customer’ and then delay for 3 days. If they don’t change the deal ticket, they would receive the ‘your ticket is about to be closed due to inactivity’. If their ticket status changes in those 3 days, you can remove them via _Settings_ \> _Unenrollment and suppression_. Make sure to re-enroll tickets when _Ticket status_ ‘Waiting on customer’ so that this 3 day period is checked again and again. Personally, I think that 3 days is too short. I don’t know the characteristics of the support you’re offering but a bank holiday + weekend alone would push a ticket into this automation. I’d lean more towards 7 days. Regarding your second workflow: If you’re making use of _Settings_ \> _Unenrollment and suppression_ to unenroll tickets when they change the _Ticket status_, then this would be fine. In my opinion, I think it’s a pretty aggressive level of escalation when a ticket is unanswered. Again, I don’t know what types of requests you’re handling and how time-sensitive they usually are but there are other tools to track could be leveraged here, e.g. reports and [SLA features](https://knowledge.hubspot.com/inbox/set-slas-in-the-inbox). Hope this helps! --- _[View the full topic](https://community.hubspot.com/t/reminder-workflow/67199)._