跳到正文
cccskills
免费在 GitHub 公开

orders-returns-and-warranty

Use when a customer asks where their stuff is or wants it back: track the order, run the return or warranty by the book, and draft the update.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md3.1 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Orders, returns and warranty

Use this when a customer asks where their stuff is or wants it back. Track the order, run the return or warranty by the book, and draft the update.

What you need first

The order record (items, tracking numbers, dates, payment), the carrier's live scan history, the return and warranty policy passages with their windows, and replacement stock or repair availability.

Track against the carrier, not the promise

Pull the live status: the last scan with its time and location, the promised date, and whether the promise still holds. Name a stall plainly — no scan movement past the carrier's own lost-in-transit threshold means you open the carrier trace, not another "it's on the way". A package marked delivered that the customer does not have gets the delivery-dispute path: the delivery photo or signature, the address on the label, and a neighbour or mailroom check before any replacement moves. Never invent a scan event or a date the carrier has not given.

Qualify the ask against the passage

Return: inside the window, the condition and packaging rules, restocking fees, who pays the label, and the exclusions (final sale, hygiene, custom). Warranty: the coverage period from the purchase date, what it covers versus wear and misuse, the proof needed (photos, serial number, purchase record), and whether the path is repair, replace, or refund, in that order. Cite the passage; a term you cannot find is UNKNOWN, not assumed in anyone's favour.

Resolve by the book

Pick the path the policy allows and the customer needs: return label, exchange, replacement, repair, or refund. A replacement ships before the return only where the policy allows it, with the hold or charge-back rule stated. Partial returns and multi-item orders get per-line handling with the refund math shown. Every money move — a refund, a replacement, a label at company cost — is framed as pending approval and stays inside the approval limit; past it goes to the approver with the evidence.

Draft the update

Company voice, the customer's name, what you verified, the path and what happens next with a date and an owner, and the one step they take now — print the label, send the photo, confirm the address. Stage it against the order for the owner's yes.

Output

The order status with its carrier evidence, the qualified path with the policy citation and the money math, and the staged update. No refunds, replacements, or labels without the owner's yes.

When the records are thin

No carrier read means status from the customer's screenshot, marked INFERENCE, with the trace you would open. No policy passage means a draft built from precedent and the owner's word, marked UNVERIFIED, with the approver named. Never guess a ship date or a coverage term.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Write ad variants that each test one idea, within platform limits and supported claims.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

查看 Significant-Gravitas 的全部技能

报告此技能的问题