imper.ai supports multiple use cases. This article helps you choose a recommended setup path based on how you plan to use the platform.

---

In this article

• Helpdesk verification

• Meeting security

• HR and identity use cases

Helpdesk verification

Use this setup path when you want to secure sensitive support actions (for example, password resets or account changes).

Recommended setup

1. Connect your identity provider (for example, Microsoft Entra ID or Google Workspace)

2. Configure applicable verification policies for helpdesk workflows

3. Define the relevant protected users (targets) and operational users (agents)

4. Validate with a test verification that reflects your real helpdesk scenario

Meeting security

Use this setup path when you want to protect live meetings and reduce the risk of unverified or impersonated participants.

Recommended setup

1. Connect your meeting platform (for example, Zoom, Microsoft Teams, or Google Meet)

2. Enable in-meeting verification and the relevant alerting/visibility behavior

3. Define protected participants (who must be verified)

4. Validate by running a meeting and confirming expected verification behavior

HR and identity use cases

Use this setup path when you want identity validation workflows for employee onboarding, HR processes, or role-based verification requirements.

Recommended setup

1. Connect the relevant HR system (if applicable) and identity provider

2. Confirm the employee attributes you plan to use in verification logic

3. Define which populations should be treated as protected users

4. Validate with representative scenarios (new employee, role change, sensitive request)

NOTE

Note: If your environment includes multiple use cases, start with the one that has the highest risk (typically helpdesk or executive meeting security) and expand from there.