These are the automated emails sent directly to investors throughout the investment lifecycle. All investor-facing emails are transactional (marked as...
These are the automated emails sent directly to investors throughout the investment lifecycle. All investor-facing emails are transactional (marked as essential) and cannot be unsubscribed from.
| Detail | Value |
|---|
| When sent | When the investment is confirmed and all prerequisites are met (SPV open, bank account registered) |
| Subject | "Your investment in [Company Name] is confirmed!" |
| What it contains | Confirmation of the investment amount and deal name. For ACH investors, a notice that funds will be debited within 48 hours. For wire investors, a link to view wire instructions on the portal. |
| Action required | ACH investors should ensure their bank account has sufficient funds before the debit is initiated |
| Triggered by | Readiness evaluation schedules ACH pull or dispatches wire/IRA |
| Detail | Value |
|---|
| When sent | When the investor's ACH payment clears or wire transfer is matched, and the investment is fully funded |
| Subject | "Payment received for [Company Name]" |
| What it contains | Confirmation that payment has been received, the investment is fully funded, and a note that the executed subscription agreement will be available after the round closes |
| Action required | None -- informational only |
| Triggered by | investment.fully_funded event (published when ACH completes or wire is matched) |
| Detail | Value |
|---|
| When sent | When an Expected Payment is created for a wire investment |
| Subject | "Wire instructions ready for [Company Name]" |
| What it contains | A link to the investor portal where wire details can be viewed. No banking details in the email itself. |
| Action required | Investor must log in and initiate the wire transfer from their bank |
| Triggered by | Readiness evaluation dispatches wire |
| Detail | Value |
|---|
| When sent | When an Expected Payment is created for an IRA investment |
| Subject | "Custodian instructions ready for [Company Name]" |
| What it contains | A link to view custodian instructions and the custodian name |
| Action required | Investor must forward instructions to their IRA custodian (Fidelity, Schwab, etc.) |
| Triggered by | Readiness evaluation dispatches IRA wire |
| Detail | Value |
|---|
| When sent | On a tiered schedule when a wire hasn't been received: 3, 7, 15, and 20 business days after the expected payment is created |
| Subject | "Reminder: Wire transfer pending for [Company Name]" |
| What it contains | A reminder that the wire hasn't arrived yet, with a link to the portal |
| Action required | Investor should check with their bank and complete the wire |
| Triggered by | Automated overdue wire check (runs daily) |
| Detail | Value |
|---|
| When sent | When an ACH payment fails or is returned due to insufficient funds and a retry is scheduled |
| Subject | "Payment could not be processed for [Company Name]" |
| What it contains | Explanation of the NSF issue and the date of the next retry attempt |
| Action required | Investor should ensure sufficient funds are in their bank account before the retry date |
| Triggered by | An ACH return or debit attempt flagged as "insufficient funds" when a retry is scheduled |
| Detail | Value |
|---|
| When sent | When all payment retries are exhausted, or a permanent (non-retriable) failure occurs |
| Subject | "Payment issue for [Company Name]" |
| What it contains | Notice that the payment could not be processed |
| Action required | Investor should contact the ops team to resolve the issue |
| Triggered by | Retry exhaustion or permanent failure |
| Detail | Value |
|---|
| When sent | When an ACH payment is returned by the investor's bank and the return is not NSF, or when an NSF return's retry was not scheduled (retries exhausted) |
| Subject | "Payment returned for [Company Name]" |
| What it contains | Notice that the payment was returned |
| Action required | Investor should contact the ops team |
| Triggered by | payments.order_returned event (only for non-NSF returns, or NSF returns where retries are exhausted) |
Note: If the return is due to insufficient funds and a retry is successfully scheduled, the investor receives the Insufficient Funds Notice instead (with the retry date). They will not receive both.
| Detail | Value |
|---|
| When sent | When an investment is cancelled, either by an admin or because the SPV was cancelled |
| Subject | "The [Company Name] SPV has been cancelled" (if SPV cancelled) or "Your investment in [Company Name] has been cancelled" (if admin cancelled) |
| What it contains | Deal card, explanation of why the investment was cancelled, and confirmation that no charges were made. Copy varies based on the reason for cancellation. |
| Action required | None -- informational only |
| Triggered by | investment.cancelled event (published by admin cancellation or SPV cancellation cascade) |
| Detail | Value |
|---|
| When sent | When an SPV is cancelled and the investor had already funded their investment (money was collected) |
| Subject | "Update on your investment in [Company Name]" |
| What it contains | Deal card, explanation that the SPV did not reach its funding target, confirmation that a full refund will be processed to their bank account on file |
| Action required | None -- the investor is told no action is needed and that a refund confirmation will follow |
| Triggered by | SPV cancellation when funded investments exist |
| Detail | Value |
|---|
| When sent | When a refund payment completes and the investor's money is on its way back to their bank |
| Subject | "Your refund for [Company Name] has been processed" |
| What it contains | Deal card, refund amount, confirmation the refund is being sent to their bank, and a note to allow 3-5 business days |
| Action required | None -- informational only |
| Triggered by | investment.refunded event (published when a refund payment order completes) |
| Detail | Value |
|---|
| When sent | When a Funding Close is settled and includes this investor's investment |
| Subject | "Your investment in [Company Name] has been finalized" |
| What it contains | Confirmation that the investment has been finalized, a note that the executed subscription agreement will be available shortly in the portfolio, and a link to view the investment |
| Action required | None -- informational only |
| Triggered by | funding_close.settled event |
- All investor emails are transactional -- they always send. Investors can't unsubscribe from these because they contain important account information.
- Wire instruction emails NEVER contain banking details -- only a portal link. This is a security requirement.
- Wire reminders follow a 4-tier business day schedule (3, 7, 15, 20 business days). Wires never auto-expire -- if an investor is unresponsive, admins cancel the investment manually.
- NSF emails include the retry date -- this helps set investor expectations and reduces support inquiries.
- Payment failure is the "last resort" email -- only sent when all automatic retries have failed. The investor needs to take action or contact you.
