Start with the scope and deadline

Fiverr and Upwork disputes over phone scripts are usually strongest when the written scope, delivery record, and response deadline all line up. Start inside the platform's written workflow.

A calm request for details can help. So can a specific repair offer.

Here, "phone script" can mean mobile automation code or a script used in phone calls. The proof changes with the deliverable. For software, show the device, operating system, build, and steps taken. For a call script, show the approved brief, delivered version, and revision history.

This is general U.S.-oriented information, not legal advice. Routine marketplace decisions are controlled by the order, contract, platform messages, and the platform's current process. If a notice in your account gives a different deadline, follow that notice.

An in-scope defect deserves a practical fix. A new device, integration, feature, or format may be a scope change instead. Keep those two issues separate from the first reply.

Build an evidence packet before you argue

A reviewer should be able to understand the case in a minute. Make that easy.

Use plain file names, such as 01-scope.pdf, 02-delivery.png, and 03-test-video.mp4. Avoid uploading a chaotic folder full of duplicates.

One recording that starts with the exact build, shows the device model and operating system version, repeats the buyer's stated steps, and ends on the claimed result is far more useful than ten minutes of unrelated features, even though it takes longer to make.

To be honest, a file dump can make a solid case look weak. Give each item a purpose.

Use a written resolution message, not a phone-call pitch

Don't rely on a phone conversation to carry the dispute. The published Fiverr and Upwork guidance focuses on on-platform requests, submissions, and supporting documents. If you speak with someone, send a brief recap through platform messages afterward.

You can adapt this message for the buyer or platform support:

Hello [name],

I am responding to [order or contract ID]. The agreed deliverable was [specific item] for [named device, operating system, format, or use case].

I delivered [file and version] through the platform on [date]. The reported issue is [brief description]. To reproduce it, please provide [steps taken, device model, operating system version, permissions, error log, or recording].

My attached test record, [file name], shows [result]. I can correct a confirmed in-scope defect by [date]. The requested [feature or change] was not included in the original scope, but I can provide a separate quote if needed.

Attached are the scope, delivery proof, test record, and relevant messages.

Thank you,
[name]

Keep the tone neutral. Ask for the missing technical details once, clearly, and give a realistic date for an in-scope fix.

Fiverr: act quickly on cancellation and refund requests

Fiverr's published client cancellation guidance describes short response windows. When a cancellation request is sent, the other party generally has 48 hours to accept or decline. If the recipient does not respond, the order can be canceled automatically.

A refund request is not a guaranteed refund. Fiverr's guidance says a client may contact support to request one when final delivery does not meet expectations.

If a canceled order leads to an approved refund, Fiverr says returns to a card or PayPal often complete within 10 days after Fiverr processes them, although the payment provider can affect timing. See Fiverr's refund timing guidance. That is a money-return timeframe, not a promise that a dispute will be decided within 10 days.

These client-facing pages also do not establish a universal seller appeal deadline, payout rule, or guaranteed outcome. Read the actual notice in your Fiverr account and preserve every message tied to the order.

Upwork: fixed-price milestones have their own clock

Use these time frames only for fixed-price work. Do not apply them to hourly contracts without checking the contract's current terms.

Under Upwork's fixed-price milestone guidance, a client has 14 days after submitted work to approve it or request changes. If the client sends a refund request, the freelancer generally has seven days to dispute it.

After funds are released, Upwork says they go through a five-day security hold before withdrawal. That hold concerns withdrawal availability. It does not decide who is right in a quality dispute.

If a fixed-price refund request arrives, follow this workflow:

1. Save the notification and note the response deadline.
2. Compare the request with the funded milestone, not with later informal expectations.
3. Reply with a short explanation of how the submitted work meets the stated requirements.
4. Attach the scope, submitted files, delivery date, test evidence, and relevant messages.
5. Try to resolve the issue directly if a sensible repair or limited agreement is available.

Upwork's milestone dispute instructions recommend trying to work things out first. They also tell freelancers to describe the milestone agreement, explain how they met it, and attach supporting documents. Treat the initial evidence submission seriously.

Match the remedy to the actual problem

A reproducible defect within scope. Offer a defined repair. Name the version, deadline, and what the buyer needs to test.

A new requirement. Explain that it was not in the original scope. Offer a paid change, a new milestone, or a limited goodwill adjustment if that makes business sense.

A missed core requirement. A prompt partial resolution or cancellation may be less damaging than arguing over an obvious gap. Put the terms in writing.

Turns out, vague promises create more disputes. "I will fix everything" invites an endless revision cycle. "I will correct the login error shown in your recording for the agreed Android version" is much safer.

Don't promise a result on an untested device or a third-party service you do not control.

Treat source-code ownership as a separate question

Source-code arguments can derail an otherwise simple delivery dispute. Keep the discussion tied to the written agreement.

The record should say whether the buyer receives source files, compiled files, a license to use the work, an ownership transfer, or some combination of those items. If it does not, don't tell platform support that ownership is automatic for either side.

A payment dispute and an intellectual-property dispute may overlap, but they are not identical. For the platform case, show what the listing or milestone promised. If the matter involves a high-value ownership transfer, alleged copying, or a legal demand, get advice from a qualified attorney rather than treating marketplace support as a copyright court.

What weakens an otherwise good case

Thing is, reviewers cannot fix missing records. These mistakes make the job harder:

• Waiting until the response window is nearly over.
• Deleting or editing platform messages after a disagreement starts.
• Sending a test video without identifying the version, device, or steps.
• Making broad accusations instead of describing the failed requirement.
• Moving the whole discussion into undocumented calls or off-platform messages.

Keep the original delivered file. Keep the version you later repaired too. The difference may matter.

If you bought the phone script

Buyers should use the same disciplined approach. State the expected result, the actual result, the device or environment used, and the exact steps that produced the issue.

On Fiverr, the published client guidance says a buyer can contact Customer Support to request a refund within 14 days of order completion if final delivery does not meet expectations. On Upwork fixed-price work, request changes within the applicable review period and keep the discussion tied to the funded milestone.

A marketplace cancellation or refund is different from a credit-card billing dispute. Use the platform process first when the problem is about the marketplace order, delivery, or revision. It creates the clearest record for both sides.

Common questions

Is a phone call required for a Fiverr or Upwork dispute?

Do not count on a phone call. The official help pages cited here describe written platform workflows and document uploads. Put your position, evidence list, and proposed remedy in platform messages.

How much time does an Upwork fixed-price client have to request changes?

Upwork says the client has 14 days after work is submitted to approve it or request changes. A freelancer generally has seven days to dispute a client refund request.

Does the buyer automatically receive source code?

No automatic answer can be assumed from the order title alone. Check the gig, proposal, milestone, messages, and delivered files for the actual promise about source files and usage rights.

Before replying, create one dated folder for the order or contract. Put the scope, delivery proof, test record, and relevant messages in order, then send the short written response before the platform timer expires.