Transactional email and a support inbox on one domain
Your app sends receipts, password resets and sign-in codes through the FutureMail API. When a customer hits reply, the message lands in a shared inbox your team actually reads, not a no-reply void.
Works with a domain you already own. One price for your whole team.
- s
support@shipnotes.app
Shared inbox for customer questions and replies
- n
notifications@shipnotes.app
Sender for receipts, resets and sign-in codes
- b
billing@shipnotes.app
Invoice questions and failed-payment replies
- s
security@shipnotes.app
Vulnerability reports and account-security mail
- f
feedback@shipnotes.app
Replies to in-app feedback requests
Unlimited addresses, catch-all and plus-addressing included.
Why FutureMail works for SaaS products
REST, or drop-in Resend compatibility
POST /v1/emails with idempotency keys, batches of up to 100 and scheduled delivery. Already on Resend? Point the official Resend SDK at the /resend base URL with a FutureMail key.
Customer replies reach a person
Set replyTo to support@ and replies to a receipt or reset email arrive in a shared mailbox your team works from, with threading and Gmail-style search.
Signed webhooks for every event
Receive email.delivered, email.bounced, email.complained and email.received as HMAC-signed webhooks, retried for about 28 hours and replayable. Prefer a stream? GET /v1/events serves Server-Sent Events.
Templates with variables
Store receipt and reset templates, publish them, and send by id or alias with your variables. Placeholders are HTML-escaped by default, so user-supplied names can't break your markup.
See what happened to every email
Each message has a delivery timeline from queued to delivered, bounced or complained, plus opens and clicks when tracking is on. Hard bounces and complaints go on the suppression list automatically.
Engineers and support, one workspace
Add support staff and engineers for one flat price with owner, admin, developer and viewer roles. Give production a send-only key limited to one sending domain, with an expiry date.
Agent-ready
An agent on support@
Subscribe to email.received and let your own agent load the conversation with GET /v1/threads/:id, then answer with POST /v1/emails/:id/reply or star the thread for a human. Its replies appear in the same inbox your team uses.
- Answer how-do-I questions from your help docs
- Reply about a failed payment after checking the account in your system
- Forward bug reports to the engineering address with a short summary
# give an agent its own inbox and a key scoped to it $ fm agents create "Assistant" \ --address assistant@shipnotes.app ✓ Created agent Assistant address assistant@shipnotes.app scopes send, read # connect Claude, Cursor or any MCP client url https://api.futuremail.dev/mcp header Authorization: Bearer fm_live_…
Set up in an afternoon
- 1
Subscribe
Create an account and start Pro for $20/month. Cancel anytime.
- 2
Connect your domain
Copy the DNS records we generate into your registrar. FutureMail checks them live and tells you when you're set.
- 3
Create your addresses
Add the addresses you need, point them at shared or individual mailboxes, and invite your team.
- 50,000 recipients a month
- Unlimited custom domains
- Unlimited addresses & aliases
- Agent inboxes with scoped API keys
- REST API, CLI & remote MCP server
- Webhooks, templates & scheduled send
- Open & click tracking
- Team roles & audit log
Paid only, cancel anytime. New accounts can send to up to 1,000 recipients a day for their first 14 days; receiving is never limited. Pricing details
Common questions
Can I use the Resend SDK with FutureMail?
Yes. Create the client with a FutureMail API key and the base URL https://api.futuremail.dev/resend. Emails, batch sends, scheduling, domains and API keys work unchanged. Webhooks use FutureMail's own HMAC signature format rather than Svix's.
Is there an SMTP relay for my framework's mailer?
No. FutureMail sends over its REST API or the Resend-compatible API only, so call it with an HTTP client or the official Resend SDK. An OpenAPI 3.1 description is published at /openapi.json.
How do I test emails without reaching real people?
Send to delivered@, bounced@, complained@ or delayed@test.futuremail.dev. Each simulates that outcome without sending real mail and doesn't count toward your limits.
Can I send product update announcements to all my users?
No. Announcements and newsletters to your user base are marketing email, which the Acceptable Use Policy doesn't allow. Accounts with bounce rates above 4% or complaint rates above 0.08% are paused automatically.
Is there an uptime SLA?
No, FutureMail doesn't offer an SLA. Failed webhook deliveries are retried and can be replayed, and idempotency keys make it safe to retry a send without duplicating it.
How much does FutureMail cost? Is there a free plan?
FutureMail is paid-only: Pro is $20/month and includes 50,000 recipients a month, unlimited domains and addresses, agent inboxes, the API and MCP server. There is no free tier or trial. Limits are hard caps, so there are never overage charges and no per-seat pricing. Charged in USD; Stripe may show your local currency and add applicable tax. Need more volume? Email support@futuremail.dev.
More answers in the general FAQ.
Related use cases
Startups
Startup email on your own domain for $20/month: founders@ and hiring@ in a fast shared inbox now, then product email and agent inboxes on the same account.
AI support agents
Run an AI support agent on support@ your domain: new mail arrives by webhook, the agent replies in-thread over the API, and your team sees every message.
QA and testing
Test signup, password reset and magic-link emails end to end: a unique plus-address per run, wait_for_email or fm wait --otp in CI, and simulated bounces.