it's dependant by your organization flows but they could be synthesized like (IMO):
email ticket: it could be an address given to a still not well known customer or extemporaneously ones customer.pl(web): well know customers and/or clients phone ticket: inbound request taken by phone by an agent or a newly created ad hoc by the same actor email ticket: outbound request - communication with the client MV On Wed, Mar 10, 2010 at 12:50 PM, manish ramteke <[email protected] > wrote: > Hi, > > Please help me with this. > > > On Wed, Mar 10, 2010 at 1:11 PM, manish ramteke < > [email protected]> wrote: > >> Hi, >> >> What are the use cases for which one should go for creating email ticket >> on web interface >> and not phone tickets or sending a mail. >> >> >> Thanks and Regards, >> Manish Ramteke >> >> >> >> > > > > Regards, > Manish Ramteke > > > > > --------------------------------------------------------------------- > 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 > > NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! > http://www.otrs.com/en/support/enterprise-subscription/ >
--------------------------------------------------------------------- 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 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/
