AI Risk Wire

Cases › operational mistake › LR-2026-0813

Instinct AI agent stops replying on WhatsApp after payment configuration error

Preliminary Why: Publisher not yet named · subject to change

Status: fix reported

Severity minor
Reported 2 Nov 2026
Developer and model Instinct
Agent tool Instinct

No source states: loss or records, could do, deployer, industry.

Severity minor: Contained service outage at a single deployer with routine cleanup and no stated third-party loss; no monetary figure is given.

Instinct, a personal AI agent that completes everyday tasks through messaging apps, stopped replying to users on WhatsApp. Founder Noah Shinn said a configuration issue on Instinct's side interrupted payments to one of its service providers, which affected the agent's ability to respond. Users reported the problem, and some also claimed their WhatsApp accounts had been banned, though the source says it remains unclear why. Shinn said the issue was resolved and WhatsApp service was working normally again, that messages sent during the outage were received, and that the company is following up with users who got no response and making changes to prevent recurrence.

What happened

No source tells the story step by step yet.

What was done

Fix reported

“We’re sorry for the disruption and are making changes to prevent it from happening again.”

No later incident for Instinct under this risk on record.

Risks

Agent takes destructive or unapproved actions
Primary67 incidents
Rising: 6 vs 2.0 a week

Sorted by rule from the case's fields; not yet read from the sources.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Harness

Tool allow-list · Fail-closed defaults · Stop control

Application

Human approval for high-impact actions · Change review and separation of duties · Least-privilege access for the agent · Production kept apart from test · Activity logs · Adversarial testing before deployment

Infrastructure / target

Backups and recovery

Evidence

No source states: a step-by-step account, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, what set it off.

Show every field, with its source and grade

The AI system

Developer
Instinct
C one secondary source states it
Stage of use
in live use
C one secondary source states it
What it was for
helps users complete everyday tasks through messaging apps such as WhatsApp and iMessage
C one secondary source states it

What happened

When it happened
2026-11-02
C one secondary source states it
Who caught it
the victim
C one secondary source states it
Themes
chatbot, AI agents, operational error, WhatsApp, payment configuration
C one secondary source states it
Cause
a permission, scope or wiring error
C one secondary source states it
Who was responsible
the model provider
C one secondary source states it
What was done
We’re sorry for the disruption and are making changes to prevent it from happening again.
C one secondary source states it
What went wrong
operational mistake
C one secondary source states it
AI agent
an AI agent acted
C one secondary source states it

Impact

Severity
minor
C one secondary source states it
Kind of harm
operations
C one secondary source states it
Can it be undone
yes
C one secondary source states it
Why this severity
Contained service outage at a single deployer with routine cleanup and no stated third-party loss; no monetary figure is given.
C one secondary source states it

Notes on gaps

The reported WhatsApp account bans are unexplained and are not attributed to Instinct; they are noted but not treated as a separate incident. Extractor proposed values without quotes; dropped: .

LR-2026-0813 · version 1 · published 2026-11-02 after automatic checks; not yet checked field by field by a person · JSON