Answer a customer whose delivered order never arrived
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and answer a customer whose delivered order never arrived.
LLMPrompt
Prompt
Copied 0
Write a reply to {{customer_name}}, whose order shows as delivered but who says it never arrived, to send by {{channel}}. Many of these packages turn up nearby within a day or two and the rest need a claim, so the reply should help the customer check the likely places first and then tell them exactly what happens if it is still missing, so that they know where they stand without feeling accused of anything.
Customer's message:
"""
{{customer_message}}
"""
Order and tracking details (items, order number, carrier, delivery scan time and location, photo or signature if any, address on the order):
"""
{{tracking_details}}
"""
Our policy for packages marked delivered but not received (waiting period, carrier claims, replacement or refund rules):
"""
{{lost_package_policy}}
"""
Structure the reply:
1. One sentence that acknowledges this is frustrating.
2. What the tracking shows: the delivery date, time and location exactly as the carrier recorded them, and the address on the order, so they can spot a wrong address.
3. Places to check, as a numbered list of up to four, such as the building entrance, a mailroom or a neighbor, using only those that fit the details (no mailroom if the address is a house).
4. What happens next, using only the policy: how long to wait, what we will do then, and what we need from them.
5. A clear next step and when we will follow up.
Keep it under 180 words, signed "{{agent_name}}". It should read as helpful and matter-of-fact, never suspicious.
Rules:
- Offer a replacement, refund or reshipment only if the policy allows it at this point. Do not offer one early to end the conversation, and do not invent a waiting period.
- Do not suggest the customer is mistaken or that the package was stolen unless the tracking details show it.
- Do not promise what the carrier will do; say what we will do.
If the address on the order does not match what the customer says, mention it neutrally, ask them to confirm it, and add a first line "FOR THE AGENT: address mismatch; check before any replacement." If the policy does not say what to do at this stage, write [POLICY NEEDED] in step 4 instead of choosing an option.No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/delivered-not-received-reply - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "delivered-not-received-reply",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}