# Grok Bot mailbot batches 4 unsubscribe candidates at a time, decided by Y/N/D

Grok · X (Twitter) · Amount undisclosed (workflow-only case; no revenue claim)

## Business summary

User set up a Grok Bot mailbot for Black Friday to present unsubscribe candidates in batches of 4 and reply Y/N/D for each batch. Suitable for rapid inbox cleanup during high-spam seasons while keeping human confirmation.

## Business value

User set up a Grok Bot mailbot for Black Friday to present unsubscribe candidates in batches of 4 and reply Y/N/D for each batch. Suitable for rapid inbox cleanup during high-spam seasons while keeping human confirmation.

## Workflow

Configure Grok Bot mailbot to scan and identify unsubscribe candidates

Bot presents them in batches of exactly 4

Execute unsubscribe (Y), skip (N) or delete (D) based on reply (inferred from conventional meaning)

## Preparation and limitations

Results and numbers are as reported by the original post author (batches of 4, Y/N/D replies). The original post does not explain what Y, N and D each trigger; the mapping in the workflow is inferred from conventional meaning. Email connector and permissions are not described. Workflow steps, freePrompt, and trial I/O are AgentFlow reconstructions and were not live-tested here.

## Starter prompt

````text
You are an inbox cleanup assistant. The user has granted read or limited-write access to email.

Task: Scan recent promotional/subscription emails, identify one-click unsubscribe candidates, and present them in batches of exactly 4.

Output format:
Batch N:
1. Sender | Subject | suggested action
2. ...
3. ...
4. ...
Reply Y (unsubscribe all) / N (skip all) / D (delete all) or specify per item.

Missing/conflict handling: If unsubscribe eligibility is unclear, mark “uncertain” and do not auto-execute. If permissions are insufficient, stop and state required permissions.

Confirmation boundaries: Never auto-send unsubscribes or deletions. Wait for explicit user Y/N/D reply before any action. Do not access payment information.

Untested.
````

## Costs and pitfalls

Results and numbers are as reported by the original post author (batches of 4, Y/N/D replies). The original post does not explain what Y, N and D each trigger; the mapping in the workflow is inferred from conventional meaning. Email connector and permissions are not described. Workflow steps, freePrompt, and trial I/O are AgentFlow reconstructions and were not live-tested here.

## Source and attribution

Ross (@rosswil)
https://x.com/rosswil/status/2121653036703748165
2026-11-15
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
