Get Luminair ↑
A store owner handling a customer dispute

Bring the whole story to a customer dispute.

A customer disputes an order and the story is split across the order, emails and shipping proof. Luminair puts it in date order and drafts a reply that sticks to what you can prove.

Disputes3 apps connected

A customer disputed order 4821. Here is the order, our emails with them, the shipping proof and our notes. Put everything in date order, mark what we can prove and what we cannot, and draft a factual reply.

The orderCustomer emailsShipping proofYour notes
  1. Claudeputs every event in date order
  2. Geminilooks for anything that contradicts our side
  3. Codexbuilds the evidence pack with page references
You get

Dispute #4821 pack

  • Chronology: 6 events, 2 with direct evidence attached
  • Missing: delivery photo, flagged as a gap not assumed
  • Response draft ready for review
How this job looks in a Luminair session. Illustration with sample content.
The problem

A chargeback lands with a claim that contradicts what your own records show. The real story is split across the order, a week of email back-and-forth, and a shipping confirmation you have to dig up separately.

Try it yourself in Luminair

Six steps. No setup beyond the AI plan you already have.

  1. 1

    Install Luminair and sign in

    Download Luminair and open it. Go to Settings → Models → Add account and sign in with an AI plan you already pay for, like Claude, ChatGPT or Gemini.

  2. 2

    Make a folder for this job

    In the sidebar, choose New folder… and name it “Disputes”. Then choose New session in this folder. Everything for this job stays together.

  3. 3

    Bring the information in

    You need: the order, customer emails, shipping proof and your notes. Connect Gmail, WooCommerce and Trello in Settings → Connectors, or export the files and drag them into the chat.

  4. 4

    Ask for the result

    Paste this into the session, or say it in your own words:

    A customer disputed order 4821. Here is the order, our emails with them, the shipping proof and our notes. Put everything in date order, mark what we can prove and what we cannot, and draft a factual reply.
  5. 5

    Get a second opinion

    Pick a different model in the model picker and ask it to check the first answer:

    Read this timeline as the customer's bank would. What is not proven, and what contradicts us?
  6. 6

    Make it repeat

    Open Flows → New and add the steps: Read new messages on the order → Update the timeline → Flag anything that contradicts it. Choose when it runs, like every Monday at 09:00. Nothing is sent or changed until you approve it.

How it plays out

Collect the originals

Make a folder for the dispute. Connect WooCommerce and Gmail in Settings → Connectors, or drop in the order, the emails and the shipping proof.

Get the timeline and a factual reply

Ask for every event in date order, each marked as proven or not, and a reply that only states what you can show. Missing proof is listed as missing, never filled in.

Check every statement before you submit

Ask a second model to read it as the other side would. You check each line against its source before sending it.

You stay in charge

Nothing here manufactures a missing fact or promises an outcome. You confirm every statement before it is submitted.

The next dispute starts from a template, not from a blank evening.

Sign in with the AI plan you already have and start with this job.

Download Luminair