# Creating tasks automatically by ticket property

**URL:** <https://community.hubspot.com/t/creating-tasks-automatically-by-ticket-property/14225>\
**Category:** Tickets & Conversations\
**Tags:** help-desk\
**Created:** [May 3, 2019, 9:55pm UTC](https://community.hubspot.com/t/creating-tasks-automatically-by-ticket-property/14225 "2019-05-03T21:55:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![JDobbin](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jdobbin/32/5125_2.png) [@JDobbin](https://community.hubspot.com/u/JDobbin)\
**Post date:** [May 3, 2019, 9:55pm UTC](https://community.hubspot.com/t/creating-tasks-automatically-by-ticket-property/14225/1 "2019-05-03T21:55:18Z")

</div>

Hey guys, I’m implementing Services Pro for my Customer Service team, and they often need to get back to that ticket/issu a couple days later to check if the suggested plan took effect or not. So, when moving the ticket to a stage they are required to input a date:

 ![ticket1.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/a/7/a7f849a856b438665a339aaad02605754a3cde68.png)

So, ideally this would create a task for the ticket owner to get back here X days from that property (Plan of action end date). Tried to mess up with the workflows a little bit but couldn’t get something like this.

---

<div class="post-metadata">

**Author:** ![Bryantworks](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bryantworks/32/94963_2.png) [@Bryantworks](https://community.hubspot.com/u/Bryantworks)\
**Post date:** [May 6, 2019, 1:40pm UTC](https://community.hubspot.com/t/creating-tasks-automatically-by-ticket-property/14225/2 "2019-05-06T13:40:37Z")

</div>

Hey @JDobbin

Could you do something like the following? This doesn’t swing off of that date you mentioned, but if you are using a status or stage to track these tickets, you could trigger the workflow based on that status/stage.

 ![Unnamed Ticket workflow _ HubSpot - Google Chrome 2019-05-06 09.39.34.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/1/2/125c470b5f24ba211365a2dbb62a161c24fde85e.png)

---

<div class="post-metadata">

**Author:** ![JDobbin](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jdobbin/32/5125_2.png) [@JDobbin](https://community.hubspot.com/u/JDobbin)\
**Post date:** [May 6, 2019, 1:55pm UTC](https://community.hubspot.com/t/creating-tasks-automatically-by-ticket-property/14225/3 "2019-05-06T13:55:50Z")

</div>

So, you gave a great insight! What I did and believe will resolve this was the following:

 ![ticket1.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/5/a/5a511355b01ef01cef0f89b525032509c3a3b252.png)

 ![ticket2.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/2/7/27fd25e9bd27d6578bd753329334f95154fde6a4.png)

So, here we have basically 2 types of “recovery plan” if a customer is falling behind: 30 and 90 days. What I’m trying to say to HubSpot is: When a plan is bigger than 60 days, then alert the CSM on day 45. And when is lower than that, in 20 days it will alert the CSM (ticket owner).

---

<div class="post-metadata">

**Author:** ![Bryantworks](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bryantworks/32/94963_2.png) [@Bryantworks](https://community.hubspot.com/u/Bryantworks)\
**Post date:** [May 6, 2019, 2:00pm UTC](https://community.hubspot.com/t/creating-tasks-automatically-by-ticket-property/14225/4 "2019-05-06T14:00:54Z")

</div>

This looks good, glad you were able to resolve!