Productivity
What RevOps Bots never do
What RevOps Bots never do turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
The prompt
What RevOps Bots never do guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning work, making decisions, or organizing complex information and you want a response that is easier to evaluate and act on.
text prompt
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 {{myRules}}. 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.
Tune the prompt, not the plumbing.
Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.
Customized prompt936 characters
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 a specific 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.
Useful structure, room to move.
What RevOps Bots never do guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning work, making decisions, or organizing complex information and you want a response that is easier to evaluate and act on.
The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.
Related prompts
Rep-level over and under
Rep-level over and under turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
ChatGPTClaudeGemini
RevOps Bot description
RevOps Bot description turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
ChatGPTClaudeGemini
Closed-lost without a reason
Closed-lost without a reason turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
ChatGPTClaudeGemini
Commit versus what closed
Commit versus what closed turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.
ChatGPTClaudeGemini