Contact the Flowmails team: advice, orders, and bug reports
Most contact pages are a single generic inbox. That works until your feature request lands in the same queue as a billing dispute and a 3 a.m. outage report. This page is a short tour of the four channels we actually read, what each one is for, and what to put in the subject line so it doesn't bounce between desks for a week.
Support
Role-based inboxes
Twitter
Why four channels, not one
A single support@ alias is fine for a hobby project. For a platform that touches billing, data residency, and a Worker running in your Cloudflare account, the first question on every inbound is what kind of request is this. Routing the classification to the user — via the address they pick — cuts a triage step and gets the message in front of the person who can actually act on it.
Each of the four channels below has a single owner, a single response window, and a clear escalation path if the topic turns out to be the wrong one for that mailbox. If you send a billing question to bug@ we will still reply, it will just take a few extra hours.
The four channels
All three mailboxes are first-class: they live on this domain's own Email Routing configuration, delivered to a Worker that pages the right person. The Twitter handle is a personal one — it is the fastest way to ping me for things that don't need a paper trail.
Use this inbox when you have an idea, a workflow that doesn't quite fit, a feature you wish existed, or a UX change that would make the platform click for you. The more concrete the better — a screen recording and the "I tried to do X, the platform does Y, I expected Z" framing is gold. We use the thread as input to the quarterly roadmap review, so even the requests that don't ship this quarter get read and ranked.
Don't use this for billing changes or for things that are actually broken — the right mailbox is faster in both cases.
order@flowmails.net — orders
Plan upgrades and downgrades, prorated invoices, refund requests, VAT / tax ID questions, missing receipts, billing access for a teammate — anything that touches money goes here. Include the billing email on the account, the domain (if it's tied to a specific zone), and the order id from the most recent receipt. That trims a round trip.
If you need a quote for an annual or multi-domain plan, this is also the right inbox — the self-serve checkout is optimised for the standard tiers, and custom shapes still go through a short email exchange.
bug@flowmails.net — bug reports
Something is broken: a Worker didn't deploy, an email didn't arrive, a route-table change left your zone in a weird state, a webhook fired twice. Send it to bug@ with a reproduction and the approximate time of the failure. The inbox is wired to the on-call rotation, so the first acknowledgement is usually fast and the fix (or a clear "we can't reproduce, here's what we need next") follows within a working day.
For security issues, please email bug@ directly rather than opening a public issue — we'd rather coordinate a fix and a disclosure timeline than have the details spread across a public thread.
Twitter — @Yaomker
For "is there an outage right now," "the dashboard is doing something weird," and other real-time questions, the fastest path is a DM or a public mention of @Yaomker. Twitter is best-effort: there is no SLA, and anything that needs a paper trail (refund, contract, security disclosure) should still go to one of the inboxes above so we have a durable record.
What to put in the first email
Whatever channel you pick, a first email that includes the following gets a faster reply than one that doesn't:
The account email on the Flowmails dashboard (the one you signed up with).
The domain the issue is on, if it's tied to a specific zone.
A one-line description of the expected behaviour versus the actual behaviour, with a reproduction if you have one.
For billing threads: the order id from the most recent receipt, and the email that should appear on the next one.
You don't need a support-tier deal to email us. The first reply is human, in plain English, and tries to solve the problem in one round rather than open a ticket.
