From customer problem to reviewed code fix.
Keep support and engineering connected through the problem itself: the customer’s conversation, a reproducible report, the coding run and the evidence that the change works.
Start with your app or websiteBy Macaron · Updated
First decide whether the problem needs code
A question about a plan, a setup mistake and a broken checkout need different responses. Read the conversation, ask for missing context and answer what you can. Create a fix report when there is behavior to investigate, rather than treating every message as an agent task.
For apps, capture the screen, build, operating system and device. For websites, include the route, browser and relevant state. Record what happened, the shortest reproduction sequence and expected behavior. The customer’s words and your diagnosis should remain distinguishable.
Prepare a bounded coding task
Prepare fix carries a saved report into run setup. Check the task text, repository, branch, machine, model and permissions. Include the checks your repository actually runs and describe the behavior the change must preserve.
A saved report needs no model key. Before a browser coding run, use your app’s Connect code and model setup. Check a public GitHub repository without a token, or grant repository-scoped read access for private code. Add a provider API key with billing enabled; this browser flow does not use a ChatGPT or Claude chat subscription. Select a compatible machine and checks before explicitly starting work. Do not put keys or customer secrets into the task text.
Review the change and the checks
Read the output and diff before accepting a change. Check that the implementation addresses the recorded problem and that the tests exercised the relevant path. A failed, stopped or completed run leaves the report open for owner verification.
Match verification to the platform. A Linux workspace can run many website checks, but cannot establish that an iOS app passes an Xcode simulator build. Use a suitable Mac for Apple tooling and leave untested behavior explicit.
Resolve with evidence, then follow up
Repeat the reproduction steps against the actual build you want to call fixed. Add a verification note naming the checks, observed result and release environment before marking the report resolved. A local patch, a deployed release and a fix confirmed by a customer are different states.
Return to the conversation and explain what changed and where it is available. If the problem returns, reopen the report so the earlier work and verification remain attached. The goal is a shorter path from a customer’s problem to a change your team can stand behind.
After replying, ask whether the problem was solved. The customer’s Yes, solved or Still need help response is recorded in the inbox. Team follow-up notes and due reminders help you return to unfinished conversations. Customer confirmation is a support outcome, not proof that code was verified or a subscription was retained.