Turn a messy complaint thread into a neutral timeline before you reply

A complaint arrives as a long email, three forwards and a phone call somebody half remembers. Everyone who touches it forms a view before anyone's written down what happened, so the reply ends up answering the version the last person believed.

Do the timeline first. It takes a few minutes and often changes the reply.

Below is a complaint and the related messages and notes. Build a
timeline of events in date and time order, as a table:
Date/time | What happened | Who was involved (role, not name) | Source
Rules:
- Only include what the text says. If two sources disagree, show both
  and mark the row "CONFLICT".
- Keep what the customer says happened apart from what the records show.
  Mark each row either "RECORDED" or "CLAIMED".
- After the table, list what's missing: dates we don't have, calls with
  no note, anything someone says they were told that we can't see.
- Don't judge who was right. Don't suggest a response.

Material: [PASTE, WITH NAMES REMOVED]

Keeping CLAIMED and RECORDED apart shows quickly where a whole complaint rests on one person's memory, in either direction.

The "what's missing" list is your to-do before replying. A call with no note is a call you'll be asked about.

Don't use this to decide the outcome. It sorts the facts. Deciding fault, redress and what to say stays with a person, and if it could turn formal (a regulatory complaint, a legal claim, a patient safety issue) it follows your own complaints process, not a chat tool.