Prepare an effective support request

Capture the context

Identify the module, version, deployment and affected workflow. Describe expected and actual results, impact and relevant times with a timezone. Include repeatable steps and any workaround already attempted.

Choose the conversation visibility

Use a private or organization-shared conversation as appropriate. Approved organization members may see a shared conversation. Internal staff notes have a separate access boundary.

Minimize the evidence

Redact secrets and unnecessary personal data from logs and screenshots. Never include a password, private key or authentication code. Agree an appropriate secure transfer route before sharing sensitive evidence.

Keep one conversation

Reply in the existing ticket when possible so the evidence and status remain together. Support scope and any response commitments follow your agreement; the website does not create a universal service-level commitment.