Ops

You can hand a team of Grok Bots the office work that pulls a small machine shop's people off the floor: reading RFQs, chasing missing prints and models, asking vendors for material and finish prices, checking what needs ordering, and filling the weekly scorecard. This playbook follows one 49-year-old shop (his X profile lists Chicago, IL) that runs five Bots for that today, explains how the jobs split, and gives you his office manager Bot as a copyable starter, with every customer send, PO and order still waiting on a person. It fits any job shop or small manufacturer that quotes from email.

Not tested: The Daily Bot has no shop inbox, quoting software, MES dashboard or QuickBooks file linked to a Grok Bot, so we haven't run any of this. Everything below comes from the owner's Oct 15 article, his posts and Cursor's docs.

Who runs it#

The setup belongs to @MFG_SMB, Russell Winter. His X bio reads "3rd Gen Tool & Die Maker | Founder, http://USMFG.com | Sm. Machine Shop Owner https://centertoolco.com", and his profile location is Chicago, IL. Center Tool Co is a "full-service machine shop" that does prototyping, CNC milling and turning, wire EDM and component repair. In the article he writes: "I am the 3rd gen to own and run the small manufacturing company that my Opa started in 1977." He also founded US MFG, whose tagline is "Supporting small manufacturers. Promoting employee ownership." It operates three verticals, including MFGio, which sells manufacturing software and network tools. A 2025 Manufacturing Happy Hour episode covers his work buying shops from retiring owners. Conflict of interest: Center Tool Co sells machining services, and US MFG's MFGio vertical sells manufacturing tools. The Oct 15 article does not pitch either, and he is not selling a Bot product or paid template; he published the Bot profiles "word for word" so other shops can copy them. We do not claim InstaQuote is an MFGio product.

On Oct 15 at about 11:50 AM ET he posted the article "I Hired 5 Grok Bots to Run the Office of my 49yr old Machine Shop", with each Bot's profile description "word for word" so other shops can copy them.

What ops uses it for#

His starting problem: "Reading RFQs. Chasing down the print. Then chasing down the model. Asking vendors for material and finish prices. Checking what needs ordering. Compiling the weekly numbers for the Level 10 meeting." Most of it, he says, "was the same facts, typed into one place or automatically gathered, then typed again somewhere else." The team is "One manager, four specialists," working "inside the tools we already run on": an InstaQuote quoting system, the shop's MES dashboard, QuickBooks and Outlook.

• Paul, the office manager. "Paul is who I chat with. He routes the work to the right bot and waits for my yes." Paul keeps a state file, brings the owner "only exceptions and approvals" in replies of "5 lines or fewer", and logs "Every approval, override and reason code".
• Quoting Bot. It "Monitors a company email, reviews RFQs received, checks that every part has its print and model (if not, follows up with customer)", then sends the RFQ and attachments to the quoting software for an instant quote and "asks for review on instant quote and permission to send to customer." Its profile requires "both a PDF and a STEP file" per in-scope part, reads inline images for target pricing, and treats crossed-out part numbers as "don't quote it". After each closed quote it writes "the fast-vs-actual difference and any human corrections to a learning file."
• Sourcing Bot. While the instant quote runs, it "requests actual material and finish prices from our approved vendors" and adds them to what he calls the "slow" quote, which exists "to compare actual prices with the instant quote and actively train the system to be more accurate." Its profile asks "at least 3 approved material vendors and 2 finish vendors through Outlook", with subject "RFQ" or "Urgent RFQ", items grouped by alloy, and flags quotes far from the median. When a customer PO lands, it creates raw material POs in QuickBooks and asks permission to release them.
• Supply Ordering Bot. It "Watches Items to Order section on our MES dashboard (can be anything from the shop needing gloves or safety glasses to soap for the bathroom)", compares the posted link ("like an amazon or McMaster link") with "what it finds as a better source," and "has a spending limit. A person approves and places the order."
• Reporting Bot. "Every Monday by 10:00 AM CT" it updates the L10 scorecard "with the prior week's KPIs" from MES, QuickBooks and quoting data and flags "missed targets with their sources."

Why it matters at work#

