Handling a referred user's complaint

When a referred user raises a complaint about fees, execution or a manager’s conduct, the first response should not be automatic defence of a commercial partner or a promise of compensation. An introducer’s role is generally to receive the concern, help identify the proper route and follow up transparently. Establish actual authority from the agreement and applicable process, not from expectations or referral income.

Record the concern without prejudging it

Identify the event, timing and requested outcome. Distinguish an account of experience, an allegation of error and an established finding. A trading loss alone does not prove misconduct; a profitable result does not make a contractual-limit breach irrelevant either.

Match the issue to the responsible party

An execution dispute may involve the host, authority or fee questions may involve the management agreement, and inaccurate referral copy may involve its publisher. Several parties may need to review different parts. Routing should not simply pass the user around. State which issue went to whom and provide a tracking reference only if one was actually issued.

Request sufficient evidence, not secrets

• A concise event description and time with timezone.
• Relevant report or instruction identifiers through an appropriate channel.
• The version of terms or content underlying the complaint.
• Relevant evidence with unnecessary third-party information removed.
• The requested outcome and necessary permission to share information with the reviewer.

Passwords, authentication codes, API keys, private keys and recovery phrases are not needed to register a complaint and must not be requested. Avoid collecting full identity or financial records without necessity and a verified secure route. Do not advertise a secure evidence-submission facility without checking that it exists.

A hypothetical referral-fee dispute

Suppose a user says a charge differs from the referral page. Retain that page version, its observation time and the fee entry, then reconcile the agreement effective at the event. The text may be outdated, there may be a misunderstanding, or a genuine discrepancy may remain. Do not promise a refund or dismiss the complaint before reviewing it.

Referral incentives must not distort handling

Disclose a relevant conflict if the partnership pays commission. Downgrading a complaint because a manager is commercially important, or promising a better ranking in exchange for resolution, is not a defensible approach. Review should follow the issue and evidence. An introducer must not claim to be the final independent authority unless that authority and independence genuinely exist.

Report status without promising outcomes

Received, referred, awaiting information and answered are different states. One party’s response does not necessarily mean resolution or user satisfaction. Communicate deadlines only where the real process defines them, with their limitations. Do not invent dates or guarantee results. Suspected unauthorised access should be directed to official host security channels without waiting for a routine review to finish.

Make closure traceable

Record the outcome, reasons, evidence reviewed and any available appeal route. Retain evidence according to necessity and actual policy, not indefinitely with universal access. Track referral-copy corrections separately so inaccurate claims do not continue. This article does not replace legal advice or formal complaint procedures.

Use the help centre for general questions and the contact and cooperation route to clarify partnership boundaries. These links promise neither complaint resolution, loss compensation nor an active implementation of every process described here.