These customer routes are reported by All Things How. Happy and Secret are community labels here, not a verified count or guaranteed main-ending recipe.
The recommended choice
For the supportive branch, keep a pre-hand-in save, do not report the discovered information and help the former Gangster restart legitimate work. Confirm the return visit and support him again.
Why the repair matters
The job deliberately separates technical access from permission to act on private information. Completing the hardware work gives you knowledge, but the story asks what responsibility comes with it. Make a save before returning the phone, not only before the final dialogue.
A completed repair can unlock the next dialogue, achievement, or story beat. Save before mutually exclusive choices when the route matters.
Complete the positive arc
Staying silent starts the favorable path. Keep speaking with him on later visits and help him move toward legitimate work. A positive first response without the later support may be enough for part of the story, but it is not the complete hidden follow-up.
Customer follow-ups are not a main-ending formula
The return visit is the customer-story checkpoint. Keep it separate from the main finale and retain the help-route save while comparing the reporting alternative.
How to view both outcomes
Protect one save before the device hand-in. Use one branch to report and observe the consequences, then restore the checkpoint and choose continued support. Do not overwrite the positive save until the return visit appears.
Positive Gangster route in one controlled sequence
Make a manual save before returning the phone and before the report-or-help decision. For the favorable route, do not report the former Gangster, respect the privacy boundary described by the story, and support the move toward legitimate work. Continue on that same save until the return visit, then choose the supportive response again. The later visit is the clearest observable confirmation that the extended route continued. A single non-reporting choice is important, but it is not a substitute for checking the callback. Keep the checkpoint until the ending is confirmed so that you can distinguish a missed later response from an unrelated progression problem. The technical repair and narrative decision are separate: a correct repair does not automatically select the positive customer outcome.
- Save before the report decision
- Do not report him on the positive branch
- Support the legitimate-work direction
- Confirm the return visit and support him again
How to compare reporting and helping outcomes
Use one untouched pre-choice save, one help-route save, and one report-route save. Record the immediate dialogue after each decision and whether a return visit occurs. Do not continue the report branch over your positive ending file. If a later patch changes wording, compare intent and observable result rather than relying on an old screenshot label. Community videos can provide leads, but verify that the build and preceding state match before treating a scene as universal. Keep the repair result as similar as possible and change only the report-or-help response. That controlled comparison is more reliable than two runs that also differ in purchases, timing, customer order, and shop rating. The purpose is to identify the minimum branch difference, not to copy every action shown by another player.
| Branch | Observe now | Observe later |
|---|---|---|
| Help | Customer response and route state | Return visit and support choice |
| Report | Immediate consequence | Whether the positive callback is absent |
| Finale | All four customer states | Ending reached on this save |
If the return visit does not appear
Verify the loaded slot, current build, active To-Do, and whether the first supportive conversation fully completed. Advance actual story objectives before using repeated sleep or shop actions as a workaround. Check that a cloud restore did not replace the positive save with an earlier timestamp. Do not buy unrelated upgrades or restart the campaign while the loaded save and active objective are still unchecked. If the issue persists, preserve the pre-choice and current saves and report the exact sequence: repair completion, report decision, later objectives completed, and last visitor seen. Include language and platform so wording or version differences are visible. This evidence can separate a route mistake from a progression defect without promising that one purchase, reload, or wait period fixes every case.
Gangster route verification and evidence boundary
A complete result includes the build, device return, report-or-help decision, first outcome, return visit, second support decision, and final ending on the same save. For a Happy route, keep the favorable result with the other major customer arcs. For a Secret route, confirm the extended return interaction. Mark the source of every claim: an official description can establish that the dilemma exists; current play establishes behavior in a tested build; a community post remains a lead until reproduced. Do not expose unrelated phone contents or story details merely to lengthen the page. The useful answer is a direct route first, followed by checkpoints, alternatives, troubleshooting, and a clear line between confirmed behavior and conditional reports.
