When AI agents fail (and what to do)

Failure mode 1: Hallucinated facts

The model invents a specific-looking detail (a form number, a tax threshold, a court case, a regulation citation) that sounds plausible but is not real. This is the most dangerous failure mode because it is invisible: the made-up fact slots smoothly into otherwise correct prose.

Concrete examples that have appeared in real AI output for Israeli users: invented Bituach Leumi form numbers, wrong tax brackets that the model confidently asserts, made-up Knesset bill numbers, and shifted-by-one section numbers in citations of Israeli laws (the model swaps a real section for a number that does not exist, with no indication of uncertainty).

How to catch: any time the agent quotes a specific number, name, regulation, or threshold, treat it as unverified. The verify protocol below applies.

Failure mode 2: Training cutoff (stale data)

The model's training data ends at some point in the past. For anything that changed since then (laws, prices, fund returns, political events, product launches), the model either confidently states the old value or hedges vaguely. Israeli regulatory data changes constantly; this is a near-permanent issue.

How to catch: ask the agent directly ("what year are you confident this number is from?"). If it cannot give you a specific recent year (2025 or 2026), the value is suspect.

Failure mode 3: Missing your specific context

The model gives a generally-true answer that is wrong for your specific situation. "The standard severance pay rate is..." is true for most cases and wrong if the employee is under a Section 14 arrangement under the Severance Pay Law (which substitutes ongoing employer contributions for an end-of-employment lump sum, and changes the calculation entirely). Generic correctness with specific wrongness is one of AI's most common failure modes.

How to catch: tell the agent the specifics of your situation explicitly, even details you think are not relevant. Then ask "does anything in my situation change the standard answer?"

Failure mode 4: No sources

The agent produces an authoritative-sounding answer with no citations. You cannot verify it. You cannot defend it if challenged. This is fine for low-stakes tasks (drafting a casual email) and dangerous for high-stakes ones (a tax position, a legal argument, a medical decision).

How to catch: ask "what is your source for that?". If the agent cannot point to a specific government page, statute, or authoritative document, treat the answer as a starting point for your own research, not a finished answer.

Failure mode 5: Your data goes somewhere

This is not a hallucination failure; it is a privacy failure, and for Israeli professionals it is regulated. When you paste a client's contract, a patient's medical history, or an employee's salary data into a free-tier ChatGPT / Claude / Gemini, that data is sent to the provider's servers. On the free tiers and some paid tiers, the provider may USE that data to train their next model. Israeli Privacy Protection Law Amendment 13 (in force August 2025) treats client data as your responsibility: if you fed identifiable client information into a service that trained on it, you are on the hook.

Where the data actually goes, briefly:

• ChatGPT free tier: data is used for training by default. You can opt out in Settings → Data Controls. ChatGPT Team and Enterprise plans do NOT train on your data by default.
• Claude free + Pro tiers: Anthropic does not train on your conversation data by default for consumer plans (verify the current policy; it has changed). Claude Team and Enterprise plans add stronger contractual data protections.
• Gemini free + paid tiers: Google's data handling depends on which account (personal Gmail vs Google Workspace) you use. Workspace data has stronger protections; personal-account data has weaker ones.

How to catch (before the leak happens, not after):

• Before pasting client data: either redact identifiers (replace real names with "[CLIENT]", real ID numbers with "XXX-XXXX") or use the team/enterprise tier of your chosen platform.
• For anything truly sensitive (health records, criminal cases, financial accounts with account numbers), do not use a chat agent at all. Use a local-only tool, a manually-anonymized version, or a regulated workflow your professional body has approved.
• Read the data-handling page of your platform once a quarter; policies change.

If you are unsure whether your situation falls under Privacy Law Amendment 13, ask a lawyer who specializes in Israeli data protection. This is a real liability question, not a theoretical one.

Failure mode 6: Biased or weird Hebrew output

Hebrew output that sounds like a translation, uses unusual word order, or makes Hebrew grammar mistakes (gender disagreement, wrong plural forms, calques from English). This is a register failure, not a factual failure, but it damages your credibility when the output goes out under your name.

How to catch: read the Hebrew aloud. Hebrew written by AI often reads "almost right." A native Israeli reader detects this in seconds. If anything sounds off, ask the agent to rewrite in natural Israeli Hebrew, then re-read aloud.

Where to read more: search for "Israel Privacy Protection Law Amendment 13" plus your professional body's guidance (Israel Bar Association for lawyers, Institute of Certified Public Accountants in Israel for CPAs, Ministry of Health guidance for clinicians). Most professional bodies have issued AI-use guidance in the past 18 months.

The verify-before-trust protocol

Run this protocol on any AI output you plan to act on:

1. Spot-check one specific claim. Pick a number, a regulation, a name. Open the primary source (gov.il, kolzchut, official ministry page). Confirm the agent's claim matches. If it does not, the entire output is suspect.
2. Ask the agent to challenge itself. "What is the weakest claim in what you just said?" Often the agent will name the exact thing you should not trust.
3. Cross-check across two platforms. If Claude and ChatGPT both produce the same answer, your confidence goes up SLIGHTLY (modern frontier models share training data, so agreement is weak evidence). Primary-source verification (gov.il, kolzchut, official ministry pages) is the only strong evidence. If they disagree, dig deeper.
4. Read it aloud (Hebrew especially). Catches register issues that silent reading misses.
5. Time-box your trust. AI outputs about "current rates", "this year", "recently" decay fast. If the output is more than a week old, re-verify before relying on it.

When to escalate to a human

The "this is not advice" rule, in one sentence: if a mistake here will cost you serious money, legal trouble, health consequences, or a regulated penalty, do not trust an AI agent alone. Call a licensed professional.

Concrete escalation triggers:

• Any tax position where you are not 100 percent sure of the answer (even small amounts compound through penalties and interest) → CPA (ro'eh heshbon) or tax advisor (yo'etz mas)
• Legal documents that will be signed by any party → lawyer (orech din)
• Medical questions beyond information lookup → doctor
• Pension / investment decisions → licensed pension advisor (yo'etz pensyoni)
• Anything criminal, contested, or regulatory → professional in that domain

AI agents are excellent at preparing you for those conversations (organizing the question, drafting initial documents, summarizing options). They are not replacements for the conversations themselves.

The most common mistake in Chapter 5: trusting an AI's first answer because it sounds confident. AI agents are trained to sound confident even when they are wrong. Build the verify habit. It is the single highest-leverage skill in this entire course.