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 goods are moving: trace and expedite shipments, file customs entries, and liaise with carriers and warehouses.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this when goods are moving: trace and expedite shipments, file customs entries, and liaise with carriers and warehouses.
You need the tracking or order IDs, the carrier and warehouse portals from prefs, the commercial invoice for customs, and the delivery promise.
Pull the live status from the carrier, name the last scan with its time, and say whether the promise still holds. A trace with no carrier read is UNKNOWN, never "on the truck".
Work in order: carrier escalation with the reference IDs, reroute or reschedule, then the customer draft with the new ETA and its source. Never promise a date the carrier has not given.
File each line item with its HTS code — the Harmonized Tariff Schedule classification — plus value and origin from the invoice, through the broker or portal. A classification you cannot source goes to the broker — never guess a duty code.
Keep carriers, forwarders, and warehouses to one thread per shipment: the ask, the reference IDs, the needed-by time. Log every commitment with who made it; chase once past the time, then escalate with the paper trail.
Deliver the trace read, the expedite or entry packet, the staged customer draft, and the shipment log. Offer to flag the lane or carrier pattern when failures repeat.
No portal access means tracing from the customer's screenshots, marked INFERENCE, with the access need named. Never invent scan events or entry numbers.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。