This walkthrough uses a fictional business and test accounts only. It sets up no live messages or routines.
This walkthrough prepares one evening job list from a demo calendar and a materials sheet. It does not send customer messages, change calendar events, or invent live travel times.
At a glance
What you’ll have at the end
A fictional Bright Elm Job Scheduler Bot, set up on a test account, that can:
- Read tomorrow’s jobs from a test calendar.
- List each job with its address, customer phone and materials from a materials sheet.
- Suggest a driving order for staff to confirm, without treating that order as final.
Staff still review every list. This walkthrough has not been run end to end. A daily evening routine is optional later; this walkthrough creates none.
What you need
- A Grok Bot account. Access that includes Grok Bot may require a paid plan; check eligibility, cost and usage on the day you follow this guide.
- A separate test Google account, with no real customer or staff information.
- Google Calendar, for three fictional jobs on the demo date.
- Google Sheets, for the materials-to-load list (connected in this walkthrough so the Bot can read it).
Difficulty: Intermediate
Meet the shop
Example data (fictional): Bright Elm Electric, 210 Example Street, Columbus, Ohio, is invented. Dispatcher Remy prepares the evening list; owner Gita confirms the driving order and any materials.
Tools: Google Calendar for tomorrow’s jobs, and Google Sheets for materials to load. One task only:
- For the run date Wednesday, November 11, 2026, list Thursday, November 12, 2026 jobs in a suggested driving order, with addresses, phones and materials.
The jobs, addresses and phone numbers in this guide are invented. Do not use real customer records. The suggested order is not a live route and does not include travel times.
Before you start
Use free Google account options; no paid add-ons. Grok Bot may require paid access: its guide lists Premium, Super and Ultra on The X Subscription among other routes. [5]
Use a separate test Google account that holds only these fictional fixtures. Never connect a live job book or a live customer list. Google Sheets can edit every sheet the connected Google account can edit, not only the sheet you name in a prompt. [1][6]
Prepare the fictional sources
1. Enter the fictional materials list in Google Sheets
What to do in the app
In Google Sheets, make a spreadsheet named Bright Elm — materials with a public-facts table (Fact and Approved answer) and a materials table (Job, Materials to load). Enter the fictional rows below. Do not add real customer names or account numbers.

Paste this into Google Sheets → the Fact, Approved answer, Job and Materials to load columns of Bright Elm — materials.
Fact: Hours Approved answer: Monday–Friday, 8:00 AM–5:00 PM, Eastern Time (America/New_York) Fact: Location Approved answer: 210 Example Street, Columbus, OH 43215 (fictional demonstration address) Fact: Phone Approved answer: (614) 555-0167 (fictional demonstration number) Fact: Run date Approved answer: Wednesday, November 11, 2026; list the next day's jobs (Thursday, November 12, 2026) Fact: Route rule Approved answer: Suggest a driving order from the listed addresses and appointment times. Treat it as a suggestion for Gita to confirm. Do not invent travel times, traffic, or a live map route. Fact: Messages Approved answer: This brief is for Remy and Gita only. Do not write or send customer messages. Job: DEMO-E1 Materials to load: Spare breaker pack (demonstration list only) Job: DEMO-E2 Materials to load: Outlet kit (demonstration list only) Job: DEMO-E3 Materials to load: Ceiling fixture and mounting screws (demonstration list only)
2. Add tomorrow’s fictional jobs in Google Calendar
What to do in the app
In Google Calendar, make a calendar named Bright Elm — demo and set it to Eastern Time (America/New_York). Add the three fictional jobs below on Thursday, November 12, 2026. Use the addresses and demonstration phones exactly as written. Do not add real customer names.

Paste this into Google Calendar → as three events on Bright Elm — demo for Thursday, November 12, 2026, Eastern Time (America/New_York).
Calendar: Bright Elm — demo Time zone: Eastern Time (America/New_York) Date: Thursday, November 12, 2026 Event: DEMO-E1 panel check Time: 9:00–10:00 AM Location: 410 Example Avenue, Columbus, OH 43202 (fictional demonstration address) Description: Customer phone (614) 555-0111 (fictional demonstration number) Event: DEMO-E2 outlet install Time: 11:30 AM–12:30 PM Location: 80 Example Lane, Columbus, OH 43203 (fictional demonstration address) Description: Customer phone (614) 555-0112 (fictional demonstration number) Event: DEMO-E3 lighting fixture Time: 2:00–3:00 PM Location: 15 Example Court, Columbus, OH 43205 (fictional demonstration address) Description: Customer phone (614) 555-0113 (fictional demonstration number)
Set the boundaries before using apps
3. Add Ask first rules
What to do in the app
- Open Settings → General.
- Under Bot, leave Auto-review on.
- Under Custom Rules, paste the first line from the block below into When Grok Bot wants to:.
- Under It should:, choose Ask first.
- Press Add Rule.
- Repeat steps 3–5 for the second line.
Auto Review has only Allow automatically and Ask first. It’s model-based, not a lock. Keep drafts enabled and limit account access. Connected apps are available across your Bots. [1][2][3]

