Grok Bot support prompts: triage and drafts, not autopilot replies
Field case: a support agent on a routine in 19 minutes. These prompts still keep the public reply behind you. Repro stays in staging. No production customer data.
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.
Triage
4 promptsMorning queue rank
1/21✨ What it does
The Bot ranks open tickets in [QUEUE] by SLA risk and customer impact, using [SLA DOC], and does not reply. You assign the work.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Rank open tickets in [QUEUE] by SLA risk and customer impact. Do not reply. Sources: [HELPDESK], [SLA DOC], [CRM FOR ARR IF ALLOWED]. 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 change status. Do not reply. Deliverable: Ticket, SLA, why it is high, suggested owner. Review point: I assign.
Pro tip: Give it SLA names. "Urgent" without a clock is theater.
Duplicate and known-issue collapse
2/21✨ What it does
The Bot clusters [QUEUE] for the last [7] days into likely duplicates of known issues and drafts an unpublished internal note. You merge them if they are real duplicates.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Cluster [QUEUE] for the last [7] days into likely duplicates of known issues. Sources: [HELPDESK], [STATUS PAGE], [KNOWN ISSUES 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 close or merge tickets. Deliverable: Cluster, sample tickets, draft internal note, draft customer workaround (unpublished). Review point: I merge if they are real dupes.
Pro tip: Do not close tickets as dupes. You do that after you read them.
Angry-and-right vs angry-and-stuck
3/21✨ What it does
The Bot flags tickets that are both high-emotion and high-evidence you actually failed, using [HELPDESK] and [CRM]. You take those first; it does not send an apology.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Flag tickets that are both high-emotion and high-evidence we failed. Sources: [HELPDESK], [CRM]. 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 reply. Do not issue refunds. Deliverable: Ticket, evidence we failed, suggested human, draft apology (unpublished). Review point: I take those first.
Pro tip: A calm VIP can be more urgent than a loud free user. Put ARR in the sources if that is the rule.
After-hours pack
4/21✨ What it does
The Bot sorts overnight [QUEUE] into cannot-wait, can-wait, and spam, and drafts unpublished replies for cannot-wait. You send the cannot-wait replies.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Overnight pack for [QUEUE]: cannot-wait, can-wait, spam. Sources: [HELPDESK], [ONCALL 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 reply after hours as me. Deliverable: Three buckets, draft replies for cannot-wait, unpublished. Review point: I send cannot-wait.
Pro tip: This is the 19-minute agent if you already have macros. Still no auto-reply.
Prompts get you started. Tutorials level you up.
A growing library of 300+ hands-on AI tutorials. New tutorials added every week.
Repro and macros
4 promptsStaging repro from the ticket
5/21✨ What it does
The Bot reproduces [TICKET] in staging with steps, expected versus actual, and screenshots, and will not use the reporter production data. You attach 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: Reproduce [TICKET] in staging. Pack: steps, expected/actual, screenshots. No prod customer data. Sources: [TICKET], [STAGING], test account via secret card. 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 use the reporter's production data. Do not reply on the ticket. Deliverable: Pack path, or cannot-repro with missing info. Review point: I attach it.
Pro tip: Fresh test account. No prod customer exports into the pack.
Macro draft from a good thread
6/21✨ What it does
The Bot turns [TICKET] into a macro with when-to-use and when-not, without creating it in the helpdesk. You create the macro.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Turn [TICKET] into a macro with when-to-use and when-not. Sources: That ticket, [MACRO STYLE]. 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 create the macro in the helpdesk. Deliverable: Macro title, body, when/not. Review point: I create it.
Pro tip: Macros without a "when not to use" become lies.
Help-center drift
7/21✨ What it does
The Bot compares [HELP CENTER] to what tickets say about [ISSUE] and lists the drift, with screenshots. You file the doc change.
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 [ISSUE], compare [HELP CENTER] to what tickets describe. List drift. Sources: Help center in the browser, sample tickets. 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 docs. Do not reply to those tickets with a guess. Deliverable: Doc claim, ticket reality, screenshot, suggested doc fix. Review point: I file a doc change.
Pro tip: Computer use. Do not edit the help center.
Needs-repro Slack bridge
8/21✨ What it does
The Bot watches [#support-eng] for "needs repro" plus a ticket link and builds a staging pack in this chat. You enable the trigger; it never posts back to Slack on its own.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: On "needs repro" plus a ticket link in [#support-eng], build a staging pack here. Never post back without approval. Sources: Slack, helpdesk, staging. 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. - Never post back to Slack without approval. Deliverable: Trigger rule and pack format. Review point: I enable.
Pro tip: Same official event shape as engineering.
Replies you still send
4 promptsDraft in our voice
9/21✨ What it does
The Bot drafts a reply to [TICKET] in our voice, with doc links, and leaves it here. You send it.
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 reply to [TICKET] in our voice. Do not send. Sources: The ticket, voice examples, [POLICY]. 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 CC the customer's boss. Deliverable: Draft, links to docs, what you assumed. Review point: I send.
Pro tip: Attach two replies you are proud of. Ban "I understand your frustration" unless you do.
Refund or credit recommendation
10/21✨ What it does
The Bot recommends refund, credit, or no for [TICKET] against [POLICY], and does not issue money. You issue it or refuse.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Recommend refund / credit / no for [TICKET] against [POLICY]. Do not issue it. Sources: [TICKET], [BILLING], [POLICY]. 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 refund. Do not email finance as me. Deliverable: Recommendation, cite, draft customer note, draft internal note. Review point: I issue or I refuse.
Pro tip: Put the credit policy in sources or the Bot will be generous with your margin.
Security-looking ticket
11/21✨ What it does
The Bot stops if [TICKET] looks like a security report, will not ask for secrets in the thread, and writes the internal handoff. You take security intake.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: If [TICKET] looks like a security report, stop. Do not ask for secrets in-thread. Write the internal handoff. Sources: [TICKET], [SECURITY INTAKE]. 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 reply to the reporter. Do not download attachments that look like dumps into /workspace. Deliverable: Why it looks like security, internal handoff, what not to say. Review point: I take security intake.
Pro tip: A Bot that asks for logs in the public ticket is the incident.
VIP path
12/21✨ What it does
The Bot checks [VIP LIST] and, if the requester is on it, drafts the VIP path instead of the generic macro. You or the account owner send it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: If the requester is on [VIP LIST], draft the VIP path, not the macro. Sources: [VIP LIST], [TICKET], [CSM 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 email the CSM's customer. Do not @ the customer in Slack. Deliverable: VIP (yes/no), draft, who should send it. Review point: CSM or I send.
Pro tip: Put the VIP list in the Bot. Do not let it invent VIPs from email tone.
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.
Routines
3 prompts19-minute agent, drafts only
13/21✨ What it does
The Bot builds the overnight pack for [QUEUE] every morning at [07:00] [TZ]: rank, duplicates, draft replies, and does not send. You enable it after a test morning.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Every morning at [07:00] [TZ], build the overnight pack for [QUEUE]: rank, dupes, draft replies. Do not send. Sources: [HELPDESK]. If it is down, fail closed. 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 replies in the routine. Deliverable: Routine card. Review point: I enable after a test morning.
Pro tip: The YouTube "24/7 agent" is a routine. These prompts keep it at drafts.
SLA breach warning
14/21✨ What it does
The Bot lists tickets that will breach the SLA in [4] hours, max [15], and drafts unpublished replies. You send those replies.
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 tickets that will breach SLA in [4] hours, max [15]. Draft replies unpublished. Sources: [HELPDESK], [SLA]. 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 change SLA. Deliverable: Ticket, time left, draft. Review point: I send.
Pro tip: Cap the list. A 200-ticket warning is noise.
Weekly theme rollup
15/21✨ What it does
The Bot rolls [QUEUE] into weekly themes with counts and sample tickets, plus a draft product note. You take that note to product.
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 themes from [QUEUE] with counts and sample tickets. Sources: [HELPDESK]. 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 customers a "we heard you". Deliverable: Theme, count, samples, draft product note. Review point: I take it to product.
Pro tip: JTBD, not button names.
Make the support Bot durable
6 promptsSupport Bot description
16/21✨ What it does
The Bot writes a support description named [NAME] for [QUEUE] and [SLA], with never-send and no production-data rules. You create that Bot.
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 support Bot description named [NAME]. Sources: [QUEUE], [SLA], [STAGING]. 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. - Never send. Never refund. Never use prod customer data in staging. Deliverable: Description, pack format, never-do. Review point: I create it.
Pro tip: Mention staging-only repro and secret-card test accounts.
What support Bots never do
17/21✨ What it does
The Bot writes a never-do list for support Bots: no public replies, no refunds, no password resets, no "send us your database". You paste those twelve items.
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 support Bots. Sources: My 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. Deliverable: 12 never-do items. Review point: I paste it.
Pro tip: Password-reset requests are social engineering until a human says otherwise.
Handoff to eng or CS
18/21✨ What it does
The Bot writes two handoff templates: support to engineering for a repro, and support to customer success when a logo is at risk. You use those templates; it does not mention whole channels.
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 handoff templates: support → eng (repro) and support → CS (logo at risk). Sources: [TICKET FORMAT], [PORTFOLIO RULE]. 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 @channels. Do not email the customer as part of the handoff. Deliverable: Two templates. Review point: I use them.
Pro tip: Ownership line: support Bot prepares, eng Bot repros, CS Bot watches logos, you send.
19-minute agent, routine not rewrite
19/21✨ What it does
The Bot designs a 19-minute setup for [HELPDESK]: queue, macros, draft format, and review time, without going live. You build it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Design a 19-minute setup: queue, macros, draft format, review time. Do not go live. Sources: [HELPDESK], [MACROS], [SLA]. 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 replies. Do not change macros. Deliverable: Setup checklist and first-day routine card. Review point: I build it.
Pro tip: The first version drafts replies. Sending is a later, separate approval.
Macro draft from real tickets
20/21✨ What it does
The Bot reads [N] tickets about [ISSUE] and drafts one macro, noting where they disagree. You publish it only if they agree.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: From [N] tickets about [ISSUE], draft one macro. Note where they disagree. Do not publish. Sources: [HELPDESK QUERY]. 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 publish macros. Do not reply to those tickets. Deliverable: Draft macro, dissent, sources. Review point: I publish if they agree.
Pro tip: If the 10 tickets disagree, you do not have a macro yet.
PII redaction before the pack leaves support
21/21✨ What it does
The Bot redacts [PACK] of emails, phones, tokens, and account numbers, keeps ticket ids, and lists what types it removed. You send the redacted 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: Redact [PACK] of emails, phones, tokens, and account numbers. Keep ticket ids. Do not send the pack. Sources: The pack file. 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 eng. Do not store the unredacted copy in a new public folder. Deliverable: Redacted path and a list of what you removed (types, not values). Review point: I send.
Pro tip: Screenshots hide less than you think. Crop or redact.
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