Look at formassembly.com and phpmailer.sourceforge.net for some good building blocks ;)
I did my form completely standalone from OTRS install. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter van Beugen Sent: Thursday, April 19, 2007 3:21 AM To: User questions and discussions about OTRS.org Subject: RE: [otrs] faster ticket-creation We also program our own webforms (in ColdFusion) and based on the input criteria send a structured e-mail to a specific e-mail address and POP all these e-mail boxes in their own OTRS queue (so we do the "Postmaster filtering" in our webforms, so we can program everything and route on every criteria we want). We also store the data from the webform in a separate MySQL database for better reporting on different type of tickets. Regards, Peter -----Oorspronkelijk bericht----- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Alexander Scholler Verzonden: donderdag 19 april 2007 7:34 Aan: User questions and discussions about OTRS.org Onderwerp: [otrs] faster ticket-creation Hi, we want to be able to create ticket with standard-issues faster and with higher data-quality (standarized informations provided in the ticket) than in standard-OTRS. Normally, * the agent have to create a mail- or phone-ticket, must write down the issue as free text and must set - priority - queue - ... * the customer - have to open a web-ticket - write down the issue as free text - set priority etc... - have to write a mail and the agent has to set queue, priority, etc... Much work if you have to handle many tickets concerning some standard-issues like * data-restore-request * mail-account-creation * access-rights-modification * ... What is your suggestion how to optimize this? Of course, you can achieve optimization in using special mail-adresses for incoming mail-tickets and postmaster-filters to preset some values (like queue, priority, ...) But I think most potential would come out if you switch from free text written by the customer to a form-based ticket-creation through the customer. E.g. if he request a data-restore, he has to provide * the exact location of the files * the date of the file that should be restored * shall the present file be overriden or not * ...? How can these forms be achieved? Not so easy with the customer-webgui? It would be easier within the comanies intranet, but then the data has to be send to otrs in a special mail-format (with extensive usage of x-mailheaders for postmaster-filter, and the intranet-form must also care for customer-authentification.... Is this the right way you would also suggest? I would welcome spreading discussion on this issue. Bye, Alex p.s. There has been some posting previously about using faq-articles as ticket-creation-templates. Without thinking too much about this, I think this can only be some kind of solution for the agent creating the ticket. But if the customer shall create the ticket... _______________________________________________ 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 or consulting for your OTRS system? => http://www.otrs.com/ _______________________________________________ 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 or consulting for your OTRS system? => http://www.otrs.com/
