OrderKeeper

After-Sales Is An Action Window, Not A Status Check

orderkeeper targets orders that already exist: missing items, wrong items, damage, price drops, warranty deadlines, invoice issues, and similar post-purchase problems. It does not decide whether to buy or compare products. Its core question is: what is the nearest dangerous deadline, and should the next move be refund, exchange, reshipment, compensation, warranty claim, or short observation.

It Compresses Order Problems Into Executable Steps

The skill first builds an order timeline, including placement, shipping, sign-off, issue discovery, price-protection windows, and warranty end dates. It then classifies the issue, identifies the nearest risk clock, and gives a direct recommendation:

• Refund / exchange / reshipment / compensation: based on whether the user still wants the item, whether the problem is fixable, and whether evidence is sufficient.
• Evidence first: remind the user to save the box, labels, missing-item photos, chat records, price screenshots, and order information before losing leverage.
• Support script: generate a concise, sendable next message for customer service.
• After-sales card: link order, receipt, warranty, current status, desired outcome, and the next checkpoint into one reusable card.

Boundary: if the user is still comparing products, sellers, or platforms, use pre-purchase skills first. If the goal is mainly receipt archiving, warranty catalogs, or asset tracking, hand off to inventory or receipt tools. orderkeeper focuses on active order lifecycle, issue triage, deadline pressure, and customer-service action.