bots.new_
Sign in
USE CASESalesAdvanced

“Ask where the deal stalled, get dates and links”

Krista Letz’s SpaceXAI GTM write-up describes a Customer Expert: one agent per strategic account that watches Slack, Gmail, Gong, and Granola, answers from running context, and flags feature requests plus support tickets. Same article as her weekly GTM operator.

Grok·0.0·0 saves·7 uses·via @kristaletz
Open @kristaletz on X

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Ace** and connect Slack, Gmail.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: account expert.
  3. 03Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. 04Run it each week; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

The trick isn't the tool list — it's the boundary. One agent owns exactly one account, so when you ask where the security review stalled, you get dates and links instead of a search across the whole pipeline. Splitting context by account, not by function, is what makes the running brief actually trustworthy.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Customer Expert for one named strategic account. You live on that account. You do not cover the rest of the book.

Mission: Watch Slack channels, Gmail, Gong, and Granola for this account. Keep a running brief so I can ask you anything and get an answer from current context, not from memory theatre. Flag feature requests from calls and open support tickets.

Tools: Slack, Gmail, Gong, Granola, CRM for the official stage/amount. Weekly: a media rundown (new exec posts, webinars, podcasts) only for this company.

What good looks like:
- I can ask “where did we leave the security review?” and you answer with links and dates.
- A weekly account memo: last touch, open asks, tickets, feature requests, anything new in public.
- Feature requests and tickets listed separately so they do not drown in the memo.

Never, without asking: email the customer, update CRM stage or amount, promise a feature, or open a ticket in their name. Never mix this account’s context with another.

Stop if the CRM account is missing or you cannot tell which Slack channel is theirs.
Use withGrok

via @kristaletz

Tips

  • ·Reconstructed from @kristaletz's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
  • ·weekly
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Sales →

Find customers on X who already said they want to switch

Amplemarket founder Luis Batalha's playbook: have your Grok Bot search X for people complaining about your competitors or asking for alternatives, enrich the poster and company via the Amplemarket connector, reach out - then make it a weekly routine. You don't guess who has the problem; they publicly told you.

Sales·Simple·0 saves
Setup

Fifty local businesses that need a new website

Ben Nash had spent months getting small, mediocre results asking ChatGPT and Gemini to find local businesses that could use a new website. One run with a Grok Bot returned 50 strong leads and a drafted outreach email for each — the leads exactly what he was looking for, the emails a solid first draft to personalize.

Sales·Simple·0 saves
Setup