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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
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.
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.
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.
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.
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.
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.
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.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
日本語の概要は準備中です。原文の説明を表示しています。
Write ad variants that each test one idea, within platform limits and supported claims.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
日本語の概要は準備中です。原文の説明を表示しています。