StackTrading Docs

Email Content Request List — For Client Confirmation

Email Content Request List — Stack Trading

Project: Stack Trading Purpose: Checklist to send to client for missing email copy (AWS SES templates require full Subject + Body defined by client marketing team; Klaviyo events are out of SotaTek scope and do not need content). Based on: docs/BA/Common_rule/list_email.md v1.3 + gap audit vs Zapier Integration V7.pdf, RFQ_ Stack Trading Prop Tech V7.pdf, CR-20260726-005.

Legend: rows with an existing Assumption draft already have a Subject + Body filled in (need client review/edit, not written from scratch). Rows with no draft are left blank for client to fill in.


A. Existing registry entries (SES-01 to SES-23)

Email IDTemplate KeyTriggerSubject (draft)Body (draft)
SES-01Welcome_Sim_Challenge_Part1Immediately after POST /execute-checkout returns HTTP 200 (pre-provisioning)Welcome to Stack Trading — Your Account is Being Set UpWelcome to the Trading Floor, [First Name].You're in. Your payment was successful and we're now securely building your trading account in the background. This typically takes just a few minutes — we'll email you the moment your credentials are ready.While you wait: [Community insights link] | [Market analysis link] | [Blog / resources link]Join Our Discord — Get connected to your fellow traders right now. Join our official Discord server: [Discord Invite URL]Once inside, go to the #verify channel, then copy the command below and paste it directly into the channel to link your account:/link [discord_link_token]This will instantly unlock your Associate Trader role and private trading floor channels — even before your platform account is fully ready.Footer: Stack Trading | support@stacktrading.com
SES-02Welcome_Sim_ChallengeAfter POST /provision-sim-user completes and returns platform_username + platform_password_ciphertextYour Stack Trading Account is Ready — Claim It NowYour Trading Platform is Ready.Your Stack Trading SIM account has been provisioned. Use the details below to get started.Your Platform Username: [platform_username][Claim Your Account →] (single-use link, valid 48 hours)Clicking the link above will prompt you to verify your email, enroll in MFA, and securely access your trading credentials from the dashboard.Connect Your Platform🔷 FUTURES TRADERS — Mandatory Step: You must download R|Trader Pro and log in using your provided credentials to activate your CME data feeds and digitally sign your exchange agreements. Your data feed will remain disabled until you complete this authentication.[Download R|Trader Pro] | [Platform connection guide for: TradeSea / Quantower / ATAS / Motivewave / Sierra Chart / TradingView]🔶 FOREX TRADERS: [MT5 connection guide] | [TraderEvolution connection guide]Join Our Discord — Already joined? Go to the #verify channel, then copy the command below and paste it directly into the channel to unlock your private trading floor channels:/link [discord_link_token]Not yet? Join here: [Discord Invite URL]Footer: Stack Trading | support@stacktrading.com
SES-03Welcome_Sim_Challenge_ResendUser clicks [Resend Activation Link] on expired claim screen (POST /public/resend-activation-link), or Admin-triggered resend via BPSYour New Stack Trading Activation LinkHere's your new account activation link.Your previous link expired. We've generated a fresh one for you below — it's valid for 48 hours.Your Platform Username: [platform_username][Claim Your Account →] (single-use link, valid 48 hours)If you continue to experience issues, contact support@stacktrading.com.Footer: Stack Trading | support@stacktrading.com
SES-04Live_Onboarding_Level_1Trader passes SIM challenge (Status = Passed_Challenge) → Flow 3 initiated
SES-05Restricted_Region_NoticePost-payment restricted region check match (Zapier fail-safe); simultaneous with automated refund, or with ledger log + Freshdesk ticket for crypto
SES-06Security_Reset_CompleteUser completes 2FA token reset / platform credential rotation
SES-07Identity_Verification_RetryVeriff webhook RESUBMISSION_REQUESTED, expired, or abandoned (auto-renewal path — CR-20260812-002)
SES-08Identity_Verification_Failed_FinalVeriff returns DECLINED after 3 failed sessions
SES-09Compliance_Review_RequiredBackground check flag or matching exception detected (internal — Ops only, not sent to trader)
SES-10Drawdown_Defense_Activated_InitialTrader hits Drawdown Defense threshold → 48-hour cooling-off lockout commences
SES-11Drawdown_Defense_Ready48-hour cooling-off window completes
SES-12Pod_Founding_Leader_WelcomeFlow 1.5: Rippling webhook (Founding Pod Leader Agreement signed)
SES-13Level_6_International_ContractorTrader promoted to Level 6 (W2 / Senior Contractor), international track
SES-14Dots_Profile_Action_NeededInternational trader's Dots payout profile suspended / action required
SES-15Monthly_Data_Invoice_AvailableMonthly market data invoice generated for Futures traders with billable data — ⚠️ exact dispatch point not confirmed in Flow 22, verify with client this email exists
SES-16Urgent_Data_Payment_RequiredNMI credit card vault payment rejected for market data subscription
SES-17Data_Feed_DowngradedPast-due balance: additional exchange feeds disabled
SES-18News_Liquidation_AlertAutomated position flattening during high-impact economic event — ⚠️ not found as an explicit "Send Email" step in Flow 23, verify with client this email exists
SES-19Overnight_Auto_Liquidation_AlertAutomated margin flatten executed 30 seconds prior to exchange lockout — ⚠️ not found as an explicit "Send Email" step in Flow 24, verify with client this email exists
SES-20Live_Account_ClosedTrader capital depleted or contract resigned → account permanently terminated
SES-23SIM_Provisioning_FailedPOST /provision-sim-user fails after 3 retry attempts

