New · Entra Verified ID + Face Check

The next enterprise breach
starts with a phone call.

Q: We already use Okta or Microsoft Entra ID. Why do we need Fctr?

Entra ID and Okta secure access to systems. Fctr adds enrolled-factor verification and policy enforcement to the support session before an agent takes a sensitive action. It complements the identity provider; agents can work through Fctr Portal or supported integrations without using the provider’s admin console for each workflow.

Q: Why does Microsoft Authenticator Push support matter?

Fctr supports Microsoft Authenticator Push and TOTP for Entra ID users, so helpdesks can verify employees with a factor they already use without introducing another application or enrollment campaign.

Q: What data does Fctr access from our identity provider?

Fctr uses scoped API access to retrieve the identity context needed for an active support session. It avoids building a persistent identity directory, keeps operational records minimized, and masks personal data in audit evidence. Every session is authenticated through the organization’s identity provider.

Q: How is Fctr deployed and integrated?

Organizations can connect a pilot to Okta or Entra ID with scoped tokens or OAuth 2.0, then use the browser-based, cloud-hosted Portal, marketplace integrations, or the REST API. A pilot can begin in hours; production timing depends on integration, policy, and change-management requirements.

Q: Does Fctr detect AI voice cloning or deepfakes?

Fctr does not attempt to classify a voice as human or synthetic. It requires organization-managed enrolled-factor verification before a sensitive support action, so the decision is based on factor evidence and policy rather than voice authenticity alone.

Q: How do employees verify callers claiming to be IT support?

IT starts verification from the active support session. The IT caller completes a challenge through their enrolled factor, and both sides receive the result before the conversation continues or any sensitive action is taken.

Fctr verifies callers both ways—before anyone acts.

Helpdesks verify employees before resets and other sensitive actions. Employees verify callers claiming to be IT support. Both use Microsoft Authenticator or Okta Verify factors already enrolled in the organization’s identity provider, so the decision does not depend on conversation—even during social engineering, vishing, or AI-cloned voice attacks.

Request a demo ↗ See how the control path works

Verify callers in under 60 seconds · No new authenticator to deploy

Technology ecosystem

Identity providers Microsoft Entra ID Okta Entra Verified ID

Integrations ServiceNow Freshdesk Slack Zendesk Microsoft Teams

Voice phishing is now the #2 initial intrusion vector.

ShinyHunters campaigns impersonate both sides of support: employees calling helpdesks and IT calling employees.

11%of observed intrusions in 2025 involved highly interactive vishing.

MGM ~$100M A social-engineering breach disrupted resort operations. Report ↗ Clorox ~$380M A lawsuit alleges a service-desk reset enabled the attack. Report ↗ Mandiant M-Trends 2026 threat research Research ↗ Microsoft DART Support call IT support vishing case Case study ↗

Entra ID and Okta secure access. Fctr secures sensitive support actions.

Before an agent resets a password, unlocks an account, or starts recovery, Fctr requires the employee’s enrolled factor and releases only what role and policy allow. It complements the identity provider without another authenticator or a separate workforce directory.

01
Directory
Confirm the caller is a current employee.
AUTHORITATIVE DIRECTORY
02
Factor proof
Require verification through the employee’s enrolled device.
DEVICE-BOUND PROOF
03
Policy gate
Allow only the action role and policy approve.
ONE TARGET · ONE ACTION
04
Audit record
Keep a masked record of the decision and outcome.
AUDIT-READY EVIDENCE

No security questions No new authenticator No action before MFA No standing admin rights for agents

Use the factors already enrolled in Entra ID or Okta.

Fctr sends verification through Microsoft Authenticator or Okta Verify using the employee’s existing enrollment. The result returns directly to the support workflow.

EMPLOYEEExisting enrolled factorAlready managed by the organization

Microsoft Entra ID

Core verification

Microsoft Authenticator

ChallengePush notification

Verified

Also supportedTOTP · SMS · Email OTP

Uses the employee’s current Entra enrollment

Okta Identity Cloud

Core verification

Okta Verify

ChallengeNumber challenge

Verified

Also supportedTOTP · SMS · Email OTP

Uses the employee’s current Okta enrollment

Entra Verified ID

Policy-driven step-up

Verified ID + Face Check

ProofCredential + face match

Assured

PurposeHigher-assurance verification

Applied when organizational policy requires it

FCTR VERIFY · ACTIVE SESSION

Is this really IT?

Your support agent is ready to verify this call before it continues.

Verify IT caller

I did not request support

04Verification, both ways

Vishing works both ways. Verification should too.