He wrote that "the office work was eating up our day" in a shop where "The majority of value we add happens on the shop floor." Before, a person read each RFQ, chased the print and the model, emailed vendors, typed their prices into a quote, and later gathered the same numbers again for the Monday meeting. In this setup the Bots carry those facts from inbox to quote to PO to scorecard, and people only decide. His summary: "The facts get typed once." He frames it as a staffing answer too: "hiring is hard so being more efficient with the people you have is paramount." His rule is the part to copy: "Nothing goes to a customer, a vendor, or a card without a person saying yes." He has not published hours saved for the five Bots.

Set it up#

Cursor's docs say to create "a separate Bot when the work has a distinct goal, set of tools, working style, approval boundary, or recurring schedule", and to "Start with a one-time task, make it reliable, save the method as a skill, and only then automate it" (docs). His five-Bot split follows the first rule. Our suggested order follows the second.

1. Start with Paul alone. Create one Bot and paste the prompt below as its first message. The docs say to give a new Bot "its job, sources, and approval boundaries, and ask it to remember them."
2. Connect the RFQ inbox. Point Paul at the company email where RFQs arrive. Run one real RFQ by hand and check that it caught every missing PDF or STEP file and every crossed-out part.
3. Add Quoting as its own Bot once the intake check is reliable. Give it the quoting software's API and intake address, and copy his rule that it takes work only from Paul.
4. Add Sourcing next. List your approved material and finish vendors and your RFQ email format (his: subject "RFQ" or "Urgent RFQ", grouped by alloy, fastest lead time). Keep every vendor email as a draft until you trust it, and keep QuickBooks POs prepared, never released.
5. Add Supply Ordering with read-only access to wherever your shop lists items to order, a spending limit in the description, and no card.
6. Add the Monday scorecard routine last. Set it for Monday by 10:00 AM in the shop's zone. Routines use the Bot's Timezone setting, and you can "Pick a zone when the routine should follow a different one, such as the office where the work belongs" (routines help). "A new routine waits for its next scheduled time", so use Test, and remember "A test does real work."

You are Paul, the office manager and chief of staff for [company name], a small machine shop in [location]. I talk only to you. You coordinate the office Bots (Quoting, Sourcing, Supply Ordering and Reporting) and you don't do their specialist work. Keep a lightweight state file, route handoffs between the Bots, and bring me only exceptions and approvals. Keep replies to 5 lines or fewer, with details in workspace files. Each approval request is one short message: the ID, the key numbers, the recommended action and evidence links. Log every approval, override and reason code. For RFQs, read the full email thread and its inline images for customer context, target pricing, files already requested and crossed-out part numbers (crossed out means don't quote it). Forward an RFQ to [quoting software email] only when every in-scope part has both a PDF and a STEP file. If a file is missing, draft the follow-up to the customer for my review. Always stop for my yes before: sending any customer quote, sending any vendor RFQ or other outgoing email, releasing any PO or supply order, any quote variance over [percentage], process exceptions and autonomy changes. Use only the APIs I give you, make one request at a time, stop after 3 failures and report the URL and error. Never send a quote or PO, place an order or use a card. All outgoing email comes to me as a draft first.

This starter is ours: a condensed adaptation of his Paul profile (not verbatim). Brackets are placeholders, as in his article. We added the customer follow-up and vendor RFQ emails to the approval list, because his own rule says "A person sends every quote/email" and Paul's profile says "All outgoing email goes to the owner as a draft first." That matches Cursor's advice to "keep sending, purchasing, deleting, publishing, and production changes behind approval" (docs).

Gotchas#

• His profiles disagree on vendor email. The Sourcing profile says it requests quotes "through Outlook", while Paul's says all outgoing email goes to the owner as a draft first. Pick the stricter rule until you have watched a few rounds.
• The file gate is the point. Quoting only starts when every in-scope part has "both a PDF and a STEP file." Skip that check and you get fast quotes on parts nobody can model.
• Who forwards to the quoting tool. His summary says the Quoting Bot sends the RFQ to the quoting software. Its profile says "Paul forwards a complete RFQ to quoting software email." Give that step to exactly one Bot so RFQs aren't sent twice.
• API only, with a stop rule. Every profile says "Make one request at a time, stop after 3 failures and report the URL and error" and never to "browse the dashboard, the quoting site, GitHub or Cursor." Copy that limit. It keeps a Bot from clicking around a live system when an API call fails.
• Read-only shop data. Supply Ordering reads the MES "through its read-only API", and Reporting uses "the dashboard token only for its read endpoints." Don't give either Bot write access to MES or QuickBooks to save a step.
• Shared logins. "Every Bot on your account uses the same computer: browser sessions, files, and command-line credentials are shared" (docs). An Outlook or QuickBooks session one Bot opens is open to all five.
• Five Bots spend more. "Each run spends usage" (routines help). His Supply Ordering profile says "Run scheduled checks only." Five Bots on tight schedules add up, so start with wide ones.
• Related quoting-tool claim. On Oct 2 he posted that InstaQuote took "2 days and $250 in credit" to build and "will save us 20hrs/week" (post). That forecast is about the quoting tool, not a measured result for the five Bots, and we don't score it here.

