Prompt Library

Grok Bot RevOps prompts that stop before the CRM write

21 copy-paste prompts

Pipeline hygiene, forecast rolls, routing audits, and data-quality packs. Distinct from outbound sales drafts and office-manager ops. The Bot does not edit stages or 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.

By Louis Corneloup · Founder, Techpresso

Last updated September 3, 2026·Hand-curated & tested by the AI Academy team

Pipeline hygiene

5 prompts

Stage SLA slip list

1/21

✨ What it does

Reads every open deal in [PIPELINE VIEW] that sat in one stage past your SLA and lists last activity plus evidence for slip versus close. You still move stages and close dates in the CRM.

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 open deals in [PIPELINE VIEW] past [STAGE SLA TABLE]. Rank by days over SLA. Do not edit stages. Sources: [CRM PIPELINE VIEW], stage-entered timestamps, last activity, [SLA TABLE]. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - If a stage-entered date is missing, mark unknown. Do not invent dwell time. Deliverable: Deal, stage, days in stage, SLA, last activity, evidence link, suggested human action. Review point: I change the CRM.

💡

Pro tip: Write the SLA in days per stage. "Stale" with no number turns the whole book into a crisis.

Blank or fake next-step hunt

2/21

✨ What it does

Scans [PIPELINE VIEW] for open opportunities with a blank next step, a next step older than [N] days, or a next step that is only a stage name. You still write the next step and owner in the CRM.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find open deals in [PIPELINE VIEW] with a missing, expired, or fake next step. Draft a real next step. Do not write it in the CRM. Sources: [CRM], next-step and next-step-date fields, last activity. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not create tasks or calendar holds. Deliverable: Deal, current next step or blank, why it fails, draft next step, owner, due date. Review point: I type the next step in the CRM.

💡

Pro tip: Treat "follow up" and the stage name as blank. Those are not next steps.

Duplicate opportunity pack

3/21

✨ What it does

Finds likely duplicate opportunities on the same account in [CRM] using name, amount, and close-date overlap, then drafts a keep-or-merge table. You still merge or delete records in the CRM.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find likely duplicate opportunities in [CRM]. Recommend keep versus merge with evidence. Do not merge. Sources: [CRM], account name, amount, close date, owner, created date. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not merge, delete, or close duplicates. Deliverable: Pair, why they look like dups, keep/merge/ask, confidence, links. Review point: I merge in the CRM.

💡

Pro tip: Same logo plus two open deals is not always a dup. Ask for the evidence, then you merge.

Stage-skip and backward-move audit

4/21

✨ What it does

Compares stage history in [PIPELINE] to your [STAGE RULES] and flags skips, backward moves, and same-day stage hops with the user who did them. You still correct stages in the CRM.

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 stage history in [PIPELINE] for [PERIOD] against [STAGE RULES]. Flag skips, backward moves, and hops. Do not revert stages. Sources: [CRM STAGE HISTORY], [STAGE RULES DOC], user who edited. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not revert or lock stages. Do not message the rep. Deliverable: Deal, from-to, when, who, rule broken, suggested fix for me. Review point: I fix the stage if it is wrong.

💡

Pro tip: Same-day hops are often a demo booked as closed-won by accident. Name the hop window.

Closed-lost without a reason

5/21

✨ What it does

