ILIAS ISM pasted a screenshot, agent closed the ticket and shipped a fix

ILIAS ISM says he pasted a screenshot of a customer support email into Cursor with 0 words in the prompt and the agent ran the whole loop on its own, because his email, analytics, payments, codebase and server deploys are all connected through MCPs (Model Context Protocol servers, the standard way agents get tool access to outside systems).

ILIAS ISM

@illyism

X

Support ticket resolved + root cause fixed on the site in 60 seconds without typing a single word

What the agent actually did

He lists six steps. The agent read the email thread in Gmail and pulled the customer's 2024 order from the Polar API. It checked his self-hosted DataFast MCP for the visitor timeline from four minutes earlier, which ran `/ -> /customers -> /courses/programmatic-seo -> /about`. From that path it concluded why the customer got lost, the "Open the course" login link sat at the bottom of the sales page and he left before scrolling down.

Then it tested the customer's license key on the live login page in a headless browser to confirm it still worked, drafted a reply containing the license key and a new portal link, added "Already purchased? Open the course" to the hero section, and deployed that change to production.

ISM's summary is that the support ticket was resolved and the root cause fixed on the site in 60 seconds without typing a single word.

What this is and is not

This is one run, posted by the person who built the setup. There is no error rate, no count of how many tickets went through the same path, and no description of what the agent does when the diagnosis is wrong. The visitor timeline step is the interesting part, because the page sequence is what turned a vague complaint into a specific UI fix, and that only works if your analytics are already exposed as a tool the agent can query.

For people building on it, note where the loop ends. The last step was a production deploy, with no human in between the screenshot and the live site. An agent that can edit your hero section unsupervised is a different risk class from one that drafts a reply and stops, and the 60 second number is the result of removing exactly that gate.