All use cases

Work

Client change requests on autopilot: an assistant bot and an editor bot

Small photo change orders from clients eat hours: find the email, find the file, fix it, send it back.

Share

What hurt

Billy (@billykyle) photographs real estate. He set up a pipeline of two Grok Bots for client change requests in about 20 minutes and keeps tweaking it before letting it run fully on its own. Not affiliated with xAI.

What to install or create

The assistant (chief of staff) scans email for change requests and organizes them by client, shoot date, and what needs fixing. The editor finds the files, edits them through the Higgsfield MCP connector (Nano Banana Pro), and saves the new versions in a separate subfolder so originals stay safe. The editor then compares old vs new as a quality check and moves passing files to the delivered folder. After the ok, the assistant replies on the same email thread.

Bots

  • Assistant (chief of staff)

    Finds change requests in email, organizes them by client and shoot date, and replies on the thread after approval.

  • Editor

    Finds the files, edits them via the Higgsfield MCP connector, saves to a subfolder, and runs the old-vs-new check.

Plugins

  • Gmail

    Required

Files

  • Shoot folders with a separate subfolder for edited versions and a delivered folder clients can see.

Routines

  • None on the first run. Watch one manual pass first.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/billykyle/status/2107582363505226023 (credit @billykyle).
  2. 2Make two bots: an assistant that reads your email and an editor that works on your files.
  3. 3Have the assistant flag change requests by client, shoot date, and what to fix.
  4. 4Connect the editor to your image tool (he uses Higgsfield's MCP connector) and tell it to save edits in a separate subfolder, never over the original.
  5. 5Add the quality check (compare old vs new) and keep the client reply waiting for your ok until you trust it.

Approval fence

Replying to clients is a send. Keep the “after receiving the ok” step: you approve the reply until the pipeline has proven itself, and the bots never overwrite original files.

What to tweak

Two narrow roles plus a before/after check beats one bot doing everything — and a separate subfolder keeps your originals safe.

Source

Billy @billykyle · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro