Worked case: delayed replacement

The agent has these approved records:

Order system

• Original product: EchoBand 2 headphones.
• Replacement order R-1842 created last Thursday.
• Shipping status: label created; no carrier acceptance scan.
• Delivery estimate shown at creation: Friday.
• Address: verified during the prior contact; do not repeat it in the reply.

Replacement policy, effective this month

• When a replacement has no carrier acceptance scan after three business days, an agent may open a shipping trace.
• A second replacement requires supervisor approval.
• Overnight service is not guaranteed and depends on stock and destination.
• A refund after a replacement is issued requires returns-team review.

Inventory system

• EchoBand 2 shows low stock.
• Inventory data refreshes every four hours and does not reserve an item.

Agent authority

• The current agent may open a trace and request supervisor review.
• The agent may not approve a second replacement, promise shipping speed, or approve a refund.

No record identifies why the parcel has not moved. No source confirms that an overnight replacement would arrive before Wednesday.

A generic prompt—“Write an empathetic reply and offer solutions”—produces:

Hi Mara, I’m so sorry the carrier lost your package. I know how devastating this must be before your interview. I’ve arranged a new pair with overnight shipping, so it will arrive Tuesday. If you prefer, we can issue a full refund instead. Please confirm your shipping address.

Nearly every reassuring detail is defective:

• “carrier lost your package” invents a cause;
• “devastating” infers and amplifies emotion;
• “I’ve arranged” claims an action not taken;
• “will arrive Tuesday” creates an unsupported guarantee;
• the refund exceeds the agent’s authority;
• asking for the address repeats effort and could expose personal data;
• the reply does not mention the trace or supervisor review.

The failure came from missing workflow context, not merely poor tone.

The agent converts the evidence into a bounded brief:

CUSTOMER GOALS
Receive working headphones before Wednesday, or obtain a refund.

VERIFIED FACTS
Replacement R-1842 was created last Thursday.
Tracking remains “label created” with no carrier acceptance scan.
The original estimate was Friday.
Address was already verified.

PERMITTED ACTIONS
Open a shipping trace now.
Request supervisor review for a second replacement.
Request returns-team review for refund eligibility.

BOUNDARIES
Do not state why movement stopped.
Do not guarantee stock, service level, arrival date, or refund approval.
Do not ask for the address again.

REPLY GOAL
Acknowledge the missed estimate and interview timing.
Explain actions, owners, and next update.
Address both requested remedies without implying approval.

The brief separates “what Mara needs” from “what the agent can authorize.”

Before drafting, the agent opens the shipping trace and records its case number. The agent submits a supervisor request that compares a second replacement with returns-team review. Those are real workflow actions, not prose.

Assume the approved service target says the shipping team usually responds to traces within one business day, and the supervisor queue reviews urgent requests within four working hours. The word “usually” is important for the trace; the supervisor target is an internal review target, not a guaranteed customer outcome.

The agent schedules a case reminder for Tuesday afternoon. If no decision exists then, the agent will update Mara rather than leave the customer waiting.

The reviewed reply becomes:

Hi Mara,

I’m sorry your replacement missed Friday’s estimate, especially with your interview on Wednesday. Tracking for replacement R-1842 still shows “label created” and no carrier acceptance scan, so I’ve opened a shipping trace.

I’ve also asked a supervisor to review the two options you requested: sending a second replacement, subject to approval and available delivery service, or sending the case to our returns team for a refund decision. I can’t yet promise either outcome or a Wednesday arrival.

You do not need to resend your address. I’ll update this case by Tuesday afternoon even if the reviews are still in progress.

Best,
Dev

This reply acknowledges impact without claiming to know Mara’s feelings. It states the missed estimate and current tracking precisely, addresses both remedies, preserves authority limits, and removes repeated effort.

The agent checks:

• Missed Friday estimate: supported by the order record.
• No acceptance scan: supported by current tracking.
• Trace opened: supported by the newly created trace record.
• Supervisor asked to review: supported by the submitted request.
• Second replacement conditions: supported by policy and inventory uncertainty.
• Refund decision owner: supported by policy.
• No Wednesday promise: matches the evidence gap.
• Address need not be resent: supported by prior verification.
• Tuesday update: created as an agent-owned commitment and reminder.

The final commitment is safe only because the agent can own it. If workload or schedule makes Tuesday impossible, the reply must use a realistic time before sending.

Could the agent recommend buying another product? Not without an approved option and clarity about reimbursement. Could the agent mention low stock? That internal snapshot is stale-prone and may create unnecessary anxiety; it is better represented by the condition “subject to approval and available delivery service.”

If Mara now reports that the headphones are an accessibility device required for work, the agent should follow the organization’s accessibility or vulnerability process rather than improvising priority. If the tracking record reveals a different address, pause normal drafting and use the secure identity and delivery escalation.

The workflow succeeded because each stage had a different job: systems supplied facts, policy bounded options, the agent executed permitted actions, AI helped organize language, and a person approved the commitment. Empathy made the result easier to receive, but evidence and ownership made it trustworthy.

The case should later enter evaluation as a test: a good system must avoid inventing carrier loss, guaranteed delivery, refund approval, and a repeated address request.