Collect a Complete 4All Support Package

Gather reproducible, redacted evidence that support can act on without repeated questions.

Written By 4ALL.LIVE

Last updated 12 days ago

Provide exact identity, timeline, configuration, reproduction, and logs while protecting credentials and participant content.

Best for: Operators, organization administrators, and support responders.

Before you start

Access to logs, billing, or internal identifiers depends on role.

  • Use a non-production reproduction when possible.
  • Record current configuration before changes.
  • Keep an independent confidence monitor and fallback.
  • Obtain approval to share event/customer data.
  • Use an approved encrypted support channel.
  • Create a redaction copy rather than altering original evidence.

Step by step

  1. Write a one-sentence expected-versus-actual summary and severity.
  2. Include organization/team, event ID/slug, affected language/output, user role, browser/app/build, OS/device, and network type.
  3. Provide timestamps with time zone and a sequence of operator actions.
  4. Attach the last preflight result, status indicators, receiver-side evidence, and minimal reproduction.
  5. Export relevant logs from web console/desktop/XPression/Encoder only for the affected window.
  6. Include a redacted configuration: engine/model, input, captions, translation, display/share, output protocol, and receiver.
  7. List every recovery action and its result.
  8. Redact passwords, passkeys, API keys, BYOK credentials, stream keys, SRT/RIST passphrases, tokens, private URLs, billing data, and unnecessary transcript content.

What success looks like: Support can reproduce or isolate the failure without requesting basic context, and no secret is exposed.

Check your setup

  • IDs and timestamps are exact.
  • The first error is included.
  • Evidence covers both sender and receiver.
  • A reviewer confirms redaction.

Troubleshooting

  • Log too large: limit to incident window and compress through approved tooling.
  • Cannot reproduce: provide timeline and state snapshot.
  • Private content required: obtain authorization and minimize the excerpt.
  • Browser console cleared: reproduce in a non-production event if safe.

Security and operational notes

Important: Treat support packages as sensitive operational records. Restrict access and delete them according to retention policy.