Ask for the smallest useful support attachment

Specify the evidence that changes the decision

Start with the unresolved question. A damaged handle may require a photograph of the affected area, not the customer’s entire room. A display problem may require an error message and product version rather than a full account screenshot. Explain what the evidence will help staff determine.

Check whether the same information already exists in an approved order or service record. Do not ask customers to repeat a document submission because an agent has not looked. Where evidence is optional or an alternative exists, say so accurately rather than presenting a preferred workflow as an unavoidable requirement.

Give clear privacy-preserving framing instructions

Describe the part to capture and the unrelated details to leave out. Ask customers to avoid including other people, unrelated messages, payment-card information or account secrets. Use an approved sample image where it makes the request easier to understand. Do not ask someone to perform an unsafe action to obtain a photograph.

Treat document and identity requests as a separate approved-owner process. A support agent should not invent a requirement for a full identity document to answer an ordinary product question. If unexpected sensitive material arrives, follow the organization’s handling and escalation procedure rather than copying it into more systems.

Check the actual upload and access route

Zendesk documents separate attachment-security controls with channel-specific limits. A file sent through a support tool is not automatically private under every setting. Have the responsible administrator verify the approved route and access controls before publishing instructions that promise confidentiality.

Tell the customer how to submit the file through that route, using a verified destination. Do not redirect them to a personal inbox or public image-hosting site for convenience. Staff should follow approved malware and file-handling procedures, and avoid opening unexpected executable content or circumventing protections to inspect an attachment.

Keep the case moving when evidence is unavailable

Provide a practical alternative, such as a text description or qualified inspection, when the customer cannot safely capture or upload the requested material. Explain any real limit on what can be concluded without it. Do not invent a diagnosis merely to close the case.

Record what was requested, why it mattered and whether it answered the question. Review repeated attachment requests for unnecessary scope, inaccessible instructions and unused evidence. Retention and deletion should follow approved policy. The useful outcome is an informed decision with proportionate evidence, not a larger collection of customer files.

Make the reasoning concrete.

A fictional furniture store asks for a full-room photograph to assess a broken drawer handle. The customer’s image includes personal documents on a desk, although a close-up of the handle would have answered the question.

Rewrite the request around the damaged component and verify the approved attachment route before using it.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Question

   What decision will this attachment inform?

2. Scope

   Which exact area or field must be visible?

3. Exclusions

   What unrelated or sensitive information should be omitted?

4. Route

   Where can the customer submit it safely?

5. Alternative

   How can the case progress without this file?

Watch for the wrong conclusion.

• Requesting full documents when one narrow fact would suffice.
• Assuming all support attachments use the same access controls.
• Asking customers to bypass safety or security protections for evidence.

Sources & scope

Frameworks, worksheets and proposed tests are original editorial synthesis. Examples are hypothetical and do not report measured outcomes. Source checking is not an independent audit of effectiveness. Platform features and applicable law can change. No named human author or reviewer is claimed.

• Zendesk: Configuring attachment security →Primary provider guidance · Supports: Documents separate attachment-access controls and channel limitations. It does not make every upload private or authorize collecting unnecessary personal information.