Grok BotWorkplace

Needs re-check

· Beginner · Active

Illustration: a closed manila file folder seen straight on, with a blank till receipt tucked into its top edge, in black and white.
Illustration

Grok Bot for trades offices: receipts filed to jobs twice daily

Not tested yet: Neither owner has shared his prompt, CRM name or setup steps. Ask or watch for follow ups and add the real setup. We haven't run a receipt filer. Test one on a safe CRM sandbox or a single test job before publishing a hands-on claim. Mike Walls's 'hours a week' and Moises Truzman's report are self-reported. Recheck their posts for numbers or problems. Reported, not yet confirmed.

Mike Walls has Grok Bot pull emailed receipt PDFs into each CRM job twice a day, a task admins hated.

Work value 8/10

You can hand Grok Bot the receipt chore that sits between the field and the books: every vendor receipt that lands in email gets pulled out and attached to the right job in your CRM, twice a day, with nobody in the office doing it by hand. This playbook follows one person who runs that job now, adds a second owner who runs a Bot for each of his four businesses, and gives you a starter prompt with the guardrails we'd add. It fits office managers, bookkeepers and owners of trades and field service companies. Both are short self-reports, and neither has shared his exact setup.

Not tested: we haven't run a receipt filer ourselves.

Who runs it#

The receipt job belongs to Mike Walls (@MikeWallsQC, Chicago). In August he wrote: "I work in sales for a painting company. I used AI to build an app layer that sits on top of our systems of record like CRM." He added: "I am not a programmer. I went to culinary school at a community college." His receipt posts say "our receipt inbox" and "our CRM" and don't name the company, so we don't either.

He has described the same job twice, five days apart. On Oct 17 at 7:54 AM ET, answering another user's question about Grok Bot tips, he wrote: "One of many helpful jobs it does for me: All our receipts land in an email folder. I have it automatically pull the pdfs and attach them to each job in the CRM for easy referencing. An admin used to spend hours a week doing this." On Oct 22 at 9:29 AM ET, answering Grok Bot staffer Matt Palmer's question "How has grok bot helped you lately?", he wrote: "Twice a day scrapes our receipt inbox and places the new receipts in our CRM under the associated job. Admins used to have to do this and hated it."

He runs several small jobs like it. In August, replying to a screenshot of Grok Bot's weekly usage at 100%, he said he stretches his usage "with the $300 plan and a bunch of bots doing small chron jobs and coding updates." He doesn't name the plan, and Grok Bot's plans have changed since (the X Subscription), so we don't map it to one. On Oct 21 he put his split at "80/10/10 grok bot/claude/gpt", with "grok for maintenance, updates and staying on top of general work."

Disclosure: Matt Palmer's X bio reads "cursor & @bot at @spacexsi". He asked the question; the answers are users' own. Mike Walls's profile links to Today List, a paid iPhone to-do app. His posts here don't mention it, and we couldn't confirm whether he's connected to it. Moises Truzman's profile links to Eagle Truck Cleaning in Medley, Florida.

A second owner, same idea#

In the same thread on Oct 22 at 11:37 AM ET, Moises Truzman (@truzmanmoises, Miami) wrote: "I run a truck wash, a hood cleaning company, a filter exchange business and a polishing shop, and I've got a bot for each one. Every morning I get a report of all my texts and emails, so I know what's urgent without digging through 5 inboxes." He added that "It answers my Indeed applicants for me, watches my Google Ads and makes changes every day, tracks my yard sales". He doesn't say how each piece is connected or whether any step waits for his approval.

Why it matters at work#

Our read: receipts are where job costing quietly breaks. A crew buys paint or parts, the receipt goes to an inbox, and someone has to match it to a job before anyone can see what the job really cost. It is repetitive, easy to fall behind on, and nobody's favorite task, which is exactly what Mike Walls says about it. A twice-a-day routine keeps the job file current without a person sitting on the inbox, and the person who used to do it moves to checking the few receipts that don't match. Moises Truzman's setup shows the other half of the pattern for a multi-business owner: one Bot per company, each with its own inbox, and one morning report so the owner sees what's urgent first.

Set it up#

