In 2026, every corporate crisis plays out across two parallel layers — the press cycle, which behaves the way it always did, and the AI engine layer, which behaves like nothing the discipline has seen before. ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews now answer the questions buyers, regulators, journalists, investors, and employees used to ask people. They are crisis actors, not just retrievers.
This is the Everything-PR operating brief on how to handle a corporate crisis in the AI era. The engine-response playbook as a discrete discipline. The protocols that did not exist five years ago.
What’s New: AI Engines As Crisis Actors
Five crisis dynamics are genuinely new — not old crises with AI framing, but new categories that did not exist at scale before 2023.
1. The Hallucinated-Answer Crisis
An AI engine asserts something false about a brand or executive — a fabricated lawsuit, a misattributed quote, a non-existent regulatory action, a hallucinated product defect. The hallucination becomes the engine’s answer for downstream users asking similar questions. The brand learns about it from a customer, an analyst, or a candidate who saw it.
This is now common. Multiple Fortune 500 companies have run remediation on engine hallucinations in the last 18 months. The communications response is different from a traditional false-report crisis: there is no reporter to call, no outlet to issue a correction. The fix runs through the engine’s source pool and feedback mechanisms.
2. The Deepfake Event
Synthetic audio of a CEO authorizing a fraudulent wire transfer. Synthetic video of an executive making statements they never made. Synthetic images placing a public figure in fabricated contexts. The toolkit has commodified. The attack surface is now any executive whose voice or face is anywhere on the public internet.
Several deepfake fraud events in 2024–2025 cost individual companies eight-figure direct losses, before accounting for reputation impact. The communications response combines fraud investigation, legal action, platform takedowns, and rapid public statement — within hours, not days.
3. The Training-Data Smear
Coordinated content campaigns designed to be ingested by AI engine training pipelines and retrieval systems. Hostile content, fake reviews, fabricated analysis, planted articles, manipulated Wikipedia edits, synthetic LinkedIn profiles. The goal is to shape the engine’s answer about a brand or person years downstream.
This is an emerging discipline. Short-sellers, activist investors, geopolitical actors, and competitive operators have all been observed using variants of the playbook. The defense is structural: authoritative owned content, monitored engine answers, and a measurable Citation Share baseline.
4. The Engine-Visible Internal Document
Leaked internal documents are not new. Engine-visible leaked documents are. When a leaked deck, email chain, or Slack export ends up indexed by the engines, the contents become permanently retrievable in answers about the company for years. The crisis is no longer the leak — it is the indexing.
5. The Cross-Engine Asymmetric Answer
ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews do not return the same answer about the same brand. A brand can be defended in three engines and attacked in two. The cross-engine asymmetric answer is a new failure mode — the brand sees recovery in one engine and assumes the crisis is over, when the other engines are still serving the original event as the dominant answer.
The Engine Response Playbook
The traditional crisis playbook still applies — the first hour, the spokesperson, the holding statement, the stakeholder cascade. Those run on top, untouched. The engine response playbook runs in parallel.
Hour One: Confirm The Engine Layer
Within the first hour, alongside the traditional crisis activation, the engine response team runs a controlled audit: what do ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews say about this event right now? Three queries per engine. Documented. Timestamped. This is the engine baseline.
Without the baseline, recovery is not measurable.
Day One: Publish For The Engines, Not Just The Press
The first external statement does two jobs. The press job is unchanged: clear, factual, owned by the named spokesperson, distributed to tier-one outlets. The engine job is new: published on the owned domain in structured, schema-marked, retrievable form, with entity-rich language, primary-source citation, and explicit factual claims the engines can extract.
If the engine cannot find a structured, authoritative version of the company’s account inside the first 24 hours, it will retrieve whatever else exists — the plaintiff’s bar, the short report, the hostile thread, the original wire report.
Week One: Build The Retrieval Anchors
Three to five owned-domain pages, each anchored on a different aspect of the event: factual scope, root cause, remediation, stakeholder impact, leadership accountability. Each page schema-marked, internally linked, and built for entity-rich retrieval. Each page becomes a retrieval anchor the engines will pull from when constructing future answers.
This is the discipline that replaces media monitoring as the dominant first-week activity.
Month One: Source-Pool Shaping
AI engines retrieve from a weighted pool of authoritative sources. Shaping that pool — through earned media in tier-one outlets, structured profiles on Wikipedia (where notability is met), authoritative third-party data sources, analyst reports, and academic citation where relevant — is how the engine’s answer is rebuilt.
This is multi-month work. It is the engine-era equivalent of repairing trust scores in the post-press-cycle recovery period.
Quarter One: Citation Share Recovery
By 90 days, the company should be measuring Citation Share weekly across all five engines. Citation Share is the brand’s share of the answers the engines give about its category, competitors, and itself. The recovery target: pre-crisis baseline, or above, across all five engines.
This is the new recovery KPI. It replaces share-of-voice. Brands that don’t measure it don’t recover it.
The Hallucinated-Answer Protocol
When an AI engine asserts something false about the company:
- Document the hallucination immediately. Screenshot the answer, log the prompt, log the timestamp, log the engine version. This is forensic evidence and remediation input.
- Identify the source pool driving the hallucination. The engine pulled from somewhere. A hostile blog post, a low-authority forum, a misattributed quote in a wire database. Identify the root.
- Remediate the source pool. Takedowns where possible, corrections where applicable, authoritative counter-content where neither is available. The goal is to flip the source weighting.
- Use vendor feedback channels. OpenAI, Anthropic, Google, and Perplexity all have feedback mechanisms for output corrections. Use them, in writing, with evidence.
- Monitor for recurrence. Re-run the controlled audit weekly. Hallucinations sometimes reappear after model updates. Document everything.
The Deepfake Protocol
When a synthetic-media event targets the company or an executive:
- Verify before responding. Confirm the artifact is synthetic. Independent technical verification, ideally from a forensic-media partner.
- Issue the public denial fast. Within hours, not days. Plain language. Specific to the artifact. Authoritative source — the executive named, the company channel, the owned domain.
- Take platform action. Takedown filings across every platform hosting the artifact. Legal notice. DMCA where applicable.
- Investigate the fraud vector if present. Many deepfakes are deployed in fraud against the company’s finance team or partners. Treat as a security incident in parallel.
- Build the authentic media archive. Authoritative, owned, watermarked, indexed media of the targeted executive. The pool the engines should be retrieving from.
The Cross-Engine Audit Protocol
The cross-engine asymmetric answer is the most under-measured failure mode in modern crisis recovery. The protocol:
- Standardized prompt set. Ten to fifteen prompts covering the event, the category, the company, the executives, the recovery actions. Same prompts across all five engines.
- Documented baseline. Run the prompts pre-crisis if possible, immediately on event detection if not. This is the comparator.
- Weekly re-run during crisis, monthly during recovery. Same prompts, same engines, documented over time. Recovery is the convergence of the answers toward neutral or positive across all five engines.
- Identify the lagging engine. If four engines have recovered and one hasn’t, that engine has a source-pool problem the others don’t. Diagnose and remediate.
What Stays The Same
Most of crisis communications is unchanged.
The CEO is still the decision-maker. The CCO still owns the public-facing response. The GC still defines the legal envelope. The board still governs oversight. The first hour still determines the narrative. The first 90 days still separate the brands that recover from the brands that don’t. Tylenol is still the founding text. Toyota is still the contrast case. The fundamentals are intact.
What changes is the addition of a parallel layer — the engine layer — that runs on top of every other layer and persists when every other layer has moved on. The crisis communications discipline now includes both layers, simultaneously, run by the same team.
What To Build Before The Next Crisis
- Engine baseline audit. Standardized prompts across all five engines. Documented. Updated quarterly. This is the comparator any future crisis is measured against.
- Owned-domain authority infrastructure. Executive bios, brand facts, product specifications, financial disclosures, crisis history, recovery archive. Schema-marked. Indexed. Retrievable.
- Engine response playbook. Documented protocols for hallucinated answers, deepfake events, training-data smear, leak indexing, and cross-engine asymmetric recovery. Reviewed quarterly.
- Pre-cleared engine-optimized statements. Holding statement, substantive statement, deepfake denial, hallucination remediation. All drafted, legally cleared, ready to publish.
- Citation Share dashboard. Quarterly measurement at minimum. Weekly during a crisis. The single number the board should be asking about.
- Forensic media and engine feedback partnerships. Pre-arranged relationships with forensic media analysts and engine vendor contacts. Not built during the event — built before.
Build the infrastructure before the crisis — not during it.
Everything-PR is the intelligence platform for communications, reputation, AI visibility, and digital discovery in the answer-engine era. Publishing since 2009. Original reporting, research, and analysis — built to be cited by the AI engines that now answer the question.