Tracy Leighton

Absolutely agree. Our workaround is cludgy and means we don't really get to use the last of the brand spots since it has to be reserved for this email. 

Max McCal - is there any improvements planned for the multibrand feature? 

This is critical for our business as we need to provide our developers with relevant information and cases with impacted customers when a problem arises. This would streamline that process a lot.

IQT (hopefully this is Nicole Saunders) Please bring this to your management!

Zendesk!  This is three CLIENTS that were told something in the sales cycle that affects the number of licenses we buy versus what we will actually need. 

IT FEELS LIKE BAIT. 

Please educate your sales team not to continue to do this. 

Thank you Limehmome GmbH - how soon is soon? 

This continues to be a daily issue for us. 

We are now limited to four brands with our subscription since our parent company has to be the fifth just for the emails. 

We have to rewrite several of our automations because our default brand has had to change as the parent company must be the default brand for the emails. 

We have to check to ensure that the brand that is our parent company is not used anywhere with a daily review of a list view.

This is something that because it has such a high level of effort for the work around is very important to us.   

Limehmome GmbH- Are you the product manager? 
This situation is untenable and we are getting no help from support. 
We need the subject line of the "Create Password" email for new users to not be set to the default brand. It either limits us to four brands OR gives the wrong branding to our clients. 

This can't be that difficult a fix to put in place so that it associates with the account name rather than a brand.  

I was asked by support to put my comments here. 

We recently moved to Professional and were told that it supported multi-brand for up to five brands under one umbrella. 

What we have found is that the DEFAULT BRAND is what is used for the Create Password email rather than the account branding. 

SO NO MATTER WHAT HELP CENTER THE CLIENT CHOOSES THEY RECEIVE AN EMAIL RELATED TO THE DEFAULT BRAND. 

This doesn't work as we have clients with very different expectations per brand. 

I'm being told this can't be changed. How can this be true? 

Agree!  Need admin access to list views and possible even groups to share them with (light, agent, admin)

Strongly agree that light agent restrictions are not clearly aligned with most support cases we have. Allowing them to be in a trigger or automation would help. 

Light agents should have a way of communicating with other agents via an @ or another method so that their presence is interactive. 

That is how ZD light agents were presented to me in the sales cycle and is not what is available.