Verification user journey from Proxi.id side

Summary

In the first iteration, customers are directed to CDot then to Proxi.id and upon successful verification GitLab emails the customer a coupon code to claim in CDot. Customers are never rejected by Proxi.id.

In the second iteration, we want to address any verification challenges that customers may face and keep them in contact with the GitLab for Education Program team throughout the process.

Potential strategies:

• Begin with a GitLab onboarding process PRIOR to CDot registration and Proxi.id verification to establish support and contact points early: #15
• Establish a check for tracking IDs generated when a CDot user attempts Proxi.id verification and check which ones have not yet completed Proxi.id verification (missing webhook confirmation)
  • https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/13977
• Could outreach to Proxi.id with these Tracking IDs to confirm status
  • Can be done via emailing a tracking ID to gitlab-support@proxi.id (tested successfully on migration day)

Next steps

• Continue exploring concept of initial onboarding in #15
• Monitor support process in first 30 days after migration to decide on an automated outreach process to applicants who do not complete verifications

Resources