B. Missing from registry — found in Zapier Integration V7 but not yet added as SES entries

Proposed IDTemplate Key (proposed)TriggerSourceSubject (draft)Body (draft)
SES-24Identity_Verification_Manual_ResetOps-triggered VERIFF_MANUAL_RESET webhook (BPS manual reset, distinct from SES-07's automated Veriff retry)Flow 3.1
SES-25Level_1_Setup_FormAsset_Class = Futures, sent after Flow 3 completionFlow 3D
SES-26Market_Data_Payment_LinkWebhook from Level 1 Setup Form submissionFlow 3F
SES-27Defense_Protocol_RechargedRecharge after 2 promotions since last defense (Flow 4), or 6 months since defense trigger for Level ≥18 (Flow 21)Flow 4 & Flow 21
SES-28Address_Correction_RequestUSPS address validation fails (Path A, USA)Flow 6
SES-29Level_6_Offer_ConfiguratorLevel 6 promotion, USA — Track & Hours selectionFlow 6 Path A
SES-30Level_6_Offer_InternationalLevel 6 promotion, International — Track & Hours selectionFlow 6 Path B
SES-31Pod_Mentorship_InviteSent after Flow 3 completion, links to Style/Asset formFlow 10
SES-32Mentor_Trading_Plan_AnalysisWebhook TRADING_PLAN_ANALYZED — notifies mentor with AI analysis + PDF attachmentFlow 10.1B
SES-33Mentorship_SLA_WarningCron SLA_Deadlines approaching/breached — Mentee 72h plan or Mentor 5-day inductionFlow 10.2
SES-34Mentor_Weekly_AI_BriefWeekly cron — trading activity vs. plan brief, sent to mentorFlow 10.3
SES-35Zombie_Account_PausePod slot freed due to trader inactivityFlow 12
SES-36DTO_Approval_NoticeDTO/Hiatus request approved (USA or International path)Flow 13
SES-37DTO_Welcome_BackDTO/Hiatus end date reached, account re-enabledFlow 13
SES-38Resend_Market_Data_InstructionsOps-triggered RESEND_RTRADER_INSTRUCTIONS webhook (BPS)Flow 39
SES-39Suit_Fitting_Request (internal, to vendor)Level 10 reached, perk limit not hitFlow 26New Level 10 Trader - Suit Fitting RequestNew Level 10 Trader: [Name] Location: [City, State] Contact: [Phone/Email] Budget Code: STACK-SUIT-L10-[ID] Please reach out to schedule.
SES-40Partner_Application_Internal_Notice (internal, to partners@stacktrading.com)Partner Application form submissionCR-20260726-005

C. Klaviyo — no content needed (client marketing team owns copy), only trigger/key confirmation

ItemNote
Pod_Spot_Available_Confirm (Flow 11)Registry currently maps this to KLA-18 Pod_Waitlist_Notification, but the description doesn't match ("slot just opened, confirm within 48h" vs. "FIFO queue status update"). Ask client to confirm if these are one event or two.
Partner Application confirmation email (Klaviyo)No KLA-xx entry exists yet. Ask client to confirm event key.
Stagnation_Warning_14/7/2/1_Days, Stagnation_Defense_Activated, Stagnation_Termination (Flow 19)Registry has one generic KLA-11 Stagnation_Warning; spec's Flow 19 implements 6 distinct templates. Ask client whether the last two (account-status-changing) should move to AWS SES instead of Klaviyo, consistent with SES-10/SES-20 handling similar account-state events.

On this page