How should organisations combine digital and face-to-face identity verification without excluding users who cannot rely on smartphones or strong internet access?

Why Mixed Verification Works Better Than a Single Channel

Identity proofing should match the person’s access conditions, not assume every user can complete the same digital flow. A mixed model lets organisations preserve stronger evidence where it is available, while still offering assisted or in-person proofing when a smartphone, stable connectivity, or camera-based checks are not realistic. That is the practical way to improve completion without lowering inclusion.

The design goal is not to treat digital and face-to-face verification as competing models. It is to use them as complementary routes into the same identity policy, so the organisation can keep assurance consistent while adapting the experience to user constraints, service criticality, and channel availability.

In practice, this works best when the organisation defines a common proofing standard first, then allows different evidence collection paths to meet it. NIST SP 800-63 Digital Identity Guidelines are useful here because they separate identity proofing, authenticator choice, and assurance expectations, which helps teams avoid making the channel itself the control.

How to Design Digital, Assisted, and In-Person Routes

The strongest programmes give users a clear route to completion even when one path fails. That usually means a self-service digital option for users with suitable devices, an assisted or branch-based option for users who need human help, and an escalation path for cases where additional document review or supervised checks are necessary. The point is to make the fallback route part of the standard design, not an exception process that only determined users discover.

Well-designed mixed proofing also reduces avoidable drop-off. If a user cannot upload documents, cannot complete a live capture step, or cannot maintain a stable connection long enough for verification, the system should not simply fail closed without a handoff. Instead, it should preserve the request, retain the evidence already collected, and allow the next channel to continue the same identity journey.

That architecture benefits from clear evidence rules and consistent review criteria. eIDAS 2.0, EU Digital Identity Framework is relevant because it reinforces the broader European direction toward reusable digital identity with cross-border trust, while still leaving room for practical verification journeys that do not depend on a single device or app.

What Good Assurance Looks Like Across Different Access Conditions

Good assurance is visible when the organisation can explain why each route is acceptable, what evidence it relies on, and how the result is recorded for later use. Digital proofing should not be stronger just because it is automated, and in-person proofing should not be weaker just because it involves a human. Both must resolve to the same identity standard, with the same decision thresholds and the same record of how confidence was established.

That means teams need to think carefully about document authenticity, liveness or presence checks, assisted enrolment, exception handling, and repeat verification. It also means the organisation should decide which steps require a trained operator, which can be self-service, and which require escalation if a user lacks the prerequisites for the main channel.

The operational benchmark is simple: users should be able to complete verification without needing a specific device class, while the organisation still preserves traceability and fraud resistance. For broader identity control design, Ultimate Guide to NHIs is a useful internal reference for lifecycle, governance, and proofing discipline, even though the core issue here is inclusive human identity proofing rather than machine identity.

Risk and Threat Considerations

Mixed verification is partly an inclusion issue, but it is also a control issue. If organisations force every user through a smartphone-dependent flow, they create abandonment risk, support burden, and pressure to weaken checks for edge cases. If they make fallback channels too loose, they create fraud and impersonation risk through weaker document review, inconsistent operator judgement, or poor linkage between the in-person event and the digital record.

Failure mechanism: The common failure is not having one identity standard with multiple proofing routes. Instead, teams either overfit to digital convenience or let manual exceptions drift into uncontrolled special handling, which erodes assurance and makes outcomes inconsistent across channels.

Impact: The result can be exclusion of legitimate users, higher onboarding abandonment, weaker auditability, and a larger attack surface for impersonation or synthetic enrolment. Once users begin to rely on informal workarounds, the identity programme loses both trust and operational predictability.

Practitioner Guidance

What to prioritise: Define the minimum proofing evidence once, then map every allowed channel, digital, assisted, and face-to-face, to that same standard. If the evidence threshold differs by channel, the programme is not truly multi-path, it is multi-policy.

What to verify: Verify that every fallback route produces a durable record of who verified the user, what evidence was inspected, and what exception was approved. If that record cannot be produced later, the path is too weak for regulated or high-impact access.

Practitioner takeaway: The right design is inclusive by default but uniform in assurance, users should have multiple ways to prove who they are, yet the organisation should still be able to defend one consistent identity decision across every route.

Related resources from NHI Mgmt Group

• How should organisations expand identity verification coverage without excluding users who hold uncommon documents or scripts?
• How should organisations implement digital identity verification without making it compulsory for users?
• How should organisations design digital identity verification journeys so users complete onboarding without creating unnecessary friction?
• How should organisations govern face verification in digital identity programmes?