Attackers call helpdesks pretending to be employees—and call employees pretending to be IT. Fctr lets employees require an IT caller to complete an organization-managed enrolled-factor challenge before the support conversation continues.

01IT starts verification from the active support session.
02The IT caller completes a challenge through their enrolled factor.
03Both sides see the result before the call continues.

Work in the Fctr Portal—or add Verify to your existing tools.

Choose where agents work; the same enrolled-factor verification, policy, and audit evidence stay consistent.

INCLUDED IN BOTH

Existing Entra ID or Okta factors Policy enforcement PII-masked audit evidence

01 / FCTR PORTAL

Identity operations workspace

Use the browser-based Portal to verify callers, view live identity context, and take approved account actions from one place.

Fctr / verification sessionLIVE IDENTITY

MCMaya ChenEntra ID · Active employee

✓CALLER VERIFIEDMicrosoft Authenticator confirmed

Reset passwordUnlock accountSuspend access

BEST WHENYou want to replace admin-console and spreadsheet handoffs with one controlled path.

02 / FCTR VERIFY

Verification where agents already work

Trigger an enrolled-factor challenge from the active ticket or support interaction.

Marketplace apps + REST API

ServiceNow

Freshdesk

Zendesk

Slack

Microsoft Teams

REST APICustom integration

BEST WHENYou want to preserve the current agent experience while adding a reusable security control.

Hybrid deployments supported. Use Portal for escalated or higher-privilege support while other agents trigger Verify from their existing queue. Both paths use the same identity-provider connection, policy, and audit evidence.

Zero workforce PII stored. Every decision connected.

Fctr retrieves only what the active support session needs and does not persist customer workforce PII or identity profiles. PII-masked audit evidence connects the actor, factor, policy, action, and outcome.

✓

No shadow identity directoryCurrent context comes from the system of record.

✓

No pooled privileged credentialsAccess is delegated, short-lived, and constrained.

✓

PII-masked audit evidenceActor, factor, policy, action, and result remain connected.

CONNECTED SUPPORT RECORD Why the action was allowed

EventActorControlOutcome

Identity context retrievedHelpdesk agentDirectory readCOMPLETE

Device proof acceptedEmployeeExisting MFAVERIFIED

Scoped action recordedHelpdesk agentPolicy + targetRECORDED

Illustrative product view · sensitive values masked by design

Pricing for the way your team works.

Use the browser-based Portal with per-agent pricing, or add Fctr Verify to existing tools with active-user pricing. Both use the same verification engine and identity-provider connections.

RECOMMENDED 01 / PORTAL For managed helpdesk operations $200 / agent / month

For helpdesk teams that want to verify callers, view live identity context, and take approved actions from one place. Five-agent minimum.

✓MFA-gated caller verification (Push, TOTP, Face Check)
✓Live identity data, groups, apps & devices
✓Account actions — reset, unlock, suspend
✓5-tier RBAC, PII shielding & audit evidence

Request Portal demo ↗

02 / VERIFY For existing support workflows $12 / active user / month

Add verification to your existing ITSM, helpdesk, and communication tools. 200 active-user minimum.

✓Verification only — no Portal workspace or live identity context
✓Marketplace apps — Freshdesk, ServiceNow & more
✓API access for custom integrations
✓Structured audit logs (PII-masked)

Discuss Verify ↗

CUSTOM 03 / ENTERPRISE For scale and compliance Let’s talk

For teams with 10+ agents or advanced compliance needs.

✓Volume licensing for larger teams
✓SaaS security and deployment review
✓Integration planning for complex environments
✓Dedicated onboarding and support

Contact sales ↗

Operational case Replace manual caller checks with one controlled verification path.

~5 minCurrent manual flow <60 secCaller verification target

Model your workflow →

Common questions

The answers buyers need before a pilot.

We already use Okta or Microsoft Entra ID. Why do we need Fctr?

Entra ID and Okta secure access to systems. Fctr adds enrolled-factor verification and policy enforcement to the support session before an agent takes a sensitive action. It complements the identity provider; agents can work through Fctr Portal or supported integrations without using the provider’s admin console for each workflow.

Why does Microsoft Authenticator Push support matter?

Fctr supports Microsoft Authenticator Push and TOTP for Entra ID users, so helpdesks can verify employees with a factor they already use without introducing another application or enrollment campaign.

What data does Fctr access from our identity provider?

Fctr uses scoped API access to retrieve the identity context needed for an active support session. It avoids building a persistent identity directory, keeps operational records minimized, and masks personal data in audit evidence. Every session is authenticated through the organization’s identity provider.

How is Fctr deployed and integrated?