An answer quoted the wrong thing
An answer that quotes the wrong thing has almost always retrieved successfully and selected badly. The usual causes are two sources that disagree, a superseded document still sitting in the bank, or a retrieval budget spent on the wrong passage because the question was read as one line rather than as a conversation. Fix the sources, not the wording.
What the symptom looks like#
The reply is fluent, confident and specific, and the specific part is wrong. It names a term you no longer offer, or an answer that was true of one product and not the one being asked about, or a detail from a document somebody uploaded a year ago and forgot.
It is worth separating this from two neighbouring symptoms. A reply that says nothing useful and escalates instead is Knowledge being *absent*, which is a different page. A reply that invents a price or a warranty is not this at all — that is refused before it is written, and if you are seeing an invented commercial term it is a much more serious report.
What it means#
Grounding in Connect is retrieval over the Knowledge a workspace has supplied. There is no vector database and nothing is inferred from the wider world: the answer can only be as current, as consistent and as well-scoped as the sources behind it. A wrong citation is therefore evidence about your sources first and about the model second.
That is a more useful diagnosis than it sounds, because it makes the problem reproducible. The same question against the same sources selects the same material, so a wrong answer can be examined rather than blamed on a bad day.
The likely causes, most common first#
| Cause | How it shows | Where it is fixed |
|---|---|---|
| Two sources disagree | The answer is right in one document and wrong in another; different questions get different versions | Resolve the conflict explicitly — one source wins, and the loser is removed or corrected |
| A superseded document is still present | The answer was true last year | Remove or replace the old source; keeping both and hoping the newer wins is not a strategy |
| The wrong passage fit the budget | The cited material is on-topic but answers a neighbouring question | Narrow the source, or add a short, direct fact that states the answer plainly |
| The question was ambiguous in the thread | The reply answers a reasonable reading of the last line, not the customer's actual point | Nothing about Knowledge will fix this; the correction belongs on the thread |
| A memory is steering it | One customer, or one mailbox, consistently gets the odd answer | Memory resolves narrowest-first, so a contact-level note can override what the workspace believes |
| The source itself contains instructions | The answer follows wording that appears verbatim inside an uploaded document or a forwarded email | Treat supplied text as data; a source that tries to give directions is a prompt-injection question, not a knowledge one |
Conflicts are the first thing to check because they are the failure that looks least like one. Nothing errors, nothing is missing, and the answer is drawn faithfully from a real document — just not the one you would have chosen. A conflict is resolved by a person deciding, never by averaging two sources into something neither of them says.
What Connect completed#
- It resolved the workspace and read only that workspace's Knowledge.
- It retrieved material and produced an answer grounded in it, rather than from general recall.
- It recorded the decision — what was answered, under which rule — so the reply can be examined afterwards rather than reconstructed.
- It applied autonomy: the reply was sent, held for approval, or prepared and stopped, according to the mode at the narrowest applicable scope.
- If the reply went out, it went through the single send boundary and is only reported as sent because a provider acknowledged it.
What Connect did not complete#
- It did not check whether a source is still current. Nothing in a document announces that it has been superseded.
- It did not resolve a contradiction between two sources. Where two disagree, one is used; which one is not a judgement Connect makes on your behalf.
- It did not look anything up outside the supplied Knowledge, so a gap in your sources is not filled from elsewhere — it stays a gap.
- It did not invent a commercial term. If the wrong answer includes a price, a deadline or a warranty, that is a separate and more serious failure to report.
- It did not change any source. Nothing about answering edits, reindexes or reorders your Knowledge.
What you can do now#
Reply to the customer yourself, on the thread, with the correct answer.
Result The customer stops waiting. Everything below is about the next occurrence, not this one.
Ask the retrieval test what the same question selects.
Result You see the material rather than guessing at it, and a conflict usually becomes obvious the moment both sources are on one screen.
Remove or correct the losing source.
Result A conflict resolved by deletion stays resolved. One left in place will surface again on a slightly different question.
Add a short fact that states the answer directly, if the correct answer is buried in a long document.
Result A direct statement is far more likely to survive a tight retrieval budget than one sentence in the middle of forty pages.
What an administrator can do, and when to escalate#
An administrator can audit the whole bank rather than one answer: which sources exist, who added them, when, and which ones no longer have an owner. Most workspaces find at least one document nobody would defend if asked about it directly, and removing it fixes several future answers at once.
Escalate beyond your own workspace in two cases. First, if a wrong answer contains a commercial term — that is the rule that prevents inventions having failed, and it is worth reporting exactly, with the channel it happened on. Second, if the cited material is not in your Knowledge at all, because that is a scoping question rather than a content one.
Questions#
Would a better model have got it right?
Not reliably, because the material it selected was genuinely in your Knowledge and genuinely said what it said. Where two of your documents disagree, no amount of model quality decides which one your business stands behind — that decision is yours and Connect deliberately does not make it for you.
Can I see which source an answer came from?
Yes, and it is the fastest step in this whole page. The retrieval test shows what a question selects before anybody sends anything, and the decision record lets you examine a reply that has already gone out.
Does deleting a source remove answers that already used it?
No. Messages that were sent are history and are not rewritten. Removing the source changes what the next answer is grounded in, which is the only thing it can change.
Is this the same as Knowledge being insufficient?
No. Insufficient Knowledge produces a refusal and an escalation — Connect saying it cannot answer. This page is the opposite failure: enough material existed, and the wrong part of it was used.