Churn Win-Back Loop is a Grok Bot setup that uses Grok Bot.
Church Research Briefs is a Grok Bot setup that uses Grok.
Support Resolution Agent is a Grok Bot setup that uses Claude.
Support Ticket Fixer is a Grok Bot setup that uses Ferndesk, Axiom, GitHub, Infisical, Codex.
Burner Account Bouncer is a Grok Bot setup that uses X.
Support Autopilot is a Grok Bot setup that uses Bento Chat, HelpSpot, Help Scout, Intercom.
Leader 1:1 Bot is a Grok Bot setup that uses Grok.
Churn Early Warning is a Grok Bot setup that uses Salesforce, PostHog, Slack.
Support Reply Drafter is a Grok Bot setup that uses Gmail.
Account Expert is a Grok Bot setup that uses Slack, Gmail, Gong, Granola.
Support Queue Pass is a Grok Bot setup that uses Zendesk, Slack.
AI Assessment Analyst is a Grok Bot setup that uses Google Drive, Google Slides.
Docs Self-Serve Assistant is a Grok Bot setup that uses Ferndesk.
Enablement Pack Builder is a Grok Bot setup that uses Gmail, Zoom, Google Drive.
What Did We Promise is a Grok Bot setup that uses Slack, Salesforce, Google Drive.
Tickets To Changelog is a Grok Bot setup that uses Zendesk, Notion.
QBR Pack Builder is a Grok Bot setup that uses Salesforce, Zendesk, Google Slides.
Help Center Updater is a Grok Bot setup that uses Intercom, GitHub.
Mappy (Talent Map) is a Grok Bot setup that uses Grok.
The docs update themselves the moment a PR merges
Damon’s Intercom + GitHub bot watches every merged PR, decides whether a help-center article needs updating, then drafts and publishes it. 82 likes / 11.4K views.
Support replies already waiting when you sit down
Lenny’s same early-access note: auto-replying to support emails, which he said saves him hours. Drafts in his voice; he stays on the send button.
Reply by text, and it works the helpdesk for you
Jesse Hanley’s thread is not a one-liner dump: he already runs a support bot against Bento Chat / helpdesk. It sweeps a few times a day, summarises what is assigned or escalated, and he texts back what to do — then it hits the admin MCP. “This is what I’ve done and it’s fantastic.”
One ticket, a root-caused PR, and a reply by morning
Wilson (euboid) built the loop after asking whether Grok Bot could debug tickets, open a PR, and draft a reply. Incoming ticket → agent reads Fern docs, codebase, Axiom logs → bug gets RCA + PR + Linear, feature request hits the board, customer reply is drafted in his voice.
An Instagram bug report that routes itself to QA
Dan Peguine's Grok Bot watches his Instagram inbox. A website-bug complaint got routed to a QA bot in the Ship channel (with his engineer bot 'David'); QA tested the funnel, found nothing, and had a Writer bot reply — and a real bug would have become David's fix and a PR.
In-policy refunds issued straight through Stripe
Gergely Orosz hooked Grok Bot to customer support email and the Stripe API so routine refunds run as an agentic workflow. 764 likes / 366K views.
- Listings
- 0
