Clear answers for security and identity teams.

Fctr is an organizational identity verification platform. People verify employees and colleagues using identities and supported factors their organization already manages. Fctr Portal brings user details, caller verification, approved support actions, and audit evidence into one helpdesk workspace. Fctr Verify brings verification into existing tools; employee-initiated requests require enablement and both participants' access to the configured app.

Neither Okta nor Microsoft provides a native, helpdesk-facing identity operations workflow. They provide authentication infrastructure; Fctr Portal gives agents a governed web application, while Fctr Verify adds enrolled-factor verification to external support workflows.

Not necessarily. Organizations can use Fctr Portal as a single identity-operations workspace or use Fctr Verify through a customer-deployed integration or the External Verification API.

Fctr Portal brings user lookup, caller verification, and approved support actions into one workspace. Fctr Verify brings verification into the tools your team already uses.

Organizations can connect a pilot to Okta or Entra ID with scoped tokens or OAuth 2.0, then use the browser-based, cloud-hosted Fctr Portal or Fctr Verify through a customer-deployed integration or the External Verification API. A sandbox demonstration requires no tenant access, and a connected pilot can be deployed in days; full rollout timing depends on integration, policy, and change-management requirements.

Training helps people recognize suspicious calls, but it does not prove who is calling or enforce a technical gate. Security-question answers can be researched, purchased, or elicited. Fctr requires verification before password resets and supported account unlocks. Role and policy checks determine which actions an agent can perform.

Fctr helps protect against AI voice cloning and deepfake vishing by requiring verification through supported organization-managed factors, rather than trusting a familiar voice or face. Biometric-protected approvals can be used where enabled by the provider and organization. Password resets and supported account unlocks require verification. Roles and policy govern support actions. Fctr verifies callers; it does not analyze audio or video to detect deepfakes.

The IT caller starts a request in Fctr Portal under the organization's verification policy. The employee independently opens Fctr in Teams or Outlook, checks the pending request, and selects the phrase the caller says. The employee never reads the choices back to the caller. This confirmation does not authorize a password reset or other support action.

Password resets and supported account unlocks require verification. Other actions, such as session revocation, follow their applicable verification requirements. Fctr checks role, provider capability, and customer policy before authorizing an action, and records the decision and outcome.

Entra ID remains the identity source. Fctr can challenge the employee’s existing Duo enrollment as the verification method and return the result to the active support workflow.

Supported options depend on the configured provider and tenant policy. Fctr supports configured passkeys for Entra ID and Okta, Microsoft Authenticator Push and TOTP, Duo MFA when configured alongside Entra ID, Okta Verify and number challenge, additional one-time-code methods where configured, and Entra Verified ID with Face Check for higher-assurance step-up.

Fctr uses scoped API access to retrieve identity context for the active support session without building a persistent workforce directory. Personal and recovery contact details are excluded from approved audit records. Organization-issued email addresses and UPNs are masked in human-readable audit labels; limited identifiers remain for security correlation and auditability.

Fctr connects verification, actor, policy, action, and outcome in PII-masked operational records. Customers may use these records as one input to audit, incident-response, or cyber-insurance evidence requests. Required evidence and acceptance depend on the insurer, broker, policy, and customer environment; Fctr does not guarantee eligibility, coverage, claim outcomes, or pricing.

Fctr Portal starts at $250 per agent per month with a five-agent minimum. Fctr Verify is $35,000 per year without Portal for organizations with up to 5,000 workforce identities and includes one integration and one sandbox environment. Enterprise pricing starts at $50,000 per year for organizations with more than 5,000 workforce identities or advanced deployment requirements. Portal customers add Fctr Verify integrations for $15,000 per year each. Fctr Verify uses predictable annual pricing rather than per-user or per-verification pricing. A 60-day pilot is available after a walkthrough.

A supported customer-deployed connector or a customer-built workflow using the External Verification API counts as one integration. Fctr Verify includes one integration; each additional integration is $15,000 per year.