All use cases

Work

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.

Share

What hurt

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.

What to install or create

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

Bots

  • CS first seat

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

Plugins

  • None on day one. Follow the first-run steps.

Files

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

Routines

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

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

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

Approval fence

Draft ticket notes freely. Sending a reply, Slack-wide alerts, and any refund or spend need your yes.

What to tweak

Steal crawl→walk→run + split-when-scope-grows. Low-confidence alerts Slack; refunds never auto.

Source

George Hong @DomainMaster · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Related team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro