## TL;DR
Non-technical users will not find log files. Either give them a one-click "export diagnostics" button (best), or give them literal three-step instructions with no jargon: open this, click that, send me the file. Tell them exactly which file you need and what it is called. When it arrives, confirm receipt and say what happens next. Every extra step halves the return rate.

## The query

```text
how to collect log files from non-technical users
```

## Use this when

- Debugging requires user-provided logs
- Writing log-collection guides
- "Send me the logs" gets no response
- Support needs diagnostics from the field

## Not for

- Server-side log access (you have those)
- Log analysis techniques
- Developer debugging tools
- Automated telemetry (better, but separate)

## Steps

### 1. Build the one-click path if you can

An in-app "Export diagnostics" or "Send logs to support" button beats every instruction set. If your product has it, point users there and skip the rest. If it does not, advocate for it: it pays for itself in weeks.

Expected output: users sending logs in one click.

### 2. Write literal three-step instructions

No jargon, no choices, numbered steps with exact labels: "1. Open [app]. 2. Click [menu] then [item]. 3. Click [Export] and email me the file." Test the steps on a non-technical colleague before publishing.

Expected output: instructions a novice can follow.

### 3. Name the exact file

"I need the file called [name], from [location]." Users faced with a folder of files freeze. One file name, one location. If there are several, say which one matters most.

Expected output: the right file requested by name.

### 4. Give them the send path

Reply to the ticket with the file attached, or a secure upload link for big files. Do not make them find a new channel. Big logs get a link; small ones ride the ticket.

Expected output: the file arrives.

### 5. Confirm and close the loop

"Got it, thanks. I am looking at it now; expect an update by [time]." Users who send logs into silence stop sending logs. The confirmation is part of the collection.

Expected output: receipt confirmed, next update promised.

## Template: the request

```text
To track this down I need a log file from your app, [Name]. Easiest way:

[If one-click exists:] In [app], go to [menu] and click "Send diagnostics to support." That is it. Let me know once you have tapped it.

[If manual:] Three quick steps:
1. Open [app] and go to [exact menu path].
2. Click [Export logs / Save diagnostics].
3. Reply to this email with the file attached. It is called [filename].

Once I have it I will dig in and update you by [time]. Thanks for bearing with me.
```

## Variant phrasings

### get logs from customer

Steps 2 through 4. Literal instructions, exact file, send path.

### user cannot find log files

Step 3. Name the file and the location precisely.

### diagnostics collection support

Full sequence. Step 1 is the strategic fix.

## Why it works

The failure mode is not unwillingness; it is friction. Each unclear step ("find the logs") loses half the users. One-click removes the friction entirely; literal instructions minimize it. Naming the file removes the choice paralysis. The confirmation keeps them willing next time.

## Edge cases

- Privacy: logs may contain personal data. Say what the logs contain and get consent, especially in regulated industries.
- Huge log files: cap the request (last 3 days) or provide the upload link. Do not ask for a 2GB email attachment.
- Mobile apps: log locations are hidden. The one-click export is nearly mandatory on mobile.
- The user sends the wrong file: thank them, name the right one again, and consider whether your instructions named it clearly enough.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_sglaBKEGDuK7vzlBvuzLLg