Most "AI for sales" tools ask you to paste a list and hope. Grok Bot is different when it is connected to the tools you already live in: CRM, mail, calendar, notes, Slack, the warehouse. It has a computer that keeps working after you shut the laptop. Krista Letz, who runs Enterprise GTM at SpaceXAI, wrote the internal Notion doc her team actually used, then published it.
This is the Academy version. We do not paste her full prompts. We keep the seats, the guardrails, and links to Grok Bot sales prompts, chief of staff, email, and meetings.
Connect the computer before you name ten bots
Her first tip is boring and it is the one that fails. Sign the shared computer into the systems you already use. If the bot cannot see Salesforce, Gmail, calendar, and call notes, it will invent a pipeline from search results.
Then teach voice on purpose. Ask it to scan sent mail and Slack for how you write, and to save a style profile. Refresh that profile when it is older than a month. A bot that has never read your outbox will sound like a bot.
The mobile app plus voice is how she dumps work between meetings: "prep the 2pm, draft the follow-up, do not send."
The seats that matter
Chief of Staff. Meeting prep, inbox drafts, traffic cop for the rest of the team. Pin it. Tell it it may propose other bots. It does not send mail.
Daily meeting prep is a routine, not a chat you remember to open. Short enough to read on a phone. Pull from CRM, mail, Slack, and notes. If the meeting is new, it may use public research and must label that as research, not as "what we heard on the call."
Prospecting. Overnight research, a live sheet (not a CSV dump), drafts in your voice. Before the first run it should ask you the setup questions: which CRM, which titles, what seniority, whose accounts, hard writing rules. It should discover the CRM's real field names instead of assuming "Stage" means what it meant at the last company.
Guardrails that belong in the Bot description, not in a hope:
- Surface open opportunity stage, amount, and last activity on every row so warm pipeline is never treated as a cold list
- Check sent mail, the sheet, and CRM activity. Mark already-touched people as skip-draft. Keep them on the sheet.
- Show you 2 or 3 email-and-LinkedIn pairs before it generates a batch
- The LinkedIn note never mentions that you emailed them
- You hit send
Customer expert. One bot per strategic account (or a top prospect). Weekly media rundown: new talks, posts, webinars. It should consume the thing, not summarize a title. If there is no transcript, it says so. Feature requests and tickets get flagged, not promised.
Product expert. She called hers "10x engineer": connected to the repo or to an internal search tool, so a live customer question does not wait on Slack. Customer-facing wording. No deploy.
Forecasting. Notes from calls, Slack, and mail, written into the CRM in a format you chose. You still own the number on the forecast call.
Slides. A master deck and a brand system. Copies per customer. Her favorite skill: stop the call recording 5 or 10 minutes early, fill the "what we heard" slide from the notes, walk out of the room with a slide that uses their words. If there was no call, the bot must say the slide is research-sourced.
Sales coach. Watches external calls. Tells you what went well and what to try. Does not email the customer a recap unless you ask.
Two routines that stay drafts
Inbox digest, every run:
Scan my work inbox since the last run for threads that plausibly need a reply. Skip newsletters, receipts, calendar RSVPs, and internal noise. For each: sender, subject, one line on what they need, a proposed reply in my voice. Do not send. If nothing needs a reply, say nothing.
Follow-up from notes, every run:
Find external calls that ended since the last run. Meeting notes are the source of truth. Draft a follow-up in chat with To, Subject, and body, next steps that were actually said. Do not send.
Longer job briefs, including ICP scoring and "do not enroll anyone," sit on the sales and customer success pages.
Skills she kept repeating
- Onboard the bot like a teammate. Record the first time you research a stakeholder. Turn the recording into a skill.
- Feed it writing you are proud of, not a brand adjective list.
- When you hate an output, make a rule and add it to the skill. She keeps an anti-slop skill and edits it.
- Ask the Chief of Staff, once a week, what you can further automate or delete. Quiet routines beat a noisy roster.
- Bots can sit in a group and call each other. Slides often get called by the Chief of Staff. You still post the deck.
What you still do
You send. You book. You discount. You update the official forecast. You take over the computer for 2FA. You do not let a prospecting bot invent a podcast the buyer never gave.
If your day is already calls, the point of this setup is the evening admin disappearing. It only disappears if the bots are drafts-only until you trust a specific routine, and even then mail stays on your side of the line.
Source
Field story: Grok Bot for GTM by Krista Letz on x.ai. Her prompts are longer and more Salesforce-specific. Ours are the seats and the never-send rule, aimed at someone setting this up this week.