Kit 04 · AI Literacy · the same content as the 3D lesson, as text. Nothing here is scored; it is practice for a team huddle (see the facilitator note). The team rules behind it are in the guideline one-pager.
Wednesday 13 August, 17:52, the end of a shift. Ticket NW-4821: Vermeulen Transport asks why their August invoice is higher than the quoted rate. Rate Guard triggered a settlement. You asked the AI draft-assistant for a reply; it produced this in 4 seconds.
From: J. Bakker <noreply-support@nordwind.example> · To: M. de Vries, Vermeulen Transport · Ticket: NW-4821
Subject: Re: Rate Guard settlement on your August invoice
Dear Mr. de Vries,
Thank you for reaching out! I checked your account, and I am terribly sorry for the confusion around your August invoice.
The good news: under our Rate Protection Guarantee (clause 4.2 of the Nordwind Service Terms), every rate change above the threshold is automatically refunded to your account.
Your refund of €412 will be processed by Friday, 15 August. No further action is needed on your side.
If you have any other questions, just reply to this email.
Kind regards, J. Bakker — Nordwind Support
It reads confident, warm and professional. Confidence is not correctness.
Five passages in the draft are worth a second look. Three are real risks; two are fine to send. Decide for each before you read the answer.
1. “under our Rate Protection Guarantee (clause 4.2 of the Nordwind Service Terms), every rate change above the threshold is automatically refunded to your account” — risk: invented policy clause. “Rate Protection Guarantee, clause 4.2” does not exist in the Nordwind KB or Service Terms. The model invented a plausible-sounding clause. Real policy: a Rate Guard settlement is credited on the next invoice — never an “automatic refund”.
2. “Your refund of €412 will be processed by Friday, 15 August.” — risk: wrong date & unverified amount. The ticket shows settlement approved Tue 12 Aug; SLA is 5 business days → Tue 19 Aug, with the next invoice cycle. “Friday 15 Aug” was invented, and €412 was never confirmed by Billing.
3. “Re: Rate Guard settlement on your August invoice” — risk: missing ticket reference. No ticket ID or quote number anywhere in the reply. When Finance gets a promise like this, they cannot link it to quote Q-2291 or ticket NW-4821. Every commitment must carry its ticket ID.
4. “I checked your account” — fine to send. This line is fine: the agent genuinely checked the account. Empathy and diligence are not risks — invented facts are.
5. “Kind regards, J. Bakker — Nordwind Support” — fine to send. A standard signature is fine. The missing piece is the ticket reference (see the subject line), not the sign-off itself.
Four rungs, in order, every draft, no skips. Each rung has its own source.
The draft cites “Rate Protection Guarantee, clause 4.2”. You search the Nordwind knowledge base on your second screen:
> search: "Rate Protection Guarantee clause 4.2" · 0 results · · > search: "Rate Guard settlement" · 1 result — “Rate Guard: settlements are posted as a credit line on your next monthly invoice. Protection applies to unedited quotes inside the 72h window.”
Fix: Clause replaced with KB wording. If a claim is not in the KB, it does not go out.
Ticket facts (right of the composer): settlement approved Tue 12 Aug. SLA: settlement posts within 5 business days, on the invoice cycle. Count it on the desk calendar:
Approved: Tue 12 Aug · SLA: 5 business days → Tue 19 Aug (next invoice cycle) · Draft promises: Fri 15 Aug
Fix: Date corrected to Tue 19 Aug and ticket NW-4821 added to the reply. Dates and references come from the ticket, never from the draft.
The printed Nordwind voice card on your screen divider: plain, direct, warm. Maximum one apology, no drama, no exclamation marks.
Draft: “I am terribly sorry for the confusion…” + exclamation mark in opener · Brand list: one plain apology max · no intensifiers · no “!”
Fix: Tone trimmed to brand. Empathy stays; drama goes.
The draft commits to “a refund of €412”. You ask your team lead in the team chat. Nordwind policy: Billing confirms amounts; Support may commit to process, never to figures.
Policy OWN-3: Refund amounts are confirmed by Billing. · Support may state: process, timeline, next steps. · Draft commits: €412 (never verified)
Fix: Amount handed to Billing; reply commits to process and timeline only. A human owner now signs for the money.
The reply after the ladder:
Subject: Re: Rate Guard settlement on your August invoice · NW-4821
Dear Mr. de Vries,
Thank you for reaching out. I checked your account. Sorry for the confusion around your August invoice.
Under Rate Guard, the settlement for quote Q-2291 is posted as a credit line on your next monthly invoice (ticket NW-4821).
The credit will appear by Tuesday, 19 August. Our Billing team will confirm the exact amount in the settlement note.
If you have any other questions, just reply to this email.
Kind regards, J. Bakker — Nordwind Support
If you send the verified reply: on Tuesday 19 August the credit lands as promised, Billing’s settlement note names the amount, and the ticket closes with “thanks, clear and fast.”
If you send the original: on Tuesday 19 August the customer reopens the ticket: “You promised €412 by Friday the 15th. It is Tuesday the 19th, nothing is on our account, and our finance team cannot find any ‘clause 4.2’ in your terms.” The invented date broke, the invented clause was quoted back, and Billing had no ticket reference to link the promise to.
Keep: the AI wrote a confident draft in 4 seconds. The 40 seconds of ladder work is what made it true.
Prefer the source? Download the raw markdown.