As an administrator, the steps involved in processing a new verification request could be different depending on two broad factors.
The type of verification badge: (Either Segment based or List based.)
For segment-based verification badges, there is a criterion defined. Any record that has to be granted a badge will first need to meet this criterion. (Dynamic)
If it doesn't, you'll need to update the record first before you grant the badge.
For list-based verification badges, there is no criterion. You just need to add the record to the ''approved list'' for that badge. (Static)
The nature of email used by the applicant: (Already on the database or not. )
If the email used by the applicant already exists some record in your database, the application will be auto-mapped to this record. You just need to review and approve the application to add this new badge to the record.
If the email used is new -- you'll need to first add this (new!) email to a record, either by mapping to an existing record or by creating a new one.
The process to reject the application is the same in both cases. You can review the form entries and hit the reject button if you feel the user is ineligible for the badge.
Please note that rejecting an application does not automatically notify the user. We recommend using the "reply by email" button to send the user a message via email and then rejecting it.
The following videos walk through the steps in processing applications for a couple of different scenarios.
- List-based verification badges,
- Applicant's email is already on file
- Segment-based verification badges
- The applicant's email is not on any record in your database.
To learn more about managing verification badges, click here
To learn about creating verification forms, click here