Start a team conversation with enough context to help
Introduce yourself with a reachable contact
The live-chat entry form asks for your name and contact number so the team can understand who is requesting help. Enter the number in a form that includes the appropriate country code and check it before starting. This public conversation does not require an account or an OTP, as shown beside the form.
That makes it useful for an initial inquiry, but it is not a substitute for authenticated account actions. If your question concerns an existing account, identify the type of issue without posting credentials into the conversation.
Explain what you need in the opening message
A short, specific opening message helps the team decide how to respond. State whether you need advertiser onboarding, publisher information, a website-development discussion or help understanding a page. Include the outcome you are trying to achieve and the step at which you need assistance.
For an operating issue, describe what happened before giving your theory about the cause. If the topic involves an existing request, provide its reference when appropriate. Avoid sending several identical messages simply because a reply has not appeared immediately; a clear initial description is easier to investigate.
Use the conversation as a record of clarification
A chat thread is useful when each reply connects to the preceding question. Answer a request for clarification directly and distinguish a newly added requirement from the original one. If a campaign date or a proposed service scope changes during the discussion, make that change explicit.
Important commercial decisions may need a separate reviewed record rather than being inferred from casual wording. Keep a note of the relevant reference and the final next step. This makes later follow-up more precise and reduces the chance that two different arrangements are treated as the same request.
Share relevant evidence with care
For a website issue, the page address, the action attempted and the visible error are often the most useful starting evidence. For a campaign question, the relevant campaign reference and measurement step may be more helpful. Remove passwords, payment credentials, OTPs and private integration values from anything you share.
A large customer spreadsheet is not a suitable first message for a routine inquiry. Provide the minimum context needed to understand the problem, then follow the appropriate process if the team requires additional documentation. Evidence should make the issue clearer rather than introduce unrelated information.
Understand what the chat screen confirms
Starting a conversation confirms that the chat route has accepted the entry details and opened the thread. It does not itself confirm campaign approval, contract activation, payment completion or a booked appointment. Those outcomes belong to their own review or transaction processes.
Ask the team which reference or account screen will show the authoritative result. If you receive an error while starting the chat, check the visible message and correct the relevant field before retrying. If a conversation is restored in the same browser, continue with the existing context instead of assuming a new blank thread is required.
Follow up with the unresolved point
When returning to a discussion, state what remains unanswered and whether you have already completed the suggested action. A brief update such as the page tested and the result observed helps the next reply move forward. Keep the follow-up tied to the issue until it is resolved; open a clearly identified new topic when the requirement changes.