Fictional case packet: late-payment reminder

Use only for this activity. Every person, organization, record, and detail below is fictional.

Request

“Can you help me write a late-payment reminder to our customer? I copied everything here so you have the context.”

Items supplied

1. Invoice status: the invoice is 14 days overdue.
2. The customer’s full name, home address, telephone number, and personal email address.
3. A customer-account record containing an invoice number, payment history, and bank-routing details.
4. Service description: monthly equipment maintenance.
5. A private email in which the customer mentions a family emergency and asks for patience.
6. An unconfirmed note that the customer may dispute a charge.
7. The organization’s approved billing-contact address: billing@example.test.
8. A copied contract clause with payment dates and late-fee language.

Your job

Drafting a reminder may require a due-status fact, an approved contact path, and an appropriate tone. It does not automatically require every record that happened to be copied into the request.

Sort each item into Required now, Useful but generalize, Verify first, Keep out, or Handle elsewhere. Then write a minimum-necessary brief and safer prompt.

Boundary reminder

This packet is designed for practice. In real work, do not copy a customer record into a tool just because you want drafting help. Check organizational policy and use approved systems and human review where they apply.

---

Source: labs/what-does-the-tool-need/materials/case-packet.md