These steps are ours, built from his posts and the docs. He hasn't shared his prompt or which CRM he uses.

  1. Give it one job. 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 name "Expense Manager" as an example job (docs). In the first message, "give the Bot its job, sources, and approval boundaries, and ask it to remember them."
  2. Point it at one email folder. Have vendors and crews send receipts to one address or folder. If you use Gmail, the Connect apps help says the connector "can search and read mail, draft and send, and apply labels on the connected mailbox." A Filed label lets the Bot skip what it already handled. If your Bot has its own mail.grokbot.com address, a +receipts alias gives receipts their own stream (our Oct 14 tip).
  3. Connect the CRM the sturdy way. The docs say "Prefer a connector when one is available: it is often more reliable than clicking through a website. Use the browser for services without a connector." Most trades CRMs won't have a connector, so expect the Bot to work through the CRM's website.
  4. Set the schedule in plain words. The routines help says to ask "in plain words, like "every weekday at 8:00 AM" or "every 2 hours"." Twice a day matches his setup.
  5. Test on one job first. The routines help warns: "A test does real work. It can change files and use connected apps. Use a safe input." Send one test receipt for one test job and check the attachment by hand.

Prompt (ours, untested):

Set up a routine for every weekday at 11:00 AM and 4:00 PM [your time zone]. Each run: open the email folder [Receipts] and find messages that don't have the label [Filed]. For each one, save the receipt PDF or image, then find the matching job in [your CRM] using the job number, customer name or job address in the email or on the receipt. If exactly one job matches, attach the file to that job and add the label [Filed] to the email. If no job or more than one job matches, don't attach anything; list it under Couldn't match with the sender, date, amount and the jobs you considered. Never delete or move emails, never edit any other field on a job, and never reply to a vendor. End each run with a short note in this chat: how many receipts you filed, to which jobs, and what's waiting on me.

Twice a day, the email folder, pulling the PDFs and attaching them to each job are his. The times, the Filed label, the match rules, the Couldn't match list and the never-edit rules are ours.

Gotchas#

  • Matching is the hard part. Our read: a receipt with a job number is easy; one that only shows a store name and a total is not. Ask crews to put the job number in the email subject, and keep the prompt's exactly-one-match rule so the Bot lists doubtful ones instead of guessing.
  • Keep the CRM as the record. "Memory is not a substitute for an authoritative source" (docs). Let the Filed label and the CRM attachment be the proof a receipt was handled, not the Bot's memory.
  • Twice a day, not every hour. "Each run spends usage, so a routine that runs often spends more than one that runs rarely" (routines help). Receipts rarely need minute-by-minute filing.
  • Web logins can expire. If the Bot works through the CRM's site, the docs note "Some websites expire sessions, enforce short timeouts, or request verification again" (docs). Have it stop and tell you rather than skip a run quietly.
  • Applicant replies go out under your name. Our read on Moises Truzman's Indeed step: messages to job seekers are a different risk from filing receipts. Start with drafts you approve before letting a Bot answer applicants.

What to watch#

  • The setup. If Mike Walls shares his prompt or names the CRM, we'll add the real steps here.
  • The numbers. "Hours a week" is his estimate. Watch for a measured before and after.
  • Moises Truzman's four Bots. Watch for how he splits the work and whether the Google Ads changes hold up.

Sources#

Prompt

Ours, untested. Set up a routine for every weekday at 11:00 AM and 4:00 PM [your time zone]. Each run: open the email folder [Receipts] and find messages that don't have the label [Filed]. For each one, save the receipt PDF or image, then find the matching job in [your CRM] using the job number, customer name or job address in the email or on the receipt. If exactly one job matches, attach the file to that job and add the label [Filed] to the email. If no job or more than one job matches, don't attach anything; list it under Couldn't match with the sender, date, amount and the jobs you considered. Never delete or move emails, never edit any other field on a job, and never reply to a vendor. End each run with a short note in this chat: how many receipts you filed, to which jobs, and what's waiting on me.

Sources

  1. x.com
  2. x.com
  3. x.com
  4. x.com
  5. x.com
  6. x.com
  7. x.com
  8. cursor.com
  9. cursor.com
  10. cursor.com
  11. docs.x.ai

Something wrong? Tell the bot