What to watch#

• Real numbers. He hasn't posted hours saved, quote turnaround or win rates for the five Bots. We'll update this playbook if he does.
• Quote accuracy. The slow quote and the learning file exist to make instant quotes "more accurate". Watch for him to report how far fast quotes land from actual vendor prices.
• Changes to the team. He says "I'm still refining the system" and that "This team and our stack is constantly evolving." Watch his posts for new Bots, new schedules or looser approval rules.
• Official patterns. Grok Bot's use cases page says to "Start with read-and-prepare work, review the result, then add approved actions or a routine," lists a Chief of Staff role, and ends with "Keep consequential external actions behind approval." His Paul reads like a shop-office version of that Chief of Staff, and his split matches the page's advice.

Related#

• Grok Bot for operations: trackers, office logistics, and vendor spend
• Grok Bot for property ops: bills, utilities and a platform switch
• Grok Bot for sales: meeting to proposal, signature, invoice and chase
• Grok Bot for finance: a bookkeeping Bot that prepares and an accountant who approves
• Make Grok Bot routines stay quiet when nothing changed

Sources#

• @MFG_SMB on X, Oct 15: I Hired 5 Grok Bots to Run the Office of my 49yr old Machine Shop (article)
• @MFG_SMB on X: profile and bio
• Center Tool Co
• US MFG
• @MFG_SMB on X, Oct 2: INSTAQUOTE (quoting tool build, related context)
• Manufacturing Happy Hour ep. 226: Russell Winter, founder of US MFG
• Cursor Docs: Work with Grok Bot
• Cursor Help Center: Routines
• Grok Bot docs: Use cases

You can hand a Grok Bot the back-office chores that eat a property manager's week: sending every emailed vendor bill into AppFolio, turning a phone photo of a mailed water bill into an entered bill, and checking that each unit's utilities got paid. This playbook follows one property management company that runs all three today, and shows how to set up the first one with a copyable prompt. It fits anyone in operations who lives in an inbox full of invoices, not only property managers.

Not tested: The Daily Bot has no AppFolio account, vendor inbox or bank linked to a Grok Bot, so we haven't run any of this. Everything below comes from the linked posts and Cursor's docs.

Who runs it#

The setup belongs to @ChrisTwiggsPM, Chris Twiggs, listed as Company President of Blair Allen Property Management on the Blair Allen team page. His X bio says the company manages property in South Dakota, Montana and Arizona. On Oct 8 he posted his roster of 20 numbered Bots (two still being built) and how he picks their jobs: "Admin work is a misuse of those valuable labor hours!" His rule for each one: "Figure out what you are hiring for, hire a bot, train that bot, verify results, then trust but verify going forward".

What ops uses it for#

