Build a live dashboard page with Grok Bot

1. Workflow

1. Plan the page before you open Grok Bot: what it should help you decide, who reads it, where every number comes from, which 3-5 numbers matter, and whether anything on it is private.

   Tool

   Grok (any chat; Claude or ChatGPT also fine)

   Why

   xAI's help page says to ask for a page by saying what it's for and what should be on it, and that a page can hold text, tables, charts and controls such as filters and switches (Grok Bot help: Pages, checked Oct 22, 2026). A short brief makes that request specific.

   Cost

   $0 on Grok Free (limited chat requests).

   Copy prompt Paste into ChatGPT, Claude or Grok.

   Preview prompt: Page brief and build request

   ROLE You are a reporting coach who helps people turn numbers they check by hand into one clear, honest dashboard. GOAL Help me plan one Grok Bot page (a dashboard, tracker, weekly report or memo) and write the request I will send my Bot to build it. WHAT THE NEXT STEP NEEDS A page brief (purpose, reader, sources, sections, controls and privacy level) plus one build request I can paste into Grok Bot in Step 3. HOW TO WORK WITH ME Do not write the deliverable yet. Interview me first. - Ask your questions ONE AT A TIME and wait for my answer before asking the next. (If I ask for speed, you may ask a short numbered batch of at most 5 questions instead.) - With every question, offer 2-3 sensible example answers or a default, so I can reply "default" or pick one. - If an answer is vague, ask one follow-up. If I don't know, choose a sensible default and tell me what you chose. - Do not generate the deliverable until I have answered every question. When you have enough, give me a 3-5 line summary of what you understood and ask me to confirm. - Do not invent facts about me, my business or my work. If something is missing, ask. QUESTIONS TO COVER (in a sensible order, skip any I already answered above) 1. What should the page help you decide or keep track of, in one sentence? Examples: how my X account grew this week, which of three quotes to pick, where my side business stands this month. (Default: a weekly snapshot of the 3-5 numbers I check most.) 2. Who will read it? Examples: only me, my team, anyone with a link. (Default: only me for now.) 3. Where do the numbers or facts come from, and which accounts would the Bot have to sign in to? Only list what the page really needs. Examples: a Google Sheet, a CSV I paste, public websites, a connected app. (Default: data I paste or upload, no sign-ins.) 4. Which 3-5 numbers or items matter most, and how should each be shown? Examples: a headline number with last week's value beside it, a table, a line chart. (Default: headline numbers at the top, one chart, one table.) 5. Which filters or switches would help? Examples: last 7 / 30 days, by product, by platform. (Default: one date-range filter.) 6. How fresh does it need to be? Examples: I'll ask for updates myself, every Monday morning, every weekday at 8:00 AM. (Default: I'll ask for updates myself at first.) 7. Is anything on it private (revenue, customer names, personal data)? (Default: yes, so keep it unshared.) THE DELIVERABLE (only after I confirm) 1. PAGE BRIEF: title, one-line purpose, reader, data sources and the apps to connect, sections in order (headline numbers, charts, tables, short written takeaway), filters and switches, freshness, and privacy level (private, team, or safe for a public link). 2. BUILD REQUEST: one message for my Grok Bot that starts "Make a page that..." and lists the sections, says where each number comes from, asks for a "Last updated" line with the date and time and a source next to every number, and ends with: "If a number is missing or out of date, say so on the page instead of guessing." 3. CHECKS: 3 things I should verify the first time the page opens. Put everything I should copy inside one clearly delimited block that starts with a line "=== COPY START ===" and ends with a line "=== COPY END ===", with no commentary inside the block. Put any notes outside it. AFTER THE DELIVERABLE Ask me: "Anything to tweak?" If I ask for changes, revise and give me the full updated block again between the same markers. Repeat until I say it is good. FINISH When I'm happy, end with one line telling me what to do next: update Grok Bot and connect only the sources on the brief in Step 2, then paste the build request in Step 3.

