In many cases, agents who are working on a certain ticket need to discuss about the actual issue with other colleagues. EriZone 3.6 that will be shortly released allows adding private notes to a ticket. Since, such notes are for internal use only and of no interest for the customer, they are visible just to the agents logged to the system.
In EriZone each ticket is assigned to an agent that formally is called his owner. Although, the ticket is managed by the owner, as described above it could be necessary that more than one agent is internally involved in its resolution. To guarantee an appropriate exchange of information among the involved agents, ticket articles of the type “internal notes” can be added to the ticket and the involved agents can be notified via email.
These notifications are intended for internal use only and are not visible to the customer through the customer self-service web portal.
internal notes. Selected agents are informed by email
Involved agents on their hands can reply to that notification.
By default EriZone sets all incoming agent notification replies as “email external”. This means that the agents’ reply will be visible as follow-up not only to the enabled agents through the agent web portal, but also to the customer through the customer self-service web portal. Obviously, this behavior sometimes could be undesired. That’s why in the last version of EriZone (3.6.0) a new postmaster filter has been added that makes it possible to change the article type of the agents’ replies. Setting it to “email internal” the created follow-up will remain hidden to the customer.
Replies to agent notification created asemail -internal notes
The described features can be enabled in SysConfig, configuring the new postmaster filter.
“Hi guys! I’m Mihail and since the university years I has been fascinated by distributed systems and measurements on them. Now when I join the Neteye project I get the possibility to continue with this passion and this is great. My free time is completely dedicated to my wife and my daughters, I simply love them.”
Author
MarinovMihail
“Hi guys! I’m Mihail and since the university years I has been fascinated by distributed systems and measurements on them. Now when I join the Neteye project I get the possibility to continue with this passion and this is great. My free time is completely dedicated to my wife and my daughters, I simply love them.”
Practical lessons learned from real-world alert routing, automation, and integrations Introduction As more teams and customers rely on NetEye as their primary monitoring stack, Jira Operations (Jira Ops) may become a central component for alert routing, on‑call scheduling, and automated Read More
Today we continue our journey into monitoring automation in NetEye. In my previous post we discussed the possibility of automating Business Processes. As you may remember, for those of us working on NetEye Cloud monitoring dozens of clients, it's important Read More
I don't really know the reason behind it, maybe because the typical scenario for notifications is just "send all events to this mailing list", or as we say: set it and forget it. But we shouldn't use this as an Read More
Sending an SMS requires time, between 5-7 seconds. This means that if you have to write a lot of SMS's, you have to attach more than one SMS gateway to your server to be able to send them within a Read More
Whenever a new monitoring project gets underway, a consultant discusses with the customer about almost any related topic: what needs to be monitored, how to monitor it, when to implement it, how to represent performance data, etc. Based on customer Read More