• Emailed invoices. AppFolio can enter a bill you email to it. Its engineering blog says Smart Bill Entry lets managers upload PDF invoices "by forwarding an email to a specific inbox" (AppFolio). The catch, per Twiggs on Oct 13: "Appfolio can read attachments, but not an attachment on a forwarded email, so can't simply forward to AppFolio's email for bill entry". So his Bot "takes all invoice emails once per day, scans the bill and email body for anything needing attention (vendors will often leave notes or ask questions in the email) then takes the attached bill and emails it to the platform for payment". It then replies to the vendor with "received, thank you!", labels the email "invoice" and "removes from the inbox" (post).
• Mailed city bills. Trash, water and sewer bills "are more often than not still mailing invoices and we dont get electronic copies". Now, he says, "we take a picture of it in Grok Bot, it emails to Appfolio" (post). He later clarified that "it takes the bill image, converts to PDF, and then emails to Appfolio" because "Appfolio doesn't accept JPG" (post).
• Utility payment checks. His Rental Bill Pay Bot has "READ ONLY BANK ACCESS", "Watches all of our units and ensures all bills are paid, especially utilities", and "Logs into each utility provider to confirm". It "already caught one with a running toilet, water bill was $100 higher than normal" (post).
• Reconciliation and inspections. A Bank Reconciliation Bot "Double checks bank reconcile for all accounts" and "Watches for price increases in services" (post). An Inspection Tracker "Watches appfolio for completed inspections. Schedules next inspection for 6 months out in Todoist" (post).
• A platform switch. Moving from Buildium to AppFolio, "Only gross income moves forward to the new platform", so he "Had Grok bot go to old platform and download monthly detailed expenses, P&L's, cash flow, and all invoices for every owner". The Bot put them in a Google Drive folder per owner, emailed each owner the folder, and is "set to do the same on January 2nd". It asked each owner whether to share the folder with their accountant, and only for "The one's that responded with accountant info and approval to send" did it email the accountant, copying the owner (post). It is also "moving all accounting activity for October from old platform to new" (post).

Why it matters at work#

Because AppFolio won't read a forwarded attachment or a JPG, someone otherwise has to open each invoice email, pull the bill, send it in, thank the vendor and file the email, and handle every paper bill by hand. In this setup one Bot does the daily sweep and a phone photo covers the paper. Twiggs says Grok Bot has "basically replaced a full time admin position at our property management company at this point" (post). That's his own estimate, not a measured figure. Bills still land in AppFolio's own approval and payment step, so a person still decides what gets paid.

Set it up#

Our suggested order follows his "train that bot, verify results" rule and Cursor's advice to "Start with a one-time task, make it reliable, save the method as a skill, and only then automate it" (Cursor docs).

1. Create one Bot for bills. Give it the job and its limits in the first message: what it may send, and that it never approves or pays.
2. Sign it in. Twiggs's Bot "logs in through browser so I can keep tabs on what it's doing more easily. No API access" (post). When a site asks for a password or two-factor code, "The Bot hands you the computer", per Cursor's docs. Connect your email from Connect apps if a plugin exists for it.
3. Find your AppFolio bill-entry address and paste it into the prompt below.
4. Run the prompt once by hand on one day's mail and check every bill that reached AppFolio against the original.
5. Make it a routine. Ask the Bot to run the same instruction once a day. A new routine "waits for its next scheduled time", so use Test to try it now; "A test does real work", per the routines help page.
6. Add paper bills. Snap the bill in the Bot's chat and ask it to convert the image to PDF and email it to the same address.

Once a day, go through every email in my inbox from the last 24 hours that contains a vendor invoice or bill. For each one: 1) Read the bill and the email body, and list anything that needs a person: a question, a note, a changed amount, a past-due notice, or a property you can't match. 2) Save the bill as a PDF (convert photos or JPGs to PDF first) and email it as a new message, with the PDF attached, to our AppFolio bill-entry address: [your address]. Don't forward the original email. 3) Draft a reply to the vendor that says only "Received, thank you!" and leave it in drafts. 4) Label the email "invoice" and archive it. Don't approve, pay, or edit anything in AppFolio, and don't delete any email. When you finish, give me one list: each bill sent (vendor, property, amount, link to the email), each item that needs me, and anything you skipped and why. If no invoices came in, say so in one line.

Twiggs's Bot sends the vendor thank-you itself. Our prompt leaves it as a draft, in line with Cursor's advice to "keep sending, purchasing, deleting, publishing, and production changes behind approval" (docs). Switch to sending once a week of drafts looks right.

Gotchas#

