Customer emails
Your customers should
hear from you.
Not from us.
Slate already writes the email at every step of a financing — approved, funded, payment taken, paid in full. Connect a domain you own and we send them under your name, from your address.
The gap
Financing is a conversation. Most of it happens without a word.
A customer takes money from you and pays it back over months. Four things happen that they would want to hear about, and by default they hear about none of them.
They apply
Silence. They wonder whether it went through at all.
You approve them
Silence. The good news arrives as a bank deposit with no explanation.
A payment clears
Silence. Every debit looks the same as an unexplained one.
They pay it off
Silence — at the exact moment they have proved they are worth lending to again.
The last one is the expensive one.
A customer who has just repaid in full is the best credit risk on your platform and the most likely to take another advance. If nobody says thank you, nobody asks.
What goes out
Ten emails, written and already live
You do not write these, template them, or wire them to a webhook. They are part of the financing engine — they fire off the same events that move the money.
While they apply
Application received
Confirms it landed, so nobody has to wonder.
Connect your bank
Prompts the one step that stalls most applications.
Signature needed
Brings them back to sign without you chasing.
Draw request received
For customers drawing against a line they already hold.
When you decide
Money is on the way
Sent at disbursement, so the deposit arrives explained.
Not this time
A clean decline, in your voice rather than none.
While they repay
Payment taken
Every debit accounted for before they go looking.
Payment cleared
Confirmation once it settles.
Payment failed
Reaches them the same day, while it is still fixable.
When they finish
Paid in full
The thank-you, and the opening to offer them the next one.
By product
What lands, and when, for each product
The journeys are not the same. A capital customer applies once and repays. A credit line is activated once and then drawn against for as long as it stays open, so the cycle repeats per draw.
Offer
Slate underwrites from your data and issues a pre-approval.
Offer ready
Offer ready
—
Start
The customer opens the embedded flow.
Application received
Application received
Draw request received
Verify
The two steps that stall a flow if nobody nudges.
Connect your bank · Signature needed
Connect your bank · Signature needed
Signature needed
Decision
Approved or not, in your voice rather than none.
Money is on the way · Not this time
Money is on the way · Not this time
Money is on the way
Repaying
Every movement accounted for before they go looking.
Payment taken · cleared · failed
Payment taken · cleared · failed
Payment taken · cleared · failed
Finish
The thank-you, and the opening for the next one.
Paid in full
—
Paid in full
A draw sits under a line that is already open, so there is no separate offer for it. A credit line stays open after the balance clears, so it has no closing email — the individual draws do.
In their inbox
The same email, sent as you
Your customer took the money from you. This is the difference between an email they trust and one they report as spam.
Without a domain
Slate <[email protected]>
to me
With your domain
Your company <[email protected]>
to me
Your name
The display name and address are yours. Slate appears nowhere in the header.
DKIM signed
Every message is signed on your domain, so inbox providers trust it.
Monitored
We watch deliverability on the domain and flag it if reputation slips.
Setup
One DNS change, then it runs itself
Everything below happens in your Slate dashboard under Emails. The only thing that leaves it is a set of DNS records for whoever runs your domain.
Name the domain
Pick a domain you already own and the display name customers should see. We suggest a subdomain so your primary mail is never touched.
Domain
Display name
Add the DNS records
We generate them the moment you register the domain. Paste them into your DNS provider — the same job as verifying any sending domain.
| Type | Name | Content | TTL | Priority | Status |
|---|---|---|---|---|---|
| MX | send | feedback-smtp.…amazonses.com | Auto | 10 | Pending |
| TXT | send | v=spf1 include:amazonses.com ~all | Auto | — | Pending |
| TXT | resend._domainkey | p=MIGfMA0GCSqGSIb3DQEB… | Auto | — | Pending |
| TXT | _dmarc | v=DMARC1; p=none; | Auto | — | Pending |
Illustrative values. Your dashboard shows the exact records for your domain, each with a copy button.
Live
We watch the records and flip the domain live the moment they resolve — usually minutes. Nothing else to request, and no follow-up from your side. From then on every email goes out as you.
Worth knowing
The questions your team will ask
Use a subdomain
Something like mail.yourdomain.com keeps your primary mail records untouched. Your customers still see your brand.
Live accounts only
Custom sending domains are configured on your live account. Sandbox keeps sending from Slate so tests never reach a real inbox.
Nothing to build
No templates to write, no webhook to wire, no send logic on your side. The emails already exist and already fire.
Change it any time
Point at a different domain or change the display name from the dashboard. Re-verification follows the same three steps.
Connect your domain.
It is one DNS change on your side. Everything after it — the writing, the sending, the timing —
already runs inside the financing engine.