Candidate surveys

Stage-triggered NPS surveys and experience analytics.

Feature flag: candidate_surveys — Independent from dei_compliance. Requires platform enable + per-tenant grant.

Candidate surveys send a one-question NPS email when an application hits a configured pipeline status. Responses roll up on the Diversity analytics tab alongside DEI metrics (when enabled).

Configure surveys

1. Confirm candidate_surveys is granted.
2. Open /dashboard/settings/compliance (section visible when surveys flag is on).
3. Under Candidate NPS surveys, click Add survey.
4. Choose a trigger status (e.g. REJECTED, HIRED, INTERVIEWING).
5. Toggle Active for each config you want live.

Available trigger statuses match application pipeline states: NEW, REVIEWING, SCREENING, INTERVIEWING, OFFER_SENT, HIRED, REJECTED.

Candidate experience

When triggered, candidates receive an email with a link to a public survey page:

Path: /survey/[token]

The page shows:

• Organization name
• 0–10 NPS scale ("How was your experience with your organization?")
• One-shot submission — revisiting after submit shows a thank-you state

No recruiter login required; token authenticates the response.

Analytics

Path: /dashboard/analytics/diversity → Candidate experience (NPS) section

Displays aggregate NPS score and response counts when candidate_surveys is enabled. If only surveys (not DEI) are granted, the Diversity tab may show NPS alone with demographics sections hidden.

Best practices

• Keep one active survey per trigger status to avoid duplicate sends.
• Review NPS monthly with recruiting ops — correlate drops with /dashboard/analytics/emails deliverability issues.

Related

• Communications — manual candidate email
• Compliance overview — flag matrix