8 Grok Bot Prompts for Research, Document Organization, and Email Drafts

When asking Grok Bot to do something, specify what to research, which materials to use, what counts as complete, and which actions it should stop before taking. This makes the results easier to check. Here are eight requests you can copy and adapt for xAI's Grok Bot. These are not prompts for regular Grok chats or automated reply bots on X.

xAI's Grok Bothttps://docs.x.ai/grok-bot/overview

The following are example requests. They do not guarantee that each task will succeed in actual use. The available actions depend on the apps you connect and their access permissions. For initial setup, see How to Set Up and Use Grokbot.

If you are considering building and operating a Bot tailored to your business, in addition to refining your requests, you can review the assistance available through ZETTAi's AI Agent Development Support.

ZETTAi's AI Agent Development Supporthttps://zettai-ai-agent-site-render.onrender.com/

Five Things to Specify Before Writing a Request

ItemWhat to specifyExample
PurposeThe decision you want to make or the output you want to createCompare updates from three competitors
InputTarget URLs, files, and time periodSpecified URLs and the past 30 days
OutputTable columns, character count, and save locationA table with company name, update date, URL, and key points
VerificationHow to handle unknowns or contradictionsMark the date as unverified if it cannot be obtained
Action boundariesHow to handle sending, publishing, and updatingDraft only. Do not send anything externally

The official guidance on making requests also advises making the desired result and action boundaries clear. Replace the [ ] placeholders in each request with your actual document names or time periods, and remove unnecessary lines before sending it. Check your company's usage rules before providing customer information or confidential company information.

official guidance on making requestshttps://docs.x.ai/grok-bot/chat-and-collaboration

1. Compare Public Information

Purpose: Prepare information to help me decide [decision to make] about [topic to compare].
Scope: Only the public pages at [URL 1], [URL 2], and [URL 3].
Comparison criteria: [pricing / features / implementation requirements, etc.]. Also check numerical units, applicable plans, and applicable regions.

Create a comparison table with criteria as rows and companies or services as columns, and include a supporting URL in each cell.
Record publication and update dates separately from the date you actually checked the information.
If information is not stated, mark it "Not stated". If you cannot read a page, mark it "Unverified".
At the end, separate "What can be concluded" from "What cannot be concluded because the conditions are not comparable".
If you cannot read a target URL, identify it and do not complete the comparison through guesswork.
Do not log in, post anything, or modify files.

Limiting the scope to the specified sources makes it easier to trace the extent of the research. The content at a URL may be outdated, so check that publication dates and retrieval dates are not confused. How to Create a Research Report explains how to conduct a comparison as a complete workflow.

2. Organize Key Points from PDFs and Internal Documents

Using only the attached [document name], create a summary that [readers] can use for [decision or task].
First, state the document name, version and date, and relevant pages. Mark any unknown information as "Not stated".
Present no more than five key points in a table with these columns: "Key point / Supporting page or heading / Relevance to the reader".
Next, separate "Decisions made", "Undecided matters", and "Questions to clarify".
Include only items explicitly identified as decisions in the document under decisions made. Do not fill in missing dates, figures, or people responsible.
If page numbers are unreadable, identify the location using a heading or quoted passage.
If you cannot read the document, explain why and stop. Do not modify the original; return the summary in this conversation.

You can attach PDFs, Office documents, and other files to Grok Bot (see the official file guide). Even after attaching a file, return to the page numbers and original text to check the figures.

official file guidehttps://docs.x.ai/grok-bot/files-and-results

3. Extract Next Actions from Meeting Notes

From the attached notes for [meeting name and date], create a list for [intended recipients] to review.
Separate "Decisions made", "Proposals and opinions", and "Pending matters", and include the supporting location in the notes for each item.
Present next actions in a table with these columns: "Task / Person responsible / Deadline / Supporting location / Points requiring confirmation".
If a person responsible or deadline is not explicitly stated, mark it "Not stated". Do not assign either through guesswork.
If statements conflict, list the issue as requiring confirmation rather than as a decision.
At the end, provide no more than three questions to confirm with the people responsible.
If you cannot read the notes, stop. Do not contact participants or create calendar events.

It is important to keep meeting proposals separate from decisions. Have a person check any rows where responsibility is unclear before sharing them.

4. Draft an Email Reply

