Thanks for the feedback . Please check some of the below points works for you
Thanks for the reply.
1. I wanted to have the ability to mark ticket status as "Pending" with timer which automaticlly change the ticket status back to "Open"
it would be usful in case the requester asking to delay handling (for example: for 2 days).
2. I would like to have an option to force kind of "workflow" into the ticket.
for example, we decided (business wise) to take specific workflow action in case of priority ticket being raised by consumer.
so I want my agents to be able to apply (manually) a workflow to remind them the staging.
i assume it would work well with tasks, like: notification call to product manager ; notification mail to CEO ; escalation to system on call engineer. etc..
as far as I understand that can only been done using scenario automation. and that actually its point....
configure case scenario and when agent choosing it, apply multiple action on the ticket to tune and prepare it (logical and methodological) accourdingly.
generally speaking, i think all four of them: "Dispatch'r", "Supervisor", "Observer", "Scenario Automations",
should gain the ability to do most actions as possible. that will give the edge of costumization accurding to the different requirements out there...
Guys, sorry for bringing this old one up but what Doron described is still very much a desired feature. Adding task is a rather poor substitute for it.
Ideally the feature should be connected to 'Scenarios' - which would allow you to do all kind of things on a schedule.
Doron, were you able to work around this issue? With a FreshPlug maybe?
Obviously it is possible to just invoke Freshservice API and manage the schedule itself in your own custom service, but i really think this should be one of the core features.
Just wanted to chime in on the "on hold with schedule (specific date and time to un-onhold the ticket)" That would be a great feature.