Use cases / Sales
Grok Bot for stale deal follow-up drafts
How to run stale deal follow-up drafts with Grok Bot: which Bot owns it, what it reads and produces, the cadence, the approval gate, and the specific risk to watch.
Short answerPipeline Bot, daily 07:30: reads deals with no activity in 7 days, produces one draft per deal in the rep's voice. Gate: every send.
| Function | Sales |
| Tools | CRM, Gmail |
| Owning Bot | Pipeline Bot |
| Cadence | Daily 07:30 |
| Reads (bounded) | Deals with no activity in 7 days |
| Produces | One draft per deal in the rep's voice |
| Approval gate | Every send |
How it runs
The Pipeline Bot owns this as part of its theme. On its cadence it reads deals with no activity in 7 days, produces one draft per deal in the rep's voice, and stops. It writes one heartbeat line to the ops log so a missed run shows up in the morning message.
The risk to watch
Drafts must never auto-send.
Setup
- Bot identity with a seat in: CRM, Gmail. See own accounts.
- Test supervised three times, then schedule.
- Four-part routine shape: routines best practices.
Part of the sales ops playbook.
Verified 28 Aug 2026 · Facts about Grok Bot change during beta. See changelog.