How Can We Troubleshoot Client Issues Without Direct Customer Contact?
Asked by
MellowPine7!
I develop and maintain an Angular web app for my company, targeting Android and iOS devices. Recently, I added an in-app camera that can capture multiple photos and upload them together. It works on almost every device, but a few clients have reported only that it "doesn't work," without providing any details. The problem could be related to unsupported Windows usage, a browser issue, device permissions, or faulty camera hardware.
I asked customer service whether I could contact those clients directly to find out which devices and operating systems they use, but they said that isn't possible and also don't want to ask the clients for more technical information. Is direct developer-to-customer contact uncommon in professional software teams? If so, what processes or workarounds are normally used to gather enough information to reproduce and fix problems like this?
Answers
If customer service won’t gather the information manually, add diagnostics to the application. When the camera fails, record non-personal technical details such as the device type, operating system, browser, camera API status, permission state, and a useful error code. Send that information through your normal logging or support system, making sure the collection is disclosed and complies with your company’s privacy requirements. This won’t replace a clear user description, but it can reveal patterns quickly.
Reply to this answer
It’s reasonable for support to close or pause a ticket when there isn’t enough information to identify or reproduce the problem, but the process should be polite and consistent. Give them a short questionnaire and make it part of the ticket workflow. If the client doesn’t provide the requested details, explain that the issue can’t be investigated yet rather than simply guessing at a fix.
Reply to this answer
Direct developer contact with customers is fairly uncommon in larger companies. It can turn into an expectation that you’ll personally handle every technical problem, and casual comments can easily be interpreted as promises about future support. A better arrangement is for developers to provide customer service with a checklist or form, while support gathers the answers and passes complete tickets to engineering.
Reply to this answer
You need specific information about what failed before you can investigate properly. At a minimum, support should collect the device model, operating system and version, browser, the steps the customer took, what they expected to happen, and any error message or screenshot. Without that, the best you can do is guess, and reproducing the issue is nearly impossible.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions