Customers will usually help support teams if the request is specific and safe.

The risky version is vague: "Send us your logs." That can lead to oversized files, unrelated browsing data, sensitive tokens, screenshots of private records, and evidence pasted into the wrong channel.

Start With the Reason

Explain what the evidence will help diagnose.

Weak:

Please send logs.

Better:

Could you send a HAR file from the failed SSO login? It will help us see the redirect sequence and identify which browser request returns the 403.

Specific requests reduce overcollection.

Limit the Capture Scope

Tell the customer what to record and what not to record.

Include:

  • Exact page or workflow.
  • Where to start.
  • Where to stop.
  • Whether Preserve log is needed.
  • Whether a screenshot is enough.
  • Whether console logs are needed.

The customer should not capture unrelated browsing, other customers, other accounts, or long sessions that are not relevant.

Name the Evidence Type

Use precise names:

  • Screenshot.
  • HAR file.
  • Console log.
  • Text log.
  • Reproduction notes.
  • Timestamp and timezone.

If you need only one of these, ask for only one. If you need several, explain why.

Provide a Safe Upload Path

Do not ask customers to paste sensitive logs into public comments, chat tools, or email threads unless company policy allows it.

A safer request includes:

  • Secure upload link.
  • Expiration window if available.
  • Who can access the file.
  • What the customer should redact first.
  • Whether raw secrets are required.

If your team does not have a safe upload path, solve that before asking for sensitive evidence as a routine workflow.

Customer-Safe Request Template

Could you send a browser evidence package for the issue in this ticket?

Why we need it:
We need to compare the browser request flow against the server-side logs for the same timestamp.

Please capture only this workflow:
[specific steps]

Please include:
- Timestamp and timezone.
- Browser and operating system.
- Screenshot of the visible error.
- HAR file from the failed workflow.
- Console log only if an error appears in the browser console.

Before uploading:
- Review or sanitize cookies, tokens, emails, account IDs, and private records.
- Do not include unrelated browsing activity.
- Upload through this secure link: [secure upload link]

Internal Support Checklist

Before asking the customer:

  • Confirm server logs are not enough.
  • Decide which artifact is needed.
  • Write the exact workflow to capture.
  • Explain what the team is looking for.
  • Provide secure upload instructions.
  • Include a redaction reminder.
  • Ask for timestamp and timezone.
  • Avoid asking for raw secrets unless necessary.

FAQ

Is it okay to ask customers for logs?

Yes, when the request is necessary, specific, limited, and routed through an approved sharing process.

What should support avoid asking for?

Avoid unrelated browsing history, full desktop captures, raw secrets, broad data exports, and logs pasted into public or insecure channels.

Should customers sanitize logs themselves?

When possible, yes. Support teams should also review files according to internal data-handling policies.

What if support needs sensitive headers?

Ask exactly which headers are required, whether partial masking works, and whether server-side correlation can replace the raw value.

CTA

Redaction Retriever gives support teams a local review step for HAR files, console logs, screenshots, and notes before support bundles are shared.