
Hello Everyone, and the next mind-boggling question: Is anyone implementing Service Level Agreements in OTRS? I was wondering how this can be implemented to ensure that our ticket do not exceed our current SLA's. I appreciate any and all comments and thank you all again for a wonderful source of knowledge here by this mailer. I hope that I can someday be helpful here as well and not always be the "leech". Vielen Dank, Shawn Beasley Support - IT Cargo Future Communications GmbH Geb. 1335 55483 Hahn-Flughafen Tel. +49 6543 983 113 Fax +49 6543 983 119 Mobil: +49 151 12 12 8934 Email: mailto:shawn.beasley@dlh.de shawn.beasley@dlh.de Web: http://www.cfc-callcenter.de/ http://www.cfc-callcenter.de

Hi Shawn, I'm also very interested on connecting OTRS to SLAs. The only features of OTRS facing towards SLAs I know are: 1) Ticket escalation depending on the queue: E.g. all the tickets are received within the INCOMING-queue. Then an agent has to view these, up to know, unknown tickets by moving it to an appropriate queue. You can "force" this by setting an escalation time of x minute on the INCOMING-queue. 2) To avoid that tickets get dusty in any queues, set the escalation time to x days on these queues. But these tickets only get escalated when the time is over and the ticket is -not- locked by an agent. 3) Use lock-timeout to ensure that a ticket isn't forgot within the "my tickets" of an agent I don't know escalation depending on the priority of a ticket. Perhaps, you can build in some more automatism by using generic agent jobs. Sorry, that's all I know, Alex shawn.beasley@dlh.de schrieb:
Hello Everyone,
and the next mind-boggling question:
Is anyone implementing Service Level Agreements in OTRS? I was wondering how this can be implemented to ensure that our ticket do not exceed our current SLA’s.
I appreciate any and all comments and thank you all again for a wonderful source of knowledge here by this mailer. I hope that I can someday be helpful here as well and not always be the “leech”.
/*/Vielen Dank,/*/
/*/ /*/
/*/Shawn Beasley/*/
Support - IT
Cargo Future Communications GmbH
Geb. 1335
55483 Hahn-Flughafen
Tel. +49 6543 983 113
Fax +49 6543 983 119
Mobil: +49 151 12 12 8934
Email: shawn.beasley@dlh.de mailto:shawn.beasley@dlh.de
Web: http://www.cfc-callcenter.de http://www.cfc-callcenter.de/
------------------------------------------------------------------------
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/
participants (2)
-
Alexander Scholler
-
shawn.beasley@dlh.de