# Support repeat contact consolidation

Illustrative planning brief; no automatic product import.

Illustrative case: A customer opens four requests about the same missing export.

## Decision

Keep one investigation thread while preserving each affected workflow.

## Owned work

- Match request evidence
  - Owner role: Service coordinator
  - Acceptance evidence: Four request IDs map to two affected reports.
- Separate unresolved questions
  - Owner role: Support specialist
  - Acceptance evidence: Export timing and missing columns have distinct evidence.
- Confirm customer-facing thread
  - Owner role: Account contact
  - Acceptance evidence: Customer knows which thread carries the next update.

## Workflow

1. Map the four synthetic request references to the two affected reports and their unresolved export questions.
2. Separate missing columns from export timing, retaining the evidence and owner for each issue.
3. Agree one customer-facing update thread and link the original references; close each issue only when its own outcome is accepted.

## Judgment

Consolidation must not hide a separate unresolved service problem.


## Filled illustrative planning example

Synthetic map: requests A and B concern missing columns in report R; C and D concern export timing in report S. One update thread links all four. Corrected columns do not close the still-open timing issue.


## Workflow questions

### Should duplicate requests disappear?

Keep their references so the customer can trace prior explanations.

### Can one answer close all four?

Only if it addresses both timing and column evidence.

## Product connection

The outline can support owned follow-up work and status updates in TeamBoost. It does not operate a support inbox, connect customer systems or import the example.

Confirm account availability before adopting this manual outline.


## One update thread, two acceptance decisions

The synthetic request map keeps communication together while preserving different customer outcomes.

### Column correctness for report R

Keep separate: Export timing for report S.

Why the boundary matters: Repairing output content does not establish acceptable completion time.

### Linked original request references

Keep separate: Unrelated customer history.

Why the boundary matters: The update stays traceable without moving private irrelevant correspondence into the investigation.