Employee Invite Batch Detail
A focused rollout detail for one invite batch with delivery state, bounce handling, role mapping, and next-step onboarding coverage.
Batch detail should anchor delivery state and acceptance coverage around one named employee wave.
Invite acceptance should be visible without forcing the operator into a second reporting lane.
Bounce correction needs to stay explicit so operators can repair the roster quickly.
Fix delivery gaps before approval operators start working from stale or incomplete roster data.
This is where a rollout owner should see if one department is stuck, one domain alias is failing, or a CSV import carried the wrong role template.
If the invites are healthy, the next action should move straight into approvals or onboarding rather than leaving the owner on a dead-end status page.
{
"invite_batch_id": "northstar_wave_3",
"sent": 240,
"delivered": 235,
"opened": 198,
"accepted": 162,
"bounced": 5,
"default_role_template": "team_member"
}Batch detail should connect delivery, acceptance, and correction work in one lane.
The operator should see the actual wave size before chasing approvals that never received an email.
Open rate helps the rollout owner understand whether employees are actually seeing the invitation.
Acceptance is what turns invite delivery into real workforce onboarding throughput.
Incorrect addresses or blocked aliases should remain visible until they are corrected or removed.
Role mapping belongs on the batch detail surface because it drives the approval and onboarding paths that follow.
This page should always point to the next operational lane rather than ending at delivery status.
The invite batch is landing cleanly with only a small correction lane still open.
Most recipients have seen the invite, which keeps queue growth predictable.
Roughly two thirds of the invite wave has already moved into account creation or approval state.
The new batch started landing across Northstar company inboxes.
Managers in Warehouse Operations accepted quickly after the invite landed.
Five stale aliases were flagged for correction before the next resend window.
An invite-batch detail surface should show how many emails were sent, delivered, opened, accepted, or bounced so operators can correct gaps before the approval queue fills up with noise.
This is where a rollout owner should see if one department is stuck, one domain alias is failing, or a CSV import carried the wrong role template.
A real operator surface should make resend, correction, and reassignment obvious without requiring the owner to rebuild the whole batch from scratch.
If the invites are healthy, the next action should move straight into approvals or onboarding rather than leaving the owner on a dead-end status page.