Sorare customer care — verified contact channels

Verified channels

What the desk does not recommend

The desk does not recommend contacting Sorare through unofficial Telegram groups, third-party Discord servers or social-media DMs. These channels are not operated by Sorare SAS and cannot resolve account-specific issues.

How to write a useful support request

1. Include your account email

   The support team needs the email associated with your Sorare account to look up your records.

2. Describe the issue in detail

   Include screenshots where they help. Note the timestamp of the issue in your local timezone.

3. List what you have already tried

   The team can skip steps you have already completed. This shortens the resolution path.

Sign in to file a request Journal contact page

Support case preparation: the questions that matter

Sorare Journal approaches how managers can document an account, card or contest problem. The starting point is evidence rather than promotion. Rules can change, card utility can move with competition design, and football availability can change close to a deadline. Managers should therefore compare the current official interface and published terms with their own account status before acting.

The desk records timestamps, transaction references, screenshots and safe communication. None of those signals deserves to be read alone. A promising player may have uncertain minutes; a scarce card may have limited contest utility; an apparently simple account action may carry wallet or record-keeping consequences. The editorial aim is to expose those trade-offs without converting uncertain information into a confident forecast.

A practical review sequence

1. Confirm the source

   Open the official product or account interface directly. Check the domain, publication context and effective wording. Search snippets, social posts and screenshots can be stale or incomplete.

2. Record the conditions

   Write down eligibility, deadline, card scarcity, competition, region and account requirements that apply. A decision log prevents memory from changing after an outcome is known.

3. Test the downside

   Ask what happens if a player misses the fixture, a transaction is delayed, a promotion does not qualify or a support review takes longer than hoped. Do not commit money needed elsewhere.

4. Verify before submission

   Recheck the final screen and retain relevant confirmations. For market activity, verify the player, season, scarcity and price denomination before bidding or listing.

What to read next

Continue with Login for the closest operational topic. Then review Wallet Kyc for a second perspective and Contact for the relevant account, rules or strategy context. Together they form a clearer decision trail than any isolated claim.

What each channel actually handles

The in-app help channel (Sorare app → Profile → Help) is the fastest path for account, KYC, wallet and payment queries. The help desk routes the request to the appropriate team based on the tags you select. Most in-app help requests receive a first response inside 24 hours and a resolution inside three business days.

The help center (sorare.com/help) is the self-serve article library. It covers the most common questions on account access, KYC verification, wallet operations, card trading and tournament entry. Most articles include screenshots and step-by-step instructions. The help center is available 24/7.

Email ([email protected]) is the right channel for documented requests that need a paper trail — refund requests, formal disputes, requests for account statements. Email requests typically receive a first response inside 1-3 business days. Complex requests may require additional documentation and take longer to resolve.

The X (Twitter) channel

The @sorarehq account is the right channel for public escalation and outage reports. Posting publicly surfaces the issue to the wider community and tends to accelerate response times during outages. The account is monitored during business hours; weekend response times are slower.

Common issues and their typical resolution

Account access issues (password reset, 2FA lockout) typically resolve inside one business day. KYC re-verification issues typically resolve inside twelve hours once the correct documents are submitted. Withdrawal delays triggered by sanctions or verification holds typically resolve inside three business days. Auction disputes typically require manual review by the auction desk and can take up to seven business days.

Operational checks before and after a decision

For support escalation, the desk recommends maintaining a dated record rather than relying on recollection. Record the question being answered, the official wording available at the time, the account or competition context, and any assumptions that remain unresolved. That discipline matters because a later outcome can make an uncertain choice look obvious. Contemporary notes preserve what a manager could reasonably know before acting.

A useful distinction in support escalation is the difference between access, eligibility and value. Access means a feature or route is available. Eligibility means the account, card or lineup satisfies the current conditions. Value is personal and depends on budget, alternatives and risk tolerance. One does not prove another. A visible option may be ineligible, while an eligible action may still be a poor fit for the manager.

Football context also changes the interpretation of support escalation. Fixtures move, players rotate, injuries emerge and competition calendars overlap. Managers should avoid treating a previous matchday as a permanent template. Recheck official football information and product rules close to the relevant deadline, while allowing enough time to avoid rushed wallet, market or account decisions.

Cost should be measured beyond the headline amount. With support escalation, consider transaction charges, currency conversion, time spent monitoring, resale uncertainty and the opportunity cost of holding a card that does not serve the intended contest. The cheapest apparent option is not automatically the least expensive over a season. The desk favours explicit limits and comparisons made in one consistent denomination.

Account security is part of support escalation, not a separate administrative chore. Navigate through a saved official address, inspect unexpected prompts, protect email access and store recovery information away from ordinary chat or cloud notes. Legitimate support should not need a password or secret recovery phrase. If a request feels unusual, stop and reopen the official support route independently.

Editorial independence requires a boundary between explanation and endorsement. Sorare Journal may describe support escalation, link to related resources and identify questions worth asking. It cannot see private account records, guarantee platform decisions or promise future card demand. Commercial links are disclosed, and readers remain responsible for checking the live terms before committing money or personal information.

After any significant action involving support escalation, run a short review. Confirm what happened, compare it with the expected process, save non-sensitive evidence and note any unresolved issue. If support is needed, provide a chronological summary rather than a long speculative message. Clear records make errors easier to identify and reduce the chance of exposing information that is irrelevant to the case.