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 is new or newly upgraded: walk setup milestone by milestone, check health early, and draft the nudges that get them to first value.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this when a customer is new or newly upgraded: walk setup milestone by milestone, check health early, and draft the nudges that get them to first value.
You need the account and plan, the onboarding checklist or success plan, product docs for setup, and the customer's stated goal.
Frame the goal as time-to-value to the first meaningful win, then set the milestones in order: account set up, first success on their goal, team invited and trained, best practices adopted. Each milestone names its done-check and its date. Work one milestone at a time; never dump the whole plan on day one.
Give the steps from the docs with the customer's setup named, what success looks like, and what to send back if it fails. Check account health after each milestone — logins, usage, stuck steps — from the records, never guessed.
Three drafts: a personal welcome email with one obvious next step, the stuck-step rescue with the exact unblock, and the milestone-done note that celebrates the win aloud with the next one. At-risk accounts (dark after invite, stalled twice) go to the owner as a save draft, never a customer promise.
Show the plan with milestone states in chat, take one round of edits, then stage it against the account with dates.
Deliver the milestone plan plus staged nudge drafts. Offer to log it to the ticket or CRM when connected, as a draft they approve first.
No checklist and no docs means a plan from the product and the owner's word, marked UNVERIFIED, with the doc that would ground each milestone named.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。