Start with the exact notice in your account. A request for identity verification, a security problem and a policy restriction can require different responses. No outside blog can diagnose your account from the fact that access changed.
Preserve the notice before responding
Save the wording, time, case reference, requested action and deadline privately. Open the platform directly through its official site or app and navigate to support. Do not use an unsolicited recovery link as your sign-in route.
| Record | Why it helps |
|---|---|
| Exact notice | Prevents a response to an issue the platform did not state |
| Dated event sequence | Shows what happened and in which order |
| Action already taken | Avoids contradictory or repeated submissions |
| Unresolved question | Gives support a specific point to clarify |
| Requested evidence | Keeps the submission relevant and limited |
Download the support-timeline template. Keep identity documents and client information out of public posts.
Write a factual note instead of a guessed explanation
Weak example: “Your algorithm banned me because I changed Wi-Fi. Restore me immediately.” The cause has not been established and the actual notice is missing.
Better fictional example: “On 18 October, my account displayed a request to complete identity verification. I submitted the requested information through the account page on 19 October. The request still shows pending. Case reference: my actual case number. Please confirm whether another action is required and the official place to complete it.”
Replace every date and statement with your real record. This is a communication template, not a tested appeal or a guarantee of restoration.
Keep platform rules separate
Use Upwork Help for an Upwork notice and Fiverr Help for a Fiverr notice. Follow the specific account instructions. Do not assume a rule about verification, account creation or payment on one platform also applies to the other.
Do not create another account to evade a restriction or submit invented documents. If the notice does not explain the issue, ask for clarification through the existing case or the provider's stated process. Sending the same incomplete message repeatedly does not add evidence.
Protect work already in progress
Keep permitted records of scope, approvals, deliverables and deadlines. Continue communication through approved channels while available. Ask official support how an active order should be handled if access is limited. Do not move payment elsewhere simply to bypass the restriction.
If an account may be compromised, use the provider's official security process and secure the associated email account. Review payout details, sessions and connected applications where the account allows it. Do not pay a stranger who claims they can influence a review or give them passwords, one-time codes or remote access.
After the issue is resolved
Record the confirmed cause if the provider gives one, the action taken and any remaining condition. Change the workflow that actually caused a problem rather than relying on unrelated rumours. Keep an authorised copy of essential project records so a single login is not your only access to delivery history.
There is no universal review timetable or guaranteed outcome in this guide. Use the deadline and instructions in your own notice, and distinguish confirmed information from anything you still do not know.
Practice work and illustrative amounts are labelled in the article. See how we prepare and correct guides and how the resource checks work. Report a specific error or broken step.