There are two doors, and picking the right one saves you a day. Anything the Mac app did or failed to do should be reported from inside the app — it can send its own logs, and we can't guess at them from here.
A run that stopped, a site it couldn't get into, a map that came out wrong, the app not launching — all of it lives in logs on your Mac. The app can bundle those and send them with your description in one go.
You can see exactly what gets sent before it goes.
In the same sheet, Work out what went wrong, on this Mac reads the app's log on your Mac with Claude Code and writes a short summary you can edit before anything is sent. It is often faster than waiting for us, and if it doesn't get there, send the report anyway.
Payments, receipts, your amount, a refund, a question before you install, an idea, or you can't get the app to run at all. This reaches one person, so plain English is fine.
Usually one of three things: your Mac slept, a login expired, or the AI hit a usage limit and parked itself. The app's own status line says which. Nothing is lost either way; a month survives being interrupted and picks up.
Paying happens on this site; having happens in the app. Open Revenue Magnet, click the Revenue Magnet icon in the menu bar at the top of your screen, and choose “Sign in to Revenue Magnet”. Use the same address you paid with. Check what your account holds.
Some sites can't be automated at all, and that's expected rather than broken. Tell us which one, and what you were trying to do.
Almost always the install step. This is the part we most want to hear about, so write here rather than fighting it. What it needs, and why.
Not a support issue. Tell it in the app what the payment was and it remembers, so the same one is named next month. That's what it's for.
Correct it in the app rather than telling us; corrections are kept and applied next month. Tell us only if it keeps making the same mistake after you've corrected it.