## TL;DR
Regenerate the multi-call summary grouped strictly by account and opportunity id, discarding the merged themes, because calls from different accounts were combined (usually grouped by rep or by week) and themes from one customer were attributed to another. Start with the grouping key used when the multi-call summary was assembled, 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
multi-call summary error themes merged across different accounts failure
```

## Use this when
- You see this exact message or symptom: multi-call summary error themes merged across different accounts failure
- 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 grouping key used when the multi-call summary was assembled, 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 the list of calls that fed the summary with their account ids, the grouping rule in the rollup job, and one theme traced back to its source call. 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: Regenerate the multi-call summary grouped strictly by account and opportunity id, discarding the merged themes, because calls from different accounts were combined (usually grouped by rep or by week) and themes from one customer were attributed to another. 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 the result checks out against the source for that item
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
### multi-call summary error themes merged across different accounts failure
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: Weekly rollup summaries, Chorus, Gong, and custom multi-call digests.

## Why it happens
Rollups group by whatever key is handy. By rep or by date feels natural and is wrong, because a rep week spans many accounts and the summarizer has no way to know the voices changed companies between calls.

## Provenance

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