bcgov / bcgov/entity

Proposal: Re-triggering Onboarding Emails for Expired Onboarding Links

Open
#34,044 1 comment 0 reactions 1 assignee Assigned to @vikas-gov View on GitHub
Entities - Data Migration Entities Team
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

**Current Opportunity**
Once the initial 7-day magic link expires, there is currently no mechanism to re-trigger it for clients who have not yet created an account. These clients effectively drop out of the SAF flow until they self-initiate contact, driving avoidable Help Desk volume and stalling migration uptake. Closing this gap is a meaningful lever to lift SAF completion rates without adding new client-facing complexity.

**Objective**
Explore and agree on how we re-trigger onboarding emails, automatically, on demand, or in bulk, to bring clients with expired links (and no account yet created) back into the SAF flow.

**Ask/Need**

- Review the existing SAF onboarding workflow and identify where and how either the original link can be re-issued or a new link generated for clients who have not yet used their magic link.
- Outline the viable options (e.g., staff-initiated single resend, bulk resend for a defined cohort, scheduled auto-resend, client self-serve regeneration) with the trade-offs of each.
- Provide a high-level effort estimate for each option
- Surface any dependencies, constraints, or risks (auth, privacy, deliverability, abuse controls) we should factor into the decision.

**Guiding Principles**

- Start small, build toward sustainable and scalable. A basic, low-effort trigger that nudges clients back into SAF is a valid Phase 1
- Keep the client experience simple, one clear next step per email.
- Respect privacy and anti-spam considerations in any repeat-contact pattern.

**Open Questions to Inform the Investigation**

- Should re-triggered links reuse the existing 7-day expiry, or a different window?
- What defines an eligible cohort, invited but no affiliation, or a broader definition?
- Frequency of retrigger - 30, 60, 90 days?
- Are there stop conditions we should build in (e.g max number of re-triggers, pause if the client is already engaged with Help Desk)?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.