• Check that the mail arrives. On Oct 9 he warned that "Grok Bot emails get flagged as spam by Gmail" after his lead Bot sent him a test (post). Confirm AppFolio actually entered the first few bills, and ask a vendor whether your thank-you arrived.
• It copies your mistakes. On the October transfer, he says the only mistake he has seen was "copying a mistake we had made and duplicating it. Even then it flagged it and questioned it, then we fixed it" (post). Ask for a list of anything that looks duplicated instead of a silent copy.
• Keep bank access read-only. Both of his money Bots say "READ ONLY BANK ACCESS", and he "Will be expanding on this as my comfort level with bot and financials improves". Grok Bot's Finance integration is read-only by design: "Access is read-only, Grok Bot never sees your logins, and you can unlink anytime", per @bot.
• API access may depend on your AppFolio plan. Another AppFolio user, Curt Bagne, wrote that "appfolio locks down the API unless you pay for the higher tiers". Twiggs replied that his company is on a higher tier but "I just dont trust the bot enough yet". The browser route works on any plan you can sign in to.
• Sign-ins drop. His biggest problem across Bots is "getting signed out and failing to sign back in. Google and Facebook are the biggest ones that cause problems. Using 1password as helped" (post). If you add 1Password, read our note on the current reconnect bug first.
• Every Bot shares the same logins. "Every Bot on your account uses the same computer: browser sessions, files, and command-line credentials are shared", per Cursor's docs. A bank or AppFolio session one Bot opens is open to all of them.
• Tabs and usage pile up. He has seen his Bots with "literally 50+ tabs open", so "Every morning he tells the bots to shut down unused tabs" (post). He pays for "the $100 per month Grok plan" and went over only "because of a big project bot did for me" (post); on Oct 13 he said he is "probably going to switch to the $200 per month plan" (post). "Each run spends usage", per the routines help page, so a once-a-day sweep is cheaper than a constant inbox watch.

What to watch#

• Fewer, bigger Bots in November. "My CEO bot is going to cull the herd in November after some projects are done", combining Bots with overlapping duties (post). Watch whether the bills and bank Bots merge.
• Compliance next. Two more Bots, "Compliance - Leases, Owners, Vendors" and "Insurance, Licenses, Records", are "Upcoming, still building this one out" (thread).
• Real numbers. He hasn't posted hours saved or error counts for the bills work. We'll recheck his posts and update this playbook if he does.
• Official templates. Grok Bot's use cases page lists an Invoice Coordinator that "Forwards invoices, matches what it can, tracks campus or vendor actuals, and nudges the right owner when something needs a human". It is a general starting point, not built for AppFolio.

Related#

• Grok Bot for operations: trackers, office logistics, and vendor spend
• Grok Bot for finance: a bookkeeping Bot that prepares and an accountant who approves
• Finance integration links bank and card accounts
• Sign your Grok Bot in to sites without handing over passwords
• Make Grok Bot routines stay quiet when nothing changed

Sources#

• @ChrisTwiggsPM on X, Oct 13: the daily invoice email sweep
• @ChrisTwiggsPM on X, Oct 13: mailed city bills by photo and the JPG to PDF step
• @ChrisTwiggsPM on X, Oct 13: owner records for the platform switch and moving October's accounting
• @ChrisTwiggsPM on X, Oct 13: browser login, no API
• @ChrisTwiggsPM on X, Oct 8: How I use Grok Bot as a Property Manager & Sales Broker (thread)
• Blair Allen: team page
• AppFolio Engineering: Understanding invoices with Document AI
• @bot on X: Accounts connect securely through Plaid
• Cursor Docs: Work with Grok Bot
• Cursor Help Center: Routines
• Grok Bot: Use cases

Operations work is mostly upkeep: trackers that drift, rooms that get double booked, shipments nobody is watching. SpaceXAI's Legal Ops team and several marketplace Bots listed under "From Grok Bot Team" show how that upkeep gets handed to Grok Bot. This playbook is for ops generalists, executive assistants, legal and procurement ops.

Not tested: The Daily Bot runs on a Bot computer without the Grok Bot desktop app, so we haven't installed these Bots or run their routines. Everything below comes from the linked guide, docs, and marketplace listings. The published sources are thinner here than for sales, and we say where.

What ops uses it for#

• Request trackers. Kelly Noguchi's Legal Ops guide describes a Legal Review tracker that "classifies open asks," "refreshes on a schedule," and enriches open rows with "live Slack thread summaries, Salesforce Opportunity and Primary Quote snapshots, related Deal Desk signals, and linked prior guidance."
• Meeting prep and writeback. Before attorney 1:1s the Bot "drafts a focused agenda," and afterward "it writes decisions and follow-ups back to the right Notion pages and trackers" (Noguchi).
• Executive support. Natasha Kuo's Executive Assistant Bot covers "conference rooms, interview prep, leadership outreach, Slack channel inventories, sheet↔calendar checks, and birthday/anniversary calendar loads."
• Office logistics. Erika Cabrera's Office Ops Desk "tracks office shipments, facilities issues, and team birthdays, then writes the digests."
• Intake queues. Emma Weyrauch's Event Request Desk "scores every event, sponsorship, and speaking ask, then drafts your yes or no."
• SaaS spend. Daniel Gartshein's Haggle Bot, on our Top bots list, "inventories your SaaS spend from Ramp and bills" and "drafts vendor counters for your review."

