RE: [otrs] Integrating OTRS with e-mail more easily

Hi guys, Thanks for the responses. Gene Parks is right that I want to run everything from e-mail, whilst taking advantage of the Web backend as a history/repository/analysis resource. Stefan, you raise a good point which is that locking is difficult via e-mail (i.e. I start writing a reply to a ticket and someone else gets in there first and we both end up replying to the message -- annoying). In our situation we only have a small number of agents and it is usually fairly intuitive who should answer each support query, so I believe the locking issue is slightly reduced. You could resolve the problem by sending out new ticket notifications to each agent. If an agent wants to reply they just click a link to lock it to them, or reply with 'lock' in the message body. If someone has already locked an error message could come back. Then the agent can reply to the success message, with the reply going straight to the original ticket raiser. An auto-unlock kicks in after a while. Having the OTRS database accessible out of an IMAP server is a brilliant idea -- that would integrate with our local systems pretty nicely, but suspect that is quite a bit more work. I think just a basic email command interface like Martin suggests would be a good enough solution for us in the first instance. Should I go about trying to hack one together, or would it be better to leave it to an OTRS expert? Many thanks, Nick.

Nick Loman wrote:
Gene Parks is right that I want to run everything from e-mail, whilst taking advantage of the Web backend as a history/repository/analysis resource.
Last year I asked an almost identical question but was persauded to try and use the OTRS web interface for a while. Well, after a month or so almost all our agents were using the web interface and the system is working well. One thing we do is to add a psuedo user to the OTRS system who has notification on new tickets (on incomming queues only) set to true. This user is actually a mailing list. This means when a ticket comes in, everyone subscribed to the mailing list gets the "new ticket notification" which includes a bit of the original email and a hyperlink to the zoomed ticket. Also anyone can reply to the mailing list post and it will be auto threaded onto the ticket since it now has the ticket number in the subject line (any such replies go to the ticket owner, not the customer). -- Phil Davis IT Action

On Fri, Jan 03, 2003 at 05:57:29PM +0000, Phil Davis wrote:
Gene Parks is right that I want to run everything from e-mail, whilst taking advantage of the Web backend as a history/repository/analysis resource.
Last year I asked an almost identical question but was persauded to try and use the OTRS web interface for a while.
Well, after a month or so almost all our agents were using the web interface and the system is working well.
One thing we do is to add a psuedo user to the OTRS system who has notification on new tickets (on incomming queues only) set to true. This user is actually a mailing list.
This means when a ticket comes in, everyone subscribed to the mailing list gets the "new ticket notification" which includes a bit of the original email and a hyperlink to the zoomed ticket. Also anyone can reply to the mailing list post and it will be auto threaded onto the ticket since it now has the ticket number in the subject line (any such replies go to the ticket owner, not the customer).
I think Phil's solution is a good way. :) Nick, anyway if you want to write an agent-email-interface feel free to do so (you will find help on dev at otrs.org).
Phil Davis IT Action
Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- "The number of Unix installations has grown to 10, with more expected." The Unix Programmer's Manual, 2nd Edition, June 1972
participants (3)
-
Martin Edenhofer
-
Nick Loman
-
Phil Davis