Target: The email with [subject, sender, and date received]. Use only [permitted reference materials] as evidence.
Purpose: Draft a reply that communicates [purpose of the response].
First, list the sender's questions and requests, and separate "Points that can be answered / Supporting evidence" from "Points requiring confirmation / Who or where to check with".
Next, provide the subject and body, communicating only verified facts politely and concisely.
Do not finalize pricing, schedules, commitments, or internal decisions without supporting evidence.
At the end, list the recipients, attachments, and unanswered questions I should check before sending.
If you cannot read the target email or reference materials, stop. Do not send or forward anything; return the draft in this conversation.

Handling email requires a connection to the relevant account. The official approval guide lists sending messages and invitations among the actions subject to explicit boundaries.

official approval guidehttps://docs.x.ai/grok-bot/approvals-security-and-privacy

5. Check for Scheduling Conflicts

Scope: [Calendar name], from [start date and time] to [end date and time]. Display times in [time zone].
Find overlapping events and combinations that do not allow [estimated travel time].
Create a table with these columns: "Event A / Event B / Overlapping time or travel-time shortfall / Reason / Suggested adjustment".
If a location is unknown, mark it "Needs confirmation" instead of guessing the travel time.
If there are no overlaps, state this along with the range of events you were able to check.
If you cannot read the calendar, stop. Do not change or create events, or contact participants.

Check calendar viewing permissions and the time zone before using this request. Also decide in advance which unannounced or private events to include.

6. Check Spreadsheet Figures

Scope: [Sheet name] in the attached [file name], covering [target rows or period].
Columns to check: [ID column], [required columns], [amount column], and [total column]. Amounts are in [unit].
Check for blank cells, duplicate IDs, and mismatched totals.
First, state the number of rows in scope and the column names. Stop if any specified column is missing.
Identify duplicate IDs using exact matches, and list suspected variations in notation separately.
Recalculate totals according to [aggregation method, tax treatment, and rounding rules]. If any required conditions are missing, ask questions first.
Present the results in a table with these columns: "Row number / ID / Original value / Issue / Expected value and formula / Verification method".
Do not overwrite the original file; present suggested corrections separately. Do not fill in unknown values.

When making decisions based on figures, recheck the rows identified by the Bot in the original file. Differences in the source data's units or aggregation periods can lead to misinterpretation even when the calculations are correct.

7. Draft an Article or Announcement

Using only the attached [confirmed product information] as evidence, create an announcement for [readers] to appear in [publication channel].
The key point to communicate is [most important fact], and the action readers should take is [action].
Present the following in order: "Three headline options", "Summary of approximately 120 characters", "Body", and "Checks before publication".
In the body, explain the intended users, changes, conditions of use, and start date to the extent supported by the materials.
Do not include performance claims, pricing, availability dates, implementation track records, or comparisons with other companies that are not in the materials.
If statements in the materials conflict, list them as points to confirm instead of making definitive statements in the body.
If you cannot read the materials, stop. Do not publish to a website or social media; return a draft.

Before publication, the person responsible should check the facts, trademarks, and link destinations. Do not configure the Bot to publish its drafts directly without review.

8. Review the Completed Output Again

Cross-check the [output name] you just created against [source document names and URLs].
Break the output down into verifiable claims, and create a table with these columns: "Relevant passage / Assessment / Supporting location / Required correction".
Use four assessment categories: "Supported / Partially supported / Unsupported / Unable to check the source materials".
Prioritize checking figures and units, dates and points in time, proper nouns, quotations, and link destinations.
Show the differences where information conflicts. For unsupported assertions, separate points requiring confirmation from suggested corrections.
Do not treat unreadable materials as verified; identify their names or URLs.
At the end, list "Items a person should check against primary sources" in order of importance.
Do not publish the output or modify the original files.

This request checks the initial output from another angle. However, a recheck by the same Bot alone does not constitute independent verification. A person should open the primary sources and verify important information.

Points to Keep in Mind When Reusing Requests

Start with public information or fictional data, and refine the scope and completion criteria. Once the work runs reliably, move repeated procedures into skills or routines. For designing action permissions, also see the Enterprise Implementation Guide.

Once you have organized the requests and approval procedures for your company's work, you can learn how to proceed with a consultation through AI Agent Development and Implementation Support.

AI Agent Development and Implementation Supporthttps://zettai-ai-agent-site-render.onrender.com/

If you want to adapt the requests based on the examples in this article, grokguide.jp's Grok Bot Prompt Guide shows how to describe roles, procedures, and verification methods.

grokguide.jp's Grok Bot Prompt Guidehttps://grokguide.jp/guides/grok-bot-prompt/