Zendesk autopopulates major domains such as outlook.com in the New organization creation screen

13 Comments

  • Amy Zuckerman

    This does not happen for us.  I can create new organizations and leave the email domains blank.  I wonder if it's a setting that can be toggled somewhere?

     

    -1
  • Tony Vardiman

    Hi Amy, thanks for your reponse.

    We can also leave the domain blank, that is not the problem.

    The problem is that Zendesk *intermittently* auto-populates domains into the New Organization creation screen (as shown in the screenshot) and we are forced to remove it prior to clicking Save.

    This may not sound like an issue at first, but if anybody forgets to remove a domain such as "gmail" or "outlook" before clicking Save, it will combine all customers with that email domain into the same organization, which is obviously a huge issue.

    My stance is that Zendesk should not auto-populate those large domains (such as gmail, Outlook, msn, etc.) which would prevent the merging of these users into a single organization.

    Does that make sense?

    1
  • Colin Piper

    I have this same problem. To be fair the global list of common domain names is huge and probably updates frequently. However I suspect it could be updated.

    1
  • Tony Vardiman

    Thanks Colin, I agree it changes frequently but we could at least remove the heavy hitters like gmail, outlook, msn, hotmail, yahoo, etc.  Think of it in terms of "top 20" and/or the 80/20 rule.  

    1
  • Tony Vardiman

    And it just happened again to me, yet another chance of adding all outlook.com customers to the new organization that I was creating.

    1
  • Mathieu Lapointe

    God please do something about that. We kept losing the Org. of 590 user due to this function !  Can we disable it ? 

    1
  • Lila Kingsley

    +1

    Due to the way we built our API to create tickets/users for our IVR calls, agents who have org permissions are  IGNORING the popup and just saving (it is populated with a default domain we use for unrecognized callers)  This causes our sales app to fail, and substantial data issues.  Agents should never create orgs (only modify them in special circumstances), but, this problem continues to occur all the time even after uptraining.  PLEASE ADDRESS THIS ZENDESK!!

    1
  • Patrick W

    +1. This is really annoying. Our confusion is that Zendesk shows the wrong organization to our agents when other users opens a ticket because earlier organizations are registered based on gmail, outlook etc..

    1
  • Patrizia Eberhart

    following, we have the same issue, it's really a problem to us, Zendesk please help!

    1
  • Jean-Sébastien Catier

    I agree. I'd love a "blacklist" of domains that should not be possible to add to an organization for user mapping.

    1
  • Sally

    I agree. We have an issue where the domains have been linked incorrectly to hundreds of users. 

    After contacting support, we realised the easiest way to rectify this is to delete the outlook.com organisation. However, this means you have to manually change the org on all of the users which were incorrectly added after you action that. Not ideal. 

    1
  • Dev Purdon

    This is a pain for us as well. Following in hope!

    0
  • Anne Flore CAIRE

    Hello,

    We have the same problem.
    And we can't control automaticaly this field!

    A user mistakenly validated the domain "gmail.com" on an organization and all tickets sent from email addresses from that domain all started to be linked to that organization. Huge problem that we had to deal with manually, ticket by ticket to release them from the organization!

    I wanted to at least set up a trigger that sends a notification to admins to warn them if there is a bad value but we cannot select the "Domains" field in the trigger conditions.

    So while waiting to be able to create a system to exclude certain domains or prevent the validation of certain domains, could we have a monitoring and / or alert solution?

    Thanks.

    0

Please sign in to leave a comment.

Powered by Zendesk