Send email to your customers

Your apps can send email from the moment your project exists. There is nothing to set up — no mail provider, no account to create, no DNS records to add. From day one, mail arrives in your customers’ inboxes as your business “via Spark,” sent from an address Spark manages, and Spark handles the technical plumbing that keeps legitimate mail out of spam folders.

Ask the agent for what you want in plain words: a receipt after every order in your online store, a booking confirmation, a “Send newsletter” button in an internal tool. The agent builds it, and you watch it work in the preview before you publish.

Who your mail reaches

Every message goes to your signed-in customers — people who have created an account with your app. That constraint is what keeps your project’s sending reputation clean: every recipient already has a real relationship with your business, which keeps your mail landing in inboxes, and it means every project can send from day one with no review queue.

There is no list import, and no way to send to an arbitrary address — see what Spark doesn’t do. If you want someone on your mailing list, invite them to sign in. Once they have an account, your apps can reach them.

You can email one customer, all of them, or everyone who owns a particular offer — useful when a message is meant only for paying subscribers.

Receipts and newsletters

Spark treats two kinds of mail differently:

• Receipts and confirmations — mail a customer’s own action caused right now: an order receipt, a booking confirmation, a “your file is ready” notice. These always arrive.
• Newsletters and announcements — everything you send on your own initiative: campaigns, updates, re-engagement.

Newsletters automatically carry an unsubscribe link, and customers who opt out stop receiving them. Their receipts and sign-in emails still arrive, so unsubscribing from your marketing never breaks their account. This split is a legal requirement for commercial email, and Spark enforces it for you — opt-out handling and the unsubscribe footer are never your problem.

Schedule a send

A send can be queued ahead of time — minutes to weeks out — and canceled while it waits. The audience resolves at delivery time, so a scheduled newsletter picks up customers who signed up after you queued it and skips anyone who unsubscribed in between.

There is no recurring schedule. A weekly newsletter works best as a button in an internal tool: ask the agent to build one, then each week you review the content and press Send. That keeps a human eye on everything your customers receive.

Send from your own domain

By default, mail comes from an address on Spark’s sending domain. To send from your own — say, hello@yourbusiness.com — open Project settings › Email:

1. Add your domain.
2. At your DNS provider, add the records the panel shows. The panel lists the exact records for your domain, each with a copy button, and checks them automatically.
3. Once the domain is verified, pick the address your mail sends from.

These records sit alongside whatever your domain already does. Your existing mail setup stays untouched — anything already using your domain for email keeps working exactly as before.

Where replies go

Customers can reply to your mail like any other email.

On the built-in sender, replies can appear in an inbox inside Spark — ask the agent for a “Replies” or “Support inbox” view in an internal tool, and you can read and answer them from there.

On your own domain, replies go to your regular mail, the same place messages to that address already arrive. If you would rather read them in Spark, turn on Receive replies in Spark in Project settings › Email; it takes one more DNS record, which the panel shows.

Test without sending

While you work in the preview, every send is captured: stored so you can inspect exactly what would have gone out, delivered to nobody. Place a test order in preview and the receipt exists for you to read, while no customer receives a thing. Once you publish, sends go out for real.

Sending caps

Sends are capped per day, and a single send caps how many recipients it can reach — the numbers live on the limits page. An audience bigger than the per-send cap is a conversation with support.