You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by pehbeh April 8, 2023
I would like to suggest that the currently available options to be informed about new tickets or new messages from customers be revised and expanded. My idea here is that the settings can be choose by each agent. Currently, the settings from the department take effect. It would be great if the agent could decide this themselves. I would like to see the following notifications:
Notify for
A new ticket
A ticket is assigned to me
A ticket is assigned to someone else
I'm @mentioned in a ticket
A ticket from my department has new updates (internal notes, due-date-updates...)
Notify me when a customer replies
To an unassigned ticket
To a ticket assigned to me
To a ticket assigned by someone else
Feature Summary
Settings for notifications that can be set by each agent themselves
How will it work once completed?
Currently, the settings from the department take effect for every agent. It would be great if the agent could decide this themselves.
The text was updated successfully, but these errors were encountered:
Discussed in #63
Originally posted by pehbeh April 8, 2023
I would like to suggest that the currently available options to be informed about new tickets or new messages from customers be revised and expanded. My idea here is that the settings can be choose by each agent. Currently, the settings from the department take effect. It would be great if the agent could decide this themselves. I would like to see the following notifications:
Notify for
Notify me when a customer replies
Feature Summary
Settings for notifications that can be set by each agent themselves
How will it work once completed?
Currently, the settings from the department take effect for every agent. It would be great if the agent could decide this themselves.
The text was updated successfully, but these errors were encountered: