Mission
Handling disputes on delivered work on Mission: a practical guide
When gig contracts fail at delivery, platform dispute mechanisms must substitute verifiable proof for emotion.
A contractor finishes fitting a custom oak door frame in a Lyon apartment, taps "Mark Complete" on his phone, and expects a €340 release from escrow. Twenty minutes later, the client turns the handle, finds a five-millimeter gap where the latch should catch, and taps "Report Issue." The funds freeze instantly. No money transfers to the contractor, and no refund reverts to the client. Both parties enter the Mission dispute lifecycle.
Disputes on service marketplaces are rarely born from deliberate fraud. They are born from mismatched expectations, vague scopes, and the friction of physical execution. On WEVONE’s Mission universe, resolving these failures requires moving past he-said-she-said rhetoric into objective, verifiable protocol.
The Escrow Lock and the Dispute Window
Every agreed job on Mission initiates a binding transactional escrow. The buyer deposits 100 percent of the agreed fee upon contract acceptance. These funds are held in an isolated ledger account managed under European payment directive compliance (PSD2).
When a provider marks a service as delivered, a strict 48-hour inspection window opens. During this timeframe, two outcomes are possible:
- Explicit or Implicit Approval: The buyer reviews the work and clicks "Confirm Completion," releasing escrowed funds minus platform protocol fees immediately to the provider's wallet. If the buyer takes no action within 48 hours and files no report, the platform automatically triggers fund release.
- Dispute Initiation: The buyer taps "Report Issue," selecting a core reason (Incomplete Delivery, Quality Defect, Damage to Property, Unresponsive Provider). The auto-release timer halts instantly.
Money remains frozen until both parties settle or platform arbitration issues a binding determination. Neither the provider nor the buyer can unilaterally withdraw escrowed capital once a dispute opens.
The Evidence Engine: Context Over Claims
Platform disputes are resolved on evidence, not arguments. When a dispute is logged, Mia—WEVONE's underlying AI architecture—compiles the job’s digital context trace into an evidence docket. Mia does not act as an unchallengeable judge; she acts as an automated clerk that aggregates objective metadata before human intervention or algorithmic settlement occurs.
The system evaluates five specific data inputs:
- Initial Scope Parameters: The exact text, attachments, and milestones agreed upon in the accepted job proposal.
- In-App Communication: Time-stamped chat messages, voice notes, and image attachments exchanged strictly within the WEVONE messaging container.
- Location and Time Logs: Geofenced check-in and check-out timestamps recorded when the provider arrived at and departed from the service site.
- Delivery Deliverables: High-resolution photos or video proof submitted by the provider at the exact moment of tapping "Mark Complete."
- Buyer Proof of Defect: Photo or video evidence uploaded by the buyer within the 48-hour window illustrating the gap between agreed scope and actual output.
Communications conducted outside WEVONE—via private SMS, WhatsApp, or verbal conversations—are explicitly excluded from the evidence docket. If a requirement was discussed verbally on site but never written into the WEVONE job thread, the platform legally treats it as nonexistent.
Worked Example: The €250 Cabinet Assembly Dispute
To understand the resolution path, consider a concrete dispute logged in Munich:
- Scope: Assembly of three flat-pack wardrobe units and wall anchoring for a €250 flat fee.
- The Trigger: Provider marks complete at 16:00. Buyer files a dispute at 17:30, uploading photos showing two wardrobes assembled, but the third unit partially unboxed on the floor, accompanied by scratched floorboards.
- Provider Claim: "The buyer lacked necessary wall hardware for unit three. I waited 45 minutes, then had to leave for my next job. Floor scratches were pre-existing."
- Buyer Claim: "The provider did not inform me about missing screws and abandoned the job unfinished, damaging my hardwood parquet."
The Resolution Path
First, Mia checks the chat history. The logs show the provider sent a message at 15:15 stating, "Wall plugs missing for unit three. I cannot anchor this safely." The buyer replied at 15:20, "Just leave it then, I will buy them later." However, no formal milestone modification was submitted to alter the payment terms.
Second, Mia analyzes the high-resolution site check-in photos submitted by the provider upon arrival against the photo submitted at exit. Metadata confirms the floor scratch appears only in the exit photo.
Mia proposes a structured settlement based on historic platform resolution matrices:
- Escrow Split: €170 released to the provider (reflecting 68% completion based on labor units), €80 refunded to the buyer for the unfinished unit.
- Damage Claim: The floor scratch is flagged as an auxiliary property damage claim. Because WEVONE includes integrated task liability insurance on verified Mission jobs, a separate insurance workflow opens for the €120 floor repair, avoiding a drawn-out civil stalemate between user accounts.
Both parties receive this proposed split. If accepted, funds distribute in milliseconds. If rejected by either party within 24 hours, the docket escalates to WEVONE’s human Trust & Safety arbitration team.
Mia Triage and Escalation Thresholds
Mia processes initial dispute dockets using deterministic rule logic rather than opaque generative scoring. The system categorizes disputes into three actionable tiers:
- Tier 1 (Micro-Discrepancies): Disputes involving <€100 where objective proof (e.g., photo evidence of missing item) is clear. Mia suggests automated refund/payout splits based on contract milestones. Acceptance rates for Tier 1 automated suggestions currently sit at 78% across active test markets.
- Tier 2 (Substantive Disagreements): Disputes between €100 and €1,000 involving conflicting claims or partial completion. Mia structures the case file, flags contradictions in chat logs, and queues the docket for human staff review.
- Tier 3 (High-Value or Property Damage): Any contract exceeding €1,000 or involving physical damage claims. Immediately assigned to a senior human operations manager, with Mia providing background fraud analysis and identity verification cross-checks.
Platform Limitations and Structural Edge Cases
The dispute architecture is designed for clarity, but it is not infallible. Two significant operational limitations exist today:
Subjective Quality Standards
While missing hardware or unpainted walls are binary facts, "poor craftsmanship" is inherently subjective. If a provider paints a wall cleanly, but the buyer argues the finish lacks "depth," algorithmic evaluation breaks down. Currently, subjective quality disputes require human review, leading to resolution timelines stretching from 48 hours to 5 business days.
Off-Platform Leakage
When users arrange contract changes verbally on site—such as asking a gardener to trim an extra hedge for cash—the platform loses data visibility. If a dispute subsequently arises regarding that unrecorded work, WEVONE enforces a strict rule: escrow covers only what is written in the digital contract. The platform will not penalize or reimburse for off-platform side deals.
Impact on the Contribution and Trust Score
Filing or receiving a dispute does not automatically trigger account penalties. WEVONE distinguishes between operational friction and malicious behavior.
A provider who experiences a dispute but cooperates fully with evidence requests and accepts fair partial settlements sees minimal impact on their WEVONE Trust Score. However, repeated patterns—such as a provider generating incomplete delivery flags on more than 5% of their total completed jobs—trigger an automated adjustment to their search ranking in the Mission marketplace.
Conversely, buyers who systematically abuse the dispute mechanism to extract forced discounts after work is completed are flagged by Mia’s anomaly detection engines. Accounts demonstrating habitual dispute patterns without photographic evidence face elevated verification checks and, ultimately, temporary or permanent suspension of their escrow privileges.
By tying monetary release directly to contextual proof, Mission transforms disputes from toxic arguments into structured, audit-ready procedures.