How to build a FINRA‑compliant texting workflow in under 30 minutes before your next audit
---Here's what the difference looks like in practice:
---Before (personal-phone text, non-compliant):
Hey John, the market's up – you might want to consider buying more AAPL.After (FINRA-compliant, platform-routed):
[Compliance-Approved] Market Update – Apple Inc. (AAPL) has risen 3% today. Review your portfolio at https://myfirm.com/portfolio. Reply "YES" to schedule a call or "STOP" to opt out.
The Complete Daily Workflow Template (Copy-Paste Ready)
The table below maps the full client communication lifecycle. Each phase has a corresponding template in the section that follows. Paste this into your compliant texting platform and connect it to your CRM so the placeholders auto-populate.
| Phase | Time of Day | Action | Template |
|---|---|---|---|
| 1. Onboarding | 08:00 AM | Send welcome and opt-in request | WELCOME_TEMPLATE |
| 2. Market Pulse | 09:30 AM | Daily market summary with CTA | MARKET_SUMMARY_TEMPLATE |
| 3. Client-Specific Alert | As triggered by price move | Targeted alert using client segment tag | ALERT_TEMPLATE |
| 4. Meeting Follow-Up | Within 1 hour post-meeting | Recap and next steps | MEETING_FOLLOWUP_TEMPLATE |
| 5. Complaint Handling | Immediate upon receipt | Acknowledge, log, and assign | COMPLAINT_ACK_TEMPLATE |
| 6. End-of-Day Archive | 05:45 PM | Auto-export to WORM storage | N/A (platform step) |
The Five Templates
Each template includes a compliance-approved prefix, opt-out language, and a single clear CTA. That structure gives your compliance officer a consistent starting point for review. Replace the {{placeholders}} with your CRM field names.
WELCOME_TEMPLATE
[Compliance-Approved] Hi {{FirstName}}, welcome to {{FirmName}}! To receive
timely market updates via text, please reply "YES". Reply "STOP" at any time
to opt out. –{{AdvisorName}}
MARKET_SUMMARY_TEMPLATE
[Compliance-Approved] Daily Market Snapshot ({{Date}}): S&P 500 +0.7%,
Nasdaq +1.2%. Review your portfolio here: {{PortfolioLink}}.
Reply "CALL" to discuss or "STOP" to opt out.
[Compliance-Approved] Alert: {{Ticker}} has fallen 5% since yesterday.
Review impact on your allocation: {{Link}}.
Reply "YES" to schedule a call or "STOP".
MEETING_FOLLOWUP_TEMPLATE
[Compliance-Approved] Thanks for meeting today, {{FirstName}}.
Action items: 1) Update risk profile ({{Link}}). 2) Review suggested
allocation ({{DocLink}}). Reply "CONFIRM" when completed.
COMPLAINT_ACK_TEMPLATE
[Compliance-Approved] We've received your concern, {{FirstName}}.
Your case #{{CaseID}} is being reviewed by our compliance team.
Reply "STOP" to end texts.
These templates cover the full client lifecycle. They're not a starting point for improvisation. They're the guardrails that keep every send inside the supervision workflow, regardless of which advisor sends it or which client receives it. Your compliance officer still reviews and approves before anything goes firm-wide — that step is the point.
---Here's the difference between using a generic AI prompt and a structured one built for this context:
Generic AI output (non-compliant):
Market is up! Check out the latest numbers here: https://finance.comUltra Prompt-guided output (compliant):
[Compliance-Approved] Daily Market Snapshot (03/22): S&P 500 +0.7%, Nasdaq +1.2%. Review your portfolio: https://myfirm.com/portfolio. Reply "CALL" or "STOP".
The generic version fails on three counts: no disclaimer, no firm-specific link, no opt-out. The structured prompt produces a message with the right structure for compliance review, without the compliance officer rewriting it by hand.
The Core Ultra Prompt for FINRA-Compliant SMS
Generate a market-summary SMS for {{Date}} that includes: S&P 500 change,
Nasdaq change, a short CTA linking to {{PortfolioLink}}, and the required
[Compliance-Approved] disclaimer. Include "CALL" and "STOP" reply options.
Keep under 160 characters.
From that base prompt, you can create two variations with a single variable change:
- High-net-worth segment: Add
Tone: formal, concise. Avoid percent references; use index points. - Retail segment: Add
Tone: plain language. Lead with the practical implication, not the index number.
Neither variation requires the compliance officer to review a brand-new template. Both are derived from the same approved base prompt, which means the audit trail is intact: prompt ID, generation timestamp, the exact output, and the approval queue entry all travel together.
---Platform Requirements and Supervision Checklist
The workflow and templates above only work if your platform can hold them. Before you go live, verify every requirement in this table. A platform that misses even one will create audit exposure the templates can't fix.
| Requirement | Why It Matters (FINRA) | How to Verify |
|---|---|---|
| Automatic opt-in/opt-out logging with timestamps | Proof of consent and documented ability to honor deletion requests | Run a query for "STOP" messages in the admin console. Confirm timestamps appear on every entry. |
Ultra Prompt's Compliance Review module can auto-assign each generated message to the approval queue and attach the originating prompt ID. That prompt ID becomes the link between the approved template, the generated variation, and the sent message, the exact chain of custody an examiner will look for. If client data security is a concern during that drafting and approval process, the same principles that apply to keeping client data safe while drafting emails apply to your SMS approval workflow too.
30-Day Rollout Plan
- Week 1: Select and configure your compliant texting platform. Verify all five checklist requirements above. Get legal sign-off on the five base templates.
- Week 3: Pilot with a small advisor cohort. Run the full workflow, onboarding through end-of-day archive, for five test clients. Log every exception.
- Week 4: Resolve exceptions. Train all advisors on the platform-only texting policy. Archive personal-phone numbers from client contact records. Go firm-wide.
Most compliance failures in this area aren't complicated. They're obvious in hindsight and preventable with the workflow above.
- Using personal cell phones. No automatic capture means any business-related text, a securities order, a portfolio discussion, a client instruction, is a business communication not recorded. That's a recordkeeping violation for uncaptured business-related texts.
- Manual copy-and-paste of ad-hoc text. If the message didn't originate from an approved template and pass through the approval queue, there's no audit trail. The compliance officer can't certify what they never saw.
- Failing to capture inbound replies. Failing to capture inbound messages is a recordkeeping violation under FINRA rules. If your platform only archives outbound messages, half the conversation is missing and your records are incomplete.
The fix for all three: enforce platform-only texting firm-wide, lock every outbound send behind the approval queue, and use the templates above as the only approved starting points.
---Frequently Asked Questions
- How do I archive and supervise text messages for FINRA compliance?
- Can financial advisors use personal cell phones to text clients?
- The five templates in the Daily Workflow section above cover the full client lifecycle: WELCOME_TEMPLATE (opt-in), MARKET_SUMMARY_TEMPLATE (daily update), ALERT_TEMPLATE (price-triggered), MEETING_FOLLOWUP_TEMPLATE (post-meeting recap), and COMPLAINT_ACK_TEMPLATE (complaint intake). Each includes a compliance-approved prefix, opt-out language, and a single CTA.