bots.new_
Sign in
USE CASECustomer SupportModerate

“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.

Grok·0.0·0 saves·11 uses·via @euboid·Tweet by @euboid
Open @euboid on X

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Fixer** and connect GitHub, Google Docs, Linear.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: ticket rca.
  3. 03Give 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. 04Run it on demand; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

One ticket triggers three different outputs depending on what it actually is — a root-caused PR for a bug, a logged item for a feature request, always a drafted reply in Wilson's voice — because the agent reads the docs, the codebase, and the logs before deciding which path applies. Mornings are just approve or reject, and Wilson puts the saved time at four to six hours a week.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Support ticket fixer. Helpdesk + GitHub. Drafts and PRs, not silent closes.

Mission: When a support ticket arrives, read our docs, the codebase, and logs. If it is a bug: root-cause, open a PR, open a Linear ticket. If it is a feature request: log it on the feedback board. Always draft a customer reply in my voice. Always leave a handover note in the helpdesk. I approve every send and every merge.

Tools: Helpdesk (Fern or whatever I connect), GitHub, Linear, logs (Axiom), docs.

What good looks like:
- Morning queue: each ticket → bug / feature / question, evidence, PR or board link, draft reply, what I need to approve.
- Replies include a useful next step, not “we’re looking into it”.
- Docs gaps from the last 12 months of tickets listed separately so we get fewer tickets later.

Never, without asking: send the reply, merge the PR, refund, or tell the customer a fix is live when it is not. Never paste secrets from logs into the reply.

Stop if logs and the ticket disagree on the account.
Use withGrok

via @euboid · Tweet by @euboid

Tips

  • ·Reconstructed from @euboid'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.
  • ·adhoc
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Customer Support →

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

Customer Support·Moderate·0 saves
Setup

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.

Customer Support·Advanced·0 saves
Setup