Grok Bot prompts for sales research that stops at drafts
Official sales-outbound shape: score the CRM view, skip people already in a sequence, draft email and LinkedIn in your voice. You send.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Account research overnight
4 promptsScore a CRM view against the ICP
1/21✨ What it does
The Bot scores every account in [CRM VIEW] against the ICP in [DOC] and ranks the top [25] with a why-now note and evidence links. You decide who is worth a draft; the Bot does not write outreach unless you ask.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Score every account in [CRM VIEW] against the ICP in [DOC]. Rank the top [25]. Sources: [CRM VIEW], [ICP DOC], company websites, [INTENT TOOL IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - Skip anyone already in an active sequence. Deliverable: Table: account, score 1-5, why now, evidence links, already-in-sequence (yes/no). Review point: Stop at the table. Do not write outreach yet unless I ask.
Pro tip: Point at a view name, not "the CRM". Vague sources make the Bot wander and burn weekly usage.
Find three contacts per account
2/21✨ What it does
The Bot finds up to three relevant contacts on each account in [LIST], with a reason and a source, and skips anyone already in the CRM. You pick who gets a draft.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: For each account on [LIST], identify up to 3 relevant contacts. Exclude anyone already in the CRM. Sources: [CRM], [LINKEDIN OR APPROVED SOURCING], company sites, [TITLE MAP IN ICP DOC]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. Deliverable: Account, name, title, why they fit, source URL, already-in-CRM (yes/no). Review point: I pick who gets a draft.
Pro tip: Ask for the evidence of the match. Title-only lists are how you email the wrong person.
Draft email and LinkedIn in my voice
3/21✨ What it does
The Bot writes one email and one LinkedIn note per approved contact, in the style of the examples you attach and using [OFFER ONE-LINER]. You send from your own accounts.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft one email and one LinkedIn note per approved contact, in the style of the examples attached. Sources: Approved contact list from this thread, [OFFER ONE-LINER], style examples attached. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - No fake personalization. If you cannot find a real hook, say "no hook" and skip. Deliverable: Per contact: hook used, email draft, LinkedIn draft, and the source of the hook. Review point: I send from my own accounts.
Pro tip: Attach two emails you actually sent. "Write like me" without examples writes like a bot.
Nightly research routine (drafts only)
4/21✨ What it does
The Bot sets a weekday run at [07:00] [TZ] that researches [CRM VIEW] and posts a review list, or reports failure if the view is empty. You enable the routine after a test run; the Bot still does not send.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Weekdays at [07:00] [TZ], run the account-research skill on [CRM VIEW] and post the review list here. Sources: Current [CRM VIEW]. If the view is empty or the CRM is down, report failure. Do not reuse yesterday. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. Deliverable: Routine card: next run, input, output, approval line, failure behavior. Review point: Test run first. I enable it.
Pro tip: Create the routine only after a second input looked as good as the first.
Prompts get you started. Tutorials level you up.
A growing library of 300+ hands-on AI tutorials. New tutorials added every week.
Calls, pipeline, and follow-up
4 promptsBuild a call brief from the last 90 days
5/21✨ What it does
The Bot writes a one-page brief for [ACCOUNT] meeting on [DATE], with last touches, likely objections, and six questions, using [CRM ACCOUNT], [EMAIL THREADS], and [DECK THEY SAW]. You run the call; the Bot does not put anything on the calendar.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: A one-page call brief for [ACCOUNT] meeting on [DATE]. Sources: [CRM ACCOUNT], [EMAIL THREADS], [SLACK IF ANY], [DECK THEY SAW]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - Separate facts in the CRM from guesses. Deliverable: Attendees, last 5 touches, stated need, likely objections, 6 questions I should ask, links. Review point: Brief only. Do not put a meeting on the calendar.
Pro tip: Tell it which CRM fields are trustworthy. Notes fields are often fiction.
Flag stale opportunities
6/21✨ What it does
The Bot lists deals in [PIPELINE] with no activity for [N] days and drafts a reopen note for each. You change the CRM; the Bot does not edit stages or close dates.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List opportunities in [PIPELINE] with no activity for [N] days. Draft a reopen note for each. Sources: [CRM PIPELINE VIEW], activity timestamps, last email if visible. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - Do not edit stages, amounts, or close dates. Deliverable: Deal, last activity, suggested next step, draft note, confidence. Review point: I change the CRM.
Pro tip: Define "stale" in days. Otherwise every quiet deal becomes a crisis.
Competitive landmine card
7/21✨ What it does
The Bot writes a one-page card for [COMPETITOR] versus you for [PERSONA] at [ACCOUNT], with where you win, where you lose, and sourced claims only. You use it on the call; the Bot does not email the buyer.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: A battlecard for [COMPETITOR] vs us for [PERSONA] at [ACCOUNT]. Sources: [BATTLECARD FOLDER], recent call notes, competitor site, [G2 OR APPROVED SOURCE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - No invented win rates or quotes. Deliverable: Where we win, where we lose, two questions that surface the gap, sources. Review point: I use it on the call. You do not email the buyer.
Pro tip: Ban invented win rates. If you do not have a source, the cell says unknown.
Handoff pack for customer success
8/21✨ What it does
The Bot builds a closed-won pack for [ACCOUNT] covering promises, stakeholders, risks, and the first 30 days. You drop it in the CS channel; the Bot does not create tasks or edit the opportunity.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a closed-won handoff pack for [ACCOUNT]. Sources: [CRM], [PROPOSAL], [CALL NOTES], [SLACK]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - Do not create CS tasks or edit the opportunity. Deliverable: Promises made, stakeholders, risks, first 30-day success definition, links. Review point: I drop it in the CS channel.
Pro tip: This is a great agent-to-agent handoff to a CS Bot, still with you on the approval.
Inbound and events
4 promptsTriage inbound demo requests
9/21✨ What it does
The Bot scores [INBOUND QUEUE] for [DATE RANGE] against your ICP and [DISQUALIFY LIST], and recommends take, nurture, or pass with a draft. You book or you pass.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Triage [INBOUND QUEUE] for [DATE RANGE]. Recommend take / nurture / pass. Sources: [FORM TOOL OR CRM INBOUND VIEW], [ICP], [DISQUALIFY LIST]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. Deliverable: Lead, score, reason, recommended slot or nurture draft. Review point: I book or I pass.
Pro tip: Give it the disqualify list (students, competitors, agency tire-kickers) or it will treat every form as gold.
Event follow-up in my voice
10/21✨ What it does
The Bot turns [EVENT] badge scans into hot, warm, and skip piles, with a draft for hot and warm using your booth notes and [OFFER]. You send from your event mailbox.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft follow-up for [EVENT] scans. Group by conversation quality. Sources: [CSV OF SCANS], my booth notes, [OFFER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. Deliverable: Hot / warm / skip, draft per hot and warm, missing-notes flag. Review point: I send from my event mailbox.
Pro tip: If you have no notes, say so. Fake "great chatting about X" is worse than a short honest note.
Quote a custom deal without sending it
11/21✨ What it does
The Bot drafts a quote explanation for [ACCOUNT] for [SKU MIX] from [PRICE BOOK] and [DISCOUNT RULES], and marks any discount that needs you. You send the quote from the official tool.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a quote explanation for [ACCOUNT] for [SKU MIX]. Do not send. Sources: [PRICE BOOK], [DISCOUNT RULES], [CRM], [EMAIL THREAD]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - Do not invent discounts. If a discount needs approval, mark it pending me. Deliverable: Line items, rationale, open questions, draft email. Review point: I send the quote from the official tool.
Pro tip: Lock discount authority in the constraints. Bots will "be helpful" and invent 20% off.
Weekly pipeline digest for me
12/21✨ What it does
The Bot writes a digest of [PIPELINE] since [FRIDAY]: what moved, what is stuck, and decisions you owe, each with a link. You share it if you want; the Bot does not post to Slack.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Weekly digest of [PIPELINE] since [FRIDAY]. Only what needs my decision. Sources: [CRM], [PRIORITIES DOC], my calendar. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - Do not post to Slack unless I later turn this into a routine with approval. Deliverable: Moved / stuck / closing this week / decisions I owe, each with a link. Review point: Post here. I share if I want.
Pro tip: Map it to your priorities doc or it will narrate every stage change like news.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
GTM desk (Krista / Instantly-style, still gated)
4 promptsBuild a sequence I will load myself
13/21✨ What it does
The Bot writes a 5-step sequence for [PERSONA] selling [OFFER], with exits for reply, bounce, and unsubscribe. You paste it into the sequencer; the Bot does not enroll anyone.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a 5-step sequence for [PERSONA] selling [OFFER] with exits for reply, bounce, and unsubscribe. Sources: [ICP], [OFFER], style examples, [COMPLIANCE NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - Do not enroll anyone in Instantly, HeyReach, or the CRM sequencer. Deliverable: Steps, delays, subject lines, bodies, exit rules. Review point: I paste it into the sequencer.
Pro tip: Community GTM packs exist. You still load Instantly or HeyReach yourself after review.
Clean a list before I upload it
14/21✨ What it does
The Bot cleans [LIST FILE] against [CRM] and [SUPPRESSION FILE] and writes keep, suppress, and ask-me counts plus a cleaned file path. You upload the file.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Clean [LIST FILE] against [CRM] and [SUPPRESSION FILE]. Sources: The attached list, [CRM], [SUPPRESSION]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - Do not upload the list to any sequencer. Deliverable: Keep / suppress / ask-me counts, and the cleaned file path on the computer. Review point: I upload.
Pro tip: List CLIs belong on the computer. Uploading a dirty list is how you burn domains.
Per-account expert Bot brief
15/21✨ What it does
The Bot writes a description for an expert that only works on [ACCOUNT], including weekly output and a refuse-list for other accounts. You create the Bot from that text.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a Bot description for an expert on [ACCOUNT] only. Sources: [CRM], [QBR DECK], [CONTRACT DATES], [CHAMPION NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - This Bot must refuse work about other accounts. Deliverable: Name, job, sources, weekly output, approval line, refuse-list. Review point: I create the Bot from this text.
Pro tip: Enterprise field pattern: one CoS plus per-account experts, not one Bot that "does sales".
Live slide updates I present
16/21✨ What it does
The Bot updates [DECK] slides [N] with current numbers from [SOURCE] for [DATE RANGE], keeps a copy of the original, and leaves narrative slides alone. You present; the Bot does not email the deck.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Update [DECK] slides [N] with current numbers from [SOURCE]. Do not email the deck. Sources: [DECK FILE], [CRM OR SHEET], [DATE RANGE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - Do not change narrative slides, only marked number slides. Keep a copy of the original. Deliverable: What changed, old vs new, source link, path to the new file. Review point: I present.
Pro tip: Ask for the cell or slide number plus the source link. "Make the deck better" is not a job.
Guardrails sales Bots forget
5 promptsNo fake personalization audit
17/21✨ What it does
The Bot reviews the drafts in this thread and flags every hook that is generic, invented, or unverifiable against the claimed source URLs. You send only the real ones.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Audit these drafts. Flag every hook that is generic, invented, or unverifiable. Sources: Drafts in this thread, and the claimed source URLs. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. Deliverable: Draft, hook, verdict (real / weak / fake), rewrite or "delete this draft". Review point: I send only the real ones.
Pro tip: This is the skill you run before you become the person who emailed "loved your post" on a private account.
Unsubscribe and consent check
18/21✨ What it does
The Bot checks [LIST] against [UNSUB FILE] and [REGION RULES] and recommends suppress, ask-legal, or ok-to-consider. You decide, and when unsure you suppress; this is not legal advice.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Check [LIST] against [UNSUB FILE] and [REGION RULES]. Recommend suppressions. Sources: Attached list, unsub file, [CRM CONSENT FIELDS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send, enroll, or contact anyone. - This is not legal advice. When unsure, suppress. Deliverable: Suppress / ask-legal / ok-to-consider, with the rule that fired. Review point: I decide. When unsure I suppress.
Pro tip: Regional requirements are yours. The Bot can flag. It cannot make you compliant by vibes.
What I will not automate
19/21✨ What it does
The Bot writes a never-automate list for your sales Bots from your rules, such as [E.G. NO PRICING BY EMAIL, NO LEGAL MARKUP, NO CUSTOMER FORWARDS], plus what a human does instead. You paste the list into every sales Bot description.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write the never-automate list for my sales Bots. Sources: My rules: [E.G. NO PRICING BY EMAIL, NO LEGAL MARKUP, NO CUSTOMER FORWARDS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. Deliverable: 10 never-do items and the approval substitute for each. Review point: I paste this into every sales Bot description.
Pro tip: If it is not written, a helpful Bot will eventually "just send it".
Account expert Bot profile
20/21✨ What it does
The Bot writes a profile that owns only [ACCOUNT], including what good looks like, who you must never email, and the weekly artifact. You create the Bot; the Bot does not email the account.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a Bot profile that owns only [ACCOUNT]. Include what good looks like, who we must never email, and the weekly artifact. Sources: [CRM ACCOUNT], [NOTES], [LAST QBR]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email the account. Do not create a second Bot until I approve this profile. Deliverable: Name, 8-line description, never-do, weekly artifact format. Review point: I create the Bot.
Pro tip: Put the account name in the Bot name. Generic "sales" Bots smear context across logos.
Overnight prospecting, Instantly drafts only
21/21✨ What it does
The Bot builds a review table for [N] new accounts from [LIST SOURCE], drafts Instantly or HeyReach copy in your voice, and skips anyone already in a sequence. You enroll the ones you want.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a review table for [N] new accounts from [LIST SOURCE]. Draft Instantly / HeyReach copy in my voice. Do not enroll. Sources: [LIST], [CRM], [VOICE SAMPLES]. Skip anyone already in a sequence. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send. Do not enroll. Do not add to Instantly. Deliverable: Account, why now, contacts, drafts, sources. Review point: I enroll the ones I want.
Pro tip: Name the "already in sequence" rule or you pay twice for the same lead.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides