Request a demo
Menu

The next enterprise breach starts with a phone call.

Fctr verifies callers in both directions.

Impersonators call helpdesks posing as employees—or call employees posing as IT support, asking them to enter device codes. Verify employees, support callers, and colleagues using factors your organization already manages.

Request a demo Explore the platform

Organizational identityVerified

Call in progress
AM
“Hi, I’m Alex. I need a password reset.”

“Let’s verify your identity first.”

Fctr Portal
AM
Alex MorganPassword reset request
Awaiting approvalPush delivered
Reset still requires role + policy checks.
Your authenticatornow
Verify this support call?

Alex Morgan · Helpdesk

Verify the other end of the call.
Helpdesk caller verification using an existing enrolled authenticator. Try Approve or Deny to see the result return to Fctr Portal. Approval supplies identity evidence; a password reset requires separate role and policy checks.

Identity providers

  • Microsoft Entra ID
  • Okta
Authenticators & verification methods
  • Microsoft Authenticator
  • Okta Verify
  • Cisco DuoMFA for Entra ID
  • Passkeys
  • TOTP
  • SMS OTP
  • Email OTP
  • Entra Verified ID + Face Check
Integrations
  • ServiceNow
  • Freshdesk
  • Zendesk
  • Slack
  • Teams
  • Verification API

A familiar voice
is no longer enough.

AI deepfakes and spoofed numbers make vishing more convincing. Fctr checks identity through supported organization-managed verification, including biometric-protected approvals where enabled, instead of relying on voice or appearance.

What this means for your organization
41%

of CISOs surveyed reported a deepfake social engineering incident during an employee audio call in the previous 12 months.

Gartner, September 2026
Mandiant

Financial-sector vishing

UNC6671 used personal-phone calls, spoofed helpdesk numbers, and urgent MFA changes.

 Microsoft Security

IT support impersonation

Fake Teams support contact led to malware installation and access toward identity systems.

 Sophos X-Ops

From a call to ransomware

One documented incident progressed from fake IT contact to Chaos ransomware in under 17 hours.

Verification is only
the first step.

Fctr Portal connects live identity context, caller verification, policy-authorized support actions, and PII-masked audit evidence in one helpdesk workspace.

  1. 01

    Find the person

    Look up the employee in your authoritative directory and review live context.

  2. 02

    Verify identity

    Require the supported verification method your organization permits.

  3. 03

    Apply policy

    Check the agent's role and policy before a reset, supported unlock, or other action.

  4. 04

    Keep the record

    Connect verification, authorization, and the outcome in a PII-masked audit trail.

Inside Fctr Portal

Our products.

Fctr Portal

From verification
to resolution.

Verify the caller, review live identity context, and perform support actions allowed by your role and policy.

Explore Fctr Portal
Fctr PortalSupport workspace
AM
Alex MorganPassword reset request
Microsoft Entra ID
  1. User detailsLive directory context
  2. Caller verifiedEnrolled-factor verification
  3. Reset authorizedAgent role + policy checked
Connected audit record
Fctr Portal workflow connecting directory context, caller verification, separate role and policy checks, and an authorized reset.

Fctr Verify

Confidence on
either end of the call.

Employees verify support callers and colleagues making sensitive requests. Bring verification into Teams, Outlook, and supported customer-deployed integrations. Employee-initiated requests are available where enabled.

Explore Fctr Verify
Fctr VerifyColleague request
JL
Jamie LeeIT support
Identity verifiedEnrolled-factor result returned to you
  1. Request
  2. Verify
  3. Check result

Teams · Outlook · Supported integrations

Employee-initiated colleague verification. The requested person completes supported enrolled-factor verification and the result returns to the requester.

Fctr Mobile Coming soon

Proof of presence.
Signed verification.

Request a colleague’s verification without relying on existing enterprise factors. They confirm the request with fresh biometric authentication or an organization-permitted passcode. A cryptographic signature binds their response to your request.

Fctr Mobile, coming soon. Check pending requests and an expanded Request verification area with Find a recipient.

Your identity platform.
Your enrolled factors.

For existing-factor workflows, use the verification methods your workforce already has. Available methods depend on provider configuration, policy, and verification direction.

Microsoft Entra ID

  • Microsoft Authenticator
  • Passkeys
  • TOTP
  • Cisco Duo MFA
  • SMS OTP
  • Email OTP
Method details
Microsoft Authenticator
Push notifications
Passkeys
FIDO2, where supported
TOTP
Timed authenticator codes
Cisco Duo MFA
For Microsoft Entra ID
SMS OTP
Code sent by text message
Email OTP
Code sent by email

