Safety & Security

Humanix launches call context for voice-led account attacks

Humanix's Complete Call Context links service desk calls with identity, ticket and policy records to expose manipulation around MFA resets, but it does not block changes.

Humanix Launches Complete Call Context to Detect Service Desk Voice Attacks
Humanix Launches Complete Call Context to Detect Service Desk Voice AttacksMV-Fotos / pixabay
By Sophie Lindqvist6 min read

Why it matters

  • Humanix launched Complete Call Context and made it available to Humanix customers.
  • Each sensitive request gets a micro-agent that checks caller claims against identity and ticketing records.
  • Alerts include a severity rating, an explanation, the call, the account change and supporting findings.
  • Complete Call Context provides detection and alerting; Humanix does not claim it blocks every reset or reverses account changes.
  • Backed by Acrew Capital, Boldstart Ventures and Evolution Equity Partners, Humanix is a 2026 RSAC Innovation Sandbox Top 10 finalist.

By Sophie Lindqvist

Humanix has launched Complete Call Context, a security capability that connects service desk conversations with identity records, support tickets and an organization’s account-recovery procedures. Humanix customers can access the feature, which extends the company’s Human Threat Detection and Response platform. The target is voice-based social engineering that can disappear inside an otherwise routine password reset or multifactor authentication change.

What gap does Complete Call Context address?

Humanix says account logs can accurately show that a help desk employee enrolled a new multifactor authentication factor. Those logs can reveal little about whether an attacker persuaded the employee to bypass the checks meant to protect the account.

The company calls this the gap between an authorized action and the conversation that prompted it. A valid action can conceal the deception behind it.

Humanix frames this as a timing problem, not merely a logging problem. In the launch announcement, Humanix founder and CEO Keith Stewart said: “AI-assisted attackers can now go from a single phone call to a full compromise in minutes.” “Controls that only engage after the call can’t keep up.”

In plain terms, the log records the authorized action but can miss the pressure that produced it. Defenders need both sides of that event.

How do the micro-agents investigate a request?

According to Humanix, Complete Call Context creates a micro-agent for each sensitive service request, such as a multifactor authentication reset. The organization’s procedures determine which evidence matters. The agent then compares the caller’s statements with relevant identity and ticketing records inside one investigation.

Humanix says each micro-agent identifies the evidence required by the company’s own account-recovery process. It checks the interaction against records held in identity provider and IT service management systems. A contradiction or missing piece of required evidence produces an alert with a severity rating and an explanation of the discrepancy.

Humanix’s example starts with a caller who claims to manage an employee and asks for a multifactor authentication reset. The caller supplies a ticket number and says the employee has already completed identity verification. Humanix turns each statement into a separate check:

  • Whether the directory identifies the caller as the employee’s manager.
  • Whether the supplied ticket exists.
  • Whether the identity provider records the claimed verification event.

If the directory names a different manager, the ticket cannot be found, or the identity provider has no matching verification event, Humanix says the alert connects those findings to the required procedure. The company presents these as illustrative discrepancies, not proof that every missing record represents an attack.

Humanix’s supplied product image shows that reasoning in one view. Call evidence, account activity and policy checks receive labels for compliant, indeterminate or violated. The display makes the relationship between a suspicious request and the resulting access change easier for an analyst to see.

In plain terms, the feature checks whether the caller’s story matches the records and the company’s rules. It does not treat a gap as an automatic verdict.

What does conversational AI add to the records?

Humanix says its broader platform analyzes calls as they happen and uses conversational AI to identify manipulation, impersonation and attempts to bypass required procedures. Through APIs, it connects with enterprise communication and service systems. The platform evaluates the language, identity claims, behavior and workflow context around each interaction.

That is different from asking only whether a voice is synthetic. Humanix says a caller can use their own voice and still impersonate a manager or pressure a support worker to skip verification. A convincing voice therefore does not establish that the requested action is authorized.

Complete Call Context adds corroboration to that conversational analysis. Instead of relying only on how persuasive or suspicious a conversation sounds, it tests each claim against operational evidence. The difference matters because conversational signals can identify manipulation while records test whether required steps actually happened.

That sequence matters because each check can fail independently. A real ticket may exist, but the directory may name a different manager. The identity provider may contain no matching verification event.

Humanix combines those answers with call evidence and evaluates them against the organization’s procedure. The system does not use a mismatch as a stand-alone verdict.

In an earlier Unite.AI interview, Humanix founder and CEO Keith Stewart described social engineering as an attack on business processes and trust. Complete Call Context puts that view into practice by tying a call to the records and checks that govern account recovery.

In plain terms, a convincing voice is only the opening claim, not proof of authorization. The records provide the cross-check.

What can an alert show—and what can’t it do?

Humanix says its platform analyzes calls as they happen, while Complete Call Context extends that view into systems of record. Each alert assembles the conversation, the resulting account change and the supporting findings. Security teams can then assess the sequence without first reconstructing it across separate tools.

The bundle separates three things an analyst would otherwise have to reconstruct. One is the conversation that requested access, another the account event that followed, and the third the policy evidence supporting or contradicting the request. Humanix says the alert links them in one place, making it an investigative record rather than a standalone warning that a password reset occurred.

Humanix describes this as detection and alerting. The release does not establish that the feature automatically blocks every reset or reverses an account change. Its usefulness depends on the evidence available from connected systems and the procedures against which each request gets evaluated.

In plain terms, the alert gathers evidence for a human decision. It does not itself block or reverse the change.

What should security teams weigh before adopting it?

The launch addresses a practical weakness in identity security: a sensitive action can be correctly logged while the deception behind it remains unseen. Connecting the caller’s claims, the organization’s verification requirements and the eventual account activity gives defenders a clearer basis for deciding whether a familiar support workflow has become an intrusion.

Humanix is backed by Acrew Capital, Boldstart Ventures and Evolution Equity Partners. The company was also named a 2026 RSAC Innovation Sandbox Top 10 finalist.

For enterprise security teams, the practical stakes sit in system coverage. Humanix says usefulness depends on the evidence available from connected systems and the procedures used for evaluation. A deployment without matching directory, ticket or identity-provider records would leave the micro-agent without corroboration it was designed to use.

Humanix’s release does not name the underlying models that power the micro-agents. It also publishes no accuracy, latency or false-positive benchmarks for Complete Call Context. That leaves customers without published figures for judging the feature’s detection accuracy, response speed or false-positive rate.

The next test for the product is whether connected systems supply enough verification detail to produce useful alerts without treating routine gaps as attacks. In plain terms, Humanix has positioned Complete Call Context as an investigative layer around existing account-recovery processes, not a preventive control that can stop every reset.

Source: unite.ai

Share this article:

More from Sophie Lindqvist

Sophie Lindqvist

Show full bio

Staff writer covering regulation, policy and their impact on artificial intelligence and machine learning at AI In Context.

749 articles

Related articles

  1. Human-in-the-Loop AI Safeguards Are Quietly Failing, Researchers Warn
  2. IBM Buys AuthMind to Watch What AI Agents Do After They Log In
  3. Incode's Know Your Agent Ties Every AI Agent to a Verified Human
  4. Grok Bot Can Now Place Phone Calls, Including Waiting 14 Minutes on Hold
  5. Salesforce Signs Deal to Buy Cresta, Betting on Voice Agents for Service

« Previous articleNext article »