Emails

Slate emails your customers at the moments that matter in their financing journey — when they submit an application, when their agreement is ready to sign, when funds are on the way, when a payment settles. Every email is rendered with your brand color, and, if you verify your sending domain, is sent from your domain so it reads as coming from you.

You pick how emails are handled in the Emails step of the onboarding checklist, and manage your sending domain afterwards from Dashboard → Email.

Emails are a complement to webhooks, never a replacement. Every event that triggers an email is also delivered as a signed webhook — see the Webhooks event catalog. Your UI should react to the webhook; the email is what the customer sees in their inbox.

Choosing how emails are sent

Option	What happens	Transactional emails
Send as Slate	Slate sends every customer email from its own address, `no-reply@notifications.tryslatehq.com`. Nothing to configure.	On
Send from your domain	You verify a domain you own and Slate sends every customer email as `no-reply@yourdomain.com`. Requires adding DNS records.	On once the domain is verified
Handle it yourself	You subscribe to webhooks and send your own customer emails from your platform. Slate only sends the core emails.	Off

Whichever option you pick, the core emails below always go out — they carry documents or actions the customer cannot do without. The option only controls the transactional emails (lifecycle updates) and which address they are sent from.

Verifying your domain

Domain verification runs against real DNS, so it is only available in live. In the sandbox, emails always send as Slate.

Register the domain — enter the domain (e.g. yourdomain.com) on the Emails step or on Dashboard → Email. Slate registers it with its email provider and returns the DNS records to add.
Add the DNS records — the dashboard lists each record (type, name, value). They authenticate your domain for sending (DKIM / SPF). Add them with your DNS provider.
Verify — click Verify DNS records. The status moves pending → verifying → verified (or failed if a record is wrong or has not propagated yet; fix it and verify again).

Once the domain is verified, every customer email — core and transactional — switches to your domain. Until then, emails send from Slate's address.

Two kinds of emails

Core emails are always sent. They contain a document the customer must keep (their signed agreement), an action only they can take (sign, confirm new terms, reconnect a bank) or an outcome they must know about (a rejection, a failed payment).
Transactional emails are lifecycle updates — a submission receipt, a disbursement notice, a payment receipt. They are sent when transactional emails are enabled (Send as Slate or a verified domain). If you chose Handle it yourself, Slate skips them and you send your own from the matching webhook.

All customer emails go to the customer's email address on file — the email you sent when creating the customer, or the one they entered in the application. A customer without an email simply receives nothing; the flow is unaffected.

Core emails (always sent)

Email	When it's sent	What the customer gets	Related webhook
Sign your agreement	Slate's team approves the application with final terms and the customer must come back to sign. (Not sent when the customer is approved while still inside the application — they are shown the terms on screen.)	Business name, approved amount and a link back to the application to review and sign.	`application.ready-to-accept`
Updated terms to confirm	Slate counters the terms the customer asked for in an adjustable terms application. Sent on every counter, including re-counters.	Offered amount (and the amount they originally requested), term, payment amount, frequency, number of payments, total to repay, the expiry date of the offer and a link to confirm.	`application.terms-countered`
Your agreement	The customer accepts the terms and the financing agreement is created. For a credit line draw, the draw executes under the master agreement signed at onboarding.	The Schedule A PDF (amount, rate, payment schedule) and, for a standalone agreement, the full contract PDF. Draws receive the Schedule A only.	`financing-agreement.created`
Your credit line is ready	A credit line is approved and created.	The facility limit. Draw facilities also attach the facility confirmation PDF.	`credit-line.created`
Application not approved	The application is rejected, by the automated decision or by Slate's team.	The reasons when Slate shares them, and the date they can apply again (90 days).	`application.rejected`
Payment failed	A scheduled debit is returned or cancelled by the bank.	The amount that could not be collected.	`financing-agreement.payment.failed`

Transactional emails

Sent only when transactional emails are enabled. The Related webhook column is the event to subscribe to if you send these yourself.

Email	When it's sent	What the customer gets	Related webhook
Application received	The customer connects their bank and the application is submitted. Not sent for Early Wage Access requests.	The requested amount and the decision SLA (24 hours).	`application.submitted`
Draw request received	An adjustable terms application against a capital offer or a draw facility is submitted.	The amount they selected.	`application.submitted`
Credit line application received	An adjustable terms application for a credit line is submitted.	A confirmation that the application is being reviewed.	`application.submitted`
You have a new offer	Slate's offer intelligence detects an opportunity for the customer and publishes it as a pre-approval. Not sent to transaction-feed customers (their offers are partner-mediated).	The offer amount, an optional description and a one-click link to apply (valid for 7 days; capital offers open in adjustable-terms mode).	`opportunity.offer.created`
Reconnect your bank	Slate asks a credit line customer to reconnect their bank account (connection expired or data too old).	The deadline to reconnect.	`credit-line.bank-reconnection-requested`
Funds on the way	The agreement is disbursed.	The amount, the last 4 digits of the receiving account and the expected arrival date (3 business days).	`financing-agreement.disbursed`
Payment initiated	A repayment debit is initiated on the customer's account.	Amount, date, balance remaining after the payment and the percentage repaid so far.	`financing-agreement.payment.initiated`
Payment received	The debit settles.	Amount, settlement date, balance remaining and the percentage repaid.	`financing-agreement.repayment`
Agreement paid in full	The last payment settles and the agreement completes.	A confirmation that nothing is owed.	`financing-agreement.completed`
A new, larger offer is available	Paying off an agreement earns the customer a renewal pre-approval. Sent as its own email, right after the paid-in-full one.	The new offer amount.	`preapproval.created`

Emails to your team

These are sent by Slate, from Slate's own address, to the people on your organization — never to your customers.

Email	When it's sent	Who receives it
Business verification result	Slate reviews your KYB submission: approved, not approved, or changes requested (with the reviewer's note).	The first owner listed on the submission.

If your team wants a copy of what your customers receive, Slate can send your addresses a blind copy (BCC) of every customer email — core and transactional, attachments included. Ask your Slate contact; it is configured per environment (sandbox and live separately).

Sandbox

Emails do send in the sandbox, always from Slate's address. Use real inboxes you control when testing.
Domain verification is live-only. Pick Send as Slate or Handle it yourself to complete the onboarding step in the sandbox, then connect your domain once you have production access.
Sandbox disbursements have no real bank account behind them, so Funds on the way shows 0000 as the account's last 4 digits.

Webhooks