Seller OS
What to include in a Fiverr support request
A Fiverr support request is not a place to vent; it is a form a reviewer has to act on. The faster your message lets them identify the account, the order, the problem, and the outcome you want, the fewer round trips it takes to reach an answer. Most delays come from missing identifiers, not from a difficult case.
This guide covers the fields every ticket should carry, a weak example next to a working one, the attachments worth sending, and the habits that turn one request into five. It is a drafting guide for the message itself. For the routes you can use to reach support, start with the contact guide instead.
Free plan available. Local-first data. Human review on every change.
Why your first message decides the outcome
Support is triaged, which means a reviewer scans your message before deciding whether to dig. A ticket that opens with a paragraph of frustration and buries the order number on line nine gets read slowly. A ticket that opens with the account name and the exact problem gets routed to the right queue on the first read.
You cannot speed up a review that Fiverr does not publish a timeline for, but you can remove the reasons it has to come back and ask a question. Every missing identifier is a round trip. Every round trip is time added before anyone looks at the substance of your case.
Write as if the reviewer has thirty other tickets open and has never seen your account. What would they need to resolve yours without needing to reply first?
The six fields every ticket should carry
The structure is the same whether the problem is a stuck withdrawal or a removed gig. Six fields, in this order, give a reviewer everything needed to start.
- Username and the email registered to the account: identifies you without a question.
- Order number, or gig URL, when one exists: identifies the exact transaction.
- What happened, in one or two sentences: the problem, not the backstory.
- When it happened, with dates and times: builds a timeline a reviewer can check.
- What you already tried: shows the ticket is not a first glance.
- The outcome you want: one specific ask, stated plainly.
A weak ticket next to a working one
The difference is not tone; it is whether the message can be acted on without a reply. The same problem, a held payout, reads very differently in each column below.
| Field | Weak | Working |
|---|---|---|
| Subject | HELP my payout is broken | Payout stuck: order 1234, requested 3 Sept |
| Opens with | A paragraph about your week | Username, order number, and the problem |
| Timeline | It has been forever | Requested 3 Sept, still pending 9 Sept |
| Tried | Nothing mentioned | Re-saved the payout method, same result |
| Ask | Fix this please | Release the payout or confirm why it is held |
Attachments that carry weight
A screenshot of the error, the order page, or the message thread removes a paragraph of description. Attach the smallest set that proves the point: one clean screenshot of the failure and the order or conversation it belongs to. Blurry photos of a monitor help less than a direct screenshot.
Do not attach your government ID or full document scans unless a specific flow asks for them inside the product. Identity documents belong in Fiverr's verification flow, never in a support message or an email attachment. Fiverr states in its help center that it never asks for ID by email, so treat any message that does as a phishing attempt, not a review step.
What to leave out of the ticket
Three things weaken a good case. Empty urgency with no facts adds nothing a reviewer can verify. A second ticket that repeats the first with a different claim splits the record instead of strengthening it. Anger aimed at a named person gives a reviewer a reason to focus on the tone rather than the issue.
If you already opened a ticket, add to it rather than starting again. One thread with a clear history beats three threads that each half-describe the same problem. The support ticket spam guide covers the pattern from the reviewer's side, and the order dispute guide covers cases that belong in a dispute instead of a general ticket.
Close with one ask, then wait
End the message with the single outcome you are requesting, in one sentence. If two outcomes would both be fair, name the one you want first and mention the second as a fallback, rather than leaving the reviewer to guess. A ticket that asks for three unrelated fixes will usually get an answer to none of them.
Then leave it in the queue. Send the message once, from the email registered to the account, and give it time. If the contact form itself is unreachable, the published fallback is to email support@fiverr.com from the registered address. That channel is for lockouts, appeals, and reactivation, not for a second copy of an open ticket.
Where Seller OS helps
Seller OS keeps the facts a support ticket needs in one place before you write it. Local client records hold usernames, order numbers, and notes, and the reports view turns them into a short dated summary you can copy into the message instead of reconstructing dates from memory.
The extension drafts and organizes; it does not contact Fiverr for you, and it is not affiliated with Fiverr. Nothing it stores leaves Chrome local storage, and a person still sends every message and attaches every file.
What to Include in a Fiverr Support Request questions
What should I include in a Fiverr support request?
Include your username, the email registered to the account, and, when there is one, the order number or gig URL. Then add what happened in one or two sentences, the dates it happened, what you already tried, and the single outcome you want. Attach one screenshot that shows the error, so a reviewer can act without replying first.
Can I email support@fiverr.com for any problem?
It is the published fallback for lockouts, appeals, and reactivation, sent from the email registered to the account, not a general first channel for every question. Start with the support options inside your account. If the normal contact path is unavailable because you cannot sign in, the email fallback is the documented way back in.
What makes a Fiverr support ticket take longer?
Missing identifiers, mostly. If the message does not name the account or the order, a reviewer has to ask before doing anything, and each question is a round trip. A second ticket that repeats the first with different wording splits the record and slows it further. Emotional content without dates or evidence adds length but gives nobody something to check.
Should I send screenshots with my ticket?
Yes, one or two clear screenshots of the error, the order page, or the message thread. A direct screenshot shows more than a paragraph of description, and it lets a reviewer verify the failure quickly. Keep identity documents out of support messages and email, because Fiverr states it never asks for ID by email; those belong inside the verification flow.
Write it once, make it actionable.
Give the account, the order, the dates, and one clear ask, then let the ticket work on its own.