Verify who's calling. Before you act.

Fctr Verify is organizational identity verification software for IT support calls and sensitive employee requests. Helpdesks can verify employees, and employees can verify IT support callers or request a colleague's verification where enabled. It uses supported organization-managed verification methods through customer-deployed integrations and configured apps in Teams or Outlook.

Employees verify IT support callers through Fctr Verify in their organization's configured Teams or Outlook app. The caller starts a request in Fctr Portal or a supported integration after meeting the organization's verification policy.

Open Fctr Verify independently, review the caller details and reason, select and submit the phrase they say, and wait for Verification complete. Never read the choices aloud. If the caller is not verified, end the call.

Yes. Fctr Verify uses supported factors your organization already manages through Okta or Microsoft Entra ID, so employees do not need another authenticator for these workflows. Available methods depend on your provider, configuration, policy, and verification direction.

Yes, where employee-initiated verification is enabled. Open Fctr Verify independently, choose Request verification, and find the person by name or work email. The selected person opens Fctr, chooses Verify yourself, and completes verification using their enrolled, organization-managed factors.

Use this for sensitive requests from HR, payroll, or finance, such as changes to bank details or an urgent payment request. Both people need access to the organization's configured app. Check the result in Fctr before continuing. If the caller is not verified, end the call. Business approvals and access checks still apply. Explore employee verification use cases.

Fctr can verify vendors and contractors who use eligible organization-provided accounts, supported enrolled factors, and your configured Fctr workflow. This lets employees check the person behind a support instruction or access request before continuing. Verification does not grant access or approve the request.

A vendor-list entry or guest invitation alone is not enough. The current Teams and Outlook workflows do not support Microsoft Entra B2B guest accounts. Discuss your vendor setup with Fctr to confirm the supported workflow.

No. Supported workflows can start in a customer-deployed integration such as ServiceNow, while employees use Fctr in Teams or Outlook. Where enabled, employees can request another person's verification directly. Portal adds the governed helpdesk workspace. Fctr Mobile is an upcoming standalone biometric path.

Reverse caller verification is the employee-verifies-support direction. Two-way, or bidirectional, verification covers both helpdesks verifying employees and employees verifying support callers.

In support-initiated caller verification, the support caller meets organizational factor policy before creating the request. The employee's phrase selection confirms the interaction without a fresh MFA challenge for that employee. For colleague requests, the selected person verifies. For an incoming helpdesk request, the employee completes the supported verification required for that workflow.

Do not treat the person as verified. End the interaction and contact the person or support using details you already trust. Do not rely on a link supplied only by the caller.

Fctr Mobile is coming soon. It will offer proof of presence and signed verification without relying on existing enterprise factors. A requester will look up a colleague and send a request. The recipient will confirm it with fresh biometric authentication or an organization-permitted passcode. Their device will sign a single-use response bound to the specific request and decision, with the verification result returned to the requester.

No. Identity verification, support-action permission, and business approvals are separate. Password resets, enrollment changes, payment requests, and data sharing still require their applicable role, policy, approval, and access checks.

No. Fctr verifies identity through supported methods rather than analyzing audio or video. Available enterprise-factor methods depend on provider, policy, and direction. Fctr Mobile will add a standalone biometric path.