Brightline Interiors: Answering a Credit Demand in 120 Words
You lead customer success at a logistics software vendor. On 3 March a platform outage lasted six hours and delayed 14 of Brightline Interiors' outbound orders. Brightline's operations director has emailed demanding a 40% credit on their annual contract of $18,000-that is $7,200-and has copied their procurement lead. Your position: the standard service-credit cap is 15% ($2,700), the root-cause report is due from engineering on Friday, and legal has said no wording may admit fault until that report is reviewed. Policy requires a first reply within one business day and a named human contact. Brightline renews in September and represents 6% of your book.
1. Write the reply. Maximum 120 words.
Read the worked answer
Model reply (114 words):
"Dear Ms Okafor,
Thank you for setting out the impact of 3 March so precisely-the 14 delayed orders give us a clear picture, and I understand why you are asking for a substantial credit.
I am not able to confirm a figure today. Our engineering review concludes Friday, and I would rather give you an accurate answer than a fast one. I will send you the findings and a credit proposal by Monday 10 March, and I would like to walk you through both on a call that day.
Could you send the affected order references? That will let us check each against the service-credit terms.
Regards, Priya Raman, Customer Success"
(Note: names and dates are placeholders to be filled from the account record.)
2. Explain the structure of your reply and the reasoning behind each move, including why you do not offer the 15% cap immediately.
Read the worked answer
Sequence: acknowledge → limit → commit to a date → request → sign.
- Acknowledge with their detail, not a formula. Naming the 14 orders shows the email was read; "I understand why you are asking" validates the request without validating the amount.
- Decline to confirm a figure, with a reason. "I am not able to confirm a figure today" is a limit on timing, not a refusal. Pairing it with the Friday review makes the delay procedural rather than evasive.
- Commit to a named date and a call. This is the part that holds the relationship: a deadline you set is one you can meet, and a call is harder to escalate past than an email thread.
Why not offer 15% now: offering the cap before the root-cause report does two things-it anchors the negotiation at 15% while Brightline is still arguing from 40%, and it implies the credit is a goodwill gesture rather than a contractual entitlement. If the report shows a breach of the service level, the credit may be owed on stronger grounds; if it does not, 15% may be too generous. Waiting for facts is the defensible position.
Also deliberate: asking for order references is a small, easy yes that keeps Brightline engaged while the substantive answer is pending.
3. Identify two phrases you would avoid in this email and explain what each would cost you.
Read the worked answer
1. "We apologise for any inconvenience this may have caused." The conditional "may have" plus the boilerplate noun "inconvenience" reads as a template, which invites the procurement lead to conclude that nobody has engaged with 14 delayed orders. Worse, in many contracts an unqualified apology functions as an acknowledgement, which is exactly what legal has prohibited. If an apology is needed, it should be specific and about the experience-"I am sorry your outbound schedule was disrupted"-not a formula.
2. "Due to a system failure on our side …" Any construction that attributes the outage to your platform concedes the mechanism before the root-cause review exists. If the cause turns out to be a third-party dependency or the customer's integration, that sentence is a written admission you cannot retract. State what happened in neutral, verifiable terms-"the outage on 3 March"-and let the Friday report supply the cause.
A third to watch: "as per our terms" used early. It is accurate but reads as a shut door, and with a September renewal six months out, the goal is to keep the commercial conversation open long enough to have it once, with facts.