History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: CHD-1998
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Fixed
Assignee: Unassigned
Reporter: Jonathan Heptinstall
Votes: 0
Watchers: 0
Operations

Clone this issue
If you were logged in you would be able to see more operations.
Cerberus Helpdesk

request for an automated EMAIL to be produced after a certain period of time

Created: 05/Aug/10 01:03 AM   Updated: 13/Sep/11 09:57 PM
Fix Version/s: We Have the Technology

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: cerberus online, outlook 2007


 Description   
I have a request and im not sure if it is possible within Cerberus.
I want to log a ticket and want Cerberus to notify me 2 days later about that particular ticket.

Ill give you the scenario:

We get a request to deliver a LOAN headset to a client on the 1st of August 2010
On the 3rd of August i would like a mail from Cerberus to indicate that the headset is to be collected.


Is this possible with the current Cerberus and if it is how would i get that implemented.


 All   Comments   Work Log   Change History      Sort Order:
Comment by Jeff Standen [WGM] [16/Aug/10 06:10 PM]
Tasks are a better way to do this.

Comment by Jeff Standen [WGM] [07/Apr/11 01:35 AM]
This would be very interesting if merged with the Virtual Attendant functionality in 5.4+. You'd be able to link an object to an attendant (using context links), which would allow it to oversee messages (SLA enforcement, etc)

Comment by Damien R [05/May/11 03:45 AM]
No idea about the new Virtual Attendant functionality noted, but just wanted to mention that this is something we've often had various use cases for. To a large extent we get around it just by setting tickets as 'waiting for reply' and reopen on the desired time, but it doesn't always suit.

Sometimes we need to leave ourselves a note to do something at some future time, and have a reminder to do it at that point. (obviously all relating to a ticket). Yes tasks probably fit that need better, but if the tools are already there do handle that (or even will be in 5.4 / 5.5) we probably need a little more by way of guidance to show us the possibilities :)

Comment by Jeff Standen [WGM] [13/Sep/11 09:57 PM]