An entry point for every file.

Start with the right reference

For an existing order, provide its reference and the step concerned: configuration, settlement, preparation, or document. Describe the expected result and what appears on screen. If the problem depends on a specific moment, add the time and the actions already taken. This information avoids having to reconstruct the situation from several incomplete messages.

To choose a GPU, specify the software, the expected duration, the observed memory, and how the work is distributed. A question like "this process uses a single card and exceeds its current memory" gives a more useful starting point than a general request for power.

Share context without exposing credentials

A description can explain an error without containing your work data. Copy only the elements needed for diagnosis and remove secrets from error messages. No password, private key, or access code is useful in this form. For payment, start from the order and the status shown in its tracking.

Find your request in your account

After signing in, the form saves a support ticket linked to your Capordia account. You can review it from the Support section, including on another browser once you sign in to the same account. The request keeps its subject and content so it remains understandable when you return to the project. To prepare a complete configuration, the scoping document lets you gather the requirements upfront.