All guides

Everyone · Step-by-step guide

Report an issue that the team can resolve

Send a clear support request with useful evidence and protect sensitive information.

4 min readWritten lessonEnglish

A reviewed tutorial in English has not been published for this lesson version. Follow the written steps below.

Before you start

  • A signed-in affiliate account for the support form.
  • A safe description of what happened, when and where.

Follow the steps

  1. Open Support

    Open the support page in your workspace. Check existing conversations before creating a second request for the same issue.

    What you should see: You can see your accessible conversations and the new-request form.

  2. Describe one issue

    Enter a specific subject and a message with the page, steps, expected result, actual result and time zone. Include the relevant offer or event reference when available.

    What you should see: An operator can reproduce or locate the issue without asking for basic context.

  3. Check visibility

    Keep account, payment and personal issues private. Never include passwords, one-time codes, API keys, private keys or unredacted identity documents in a support message.

    What you should see: The request has the intended visibility and contains only appropriate diagnostic details.

  4. Submit and follow the conversation

    Submit the form once, open the resulting thread and reply there when the team asks for more information.

    What you should see: Your request appears in the conversation list and retains the discussion in one place.

If something goes wrong

You cannot sign in to open support

Use the account recovery page or the operations contact provided with your invitation.

You accidentally included a credential

Contact operations immediately and rotate the exposed credential through its provider. Removing text alone does not secure a leaked credential.

Try it in training

Submit a private request in the training workspace with the subject 'Training: offer access check' and an explicit note that no production action is requested.

Check your understanding

What makes a useful issue report?

A specific page, repeatable steps, expected and actual results, timestamp/time zone and safe reference IDs.