2. Update Grok Bot to version 0.60.0 or later on your computer (1.14.0 or later on your phone), then connect only the apps the brief lists under Connect apps, or have the data ready to paste or upload. If you don't see pages yet, it may not have reached your account.

   Tool

   Grok Bot app

   Why

   The help page says Pages is rolling out gradually, isn't on Enterprise teams yet, and needs those versions. Grok Bot is listed from the Premium plan; it isn't on Free or Plus (xAI pricing, checked Oct 22, 2026).

   Cost

   Grok Bot is listed from Premium ($30/month); it is not listed on Free or Plus.

3. Ask the Bot for the page by pasting your build request. It posts a card with the page title and Open; on desktop the page fills the window and the chat stays open beside it.

   Tool

   Grok Bot

   Why

   This is the flow on xAI's help page, which gives the example "Make a page that compares the three quotes in this thread, with a table and a short recommendation." The official Grok Bot announcement (Oct 21, 2026) describes pages as reports, memos and dashboards.

   Cost

   Uses your plan's shared usage pool; xAI doesn't publish a cost per page.

   Copy prompt Paste into your Grok Bot's chat, followed by your build request from Step 1.

   Preview prompt: Build the page

   ROLE You are my Grok Bot. You are building a page (a report, dashboard, tracker or memo) that I will read, refine with you and maybe share. GOAL Build one page from my build request, using only real data from the sources I name. WHAT THE NEXT STEP NEEDS A first version of the page posted in this chat as a page card I can open, plus a short build note: the sources you used, what's missing, and anything you had to assume. HOW TO WORK WITH ME Do not write the deliverable yet. Interview me first. - Ask your questions ONE AT A TIME and wait for my answer before asking the next. (If I ask for speed, you may ask a short numbered batch of at most 5 questions instead.) - With every question, offer 2-3 sensible example answers or a default, so I can reply "default" or pick one. - If an answer is vague, ask one follow-up. If I don't know, choose a sensible default and tell me what you chose. - Do not generate the deliverable until I have answered every question. When you have enough, give me a 3-5 line summary of what you understood and ask me to confirm. - Do not invent facts about me, my business or my work. If something is missing, ask. QUESTIONS TO COVER (in a sensible order, skip any I already answered above) 1. Paste the build request from Step 1. 2. Which of the sources it names are connected or attached right now? For anything missing, tell me what to connect under Connect apps, or ask me to paste or upload the data, and wait for me. (Default: use only the data I paste or upload.) 3. Is there an example page, chart style or layout I like? (Default: headline numbers at the top, then charts, then tables, then a 3-line takeaway.) 4. Should anything be left off because it's private? (Default: no customer names, emails or account numbers on the page.) THE DELIVERABLE (only after I confirm) 1. THE PAGE: build it as a page (not a chat reply) with the sections in my build request, a "Last updated" line with date, time and time zone, and a source next to every number. Mark any missing or stale number as missing instead of estimating it. 2. BUILD NOTE: the sources you used, the time range covered, what you couldn't get and why, and anything you assumed. 3. If a site asks for a password, a code or a payment confirmation, stop and ask me to choose Take over instead of asking me to type it in chat. Do not send, post or share anything. Put the build note I should copy inside one clearly delimited block that starts with a line "=== COPY START ===" and ends with a line "=== COPY END ===", with no commentary inside the block. Put any notes outside it. AFTER THE DELIVERABLE Ask me: "Anything to tweak?" If I ask for changes, revise and give me the full updated block again between the same markers. Repeat until I say it is good. FINISH When I'm happy, end with one line telling me what to do next: open the page card, then go to Step 4 and type changes in the chat panel beside the page.