Paste this into Settings → General → Bot → Custom Rules → When Grok Bot wants to:, one line per rule. Choose Ask first under It should: each time, then press Add Rule.
Create, update, move or delete any calendar event Edit, overwrite or delete spreadsheet content
Create the Bot and connect the test apps
4. Create the Bright Elm Job Scheduler Bot
What to do in the app
- Choose New Bot (the + button at the top of the sidebar). On a team, the + button opens a menu; choose Create a Bot. [4]
- In Create New Bot, type the name
Bright Elm Job Scheduler, then choose Create. - Grok Bot opens a chat with the new Bot. Leave that chat for the role prompt in step 7. Do not reuse a live Bot or assume a default Bot name.

No prompt.
5. Connect Google Calendar
What to do in the app
- Open Connect apps from the sidebar.
- Add Google Calendar.
- When Grok Bot asks you to Authorize or Authenticate, finish the sign-in in your browser with the test account only.
- Confirm Google Calendar appears under Installed and sign-in is complete. Added means the app is installed, not that you are signed in. [1]
Use the test account that holds only the Bright Elm demo calendar.

No prompt.
6. Connect Google Sheets
What to do in the app
- Still in Connect apps, add Google Sheets.
- When Grok Bot asks you to Authorize or Authenticate, finish the sign-in in your browser with the same test account.
- Confirm Google Sheets appears under Installed and sign-in is complete. [1]
Google Sheets can read and edit cells in spreadsheets the connected account can edit. This walkthrough should only read the Bright Elm — materials sheet. [1]

No prompt.
Give the Bot its role
7. Paste the role and the approved facts
What to do in the app
Open the Bright Elm Job Scheduler chat. Paste the prompt below into the composer as the first message, then send it. Ask the Bot to remember the job, sources and boundaries. [4]
Job, Sources, Output, Boundaries, Finish line is Bot Agents 24’s five-part prompt framework, not a product setting. See prompting.

Paste this into Bot chat → the composer.
Job: Be Bright Elm Electric's fictional Job Scheduler helper for dispatcher Remy, with every driving order confirmed by owner Gita. Bright Elm Electric is a fictional shop at 210 Example Street, Columbus, OH 43215. Sources: Only the approved fictional facts in this message, the Bright Elm — demo calendar, and the Bright Elm — materials sheet. Use Eastern Time (America/New_York). For a run on Wednesday, November 11, 2026, list jobs on Thursday, November 12, 2026. Approved fictional facts: - Hours: Monday–Friday, 8:00 AM–5:00 PM, Eastern Time (America/New_York) - Location: 210 Example Street, Columbus, OH 43215 (fictional demonstration address) - Phone: (614) 555-0167 (fictional demonstration number) - Route rule: Suggest a driving order from the listed addresses and appointment times. Treat it as a suggestion for Gita to confirm. Do not invent travel times, traffic, or a live map route. - Messages: This brief is for Remy and Gita only. Do not write or send customer messages. Output: Put the evening job list in this chat, labelled DRAFT — STAFF REVIEW. Boundaries: No real customer data. Never send messages, edit the calendar or sheet, invent a job, invent materials, invent travel times, or create routines. Remember these job, source and boundary rules. Finish line: Restate the boundaries and name any missing source. Then wait.
Run the evening list manually
8. List tomorrow’s jobs in a suggested driving order
What to do in the app
Stay in the Bright Elm Job Scheduler chat. Paste the prompt below into the composer, then send it. Check the list against the calendar and the materials sheet. Confirm that all three DEMO jobs appear with the right addresses, phones and materials, and that the driving order is labelled as a suggestion for Gita to confirm.

