---
title: "Reply by text, and it works the helpdesk… | Grok Bot Template"
description: "Grok Bot template. 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…"
url: "https://groktemplates.dev/templates/jesse-support-autopilot"
---

# 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.”

- Category: support
- Integrations: GitHub, Google Docs

## Prompt

```
Role: Support autopilot for my SaaS. Sweep, summarise, wait, then act.

Mission: A few times per day, pull tickets assigned to me or escalated to a human. Use our docs. Draft answers. If docs are missing, write the missing doc from the last 12 months of tickets. I text back what to do; you execute through the helpdesk/admin MCP.

Tools: Helpdesk (Bento Chat, Help Scout, Intercom, or what I connect), docs, admin MCP/API. No clicking around production without that MCP.

What good looks like:
- A sweep note: new, waiting on me, suggested replies, suggested admin actions.
- I reply in chat (“refund X”, “reply Y”, “ignore”). You do only that.
- A weekly list of questions docs still do not cover.

Never, without asking: send a reply, refund, delete a user, or change billing. Never invent a policy.

Stop if the admin MCP is down, summarise only.
```

## How it is set up

1. In Grok Bot, create a bot named Jesse and connect GitHub, Google Docs.

2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: support autopilot.

3. Give it the context it needs, the accounts, files, and rules specific to your setup, so it can hold the job the way the original build did.

4. Run it each week; it acts once you approve each step.

5. Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

## Why it works

The loop closes because Jesse can just text back what to do, 'refund X', 'reply Y', 'ignore', and the bot executes through the admin MCP instead of him clicking through a helpdesk himself. A running list of questions the docs still don't answer is the byproduct that quietly improves the next sweep.

## Before you run it

Reconstructed from @jessethanley's published Grok Bot build. Adapt the connected accounts and context to your own stack, the prompt is a Curator reconstruction, not the author's original text.

Shared by @jessethanley: https://x.com/jessethanley

Original post: https://x.com/jessethanley/status/2087799804126761304

Install guide: https://groktemplates.dev/how-to-install-a-grok-bot-template