Good morning,
I am new here and hope you can help me.
We get a lot of tickets where we have to put users out of service. This happens on the day itself, so sometimes it is a month later, but sometimes it is only after 3 months. I now put the status on hold, but it does pollute the overview.
Is there a possibility that the tickets will be closed and then automatically reopened on a specific date?
Hope to hear from you, thanks in advance.
Greetings Maikel
+2
I believe you can do something like that through Expression Builder. I’m looking to do something similar to put tickets into a custom status, and then re-open x days prior to the date selected in the ticket. I can help when I figure it out myself. :)
I believe you can do something like that through Expression Builder. I’m looking to do something similar to put tickets into a custom status, and then re-open x days prior to the date selected in the ticket. I can help when I figure it out myself. :)
Thanks, let me know
For the cluttering the overview issue, couldn’t that be solved by adjusting the filter to not show tickets which are on hold? Or if that status is also used for other tickets maybe create a custom status for these kind of tickets and then exclude that status from your filter/s.
I think it would be good to get a few more details around your plans to see how they could be achieved. Like:
If it is logging via the portal, you could use custom fields like a date picker, to get dates, which gives some nice (and I think new unless I have never seen them before) options in the workflow automator. If it is via email, you likely will have to use the expression node to read information from the email and then use that in the workflows.
There is also is a timer node in the workflowautomator so I guess a very simple workflow could be:
Ticket is raised → Category/Service Item is, idk, “Leaver” → update status to “on hold” → timer node “wait 1 month” → update status to “in progress”
Obviously, this disregards your statement of “it could be 1 month or 3” but maybe it’s a starting point if it’s always at least one month?
Hi, thank you for the reply. The tickets come in via email. The termination date is stated in the ticket, see attachment. I have no experience with the expression node yet
I wish I could tell you I was amazing with it but that is not (yet) true. I mostly just follow the Freshworks videos to a T and hope that it works.
Luckily for you and me both, there is one already that might do just what you need:
I think you can almost follow this step for step to get the date from your email.
We’re also very keen for this feature or the upcoming timer node with a specific date.
We often have tickets that may need re-opening in X Months. For example when a user is granted a temporary upgrade on their mobile plan to include global roaming to travel, we need to ensure we remove it later.
There is many more examples we use follow ups for.
I wish I could tell you I was amazing with it but that is not (yet) true. I mostly just follow the Freshworks videos to a T and hope that it works.
Luckily for you and me both, there is one already that might do just what you need:
I think you can almost follow this step for step to get the date from your email.
This is for me very comlex to build :) Hope there is a simpler solution comming
We also want such a feature integrated into freshservice itself. For now I achieve this with a small python script using the api in a daily cronjob. It looks if the date in a custom date field matches today and changes the status back to open.
But this seems like a feature that should be mandatory for every ticket system (in my eyes at least) and shouldn’t need hacky workarounds (and external resources on our end)
+10
Hi
Have you looked at Supervisor automation? It runs hourly so I bet you could put a condition where it compares the termination date to today’s date.
(1) Create an automator to extract the date off the subject line and populate it into a ticket field and set the ticket status = closed, you could even use a tag like “needs to reopen”
(2) Create a supervisor rule where:
Please see my other post for specifics on writing an Automator workflow for extracting content from email to populate ticket properties
Added a small edit to keep the Supervisor rule from running after you close the ticket for good.
HTH
Bryn @ CYDEF.ca
+2
(2) Create a supervisor rule where:
I was under the impression that tags, custom date fields, or ticket date fields in general, are not accessible in Supervisor Rule conditions? I don’t see a way to set a condition using any of those fields. If I am wrong, someone please give me some guidance on how I can use them.
As an SEO executive, you would like to obtain backlinks from the "Automatic Reopening Tickets on Specific Date" forum and ensure that the keyword "Pembio" is used in a relevant manner.
To accomplish this, you could search for relevant discussion threads or topics on the forum that relate to the keyword "Pembio" or are related to your website's niche or industry. You could then engage in those discussions and provide valuable insights or information while naturally including a link to your website or webpage.
It's important to keep in mind that the key to successful link building is creating high-quality content that is relevant and valuable to your target audience. By participating in online communities and providing value to users, you can build relationships and establish your website as a valuable resource in your industry, which can ultimately lead to more backlinks and increased visibility in search engine results pages.
+1
This solution may not work for everyone, but what I do is
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
