25 コメント

  • Jake Holman
    コメントアクション Permalink

    Got any example of the sort of wildcarding you would like to do?

    1
  • Conrad Selle
    コメントアクション Permalink

    So, in this example, I'd like a default mapping for any non-defined domain to automatically be assigned to a specific organization.  In the organization settings of Zendesk, the map users to organization would be "*", as a catch all for automatic user assignment to this organization...UNLESS a user's domain is already defined for mapping to a different org.  This would only affect new user registration.

    1
  • Wb
    コメントアクション Permalink

    I need a simplified version of this:

    My use case is as follows:

    We have automated emails(notifications and such) from our site which get sent from a standard email address. We also have some SLA targets (unassigned tickets get assigned with X hours, etc). The problem is that we can't filter out the automated emails from the SLA targets. I've already assigned the automated emailer to its own organization, but I can't set a default organization for everything else. This leaves me with two choices:

    1. An SLA target which matches every ticket, including the ones I don't want.

    2. An SLA target which matches NO tickets, since customers emailing us have no organization.

     

    Some way to set a default organization for every user, or some way to specify that the SLA target does not match tickets from an organization would both solve this issue.

    1
  • Rob Winn
    コメントアクション Permalink

    I have the exact same use case as Mr. Selle.

    1
  • Michelle Dunn
    コメントアクション Permalink

    I have the same case as Mr. Selle as well. This would be so helpful for me!

    1
  • Aric Asti
    コメントアクション Permalink

    Was any progress made on this?  

    1
  • Jimmy Maher
    コメントアクション Permalink

    I'd like to see this feature too. Use case a global enterprise XYZ Corporation has email domains @xyz.com, @jp.xyz.com, @xyz.fr etc. I would like to use *.xyz.* to cover all combinations of their domain.

     

    3
  • Joe Spirk
    コメントアクション Permalink

    I'm attempting to do the same, want to map all incoming requests from the email domain *com.au to effectively draw in all emails from Australia. 

    1
  • Karl Hiramoto
    コメントアクション Permalink

    Yes I work with companies that  have @company.com @country.company.com (sub domain for each country)   and @company.country (country level TLD)  For us we want to group them together as they are the same customer.   As some big companies are in dozens of countries it's terribly pain-full to manually add in each domain to the organization group. 

    1
  • Scott Carpenter
    コメントアクション Permalink

    We require this configuration as well, and it's limiting our use of Zendesk for business development.

    1
  • Ricardo Nash
    コメントアクション Permalink

    We have a similar situation as well which also limits our business tracking and development.

    1
  • Khaled Zaky
    コメントアクション Permalink

    Any update on this? Has it been implemented?

    0
  • Stewart Fulton
    コメントアクション Permalink

    Any update on this? I need to be able to set a domain wildcard of *.school.nz 

    0
  • David L
    コメントアクション Permalink

    Can we get an update?

    0
  • Sebastiaan Wijchers
    コメントアクション Permalink

    I need this as well, although a wildcard won't be needed in my case. It would be great if subdomains are automatically mapped.

    So that 'domain.com' will include all of these adresses in the organization:
    netherlands@nl.domain.com
    germany@de.domain.com
    france@fr.domain.com

    4
  • Jahmai Lay
    コメントアクション Permalink

    +1 to implicit sub domains. Almost all of our customers have maindomain.com, and then a handful of email subdomains like department.maindomain.com.

    2
  • Helen Foot
    コメントアクション Permalink

    Another +1 for the wildcard functionality for Domain-based user mapping to organisations, and the implicit subdomain mapping would be even better. This feature would really help us out.

    1
  • Marshall White
    コメントアクション Permalink

    +1 for implicit subdomain mapping. We have organizations with dozens of domains, and potentially hundreds of subdomains beyond that. It would be much easier to manage if only tracking the domain names was necessary 

    0
  • Julia Whistler
    コメントアクション Permalink

    +1, surprised there have been no updates or responses to this in 7 years. Yikes!

    0
  • Jonathan Jongkind
    コメントアクション Permalink

    +1 for this feature. In our scenario, a customer has thousands of subdomains that unfortunately we cannot easily capture in one organisation because of this.

    0
  • Nicole - Community Manager
    コメントアクション Permalink

    Hey Julia - 

    We're working on improving the communication in the Product Feedback topic, so that there will no longer be long-standing threads without responses. 

    I encourage you all to continue sharing detailed use-cases so that our Product Managers can better understand the problem you're looking to have solved. 

    0
  • Vladan Jovic
    コメントアクション Permalink

    I need this too, +1 :)

    0
  • GIRAUD Alexandre
    コメントアクション Permalink

    Hi,

     

    This feature is really need there too. I've some "federal" customers where using root domain for main organization ***@contoso.com and then all regional department have a dedicated subdomain like ***@region1.contoso.com ***@region2.contoso.com etc...

    It could be just enough to permit add *.contoso.com for validate all subdomain.

    The best could be a regex ;)

     

    Regards
    Alexandre

    0
  • Andrew Deming
    コメントアクション Permalink

    We (Socrata) would like this as well - we have government customers as well where different departments use different subdomains and mapping all of these users to a single organization is extremely difficult without the use of a wildcard. 

    1
  • Nicole - Community Manager
    コメントアクション Permalink

    Thanks for the feedback, Conrad and Andrew!

    0

ログインしてコメントを残してください。

Powered by Zendesk