IDENTITY VERIFICATION · Workflow idea

Confirm identity through two channels—and keep access under human control.

Guide a person through separate phone and email checks using details they provide and verification codes delivered to them. Show whether each check was completed, but treat that result as one part of identity review: an authorized person must approve account access, recovery, or other security changes separately.

A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
Identity check request
Produces
A clear status for each verification step, ready for an authorized reviewer; verification alone does not grant or change account access.
Category
Reviews & approvals

01 / The starting point

A clear request.
A useful direction.

A person’s submitted contact details and request to verify their identity

“Coordinate phone and email verification, make incomplete or mismatched checks visible, and hold account access or security changes for authorized human approval.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps a person complete a two-channel identity check and gives an account owner a reviewable result before security decisions are made.

  1. Receive an identity check request

    Confirm which person and account the request concerns and collect only the contact details needed for the check.

  2. Verify access to the phone number

    Deliver a short-lived code to the submitted number and ask the person to enter the code they received.

  3. Verify access to the email address

    Send a separate code to the submitted email address and check the person’s response without exposing the code to others.

  4. Show incomplete or mismatched checks

    Keep each result visible and route failed, repeated, or unexpected attempts to an authorized reviewer.

  5. Approve account actions separately

    Require an authorized person to confirm the identity and approve any sign-in, recovery, or access change before it takes effect.

03 / The result

Something useful.
Something to build on.

A clear status for each verification step, ready for an authorized reviewer; verification alone does not grant or change account access.

AmbactiWorkflow folio · 5 steps

Review two-step identity checks

Reviews & approvals · Example outcome

The handoff

A clear status for each verification step, ready for an authorized reviewer; verification alone does not grant or change account access.

Keep in mind

Verification codes and contact details are sensitive, and a completed check does not by itself establish that an account change is safe. Keep codes private, confirm that the requester is entitled to use the account, and require an authorized person to approve sign-in recovery, access changes, or other security actions.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Define the identity review process

Choose which people and requests use the two-channel check and what additional evidence an account owner may need.

Set code and privacy practices

Use short-lived codes, limit who can view contact details, and make sure verification information is not included in general alerts.

Assign security approvers

Name the authorized people who can approve account access, recovery, and security changes after reviewing the verification result.

Test failed and unexpected attempts

Check mistyped details, expired codes, repeated attempts, and requests for another person; confirm the process stops for human review.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