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 receipt it couldn't find, a bank it couldn't get into, a packet 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 see the exact payload before it sends, and you can veto any of it.
The same pane has Investigate with Claude Code. It opens a session with your description, the recent logs and the state of your books already loaded, and you can watch it work through the problem. Often faster than waiting for us — and if it doesn't get there, send the report anyway.
Money, invoices, VAT, 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 close survives being interrupted and picks up.
Paying happens on this site; having happens in the app. Sign in at Settings → Account with 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 — drop the file into your books folder and it carries on from there. If it's a site you think should work, tell us which one.
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 — paste their reply into the period and it goes and gets what they asked for. That's what it's for.
Correct it in the app rather than telling us — corrections are kept and applied next period. Tell us only if it keeps making the same mistake after you've corrected it.