Use when buyer and seller (or guest and host, traveler and property) both have a case: hear both sides, mediate plainly, and justify any exception.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this when buyer and seller (or guest and host, traveler and property) both have a case. Hear both sides, mediate plainly, and justify any exception.
Both sides' records — orders, messages, photos, timestamps — the marketplace policy passage for this dispute type, the payment and fee history, and the escrow or hold state of the money.
Item not received, not as described, damaged, cancelled late, a no-show, a fee or payout question, or conduct. Each type has its own policy passage and its own evidence standard; a case that fits none goes to the owner rather than a made-up rule.
What each claims, what the evidence confirms — timestamps, photos, tracking, the platform messages — and what stays UNKNOWN. Weigh evidence the platform saw over evidence one side describes. Never share one side's private details, messages, or identity with the other, and never take a side in the tone of a message.
Name the outcome the policy gives and the evidence that decides it. Partial remedies are normal: a partial refund for a partial failure, a fee waived without a payout reversed. An exception from the passage needs its reason written and stays inside the approval limit; past it, or where both sides have a plausible case the evidence cannot settle, the packet goes to the senior or legal path, not to a guess.
Each side gets its own draft: the decision, the evidence it rests on, the next step with a date and an owner, and how to appeal. Plain, neutral, no blame. Both stay staged for the owner's yes, and money moves — refunds, payouts, holds, fee waivers — only after that yes.
The dispute read with the policy citation, the ruling with its evidence, and the per-side drafts. No payouts, waivers, holds, or exceptions without the owner's yes.
Thin records mean a narrower ruling, not invented facts. Say which record — a photo, a tracking scan, a message — would settle each UNKNOWN, and ask the side that would have it.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.