Email API for SaaS support teams — shared mailboxes, one API, one route table
Support teams usually want a multi-mailbox setup — `support@`, `billing@`, `abuse@` — with events reaching the ticketing system. Most hosted ESPs handle this with mailbox aliases, but the data lives in their database and you can't easily query it from your own backend. Flowmails keeps the routing and the inbox behind one API, so your ticketing service can read the mailbox with the same calls it already uses for everything else. A route table decides which local parts are accepted per domain, and events reach your ticketing system over a signed webhook. The CRM integration becomes a query against your own data, not a daily CSV export.
What hurts today
The saas support teams pain points
Hosted ESPs treat mailboxes as opaque — there's no queryable API over the inbox
The inbox copy lives in someone else's database, so you can't correlate it with your own data
Per-mailbox pricing scales worse than per-domain pricing as you grow
How Flowmails answers
What you get instead
The inbox is queryable through the API — list and fetch messages per mailbox
A route table scopes the accepted local parts per domain, so a catch-all can't be abused
Add a new shared mailbox (e.g. `press@`, `legal@`) by appending a routing rule — no plan change
FAQ
Common questions from saas support teams
Other personas