仕事

CS crawl→walk→run: Build / Reply / Alert / Tune, refunds stay human

Support wants a fleet on day one — start with one bot or the scope eats you.

困っていたこと

George Hong (@DomainMaster) recapped Grok Bot for Customer Support with David (SpaceX AI user ops) on Galaxy Day 2. CS use cases: crawl→walk→run ticket replies (draft note → send); churn/threat scanners on a schedule into Slack; internal Slack Q&A on the same KB (public docs + private SOPs); self-improve from traces / last week of tickets. Fleet demo (Flylo airline toy): Build · Reply · Alert · Tune — start with one bot, split when scope grows. Low-confidence Slack alerts; refunds need a human. Community recap — not official xAI text; not affiliated with xAI. Distinct from the Cora/Pete/Ashley prompt set.

インストールまたは作成するもの

One bot first. Draft replies before send. Split into Build/Reply/Alert/Tune when scope grows. Refunds stay human.

ボット

CS first seat
Starts as one bot: draft replies from the KB. Splits into Build/Reply/Alert/Tune later.

プラグイン

初日から入れるものはありません。初回の手順に従ってください。

ファイル

KB = public docs + private SOPs. Confidence rule: low → Slack, do not send. Refunds = human only.

ルーティン

Optional later: scheduled churn/threat scan into Slack; weekly tune from last week's tickets.

プロンプト

これはヒントであり、貼り付けられるシステムプロンプトではありません。作者はプロンプトを公開していません。初回の手順に従ってください。

初回実行

1Read https://x.com/DomainMaster/status/2100371923238563892 — recap only; do not paste the Flylo Cora/Pete/Ashley prompts here.
2Point one bot at your KB (public docs + private SOPs). Crawl: draft a ticket note, do not send.
3Walk: you send the draft. Run: only after confidence is high and you still approve the first live sends.
4When scope grows, split Build / Reply / Alert / Tune. Low-confidence → Slack, not the customer.
5Refunds and spend stay human. Start one bot — do not hire the whole fleet on day one.