Support Ticket Fixer

Success Based on this tweet by @euboid · scouted by @elie2222

The prompt

Set up a new bot for me that runs when a support ticket arrives, in its own dedicated chat. Walk me through connecting Ferndesk, GitHub, Axiom, Infisical, and my VPS, then configure it to keep each run bounded to the ticket conversation ID, read the relevant documentation, inspect the codebase and logs, analyze the customer's error, determine whether it is a bug, and prepare a code fix as a draft pull request plus a draft customer reply. Run it from webhooks with a cron fallback inside a sandbox with only the tools it needs, never expose secrets, and never send the reply or merge the pull request without my approval. Ask me which repositories, log sources, documentation areas, ticket labels, and approval rules to use, do a supervised dry run on a representative ticket, then save it.

Paste it into Grok Bot, Rakazo or any agent you already use. It asks for what it needs, then saves itself as a bot.

Connect first

FerndeskAxiomGitHubInfisicalCodex

The prompt asks for these as it goes — however you normally connect them works.

Tired of signing in to each service for every harness? Executor signs you in once — every client shares the credentials. Try Executor → Sponsored

Run Support Ticket Fixer yourself

Free to copy, adapt, and edit after setup.

View source
Sponsored advertise →