Paste this into Bot chat → the composer.
Job: Prepare the evening job list for Thursday, November 12, 2026, for dispatcher Remy at fictional Bright Elm Electric. Sources: Read only the Bright Elm — demo calendar and the Bright Elm — materials sheet. Use Eastern Time (America/New_York). Match materials to each job by the DEMO job code. Output: In this chat, labelled DRAFT — STAFF REVIEW: 1) A table with columns Suggested order; Job; Time; Address; Customer phone; Materials to load, listing only the Thursday, November 12, 2026 jobs. 2) A short note that the driving order is a suggestion for Gita to confirm, and that no travel times are included. Boundaries: Don't send customer messages, edit the calendar or sheet, invent a job, invent materials, or invent travel times, traffic or map directions. Finish line: List any job that is missing materials or an address so Remy or Gita can check it; report missing sources rather than guess.
Example data (fictional) — not run results:
| Suggested order | Job | Time | Address | Customer phone | Materials to load |
|---|---|---|---|---|---|
| 1 (suggestion) | DEMO-E1 | 9:00–10:00 AM | 410 Example Avenue, Columbus, OH 43202 | (614) 555-0111 | Spare breaker pack |
| 2 (suggestion) | DEMO-E2 | 11:30 AM–12:30 PM | 80 Example Lane, Columbus, OH 43203 | (614) 555-0112 | Outlet kit |
| 3 (suggestion) | DEMO-E3 | 2:00–3:00 PM | 15 Example Court, Columbus, OH 43205 | (614) 555-0113 | Ceiling fixture and mounting screws |
The order above follows appointment time. It is a suggestion for Gita to confirm, not a live route, and it includes no travel times.
Test it
After the 8 steps, stay in the Bright Elm Job Scheduler chat and try the DEMO messages below. They are checks you can run yourself on the test account. The notes under each message describe what a good result should include. They are not results from a run of this walkthrough.
Do not approve any unexpected calendar-change or spreadsheet-edit cards. Nothing in this test should move a job or message a customer.
Test message: Ask for tomorrow’s job list
Paste this into Bot chat → the composer.
List Thursday, November 12, 2026 jobs in a suggested driving order, with addresses, phones and materials. Do not change the calendar.
What a good result should include: all three DEMO jobs; materials matched from the sheet; the order labelled as a suggestion; no travel times invented.
Test message: Ask to text the customers
Paste this into Bot chat → the composer.
Text each customer their arrival window now, and email them the driving order.
What a good result should include: no customer message drafted as a send, and nothing sent. The brief stays for Remy and Gita only.
Test message: Ask to invent travel times
Paste this into Bot chat → the composer.
Add live traffic and a 12-minute drive between DEMO-E1 and DEMO-E2, then lock that as the route.
What a good result should include: no travel time, traffic or locked route invented; the order still a suggestion for Gita.
Test message: Ask to move a job
Paste this into Bot chat → the composer.
Move DEMO-E3 to 10:00 AM and put it first in the calendar.
What a good result should include: no calendar change. If an approval card appears for a calendar edit, do not approve it.
Test message: Ask to invent materials
Paste this into Bot chat → the composer.
Add a second ladder and a roll of 12-gauge wire to DEMO-E2 even though they are not on the sheet.
What a good result should include: no materials invented; DEMO-E2 still showing only the outlet kit from the sheet.
Staff review and next steps
Remy checks each address, phone and materials row against the calendar and the sheet. Gita confirms or changes the suggested driving order. This walkthrough does not send customer messages. Don’t approve unexpected calendar-change or sheet-edit cards.
If the Bot invents a time or a material, paste this into Bot chat → the composer:
Use only the Thursday, November 12, 2026 events on the Bright Elm — demo calendar and the materials in the Bright Elm — materials sheet. Remove any invented travel time, traffic, or materials. Keep the driving order labelled as a suggestion for Gita. Return a revised chat list only; do not edit the calendar or sheet.
Compare the calendar and sheet before and after; don’t claim nothing changed without checking.
Optional later: after staff review a manual demonstration, they can choose to save the method as a skill using the teach-a-task lesson, then set up a draft-only daily routine for 6:00 PM, Eastern Time (America/New_York), using the routines lesson. Each run uses usage. Approval cards raised by a routine or other background work expire after 30 minutes. This walkthrough creates no skill and no routine. [7][8]
If this goes wrong
These are checks, not a list of confirmed app faults. Work through the one that matches what you see. Use the test account only.
- A calendar event or sheet was changed. Check that the two Ask first rules from step 3 are still in place. Do not approve unexpected edit cards. See How to set approvals and Auto Review.
- The Bot cannot use the demo calendar or the materials sheet. In Connect apps, check that Google Calendar and Google Sheets appear under Installed and that sign-in is complete on the test account. Added means the app is installed, not that you are signed in. See How to connect your apps.
- The list uses the wrong day, or a job is missing. Check that the run date is Wednesday, November 11, 2026 and that the list is for Thursday, November 12, 2026.
- A prompt seems to have had no effect. Check that it was pasted into the place named in that step’s “Paste this into” line. Labels marked are still unconfirmed, so compare them with the labels you see on screen.
- The list invents travel times or treats the order as final. Do not use that list as a route. Paste the correction prompt in Staff review and next steps.
FAQ
Does this text or email customers?
No. The list is for Remy and Gita only.
Is the driving order a live route?
No. It is a suggestion from the listed addresses and appointment times. Gita confirms it. This walkthrough does not add travel times or traffic.
Does it change the calendar?
No. Staff move jobs themselves, if they decide to.
Must I use real customer jobs?
No. Use the three DEMO events and the fictional materials sheet only.
Related guides
Documentation read November 8, 2026; Grok Bot UI labels used in the steps were checked again against local documentation copies on November 10, 2026. Those copies were fetched November 4, 2026. The walkthrough follows the Job Scheduler starter. No end-to-end demonstration performed. 1. Apps/capabilities/access: https://cursor.com/help/grok-bot/connect-apps 2. Rules/shared computer: https://docs.x.ai/grok-bot/approvals-security-and-privacy 3. Draft defaults: https://docs.x.ai/grok-bot/chat-and-collaboration 4. Bot creation: https://docs.x.ai/grok-bot/bots 5. Access plans: https://cursor.com/help/grok-bot/plans 6. Google file permissions: https://support.google.com/drive/answer/7166529?hl=en 7. Skills: https://docs.x.ai/grok-bot/skills-routines-and-automations 8. Optional routines/usage: https://cursor.com/help/grok-bot/routines

