The next enterprise breach starts with a phone call.

Fctr helps your workforce verify callers in both directions.

Helpdesks can verify employees calling for support. Employees can verify unexpected IT callers. Use the verification methods your organization already manages.

  • Uses your existing MFA
  • No shadow directory
  • 60-day hands-on pilot

Workforce identity verification

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
  • Entra Verified IDFace Check
  • TOTP
  • SMS OTP
  • Email OTP
Integrations
  • ServiceNow
  • Zendesk
  • Slack
  • Freshdesk
  • Teams
  • Verification API

A familiar voiceis no longer enough.

AI voice cloning and spoofed numbers broke verbal verification. Security questions and caller ID won’t stop a determined imposter—verified proof from your organization’s authenticators will.

41%

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

Source: Gartner, September 2026

Not just the helpdesk.Verify before you act.

Three moments to verify who’s asking.

01 · Employee → Helpdesk

Lockouts & account recovery

Verify an employee before resetting a password or unlocking an account.

Explore Portal
02 · IT → Employee

Inbound “IT support” calls

Give employees a way to verify an unexpected IT caller before sharing their screen.

See IT caller flow
03 · Colleague → Colleague

Finance, HR & executive requests

Where enabled, verify a colleague before changing payroll details or acting on an urgent payment request.

See colleague checks

One platform.Both sides of the call.

More than a standalone verification tool. Fctr unites helpdesk verification, governed recovery, and Teams/Outlook checks in one cohesive portal and audit trail.

Fctr Portal · For helpdesks

Verify the caller.
Restore access safely.

One workspace to verify callers, check live Entra ID or Okta context with personal PII masked, and run only the support actions allowed by your role and policy.

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 · For employees

Verify who’s calling
before you act.

One-time verification phrases and colleague checks inside Teams and Outlook—so staff never have to guess who’s on the line.

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 Private beta

Verify colleagues
from your phone.

A colleague confirms your request with a fresh biometric check or an organization-permitted passcode on their device. Available by invitation.

See Fctr Mobile in a demo
Fctr Mobile, private beta — available by invitation. Check pending requests and an expanded Request verification area with Find a recipient.

Use the authenticatorsyou already manage.

Verify callers using supported methods already enrolled in Microsoft Entra ID or Okta, from authenticator push to passkeys.

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.

Keep agents in their tools.Add verification where they work.

Use Fctr Portal or embed caller verification in ServiceNow, Zendesk, Freshdesk, Slack, or custom apps through supported integrations.

Works with your tools

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

Every support action.Auditable down to the proof.

No more “verified verbally” ticket notes. See who acted, which factor proved identity, why policy allowed the action, and the outcome in Portal’s PII-masked audit trail.

Example record · Why access was restored

Events in a governed support interaction
EventActorControlOutcome
Live directory context retrievedHelpdesk agent (J. Patel)Scoped Entra ID read · PII maskedComplete
Enrolled-factor proof acceptedMaya Chen (Finance)Microsoft Authenticator PushVerified
Temporary Access Pass issuedHelpdesk agent (J. Patel)Agent role + non-privileged policyRecorded

Live context, no shadow directory

Identity context is retrieved for the active support session—never copied into a standing workforce database.

Zero broad admin roles

Give helpdesk agents the exact recovery actions they need without assigning broad Entra ID or Okta admin privileges.

Dedicated customer environment

Fctr uses separate customer tenants for most platform components, helping reduce cross-customer exposure.

Start with the coverage you need.Expand when you’re ready.

Begin with helpdesk coverage, add two-way verification, or scope an enterprise rollout—tailored to your environment.

For helpdesks

Helpdesk verification

Verify callers and govern account recovery.

  • Fctr Portal workspace (Entra ID & Okta)
  • Existing-factor caller verification
  • Live directory context with PII masked
  • Scoped resets, unlocks, TAP & TAC
  • Role controls, exclusions & audit trail
  • Dedicated customer environment
Request pricing

Custom quote

Enterprise

For larger organizations needing tailored rollout and commercial terms.

Start with either plan, plus:

  • Tailored quote scoped to your needs
  • Rollout across teams and business units
  • Dedicated onboarding & architecture review
  • Guided 60-day pilot, security review & DPA
Talk to us

Fctr Mobile Private beta

Verify colleagues from your phone.Mobile pricing will be announced soon.

See Fctr Mobile in a demo

Already work in ServiceNow or Zendesk?

Add supported integrations to either plan.
Scoped and quoted for your deployment.

A few thingsworth 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 is Fctr?

Fctr provides workforce identity verification (IDV) in one complete platform—not a one-off caller-verification tool. It combines Fctr Portal for live context, verification, and governed recovery with native Teams and Outlook apps, using your existing managed methods.

What is the difference between Fctr Portal and Fctr Verify?

Fctr Portal gives agents one workspace to find users, verify callers, and perform approved support actions. Fctr Verify brings identity verification into existing support tools and configured employee apps in Teams or Outlook. Where enabled, employees can also verify colleagues making HR, payroll, or finance requests. Choose either or combine them.

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. Fctr Mobile offers a separate standalone biometric path in private beta, available by invitation.

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. See the security model and DPA.

How does Fctr help with AI voice cloning and deepfake vishing?

Fctr helps address AI voice cloning and deepfake impersonation by checking identity through supported organization-managed methods, rather than trusting a familiar voice, face, or caller ID. It does not detect synthetic audio or video. Available verification methods and their assurance depend on your provider, configuration, and policy.

Watch a live verification.Not a slide deck.

See both sides of caller verification live, without connecting your tenant. Plan for about 30 minutes.

01
Live walkthroughShaped around your helpdesk, IT, and colleague call scenarios.
02
Test the call experience yourselfSee both sides of verification in real time.
03
Optional 60-day hands-on pilotConnect your identity provider and validate with your own team.

A product specialist—not a cold-call script—will reply within one business day.

Prefer email? [email protected]

Request a live demo

Tailor my demo Optional

Used only for this request. No spam. Privacy policy.