A prop firm’s post-purchase email lifecycle starts with a confirmed challenge order. From there, each message should tell the trader what changed, what they can do now and where to get help. Use confirmed payment, account and reward events so the email agrees with the dashboard when the trader opens it.
Separate order status from account status
A paid challenge and a usable trading account can arrive at different times. Send a receipt when payment is confirmed, with the programme, fee and order reference. If the account is still being set up, explain what is pending and where a trader can check its status. Send the account-ready message when the dashboard can actually show the correct account. Use a dashboard link and keep credentials and sensitive identity details out of the email.
Give each trigger a source of truth. The order system confirms payment and refunds. The account platform confirms provisioning, phase changes and final evaluation status. The reward system confirms each request’s progress. Have your automation check the current record before it sends a delayed message.
Adtrend’s public email portfolio includes MultiFunded’s saved checkout and rules explainer designs. The checkout email has a clear return path and the explainer makes the relevant rules easy to find. The same structure works after purchase: state the event, link to the right dashboard view or rules, and give the reader one useful next step.
Give each message a send rule and a stop rule
Use this example map to review the first set of workflows with operations and support. Replace every trigger and state with the terms used by your systems.
| Message | Send when | Stop or change course when |
|---|---|---|
| Purchase receipt | Payment reaches the confirmed paid state | Suppress duplicate receipts for the same confirmation. Route a later refund to a refund notice. |
| Account ready | The corresponding account is provisioned and visible in the dashboard | Hold if the order has been reversed or account access is pending. |
| Getting started reminder | The account is ready and the trader has yet to finish the relevant setup step | Exit when setup is complete, the account is closed, or the offer is no longer available to that trader. |
| Phase complete or evaluation closed | The relevant status is confirmed by the account system | Route a pending or disputed decision to review before telling the trader it is final. |
| Reward request update | The reward system records the status you intend to communicate | Check newer events before sending. Keep requested, approved and paid as separate statuses. |
| Optional offer | The person is eligible for the offer and has the applicable marketing subscription | Suppress on unsubscribe, an unresolved complaint or payment dispute, or when the offer expires. |
On Customer.io, an event can start a workflow and exit criteria can stop it when a record changes or a person matches a defined condition. Confirm how exits apply to the specific account or order, since a trader may have more than one. For example, a second challenge purchase should start the second account’s onboarding without restarting the first one or ending its active support journey. Customer.io automation triggers · Customer.io exit conditions
Keep promotional email separate
Use separate templates and sending rules for service notices and marketing. A receipt, access notice or material account update should help someone use or understand a service they already requested. A promotion, reset offer or new challenge invitation belongs in a marketing workflow. Check subscription preferences and the rules that apply to your audience before activating it. An unsubscribe should suppress pending promotional messages as well as new ones. Customer.io transactional messages · Customer.io subscription settings
Verify your sending domain and review Gmail’s current sender requirements. Gmail sets additional authentication requirements for bulk senders and requires them to support one-click unsubscribe for marketing and subscribed messages. Test both the visible unsubscribe link and what happens to future promotional delivery. Gmail sender guidelines
Test account changes before sending to customers
Use synthetic contacts and orders in a test workspace. Record the incoming event, the message decision and the result at the email provider. Run these cases before opening each flow to customers.
- A payment notification arrives twice. Check that one order produces one confirmation. Use stable event and order identifiers and verify how your email integration handles duplicate events.
- The payment passes but account provisioning is delayed. The receipt arrives and the account-ready message waits until the account is usable.
- A trader has two accounts. A phase change or closure on one account leaves the other account’s messages and links intact.
- A refund or unsubscribe arrives during a delay. The workflow checks the latest state before sending the affected reminder or promotion.
- A reward request moves through multiple statuses. Check the wording and link at each stage, including a delayed event that arrives after the latest status.
Review confirmed deliveries, duplicate sends, account setup completion and support requests about access, rules or order status. For eligible promotional flows, compare verified purchases and refunds over a defined window. Use GA4 and order reconciliation to confirm the paid events. Prioritise whichever message prevents the most confusion for a trader trying to access or understand their account.