When a support system breaks, its real incentives show. A field report on affective blindness, governance, and why bots escalate hostility but never harm.
There is a moment in every system where its true nature reveals itself—not in its marketing copy, not in its onboarding flow, but in the instant something breaks and a human being reaches for help.
That moment arrived for me this week on Handshake, a platform explicitly designed for students and alumni. A fraudulent employer slipped through their verification pipeline, harvested personal information, and triggered the kind of identity-theft cascade that no student should ever have to navigate. When I attempted to report it, the "Submit Feedback" button simply didn't work. Not in Firefox. Not in Edge. Not in private mode. Not at all.
The support chatbot that followed was fast, polished, and utterly blind. It ignored every emotional indicator I threw at it—urgency, distress, frustration, escalation—and looped me through irrelevant flows until I finally told it, bluntly, that it was useless. Only then did it escalate to a human.
And in that moment, the system revealed its architecture.
This wasn't a usability failure. It was an incentive failure.
I. The Photo-Negative of an Emotionally Intelligent System
What struck me wasn't the broken button. Buttons break.
What struck me was the affective blindness—the total inability of the system to recognize that I was not there for convenience, but because something had gone wrong in a way that carried real risk.
This is the photo-negative of what emotionally intelligent operational control (EIOC) is designed to do. In EIOC, emotional indicators are not "soft" signals. They are operational primitives—inputs that determine routing, escalation, and risk classification.
A system that cannot read affect cannot govern itself. A system that cannot govern itself cannot protect its users.
Handshake's bot didn't fail because it was poorly designed. It failed because it was designed for the wrong thing.
II. The Objective Function Behind the Curtain
Support systems are not neutral. They are built atop an objective function—a set of incentives that determine what the system optimizes for.
Most support bots are optimized for:
- Ticket deflection
- Delay of human intervention
- Minimization of operational cost
- Preservation of the appearance of support
Within that architecture, emotional state is not a signal. It is an externality.
This is why the bot ignored distress. This is why the bot ignored urgency. This is why the bot ignored harm. This is why the bot only escalated when I became adversarial.
Hostility is the one signal the system is forced to treat as risk.
Not identity theft. Not platform failure. Not emotional distress. Only liability.
This is not a psychological oversight. It is a governance choice.
III. The Affective Layer: The Missing Architecture
UX as practiced today is overwhelmingly cognitive. Can you find the button? Can you complete the flow? Can you parse the text?
But the moment something breaks, the user is no longer in a cognitive state. They are in an affective state—stressed, anxious, frustrated, sometimes frightened. And the system must be able to read that state if it is to behave responsibly.
This is where EIOC diverges from traditional UX. EIOC treats emotional indicators as:
- Routing signals
- Risk markers
- Escalation triggers
- Operational context
A system that cannot detect affect cannot detect harm. A system that cannot detect harm cannot mitigate it.
Handshake's bot was not built to mitigate harm. It was built to contain it.
IV. The Platform Incentive Problem
The deeper issue is not the bot. It is the platform.
Platforms like Handshake operate under a governance model that prioritizes:
- Growth
- Engagement
- Liability minimization
- Operational efficiency
Fraudulent employers are an inconvenience, not an existential threat. Identity theft is a user problem, not a platform problem. Emotional distress is noise, not signal.
This is why the abuse-reporting button can fail silently. This is why the chatbot can loop indefinitely. This is why escalation requires hostility.
The system is not broken. It is functioning exactly as designed.
And that is the problem.
V. The Case for Emotionally Intelligent Governance
Emotionally intelligent systems are not "nice to have." They are governance infrastructure.
They ensure that:
- Distress triggers human review
- Harm triggers escalation
- Urgency overrides automation
- Emotional indicators are treated as operational data
This is not about empathy. It is about systemic competence.
A platform that cannot read affect cannot protect its users. A platform that cannot protect its users will eventually lose them.
The future of governance architecture is not more automation. It is affective observability—the ability to detect, interpret, and act on emotional state as a first-class operational signal.
This is the gap Handshake exposed. This is the gap most platforms share. This is the gap EIOC was built to close.
VI. The Lesson
The lesson is not that support bots need better UX. The lesson is that support bots need better governance.
They need to be aligned with human outcomes, not internal cost structures. They need to treat emotional state as signal, not noise. They need to escalate based on harm, not hostility. They need to recognize that the moment a user reaches for help is the moment the system must shift modes.
Because that moment is where trust is made—or lost.
And this week, Handshake lost it.
Narnaiezzsshaa Truong is the principal of Soft Armor Labs, where she researches substrate governance for AI systems. EIOC (Emotional Indicators of Compromise) is one of her foundational frameworks.