Lists deals marked closed-lost in [PERIOD] that are missing a reason code, competitor, or loss note against [REQUIRED LOSS FIELDS]. You still fill reason codes in the CRM.

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 closed-lost deals in [PERIOD] missing [REQUIRED LOSS FIELDS]. Draft the missing reason only when notes support it. Otherwise mark unknown. Sources: [CRM], loss reason, competitor, close notes, [REQUIRED LOSS 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not invent a competitor or a reason. Unknown is allowed. Deliverable: Deal, missing fields, sourced draft or unknown, link. Review point: I fill the reason in the CRM.

💡

Pro tip: A closed-lost with no reason is a hole in the forecast story, not a cleanup chore.

Forecast accuracy

4 prompts

Commit versus what closed

6/21

✨ What it does

Pulls the last [N] weeks of commit from [FORECAST VIEW] against what actually closed and shows over, under, and the deals that flipped after lock. You still change forecast categories in the CRM.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare commit at [LOCK TIME] to closed-won in [PERIOD] from [FORECAST VIEW]. List flips after lock. Do not edit forecast categories. Sources: [CRM FORECAST VIEW], lock snapshot if you have one, closed-won in the window. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not change commit, best case, or pipeline category. Deliverable: Commit, actual, gap, flips with before/after, links. Review point: I change categories if they were wrong.

💡

Pro tip: Pin the lock timestamp. A commit that moves after the call is a finding, not a vibe.

Rep-level over and under

7/21

✨ What it does

Builds a per-rep table from [FORECAST SHEET OR CRM] of commit, best case, pipeline coverage, and slip count for [PERIOD]. You still edit commit calls in the CRM.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Per-rep forecast table for [PERIOD] from [FORECAST SHEET OR CRM]: commit, best case, coverage vs [QUOTA], slips. Do not edit commit. Sources: [CRM OR FORECAST SHEET], quota, close-date history. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not post this to Slack. Do not message reps. Deliverable: Rep, commit, best case, coverage, slips, one question I should ask each. Review point: I run the forecast call.

💡

Pro tip: Coverage without slip count hides the sandbagger and the hero-forecast in the same number.

Repeat close-date push-outs

8/21

✨ What it does

Finds opportunities in [PIPELINE] whose close date moved later [N] or more times and lists each push with the old date, new date, and note if any. You still reset close dates in the CRM.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find deals in [PIPELINE] with [N]+ later close-date moves. Show each push. Do not change close dates. Sources: [CRM] close-date history, notes, stage at each push. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not reset close dates. If history is missing, say so. Deliverable: Deal, push count, old vs new dates, note or none, suggested inspect question. Review point: I reset the date if it is fiction.

💡

Pro tip: Three silent pushes is a process bug. One push with a note can be a real delay.

Coverage versus quota by segment

9/21

✨ What it does

Calculates pipeline coverage versus [QUOTA] by [SEGMENT FIELD] from [PIPELINE VIEW] and flags segments under [X]x with the deals driving the gap. You still rebalance owners and amounts in the CRM.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Coverage vs [QUOTA] by [SEGMENT FIELD] from [PIPELINE VIEW]. Flag segments under [X]x. Do not reassign or edit amounts. Sources: [CRM PIPELINE VIEW], quota by segment, [SEGMENT FIELD]. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not create filler opportunities to make coverage look healthy. Deliverable: Segment, coverage, gap to [X]x, deals driving it, links. Review point: I decide hiring, routing, or amount fixes.

💡

Pro tip: Name the segment field. "The pipeline looks thin" is not a coverage read.

Routing and assignment

4 prompts

Speed-to-lead SLA breaches

10/21

✨ What it does

Measures time from form submit to first owner touch in [INBOUND VIEW] against [SLA MINUTES] and lists breaches with the assigned rep and source. You still reassign leads in the CRM.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Measure submit-to-first-touch in [INBOUND VIEW] vs [SLA MINUTES] for [PERIOD]. List breaches. Do not reassign. Sources: [CRM INBOUND VIEW], created time, first activity, owner, 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not email the lead. Do not change the assignment rule. Deliverable: Lead, source, minutes to first touch, SLA, owner, breach yes/no, link. Review point: I reassign or I change the rule.

💡

Pro tip: First touch means a logged activity, not "the lead exists." Created-at is not a touch.

Territory and round-robin mismatch

11/21

✨ What it does

Compares owner on each new lead in [INBOUND QUEUE] to [TERRITORY RULES OR ROUND-ROBIN SHEET] and flags mismatches with the owner the rule would have picked. You still change owners in the CRM.

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 new leads in [INBOUND QUEUE] for [PERIOD] against [TERRITORY RULES OR ROUND-ROBIN SHEET]. Flag mismatches. Do not change owners. Sources: [CRM], [RULES OR SHEET], owner, country or state, company size if used. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not edit assignment rules or workflows. Deliverable: Lead, current owner, rule owner, why, confidence, link. Review point: I change the owner if the rule is right.

💡

Pro tip: Paste the live rule, not the wiki from last year. Routing pages rot.

Wrong-queue ICP routing

12/21

✨ What it does

Scores inbound in [INBOUND VIEW] against [ICP DOC] and lists leads that landed on the wrong queue, such as AE versus SDR or partner versus direct. You still move records between queues in the CRM.

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 [INBOUND VIEW] against [ICP DOC] and [QUEUE MAP]. Flag wrong-queue placements. Do not move records. Sources: [CRM INBOUND VIEW], [ICP], [QUEUE MAP], [DISQUALIFY AND PARTNER LISTS]. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not enroll anyone in a sequence. Do not email the lead. Deliverable: Lead, current queue, suggested queue, ICP evidence, pass/nurture/AE, link. Review point: I move the record.

💡

Pro tip: Give the disqualify and partner lists or every student form becomes an AE lead.

Orphan and departed-owner records

13/21

✨ What it does

Finds leads and contacts in [CRM VIEW] with no owner, a deactivated owner, or an owner who left after [OFFBOARD DATE], plus a suggested new owner from [RULES]. You still assign owners in the CRM.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find records in [CRM VIEW] with no owner, a deactivated owner, or an owner offboarded after [OFFBOARD DATE]. Suggest a new owner from [RULES]. Do not assign. Sources: [CRM], owner status, [OFFBOARD LIST], [ROUTING RULES]. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not assign, deactivate, or email anyone. Deliverable: Record, current owner or blank, why it is orphaned, suggested owner, rule used. Review point: I assign in the CRM.

💡

Pro tip: Deactivated users silently park inbound. Run this after every offboard, not once a year.

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.

Try AI Academy Free

CRM data quality

4 prompts

Duplicate contacts and accounts

14/21

✨ What it does

Dedupes contacts and accounts in [CRM] by email, domain, and name, and writes a keep-or-merge file with evidence links. You still merge records in the CRM.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find duplicate contacts and accounts in [CRM]. Recommend keep versus merge. Do not merge. Sources: [CRM], email, domain, name, parent account 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not merge or delete. Write the pack as a new file on the computer. Deliverable: Keep / merge / ask counts, pair table with evidence, file path. Review point: I merge in the CRM.

💡

Pro tip: Email match first, then domain, then fuzzy name. Fuzzy-only merges are how you glue two companies together.

Required-field completeness score

15/21

✨ What it does

Scores every open deal in [PIPELINE VIEW] against [REQUIRED FIELDS] and ranks reps by percent complete, with the worst records first. You still fill the missing fields in the CRM.

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 open deals in [PIPELINE VIEW] against [REQUIRED FIELDS]. Rank reps by completeness. Do not fill fields. Sources: [CRM], [REQUIRED FIELD LIST], owner. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not invent amount, close date, or champion to raise the score. Deliverable: Rep completeness %, then deal, missing fields, link. Review point: I fill or I send the list to the owner.

💡

Pro tip: Pick the fields that change a forecast, not every optional box marketing added in 2023.

Lifecycle versus opportunity mismatch

16/21

✨ What it does

Compares contact lifecycle or status in [CRM] to open and closed opportunities and flags contacts marked customer with no closed-won, or closed-won with a still-open lifecycle. You still fix lifecycle values in the CRM.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare [LIFECYCLE OR STATUS FIELD] to opportunities in [CRM]. Flag customer-without-won and won-without-customer. Do not edit lifecycle. Sources: [CRM] contacts, lifecycle field, opportunity outcomes. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not change lifecycle, status, or marketing lists. Deliverable: Contact, lifecycle, opp outcome, mismatch type, suggested value, link. Review point: I fix lifecycle in the CRM.

💡

Pro tip: Lifecycle and opportunity are two systems that drift. Treat mismatch as a finding, not a vibe.

Bad emails, domains, and countries

17/21

✨ What it does

Flags contacts in [LIST OR VIEW] with disposable emails, role addresses, country or territory conflicts, or domains that do not match the account website. You still edit emails and countries in the CRM.

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 [LIST OR VIEW] for disposable email, role addresses, country/territory conflicts, and domain-vs-account mismatches. Do not edit records. Sources: [CRM OR LIST], account website, [TERRITORY RULES], [DISPOSABLE DOMAIN LIST 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not upload a cleaned list to a sequencer. Do not email these contacts. Deliverable: Contact, issue, evidence, keep/fix/suppress recommendation, link. Review point: I edit or I suppress.

💡

Pro tip: Role addresses (info@, sales@) and disposable inboxes are how sequencers burn a domain. Flag them before anyone uploads.

RevOps Bot roster and never-do

4 prompts

RevOps Bot description

18/21

✨ What it does

Writes a Bot description named [NAME] that owns pipeline hygiene, forecast packs, and routing audits, with a hard never-edit-the-CRM rule. You still create the Bot and change the CRM.

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 RevOps Bot description named [NAME]. One job: hygiene, forecast, routing, data quality. Never edit the CRM. Never send. Sources: [CRM VIEWS], [SLA TABLE], [FORECAST CADENCE], [REVIEW TIME]. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - This Bot must refuse stage edits, sends, and workflow publishes. Deliverable: Name, 8-line job, sources, weekly artifacts, never-do, approval line. Review point: I create the Bot from this text.

💡

Pro tip: One job: the CRM truth. Not outbound drafts (sales) and not invoices (ops).

Monday hygiene pack routine

19/21

✨ What it does

Designs a Monday routine that posts a hygiene pack for [PIPELINE VIEW]: SLA slips, missing next steps, forecast flips, and routing breaches. You still make every CRM edit after you read the pack.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Mondays at [07:00] [TZ], post a hygiene pack on [PIPELINE VIEW]: SLA slips, blank next steps, forecast flips, routing breaches. Do not edit the CRM. Sources: Current [PIPELINE VIEW], [INBOUND VIEW], [FORECAST VIEW]. If a view is empty or the CRM is down, report failure. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not post to Slack unless I later turn this into a routine with approval. Deliverable: Routine card: next run, inputs, output format, approval line, failure behavior. Review point: Test run first. I enable it.

💡

Pro tip: Fail closed if the CRM view is empty or down. Do not reuse last Monday.

Forecast-lock pack before the call

20/21

✨ What it does

Builds a pre-call lock pack from [FORECAST VIEW] for [MEETING TIME]: commit math, at-risk deals, push-outs, and questions per rep. You still lock or change forecast categories in the CRM.

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 lock pack from [FORECAST VIEW] due [MEETING TIME]. Commit math, at-risk, push-outs, one question per rep. Do not lock categories. Sources: [FORECAST VIEW], [QUOTA], close-date history, last week's lock 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. - Do not email the team the pack. Do not change categories. Deliverable: One-page pack plus links. Facts vs guesses labeled. Review point: I run the call. I lock the CRM.

💡

Pro tip: Cap it at one page or nobody reads it on the call. Questions, not a novel.

What RevOps Bots never do

21/21

✨ What it does

Writes the never-do list for RevOps Bots from [MY RULES], covering stage edits, amount edits, sends, mass deletes, and workflow publishes. You still paste the list and you still change the CRM.

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-do list for my RevOps Bots from [MY RULES]. Cover stages, amounts, owners, sends, merges, deletes, and workflow publishes. Sources: My rules: [E.G. NO STAGE EDITS, NO MASS DELETE, NO WORKFLOW PUBLISH]. 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 edit stages, amounts, close dates, owners, or workflows. Do not send, enroll, merge, delete, or contact anyone. Deliverable: 12 never-do items and the approval substitute for each. Review point: I paste this into every RevOps Bot description.

💡

Pro tip: If it is not written, a helpful Bot will "just fix the stage" at 2am.

Free tool

Prompt Optimizer

Turn a rough idea into a structured, professional AI prompt.

Try it free →

Frequently Asked Questions

Grok Bot is an always-on AI teammate from xAI / SpaceXAI that runs on a persistent cloud computer (browser, files, terminal). You message it like a coworker and it finishes work inside the apps you already use. Grok on grok.com or in the X app is a chat assistant with live search and Grok Imagine. These pages are only for the teammate product. For chat and Imagine prompts, use the Grok prompts library.

Yes. Official docs are explicit: isolation is per user, not per Bot. Files, browser logins, and plugins on the computer are visible to every Bot on your account. Do not treat a second Bot as a security boundary. Put irreversible actions (send, pay, delete, production changes) behind approval.

Access has expanded since the August 2026 launch. It is included with SuperGrok plans and with Cursor Pro and Cursor Teams, plus a limited free trial for everyone else at times. Plans and weekly usage change. Check the official Grok Bot plans page before you buy a seat for this product.

It can open the CRM in the browser and read saved views. These briefs still stop at tables and drafts. You change stages, amounts, owners, and close dates. A Bot that "just fixes" a stage is how a commit number moves with no human on the hook.

The sales page is outbound: ICP scoring, contact finding, and email or LinkedIn drafts you send. This page is RevOps: pipeline hygiene, forecast accuracy, routing, and CRM data quality. Reopen notes for stale deals live on sales. SLA slips and duplicate-merge packs live here.

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.

Start 7-Day Free Trial AI for entrepreneurs

7-day free trial. Cancel anytime.

Browse All Prompt Collections

Popular prompt collections

AI Photo Editing Prompts ChatGPT Jailbreak Prompt Best ChatGPT Prompts Funny Hinge Prompts ChatGPT Caricature Prompts