Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)
The tools ZD provides to bulk-import users should allow for verification of identities during the import process.
What problem do you see this solving? (1-2 sentences)
This would prevent bulk-loaded users from showing up as unverified in the system, requiring that either the end-user or the Agent manually verify their identities, or for the need to write script to automate the process.
When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)
We are standing up a ZD instance to replace our legacy email support SOP. Pre-launch we will be bulk-importing many hundreds of end-users from the existing solution. All of these end-users have verified email addresses (1 or 2 per user). When we load these into ZD, they will also show up as unverified.
Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)
There is no existing automation solution for this problem. So our choices are:
- End-user verification on an ad-hoc basis
- Agent verification on an ad-hoc basis
- Expending the resources to write script to automate verification via API post-load.
We will most likely wind up scripting this, but TBD depending on resource availability
What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)
The import tools should recognize the “verified” field that exists in the user record in the API and apply it to all identities in the import record being created/updated.
Although, frankly, I don't understand why verifed=true isn't the default in all bulk-import circumstances. It doesn't make sense that an admin expressly bulk-importing users would ever want them to be unverified…
Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!