Support
One address, and one person reads it. There is no ticket queue to be routed through and no bot in front of it.
That covers all of it: a bug, a feature request, a billing or refund question, a privacy request, or a security disclosure.
What to include
Section titled “What to include”Nothing formal. But these save a round trip:
- A bug — what you did, what happened, and what you expected instead. The recipe name helps; a screenshot of the vitals rail helps more.
- A number that looks wrong — open the explain popover behind it (every headline figure in the vitals rail has one) and say what it reported. It names the formula that produced the number, which usually resolves the question immediately. The calculator reference may resolve it before you write at all.
- A billing question — email from the address on the account, or say which address it is. A Paddle receipt number helps but is not required.
- A refund — say what you want refunded. The refunds policy is the shorter read.
Things you can answer yourself
Section titled “Things you can answer yourself”- Your subscription, card, invoices or cancelling — Settings → Account → Plan → Manage billing opens Paddle’s portal, which owns all of that. See Plans, billing and trial codes.
- “Why is my FG so high?” and questions of that shape — the assistant reads your actual recipe and runs the actual engine. ⌘J.
- “Where did my recipes go?” — check the sync indicator in the sidebar first. Guest means the workspace on this device is not the one on your account. Offline explains all five states.
What is coming
Section titled “What is coming”Support is moving into the app: a Support section in Settings where you pick a category and write a message, and the reply continues in the same place rather than in your inbox. Email will become the nudge — “you have a reply” — rather than the conversation.
Until that ships, the address above is the channel.