Ask the support assistant a question it can help clarify
Choose one question for the first message
The support assistant is a starting point for understanding ADJODO workflows. A focused question about campaign creation, tracking or the payout process gives the conversation a clearer direction than a long message covering unrelated issues. Explain what you are trying to do and where you became uncertain.
You can use the suggested questions as an introduction, but adapt the wording to your situation. If a reply addresses a different step, say which part you meant. The purpose of the conversation is to help identify the next useful action rather than to turn every topic into a generic explanation.
Distinguish general guidance from an account decision
A description of how campaign review works is different from an approval for your specific campaign. Similarly, an explanation of withdrawals cannot establish that a particular balance is ready to pay. Account-specific questions require the appropriate authenticated context and may need the responsible team to review the record.
Avoid treating a general reply as an instruction to change commercial terms or as confirmation that a financial action has completed. Ask which account page or support route can verify the relevant status. Keeping this distinction clear makes the assistant useful without replacing the underlying account process.
Describe the sequence rather than guessing the cause
When something does not work as expected, explain the step you took, the result you expected and the result you observed. Include the page or feature involved and any visible error wording that does not contain sensitive information. A statement such as 'the link opened but the expected event is missing' gives more context than an unsupported claim about the cause.
If the problem changed after another action, mention that change. The conversation can then narrow the investigation instead of repeatedly discussing a cause that has not been established.
Keep private information out of ordinary messages
A useful support description does not require passwords, one-time codes, payment credentials or an API secret. Do not paste those values into the chat. If a screenshot helps explain the issue, remove details unrelated to the question before sharing it through an appropriate support route.
Campaign or record references can be supplied when they are needed to identify the issue in the authorized account context. For a public explanation, a redacted example is usually enough to discuss a format or a workflow. The goal is to preserve useful technical context without turning the conversation into a store of private credentials.
Use follow-up questions to confirm understanding
After receiving guidance, restate the step you intend to take and clarify any condition that remains unclear. If the response does not match the actual screen, explain the difference rather than trying to force the interface to fit the description. A support conversation should help you make a justified next move.
It should not encourage repeated submissions when the first attempt may already have created a record. For unresolved issues that need a person to inspect the account or a commercial arrangement, continue through the direct team support channel with the relevant context from the conversation.
Choose the right conversation for the job
This page and the direct live-chat page serve different purposes. Use the assistant for an initial explanation, and use the team conversation when the matter requires a human reply or a review of the submitted details. Keeping the two routes distinct helps you understand who needs to answer and what evidence they will need.