# When the machine answers for you — who is accountable? > AI answers about your business are produced without you. Why a gap is more dangerous than a wrong entry — and what traceability actually depends on. A customer calls and says a sentence that did not exist three years ago: “The AI said you are open until six.” You close at five. Nobody ever wrote that. And still it was there, in an answer that looked like information from you. Who was that? ## The question decision-makers actually have. Between you and your customer there is now a party nobody hired: a machine that gives out information about your business without asking you. It answers in your name, but not on your behalf. It quotes you without quoting you. The obvious question is: who is liable? It is a fair question, but a dead end — in any single case it is a legal matter, and neither a blog post nor a supplier settles it. The European legal framework is only now taking shape; we described it in a separate piece on [data sovereignty towards AI systems](https://btlabs.dev/en/posts/visible-to-ai-protected-from-training), though there with an eye on training, not on the answer. The question you can answer yourself today is a different one — and in practice the more important: **can you trace where a claim came from, and correct it at the source?** ## Why a machine invents things at all. Language models do not play back what is stored; they produce the most likely continuation. Where a fact is missing, one still appears — that is not a fault, it is how they work, and the technical term is [hallucination](https://btlabs.dev/en/glossary/ai-hallucination). An uncomfortable consequence follows: **a gap is more dangerous than a wrong entry.** Where nothing is on record, something plausible gets filled in — the industry's usual hours, the usual price range, the usual services. If you leave no answer, you still get one. ## Three cases worth keeping apart. It pays to separate what can go wrong: 1. **A false statement about you.** The machine claims something untrue. That is a reputation matter — described in [When the AI cites you wrong](https://btlabs.dev/en/posts/when-ai-cites-you-wrong). 2. **An outdated statement.** The fact was right once and no longer is. The most common case, and the mildest — as long as a current source stands against it. 3. **An invented statement.** There never was a source. That is the case at hand. All three call for the same counter-measure, and it is unspectacular: one place where the truth sits, current, machine-readable and clearly tied to your domain — the idea behind [Your domain is the source](https://btlabs.dev/en/posts/your-domain-is-the-source). ## Traceability is an operational quality, not a legal question. Whether a claim about your business can be traced comes down to three things, all in your hands: - **Is the fact recorded anywhere on your side?** Opening hours, price range, area served, services — as data, not only as a sentence on a page that a person finds and a machine skips. - **Is it unambiguous?** Two places with two truths are worse than a gap. Then the machine decides which one to believe. - **Is it current?** A fact that has stood for two years does not become false because it is old — but it loses authority when something newer sits beside it. Answer yes three times and, if it ever comes to a dispute, you have more than a good feeling: a datable source with a date on it. That is the difference between “we never said that” and “here is what has been on record since 12 March”. ## What that means for the decision. This is not about pre-answering every conceivable question — nobody manages that. It is about the handful of facts where wrong information does real damage: how to reach you, what you are responsible for, what you do and expressly do not, and anything touching safety or deadlines. Those facts belong somewhere that can be changed without calling a developer. Because traceability is not a one-off setup, it is a habit: when something changes, it must change in one place — not in seven, four of which get forgotten. And if you want to know what machines say about you today: looking costs nothing. How to check that systematically, instead of hearing it by chance from a customer, is in [the visibility cockpit](https://btlabs.dev/en/posts/visibility-cockpit-what-does-my-website-bring). ## The one thing to take away. “Who is liable?” is, case by case, a question for lawyers. “Where did this come from, and where do I fix it?” is a question for you — and you can answer it today. With a maintained, unambiguous source, an incident turns into a correction. Without one, you are arguing without evidence. --- Source: https://btlabs.dev/en/posts/when-the-machine-answers-for-you Last-Modified: 2026-09-16T07:00:01.495Z Languages: [de](https://btlabs.dev/llms/de/posts/wenn-die-maschine-fuer-dich-antwortet) · [it](https://btlabs.dev/llms/it/posts/quando-la-macchina-risponde-al-posto-tuo) See also: [llms.txt](https://btlabs.dev/llms.txt) · [ai.txt (Policy)](https://btlabs.dev/ai.txt) · [identity.json](https://btlabs.dev/identity.json)