Recent searches
No recent searches

JD Trout
Joined Apr 08, 2022
·
Last activity Jun 09, 2022
Following
0
Followers
0
Total activity
8
Votes
3
Subscriptions
2
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by JD Trout
JD Trout commented,
Hello Konstantin,
The software that we deploy allows the user to create local accounts or leverage their own SSO. The request that I am making is when they run into an issue they will email support@myco.com, not necessarily try and log in and create a ticket. Therefore, I would like to allow any email coming from the customer's domain to be accepted.
View comment · Posted Jun 09, 2022 · JD Trout
0
Followers
0
Votes
0
Comments
JD Trout commented,
For those looking to have the allowlist/blocklist modified via API I have created a feature request here. Please upvote it if you care about this feature.
View comment · Posted Jun 09, 2022 · JD Trout
0
Followers
0
Votes
0
Comments
JD Trout created a post,
Feature Request Summary:
Extend the Zendesk API to support allowlist/blocklist.
Description/Use Cases:
We programmatically onboard customers and would like to add their email domain to our allowlist so anyone from their company can submit a ticket. Given that the onboarding is programmatic, manually having to go in a modify the allowlist is not a scalable solution and will create friction when onboarding a new customer.
Business impact of limitation or missing feature:
When we add a new customer we have to manually perform a step to add the new customer's domain to the allowlist. The rest of the onboarding process is programmatic, so it creates friction and the possibility of a missed action because the person who has access to the allowlist is not part of the onboarding process. Modifying the allowlist should be part of the API.
Posted Jun 09, 2022 · JD Trout
6
Followers
4
Votes
3
Comments