4. Refine it in the panel beside the open page (labeled Message about and the page's title). The Bot edits the same page; click the title to rename it. Filters and switches only change your view and aren't saved.

   Tool

   Grok Bot

   Why

   The help page says only the Bot changes a page, everyone who can open it sees the edit, and nothing you do with the page's controls is saved. When the Bot updates a page, the earlier card in the chat shows Updated.

   Cost

   Uses your plan's shared usage pool.

   Copy prompt Type in the Message about panel beside the open page.

   Preview prompt: Tighten the page

   ROLE You are my Grok Bot, reviewing the page we just built with a critical editor's eye. GOAL Make the page easier to read in under a minute, and fix anything that's wrong, unsourced or out of date. WHAT THE NEXT STEP NEEDS An updated version of the same page (not a new one), plus a change list I can check. HOW TO WORK WITH ME Do not write the deliverable yet. Interview me first. - Ask your questions ONE AT A TIME and wait for my answer before asking the next. (If I ask for speed, you may ask a short numbered batch of at most 5 questions instead.) - With every question, offer 2-3 sensible example answers or a default, so I can reply "default" or pick one. - If an answer is vague, ask one follow-up. If I don't know, choose a sensible default and tell me what you chose. - Do not generate the deliverable until I have answered every question. When you have enough, give me a 3-5 line summary of what you understood and ask me to confirm. - Do not invent facts about me, my business or my work. If something is missing, ask. QUESTIONS TO COVER (in a sensible order, skip any I already answered above) 1. What did you look for first when you opened the page, and did you find it quickly? (Default: the headline numbers should be the first thing I see.) 2. Is any number wrong, missing or unclear? Name it. (Default: none that I noticed; check every source anyway.) 3. What should be cut, merged or moved? Examples: drop a chart nobody uses, merge two tables, move the takeaway to the top. (Default: cut anything that doesn't help the one decision on the brief.) 4. Should the filters or switches change? Remember they only change the view, not the page. (Default: keep one date-range filter.) 5. What should the title be? (Default: keep it; I can rename it by clicking the title.) THE DELIVERABLE (only after I confirm) 1. Edit the same page in place with my changes. Re-check every number against its source and update the "Last updated" line. 2. CHANGE LIST: what you changed, what you re-checked, and anything still missing. 3. One sentence on whether the page holds anything private, so I know if a public link would be safe. Put the change list I should copy inside one clearly delimited block that starts with a line "=== COPY START ===" and ends with a line "=== COPY END ===", with no commentary inside the block. Put any notes outside it. AFTER THE DELIVERABLE Ask me: "Anything to tweak?" If I ask for changes, revise and give me the full updated block again between the same markers. Repeat until I say it is good. FINISH When I'm happy, end with one line telling me what to do next: go to Step 5 if the page should stay current, or Step 6 to pin and share it.

5. Keep it current: ask the Bot to update the page when you need it, or have it set up a routine that updates the same page on a schedule, then run a Test run.

   Tool

   Grok Bot

   Why

   xAI's announcement says you can have the Bot keep a page up to date, but the help page doesn't say how. A routine is our suggestion: xAI's docs say a routine tells one Bot when to run a workflow on a schedule, runs while your laptop is closed, must be at least five minutes apart, and a Bot can own up to 50 (xAI docs: Skills and routines).

   Cost

   Each update uses the shared usage pool; xAI doesn't publish a cost per run.

   Copy prompt Paste into the same Grok Bot chat that built the page.

   Preview prompt: Keep the page up to date

   ROLE You are my Grok Bot. You keep one page current so I don't have to rebuild it by hand. GOAL Agree how and when this page gets updated, then set that up, keeping every update inside the same page. WHAT THE NEXT STEP NEEDS Either a simple 'update on request' rule, or a routine with a schedule, time zone, sources and a no-data rule that updates the same page, plus a test update. HOW TO WORK WITH ME Do not write the deliverable yet. Interview me first. - Ask your questions ONE AT A TIME and wait for my answer before asking the next. (If I ask for speed, you may ask a short numbered batch of at most 5 questions instead.) - With every question, offer 2-3 sensible example answers or a default, so I can reply "default" or pick one. - If an answer is vague, ask one follow-up. If I don't know, choose a sensible default and tell me what you chose. - Do not generate the deliverable until I have answered every question. When you have enough, give me a 3-5 line summary of what you understood and ask me to confirm. - Do not invent facts about me, my business or my work. If something is missing, ask. QUESTIONS TO COVER (in a sensible order, skip any I already answered above) 1. Which page should stay current? (Default: the page we just built.) 2. On request or on a schedule? Examples: I'll ask "update the page", every Monday at 8:00 AM, every weekday at 7:00 AM. Schedules must be at least five minutes apart. (Default: every Monday at 8:00 AM in my time zone.) 3. Which sources should each update use, and are they all still connected? (Default: the same sources as the build note.) 4. What should an update do if a source is down, empty or unchanged? (Default: keep the old number, mark it as not updated and say why on the page; never guess.) 5. Should each update also post a short summary in this chat? (Default: yes, 3 lines: what changed, what's missing, when the next update runs.) THE DELIVERABLE (only after I confirm) 1. UPDATE PLAN: on request or the routine spec (schedule and time zone, sources, which page it updates, the no-data rule, and where the summary goes). Updates must edit the same page so shared links keep working, and must never send, post or share anything. 2. If it's a schedule, after I confirm, create the routine and show me its next run, then offer a Test run with safe inputs and report: did it update the same page, did the "Last updated" line change, does every number still have a source, and are missing numbers marked plainly. Put the update plan I should copy inside one clearly delimited block that starts with a line "=== COPY START ===" and ends with a line "=== COPY END ===", with no commentary inside the block. Put any notes outside it. AFTER THE DELIVERABLE Ask me: "Anything to tweak?" If I ask for changes, revise and give me the full updated block again between the same markers. Repeat until I say it is good. FINISH When I'm happy, end with one line telling me what to do next: do Step 6: pin the page in the Library and choose who can view it.

