Elsewhere an extra; in Zammad a standard feature: individual fields. Old time help desk pros know what I’m talking about. It’s about the fact no software knows your business as well as you do. It’s as simple as that.
All signed and sealed.
If by “Individual Fields”, some farming image comes to mind, you’re probably not the only one standing in that particular field. Quite simply, all it really means is that in Zammad you yourself can determine what attributes a ticket, customer or organization has. In the abstract this feature little traction, so here’s an example.
For example: Wine.
Let's stay in the field: A winemaker uses Zammad to manage the communication with dealers and retail customers. For him, of course, the respective wine is important, as is the vintage and point of sale. So he creates specific fields for these three pieces of information in Zammad. And so he doesn’t need to constantly re-enter the same terms, Zammad supports the use of drop down menus and multiple selections. In contrast to a manual, text-based recording, these fields can also help to make evaluations: Thus on the basis of the requests the winemaker can evaluate his products and services specifically and ideally even improve them.
The customization of attributes can be done at the ticket, customer or organizational level. This is another feature that distinguishes Zammad from other vendors, who only support modification at the ticket level. And if you narrow the search radius to the existing open source solutions, then you’ll be seeking in vain, like looking for a bottle of fine German Rebstock Schwarzriesling wine in Tuscany.
Thus winemakers, lawyers, sailing clubs and web startups have the ability to define and collect the information that’s specific to them. This truly lets you turn Zammad into personal toolkit.
And in Zammad nature it looks like this way: