Legal and financial firms targeted
Active vishing campaigns impersonate internal IT to bypass helpdesk checks.
AdvisoryFctr 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.
“Hi, I’m Alex. I need a password reset.”
“Let’s verify your identity first.”
Alex Morgan · Helpdesk
Identity providers
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.
of CISOs surveyed reported a deepfake social engineering incident during an employee audio call in the previous 12 months.
Source: Gartner, September 2026Active vishing campaigns impersonate internal IT to bypass helpdesk checks.
AdvisoryProsecutors say callers posed as executives and attorneys to persuade employees to authorize transfers.
DOJ releaseAttackers use ordinary employee names in malicious Teams calls to gain remote access.
Microsoft reportThree moments to verify who’s asking.
Verify an employee before resetting a password or unlocking an account.
Explore PortalGive employees a way to verify an unexpected IT caller before sharing their screen.
See IT caller flowWhere enabled, verify a colleague before changing payroll details or acting on an urgent payment request.
See colleague checksMore 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
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 Verify · For employees
One-time verification phrases and colleague checks inside Teams and Outlook—so staff never have to guess who’s on the line.
Teams · Outlook · Supported integrations
Fctr Mobile Private beta
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 demoVerify callers using supported methods already enrolled in Microsoft Entra ID or Okta, from authenticator push to passkeys.
Uses the employee’s existing enrollment.
Uses the employee’s existing enrollment.
Credential and face-match verification for supported employee workflows.
Available where configured for the workflow.
Use Fctr Portal or embed caller verification in ServiceNow, Zendesk, Freshdesk, Slack, or custom apps through supported integrations.
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.
| Event | Actor | Control | Outcome |
|---|---|---|---|
| Live directory context retrieved | Helpdesk agent (J. Patel) | Scoped Entra ID read · PII masked | Complete |
| Enrolled-factor proof accepted | Maya Chen (Finance) | Microsoft Authenticator Push | Verified |
| Temporary Access Pass issued | Helpdesk agent (J. Patel) | Agent role + non-privileged policy | Recorded |
Identity context is retrieved for the active support session—never copied into a standing workforce database.
Give helpdesk agents the exact recovery actions they need without assigning broad Entra ID or Okta admin privileges.
Fctr uses separate customer tenants for most platform components, helping reduce cross-customer exposure.
Begin with helpdesk coverage, add two-way verification, or scope an enterprise rollout—tailored to your environment.
For helpdesks
Verify callers and govern account recovery.
For helpdesks + workforce
Protect both ends of every high-stakes call.
Everything in Helpdesk, plus:
Custom quote
For larger organizations needing tailored rollout and commercial terms.
Start with either plan, plus:
Verify colleagues from your phone.Mobile pricing will be announced soon.
Add supported integrations to either plan.
Scoped and quoted for your deployment.
Explore the workflows in detail, or bring your questions to a demo.
Read the documentationAuthentication 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.
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.
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.
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.
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.
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.
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.
See both sides of caller verification live, without connecting your tenant. Plan for about 30 minutes.
A product specialist—not a cold-call script—will reply within one business day.
Prefer email? [email protected]