Uses the employee’s existing enrollment.

Okta Identity Cloud

  • Okta Verify
  • Passkeys
  • TOTP
  • SMS OTP
  • Email OTP
Method details
Okta Verify
Push and number challenge
Passkeys
FIDO2 WebAuthn, where supported
TOTP
Timed authenticator codes
SMS OTP
Code sent by text message
Email OTP
Code sent by email

Uses the employee’s existing enrollment.

Entra Verified ID

Step up when policy requires it.

Credential and face-match verification for supported employee workflows.

  • Verified ID credential
  • Face Check
Method details
Verified ID credential
Verifiable identity credential
Face Check
Face match against the credential

Available where configured for the workflow.

Discuss step-up verification

Add caller verification
to your existing tools.

Customer-deployed integrations bring Fctr Verify into tickets, support sessions, and applications. Use Fctr Portal, your existing tools, or both.

Explore integrations
  • ServiceNow
  • Freshdesk
  • Zendesk
  • Slack
  • Teams
  • Verification API

Every support action.
Recorded and auditable.

Fctr Portal connects the agent, verification result, policy checks, action, and outcome in a PII-masked audit trail. See who acted, what was checked, and why the action was allowed.

Review the Trust Center

Why the action was allowed

Events in a governed support interaction
EventActorControlOutcome
Identity context retrievedHelpdesk agentDirectory readComplete
Factor proof acceptedEmployeeExisting MFAVerified
Scoped action recordedHelpdesk agentRole + target policyRecorded

Live context

No shadow directory. Identity context is retrieved for the active support session.

Scoped access

Helpdesk tools without assigning agents broad provider admin roles.

PII-masked audit trail

Trace support actions for operational reviews, compliance, and evidence requests.

A clear fit.
A predictable price.

Start with Fctr Portal for your helpdesk, or bring Fctr Verify into your existing tools.

Fctr Portal

For helpdesk teams

$250per agent / month

Five-agent minimum

  • Caller verification with enrolled factors
  • Live user, group, app, and device context
  • Supported reset, unlock, and suspend actions
  • Five-tier role model and PII shielding
  • Connected audit history

Add Fctr Verify integrations:
$15,000/year each.

Discuss Portal

Fctr Verify

Standalone caller verification

$35,000per year

Up to 5,000 workforce identities

  • One standard integration included
  • One sandbox environment
  • Verification in existing support tools
  • Supported organization-managed factors
  • Annual pricing, not per user or verification

Additional integrations:
$15,000/year each.

Discuss Verify

Enterprise

For larger organizations

From$50,000per year

Over 5,000 identities or advanced deployment requirements

  • Custom connectors and implementation
  • Dedicated deployment options
  • Premium support and SLA options
  • Multiple-environment planning

Requirements scoped with your team.

Discuss Enterprise

A few things
worth knowing.

Explore the workflows in detail, or bring your questions to a demo.

Read the documentation
We already have Entra ID or Okta. Why add Fctr?

Authentication protects login. Fctr brings identity verification into calls and sensitive support requests, then connects the result to live context, approved actions, and audit evidence. Existing-factor workflows use your supported Entra ID or Okta methods.

What does organizational identity verification mean here?

It means verifying the person through an identity recognized by your organization. Fctr supports helpdesk caller verification and employees verifying support callers and colleagues. Fctr Mobile will add a standalone biometric path.

Does Fctr verify callers in both directions?

Yes. Helpdesks can verify employees, and employees can verify support callers or request a colleague's verification where enabled. Each direction has its own workflow; both parties do not automatically complete a challenge on every call. See the caller verification workflows.

Do employees need another authenticator?

Existing-factor workflows use supported methods already managed through Entra ID or Okta, including Cisco Duo MFA for Entra ID. The upcoming Fctr Mobile app will offer a separate standalone biometric path.

What data does Fctr access?

Fctr retrieves live identity context needed for active support workflows rather than maintaining a shadow workforce directory. Agent-facing personal information is masked according to role. Review the security model and DPA for your review.

Does Fctr detect deepfake audio or video?

Fctr verifies identity through supported verification methods rather than analyzing voice or video. A familiar voice, convincing appearance, or caller ID should not replace an identity check.

See it first.
Try it in your environment.

Walk through caller verification, policy, and supported actions in Fctr's sandbox. No access to your tenant is needed for the demo.

01A demo shaped around your workflow
02A scoped pilot with your Entra ID or Okta tenant

Hands-on evaluation is available for 60 days. Rollout timing depends on your environment and integrations.

Prefer email? [email protected]

Let's talk about your workflow.

Tailor the demo Optional

Used only for this request. Privacy policy.