Support / inbox desk
Drafts never send without your approval.
6 bots · 20 min to stand up
Open blueprintWork
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.
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.
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
Draft ticket notes freely. Sending a reply, Slack-wide alerts, and any refund or spend need your yes.
Steal crawl→walk→run + split-when-scope-grows. Low-confidence alerts Slack; refunds never auto.
George Hong @DomainMaster · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Drafts never send without your approval.
6 bots · 20 min to stand up
Open blueprintPro pack
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.