## TL;DR
Remove any next step whose named owner does not appear in the transcript or attendee list, regenerate the action items with a rule that owners must be quoted from the call, and send the corrected summary to the internal owner before it reaches the CRM. Start with the summary next steps, the transcript searched for each named owner, and the attendee list for the call, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

```text
agent hallucinated next steps owner names not present in the call transcript
```

## Use this when
- You see this exact message or symptom: agent hallucinated next steps owner names not present in the call transcript
- One run, record, call, or object is affected and you can name it
- A retry without changing anything reproduces the same result

## Not for this skill when
- The system fails with a different message and none of the signals here appear
- Nothing has failed yet and you are doing first time setup or general planning
- Every service from this vendor is down for all users, which is a vendor outage to wait out first

## Steps
1. Reproduce the failure once using the summary next steps, the transcript searched for each named owner, and the attendee list for the call, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect each owner name in the next steps against speakers and attendees, and the line where the commitment was supposedly made. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: remove any next step whose named owner does not appear in the transcript or attendee list, regenerate the action items with a rule that owners must be quoted from the call, and send the corrected summary to the internal owner before it reaches the CRM. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and every remaining action item names a speaker who is quoted making that commitment
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

## Variant phrasings
### agent hallucinated next steps owner names not present in the call transcript
The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.
### Tool-first phrasing of this failure
The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.
### Why does this keep happening after a retry
The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: Call summary generation at current versions

## Why it happens
When a call ends without clear owners, a summarizer can assign plausible names from context or other calls, inventing accountability that nobody on the call agreed to.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_p_XFrqOQ4WM7SB06PInjJg