When recieving emails from cloud hosted zammad it would be nice if the name part of the email wasn’t Notification Master and instead was the branded name we have specified for our helpdesk.
When though it still came from noreply@zammad.com.
And in the best scenario it should have been sent out with our email adress, setup in the system.
Please contact the Zammad support and request the notification channels display name to be adjusted. That‘s definitely possible already, I built it back then.
It seams that this is only possible on selfhosted zammad not cloud hosted.
Changing the display name NOT the email address is perfectly possible. I don‘t see a reason why it‘s not.
Hi @FredrikN,
that’s an interesting request. The Notification Master and no-reply address is only used internally to send out notifications to your agents.
What do you want to achieve with that change?
Best regards
De Long
As @MrGeneration said, normally our Support can change the “Notification Master” naming for the instances when requests.
That we use a consistent language for both internal and external communication, it’s branding of the system. Now we will get one display name for internal and one for external.
No. The branding of your Zammad instance has nothing to do with the notification channel.
I also don’t agree with @Dr4gon entirely. Notifications can also be sent to customers, if they e.g. reset their password. Apart from the wording “Notification master”, you’d usually prefer something like “COMPANY Notification” or something like that so that the users know that it’s nothing shady.
The display name of your notification channel has nothing to do with the display name of other email channels. They all can differ from each other.
The ultimate solution would be that all emails from a zammad instance was sent using a certain customers configured email setup. Why have different email delivery systems.
I’m having trouble to understand the problem.
SaaS enforces the notification channel on you, in order to ensure that you are always able to get back into your Zammad instance without Support interaction. So basically to make your life as easy as possible.
Because if credentials change or no longer work (and I’ve seen that a lot in the past), you’re not able to use ot and that can be huge trouble. It only affects the notification channel, no other email channels. So you’re not forced to use the instance@zammad.com email address at all and use your own stuff, no matter if own email mtas, gmail or microsoft365 stuff.
Hey @FredrikN,
I missed that. I agree with his disagreement. We agree to disagree 
As @MrGeneration said. Plus Zammad allows by design flexibility in a lot of configurations. You could’ve IT Support for internal and external via it-support@yourcompany.de with display name “The Support Heroes” and simultaneously for internal purposes only hr@yourcompany.de with the display name “The Humans Care for Humans Team”. That would distinguish the communication from each other and give context with every mail that is sent. Now adding the Notification Master in the mix and you’re instantly aware that’s an update on one of your tickets and no external communication (as you get them as agents). Once this system is in place your agents will be able to work more intuitively day by day and save brain power for decision making.
Best regards
De Long
1 Like