THE IDEA
Here’s what you need to know.
Claude can turn receipts and order records into a structured refund audit, but it cannot automatically see every purchase or guarantee that a merchant owes you money. Give it only the evidence it needs, verify every claim against current official sources, and review each request before it is submitted.
See the visual breakdown
- 1
Collect receipts and evidence
- 2
Flag possible claims
- 3
Verify current policies
- 4
Draft each request
- 5
Review and submit
Correct order
The merchant, order number, item, date, and amount all match.
Useful evidence
Receipts, tracking, photos, and support messages support the issue.
Current source
An official policy or consumer-rights page supports the requested remedy.
Your approval
You check every detail before the request is submitted.
Set up and use Claude safely
- Open
Get started with Claude in Chrome
Anthropic's current setup guide for browser tasks from Chat, Cowork, and Claude Code.
- Open
Claude in Chrome permissions
How automatic and manual approval modes control browser actions.
- Open
Use Claude Cowork safely
Anthropic's guidance on trusted sites, sensitive data, browser risks, and review controls.
Official consumer guidance
PUT IT INTO PRACTICE
Follow the steps.
Tick off each step as you go. Your progress is saved on this browser.
- STEP 01
Gather the last six months of receipts, order confirmations, tracking updates, fault photos, price-protection evidence, and support messages. Remove passwords, full card numbers, ID documents, and unrelated private details.
Help me build a refund audit for purchases from the last six months. First, tell me which receipts, order confirmations, tracking updates, photos, price-protection evidence, and support messages you need. Do not assume you can access my orders unless I upload them or explicitly connect a relevant source. Do not ask for passwords, full payment details, ID documents, or unrelated personal information.
- STEP 02
Separate late or missing deliveries, faulty or damaged goods, incorrect items, duplicate charges, and possible price protection. A later price drop does not automatically create a refund right.
Review the order records I provide. Create a table with merchant, order number, item, purchase date, promised delivery date, actual outcome, amount paid, possible issue, evidence available, deadline, and next step. Flag late or missing deliveries, faulty or damaged goods, incorrect items, duplicate charges, and possible price-protection claims. Do not say a refund is legally owed unless a current official policy or applicable consumer-law source clearly supports it. Mark every uncertain claim for manual review.
- STEP 03
Have Claude check the merchant's official policy and an official government consumer-rights source for your location. The supported remedy may be a refund, repair, replacement, cancellation, or store credit.
For every possible claim, find the merchant's current official returns, delivery, warranty, or price-protection policy. Also find the relevant official government consumer-rights source for my location. Quote only the short clause that matters, link to the source, record when you checked it, and explain whether it supports a refund, repair, replacement, cancellation, store credit, or no clear remedy. If the policy or law is unclear, say so instead of guessing.
- STEP 04
Create one short message per order. Keep it factual, attach the right evidence, cite the source that supports the remedy, and avoid threats or exaggeration.
Write a separate refund or remedy request for each supported claim. Keep each message short, calm, and firm. Include the order number, the problem, the date, the remedy requested, the relevant policy or consumer-rights clause, the source link, and the evidence I can attach. Do not threaten, exaggerate, or claim rights the source does not establish. End by asking for a written response within a reasonable timeframe.
- STEP 05
Open Cowork and use its built-in browser or Claude in Chrome. Claude can navigate, click, type, and fill forms, but browser availability depends on your plan and settings. New sites, sensitive actions, sign-ins, and safety checks can require your approval.
Use the browser available in this Cowork session to open each merchant's official help page and prepare the supported refund requests from this chat. Match every request to the correct merchant and order. If browser use is unavailable, tell me which setting or connector is missing. Do not open unrelated tabs or enter passwords, full payment details, or ID documents into chat.
- STEP 06
Keep the process supervised. Check the merchant, order, requested remedy, attachments, and wording before each final submission. Claude may stop for logins, CAPTCHAs, site permissions, or blocked actions.
For each supported claim, fill the official form or prepare the support message using the approved draft and evidence. Stop before every final submission so I can verify the merchant, order number, requested remedy, attachments, and exact wording. If the site requires sign-in, CAPTCHA, a permission prompt, an unsupported action, or information that is not in my evidence, pause and tell me exactly what I need to do. After submission, record the date, case number, reply deadline, and confirmation link or message.
A FEW THINGS THAT HELP
Get more out of it.
- Use official merchant and government pages. Search summaries and screenshots can be outdated.
- A price drop usually depends on the merchant's price-protection policy. It is not an automatic refund everywhere.
- A faulty item may qualify for repair or replacement rather than an immediate refund, depending on the facts and local law.
- Keep browser approvals on and watch for unexpected pages, prompts, or requests for sensitive information.
- Review every request before submission. The merchant, amount, order, attachments, and remedy must match.
- Track the submission date, case number, promised response date, and result for every claim.