Reviewing a prepared customer response

Start with the trigger, not the text

A prepared response comes with the trigger that prompted it and the outcome it is expected to produce. Read those first. It is a small discipline with a real effect: opening the draft first anchors you on the wording, and you end up editing sentences in a message that should not have been drafted at all.

The trigger also tells you whether the system's reading of the situation matches yours. When it does not (the response is pitched at a concern the account resolved last month, or it treats a routine question as an escalation) the wording is irrelevant and the useful feedback is about the trigger.

Three questions in order

Reviewing well is mostly a matter of asking things in the right sequence, because each question makes the next one cheaper. Should we be responding to this at all? Then: is this the right thing to say? Only then: is this the right way to say it?

Most reviewers start at the third question, since wording is what is in front of them and it is the easiest thing to have an opinion about. That is how a well-written response to the wrong situation gets approved, polished, on-brand, and answering something nobody asked.

• Should this response exist? — a trigger question
• Is the substance right? — an argument question
• Is the wording right? — the cheapest question, and the one to ask last

Edit or send back

Once you know what is wrong, the choice between editing and rejecting is a question of what recurs. Tone, phrasing and a detail specific to this customer are faster to fix than to explain, so fix them and move on. A wrong argument, a wrong trigger, or a claim that should not have been made is a defect that will show up again on the next account, and returning it is what gets it fixed.

Reject properly when you do. A rejection with a reason is a correction to the system; a rejection without one is a message that says only that something was wrong, which cannot be acted on. This is the same discipline as the campaign course's pattern-versus-instance distinction, arriving in a different queue.

A worked example: the response that was well written and wrong

A response arrives for an account that has gone quiet. The draft is good: warm, specific, references the last QBR, asks a clear question. Reviewed on wording alone it sails through.

The trigger says it was prepared because engagement dropped below a threshold. Reading that first changes the question. Engagement dropped because the champion has been on parental leave for six weeks, which is recorded on the contact and was not part of what the threshold looks at. The account has not gone quiet; one person has.

The right outcome here is not an edit. Editing the wording ships a well-phrased message to a covering stakeholder implying their team has gone silent, which is both wrong and slightly insulting. The right outcome is to reject it with the reason, because the same threshold will fire again on the next account whose main contact is on leave, and the reason is the only thing that can prevent that.

This is the case that makes the trigger-first habit worth the two seconds. Read in the other order, nothing about the draft invites suspicion, and a fluent message papers over a wrong premise.