6. Pin and share: in the Bot's details open the Library tab, then use the three-dot menu to Pin the page. To share, open the page, click Share and choose Who can view: people you invite, your team, or anyone with the link (only if nothing on it is private). Manage shared pages later under Shared Canvases → Grok Bot Pages on your Cursor dashboard.

   Tool

   Grok Bot app and Cursor dashboard

   Why

   Per the help page, a new page is private until you share it, invitees get Viewer access, a public link gets a pages.grok.bot address made from the title that stays the same after a rename, anyone with it can open the page without signing in, and deleting a shared page cuts off the link. Public sharing is off on Enterprise teams.

   Cost

   $0 (sharing settings).

2. Recommended tool chain

1. Grok (any chat; Claude or ChatGPT also fine)
2. Grok Bot app
3. Grok Bot
4. Grok Bot
5. Grok Bot
6. Grok Bot app and Cursor dashboard

3. Total cost

Unpriced items are left out of the total (marked “cost not sourced”), so the real total is higher. All totals are our arithmetic from sourced unit prices.

4. Current promos

• The X Subscription: Grok, Grok Bot, Cursor and X Premium in one plan

  xAI's plan bundles Grok, Grok Bot, Cursor and X Premium. Grok Bot is included on Premium ($30/month), Super ($100/month) and Ultra ($200/month), not on Plus. Existing Cursor, SuperGrok and X Premium plans continue, and switching is optional, with a prorated refund for unused time on eligible plans.

  Applies to: Grok Premium on the cheapest route, Grok Super on the best route

  A standing plan bundle, not a time-limited sale.

  Source: xAI docs: X Subscription pricing, checked Oct 22, 2026

5. Learn it

Last verified Oct 22, 2026. Items older than 30 days are marked.

6. Caveats and assumptions

• Pages is rolling out gradually and isn't on Enterprise teams yet. If you don't see it after updating to 0.60.0 (desktop) or 1.14.0 (phone), it may not have reached your account.
• xAI says the Bot can keep a page up to date, but its help page doesn't explain how. Using a routine for scheduled updates is our suggestion; check the first few runs and the Updated label on the page card.
• A page is only as accurate as its sources. Ask for a source and a "Last updated" line next to every number, and don't use it for money decisions without checking the source.
• Anyone with a public link can open the page without signing in. Use Anyone with the link only when nothing on the page is private, and delete or narrow access from Shared Canvases on your Cursor dashboard if that changes.
• Filters and switches only change your view and aren't saved; to change the page itself, ask the Bot.
• A Test run of a routine does real work. Use safe inputs and keep sends, posts and purchases behind approval.
• xAI doesn't publish how much usage a page or an update takes. Check Weekly usage after the first week.
• Plan features and prices are from xAI's pricing page on the verified date and can change; costs are our arithmetic, one month unless stated.

Last verified Oct 22, 2026.