Hi Shawn, Well, yeah, I completely agree with you. We have OTRS installed in a NOC environment, network operations center. And given the nature of our customers and suppliers, it is always needed to provide agent numbers, skype contact and MSN ID's; this is all used for live support to solve technical issues etc...
Thanks and Best Regards, Muhammad El-Sergani. On Mon, May 9, 2011 at 9:20 AM, Shawn Beasley <[email protected]>wrote: > Hi Muhammad, > > On May 8, 2011, at 17:10 , Muhammad El-Sergani wrote: > > > Is there anyway to define a signature per agent, and not just a shared > signature? > > > > Unfortunately no, because the signatures come from the queue. But, as > stated, if you use variables, you can get the agents name in the signature. > As OTRS is designed for working in teams, the philosophy of an centrally > configured standard signature per queue is the de facto. What is the purpose > of having individual signatures in an organization working in teams? What > business case are you researching/implementing? Have you looked to > http://otrsteam.ideascale.com/ to add your feature request? This is a good > start for sending us feedback about your use case and implementation ideas. > > ///shawn > --------------------------------------------------------------------- > 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 >
--------------------------------------------------------------------- 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