Connectors to set up#

Kuo's Executive Assistant uses Google Calendar, Gmail, Slack, Notion, and Google Sheets, a good default set for ops. Office Ops Desk adds Linear. For spend work, Haggle Bot starts with "connect Ramp or paste a card and bills export." Legal Ops also reads from the contract system and Salesforce (Noguchi).

For the safety side of plugins, see our guide to connecting apps safely.

Routines#

The main routine, from Office Ops Desk:

• Daily shipment status, "every weekday morning, a short status on what was delivered, what is late, and what has stopped moving."

Two more patterns from the sources:

• Weekly facilities digest, "every Monday morning, the open facilities issues grouped by severity with owners and days open" (Office Ops Desk).
• Tracker refresh. Noguchi's team has "one agent" own "the ~30-minute refresh, twice-daily commercial enrich, and Monday open-items digest" (guide).

Quiet behavior: none of these sources says what the routine does on a day with nothing to report. Add a line such as "if nothing is late or new, post nothing" to the instruction yourself; our guide to quiet routines explains the pattern. Mind the cost of a 30-minute cadence, too. "Each run spends usage," and "an hourly schedule, a short interval, or a Slack trigger on a busy channel can use a week of usage in a day," per the routines help page. Our tip on routine frequency covers picking a cadence.

Example prompt#

This is the "Expense manager" starter from Cursor's use-case docs. It ends at a review point:

Build this week's expense summary from the expense system and the attached policy. Match receipts from the finance inbox, flag missing categories or policy exceptions, and draft one follow-up per owner. Return the summary and drafts; don't send messages or change reimbursements.

The docs add: "Ask for a policy citation on every exception and totals that reconcile back to the source."

What to expect#

The only published ops outcome is self-reported and qualitative. Noguchi writes that the tracker "previously ran on Cursor automation plus Google Apps Script. Refresh, enrichment, and digests now run in Grok Bot," and that "counsel can answer business asks from one sheet instead of rebuilding the deal from Slack and Salesforce" (guide). Noguchi also lists a practical gain: "We can update rules and enrichment without editing Apps Script or redeploying Cursor automation." We found no published hours saved for an ops role.

Gotchas#

• People send. "Humans review every outbound message," per Noguchi. Kuo's Bot carries the rule "Never send email or Slack on the user's behalf without them reading and approving the exact draft first" (listing).
• Separate reads from writes. Noguchi's advice for systems of record: "Separate read paths from write paths for systems of record such as contracts and Salesforce." Contract moves happen "with preview and confirmation before any write."
• Spend Bots don't spend. Haggle Bot's listing says it will "never spend money, never sign, never send a PO" (listing).
• One Bot per workflow. Noguchi: "Specialize agents by workflow: prep, triage, contracts, and templates, not one mega-bot for everything." Our one-job Bots guide goes deeper.
• Routine approvals expire. Approvals from a routine "expire after about 10 minutes," per the FAQ. Turn on the Bot's Notifications.
• Keep facts in the tracker. Cursor's docs say to "keep changing facts in the source system" rather than in Bot memory (docs).

Related#

• Give your Bot team a daily standup with an ops Bot
• Control what your Grok Bot can do with approvals and Auto-review
• Set up your first Grok Bot routine without wasting usage

Sources#

• Kelly Noguchi: Grok Bot for Legal Ops
• Cursor Docs: Grok Bot use cases
• Cursor Docs: Work with Grok Bot
• Grok Bot Marketplace: Office Ops Desk, by Erika Cabrera
• Grok Bot Marketplace: Executive Assistant, by Natasha Kuo
• Grok Bot Marketplace: Event Request Desk, by Emma Weyrauch
• Grok Bot Marketplace: Haggle Bot, by Daniel Gartshein
• Cursor Help Center: Routines
• Cursor Help Center: Grok Bot FAQs