The Two-Paragraph Email That Must Persuade
You manage a small customer-support team of six people. Your company has announced that the support desk will move from email to a live-chat system on 1 September, six weeks away. Your team is anxious: two members have limited typing speed, one works part-time and worries about coverage, and all six fear that response-time targets will become harder to meet. Your manager has asked you to write a two-paragraph email to the team that (a) explains the change accurately, (b) acknowledges the specific concerns without dismissing them, and (c) proposes one concrete next step. You have 30 minutes to draft it. You know the chat system has a canned-response feature and a queue that routes chats by topic, but you do not yet know whether typing-speed accommodations are available.
1. Draft the two-paragraph email. Then explain the choices you made about audience, register, and what you left out.
Read the worked answer
Draft email:
"Team, I want to share what I know about the move to live chat on 1 September. The change is confirmed, and the reason is that customers increasingly expect immediate replies. I also want to be direct: I know this raises real concerns. Two of you have told me that typing speed is a worry, and I take that seriously. The part-time schedule and the coverage question are also unresolved, and I am not going to pretend otherwise. The new system does include canned responses for common questions and a queue that routes chats by topic, which should reduce the number of chats each person handles at once.
Here is what I propose: on Monday we spend 30 minutes as a team listing the three things that must be settled before 1 September, starting with typing-speed accommodations and part-time coverage. I will take that list to my manager the same day and report back by Wednesday. If you have a concern you would rather raise privately, message me before Monday and I will include it without naming you."
Choices explained:
- Audience: The team knows the context, so the email does not explain what live chat is. It names the specific worries (typing speed, part-time coverage) because generic reassurance would read as dismissive.
- Register: Direct and plain. 'I am not going to pretend otherwise' signals honesty; 'I take that seriously' acknowledges without overpromising. The email avoids corporate phrases like 'exciting opportunity,' which would clash with the team's anxiety.
- What I left out: I did not promise that accommodations exist, because I do not know. I did not claim response-time targets will be easier, because I cannot verify that. I did not set a final decision date beyond Wednesday, because I do not control the accommodation decision.
- Concrete next step: A 30-minute Monday meeting with a specific output (three issues) and a specific follow-up (report back by Wednesday). A vague 'we will discuss this soon' would not satisfy the brief.
2. A team member replies: 'You said you take our concerns seriously, but you also said the change is confirmed. That is contradictory.' Write a response that addresses the criticism honestly, and explain the rhetorical strategy.
Read the worked answer
Response:
"You are right that those two statements sit awkwardly together, and I should have separated them more clearly. The change itself is confirmed; I cannot undo it. What is not settled is how we implement it, including typing-speed accommodations and part-time coverage. When I said I take your concerns seriously, I meant that I will push on those implementation questions, not that I can reverse the decision. I understand why that distinction matters, and I should have stated it in the first email. Monday's meeting is still the place to list what must be settled, and I will report back by Wednesday on what my manager can approve."
Rhetorical strategy:
- Concede the point directly. The team member has identified a real tension, and denying it would damage trust. 'You are right' is a strong opening because it validates the criticism before explaining.
- Separate the decision from the implementation. This is the substantive clarification: the decision is fixed, but the implementation has room for negotiation. Naming that distinction resolves the apparent contradiction rather than talking around it.
- Define what 'taking concerns seriously' means. The phrase was vague; the response gives it operational content (pushing on accommodations and coverage).
- Own the communication failure. 'I should have stated it in the first email' accepts responsibility without excessive apology.
- Restate the concrete commitment. Monday's meeting and the Wednesday report give the team something checkable, which is more persuasive than further reassurance.
The strategy is concession, clarification, and a checkable commitment, in that order. It treats the criticism as legitimate rather than as resistance, which is what keeps the team's trust intact during an unwelcome change.