Buyer used AI on my Fiverr delivery? What to do

Spot the AI-generated revision pattern

AI revision notes share telltale markers. They use generic improvement labels ('enhance readability,' 'optimize structure,' 'elevate tone') without quoting a specific sentence. They often contradict: 'shorten the introduction' followed by 'add more context to the introduction.' They reference sections, data points, or formatting that do not exist in your delivery — hallucinated citations. They never say 'change X to Y on line 12'; they say 'consider improving the overall impact.'

Human feedback, by contrast, quotes your text, names the exact requirement from the brief that is unmet, and proposes a concrete change. If the buyer's note has zero quotes from your delivery, zero references to the original requirements, and three or more generic labels, treat it as likely AI-generated.

The clarifying-question script

Do not guess. Reply once with a structured question that forces the buyer to be specific. Template: 'Thanks for the notes. To make sure I address exactly what you need, could you point to the specific sentence or section in the delivery that should change, and quote the brief requirement it relates to? For example: "On page 2, paragraph 3, the brief asked for X but the delivery says Y." This lets me revise precisely and avoid rounds of back-and-forth.'

This script does three things: it signals you are ready to revise, it defines the evidence standard (quote + brief reference), and it creates a record. If the buyer replies with specifics, you have a real revision. If they ghost or repeat generic labels, you have evidence the revision request is not scoped to the brief.

Revisions cover the brief, not AI taste

Fiverr's help center states that the number of revisions a client can request depends on what is included in your gig package or agreed-upon order scope. Revisions are for aligning the delivery with the agreed scope — not for satisfying an algorithm's style preferences. If the buyer's AI tool prefers active voice but the brief did not specify voice, that is not a revision; it is a new preference.

Illustrative example: The brief asks for 'a 1,000-word blog post on topic X in friendly tone.' You deliver 1,000 words on topic X in friendly tone. The AI revision says 'use more authoritative tone' and 'add three statistics.' Neither was in the brief. You are not obligated to revise for either. Reply with the clarifying script; if the buyer cannot quote a brief requirement, the revision is out of scope.

When to hold the line on revisions

You have delivered to the brief. The buyer sends AI-generated notes. You send the clarifying script. The buyer either ignores it, repeats generic labels, or admits they 'just want it better.' At this point, you have two paths. If you have revisions remaining in the package, you can make one small, good-faith edit (e.g., tighten three sentences) and redeliver with a note: 'Adjusted per your note on flow. The brief did not specify tone; I kept the friendly tone as agreed. Let me know if a specific brief requirement is unmet.' This shows willingness without accepting scope drift.

If you have zero revisions left, or the buyer demands changes that would require a new order, reply: 'I have delivered to the agreed brief. The revision notes do not reference a specific brief requirement. Per our package, revisions cover the brief scope. If you need work beyond the brief, I can send a custom offer for the additional scope.' Fiverr's custom offer system lets you price the extra work cleanly.

When to use the Resolution Center

Open the Resolution Center when the buyer refuses to accept a delivery that meets the brief, demands out-of-scope work as a revision, or threatens a negative review unless you comply. Fiverr's Resolution Center handles order-related requests without Customer Support. Seller options: Extend delivery date, Offer partial refund, Cancel order. A partial refund (up to 60% of order value, minimum $5, order over $50) can close a stuck order without affecting your metrics if accepted. A mutual cancellation protects your Order Completion Rate if the buyer accepts or auto-accepts after 48 hours.

Do not open a dispute for a single AI revision round. Use the clarifying script first. Escalate only when the buyer makes it clear they will not accept a brief-compliant delivery. Keep your Resolution Center message factual: 'Delivery meets all brief requirements [list]. Revision notes reference no brief requirement. Buyer requests out-of-scope changes. Requesting mutual cancellation.'

Prevention: brief clarity reduces AI noise

You cannot stop buyers from running your work through AI, but you can make the brief unambiguous so AI tools have fewer gaps to hallucinate. In your gig requirements, ask for: target audience, required sections with headings, word count per section, tone keywords (friendly, authoritative, clinical), must-include facts or data points, and format (Markdown, Word, Google Doc). The more constrained the brief, the less room for 'make it better' to mean anything.

A common mistake sellers make is accepting vague briefs ('write a good article about X') because they want the order. Vague briefs invite AI revision loops. Require the buyer to fill a structured requirements form before you start. If they refuse, send a custom offer with a detailed scope attachment and confirm acceptance before work begins.

Where Seller OS helps

Seller OS inbox assistant drafts the clarifying script and the scope-holding reply, pulling the original requirements from the order page so you can quote them exactly. The gig optimizer reviews your requirements form and flags vague fields that invite AI revision noise. Local client records track buyers who have used AI revision patterns before, so you can pre-empt with a stricter requirements form on the next order.

It cannot prevent buyers from using AI tools, cannot force a buyer to quote the brief, and cannot auto-accept or reject revisions. Every redelivery and Resolution Center action remains yours.

Related guides