# TWILIO USE CASE ANALYSIS
**Cold Bore Ballistics LLC — Confidential**
Last updated: 2026-06-05
Status: Planning — account not yet created

---

## Overview

Twilio is the recommended unified communications platform for all CBB products. A single Twilio account covers telephony (voice, SMS), programmatic messaging, and transactional email via SendGrid (Twilio-owned). Estimated cost at initial launch (Phase 1): ~$3–4/month. Full build-out across all 16 use cases: ~$65–75/month at moderate scale, with the majority of that cost offset by SaaS subscription revenue.

This document analyzes each use case by level of effort, cost, customer value (perceived vs. real), and acquisition impact.

---

## Use Case Framework

Each use case is evaluated across four dimensions:

| Dimension | Description |
|---|---|
| **Level of Effort** | Build complexity and time — Low / Medium / High |
| **Cost** | Recurring and one-time costs |
| **Customer Value** | Perceived (what they think they're getting) vs. Real (what actually drives behavior/retention) |
| **Acquisition Impact** | How this affects attractiveness and valuation to a buyer |

---

## Use Cases

---

### UC-01 — 800 Number (Corporate Forwarding)

**Product:** CBB Corporate
**Status:** Recommended at account creation

#### Level of Effort
**Low.** Purchase number via Twilio Console, configure forwarding to personal cell. No code required. 15-minute setup.

#### Cost
| Item | Cost |
|---|---|
| Toll-free number | ~$2.00/month |
| Inbound minutes (forwarded) | $0.0085/min — negligible at low volume |
| **Estimated monthly** | **~$2–3/month** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Professional presence — customers and partners see a business number, not a personal cell |
| **Real** | Protects personal cell from public exposure; enables outbound caller ID masking (see UC-04); establishes a transferable business asset that survives a founder exit or acquisition |

#### Acquisition Impact
**High.** A registered toll-free number is a transferable business asset. A buyer inherits a working customer-contact number — no disruption to any communications that reference it. A personal cell number on business materials is a red flag in due diligence (single-person dependency, non-transferable). This is a $2/month fix for a real diligence liability.

---

### UC-02 — Feedback Form → SMS Notification

**Product:** `feedback-service`
**Status:** Recommended immediately after account creation

#### Level of Effort
**Low.** ~5 lines of Python added to the existing Flask `feedback-service`. Twilio Python SDK (`twilio` pip package). One environment variable for the destination number. No new infrastructure.

#### Cost
| Item | Cost |
|---|---|
| Outbound SMS (domestic) | $0.0079/message |
| At 100 feedback submissions/month | ~$0.79/month |
| **Estimated monthly** | **<$1/month** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | N/A — this is an internal operational notification; customers don't see it |
| **Real** | Instant awareness of feedback submissions; eliminates the need to poll email or a dashboard; faster response time to user-reported issues directly improves user experience and retention |

#### Acquisition Impact
**Moderate.** Demonstrates operational responsiveness — a buyer sees that feedback loops are monitored in real time, not batched. Minor individually, but part of the broader picture of a well-instrumented, professionally operated service.

---

### UC-03 — Transactional Email via SendGrid

**Product:** All CBB products
**Status:** Recommended at account creation (parallel to 800 number)

#### Level of Effort
**Low–Medium.** SendGrid is owned by Twilio and provisioned through the same account. Integration requires:
- SendGrid account activation within Twilio Console
- Domain authentication (DNS TXT/CNAME records on `coldboreballisticsllc.com` and `scope-dope.com`)
- Python SDK integration in `feedback-service`; future integration in Club SaaS and Community Accounts

#### Cost
| Item | Cost |
|---|---|
| SendGrid Free tier | $0/month — up to 100 emails/day |
| SendGrid Essentials (if >100/day) | $19.95/month for up to 50,000/month |
| **Estimated at launch** | **$0/month** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Professional, branded email communications (receipts, confirmations, notifications) arriving from `@coldboreballisticsllc.com` or `@scope-dope.com` rather than a generic sender |
| **Real** | Deliverability — transactional email sent through SendGrid avoids spam filters that catch mail sent directly from a server IP; critical for any time-sensitive communication (match day reminders, account verification, job completion notifications) |

#### Acquisition Impact
**High.** A buyer inherits a configured, authenticated transactional email pipeline with domain reputation already established. An unconfigured or ad-hoc email setup (sending from a personal Gmail or raw server) is a diligence flag. SendGrid also provides delivery analytics — open rates, bounce rates, spam reports — which are valuable operational metrics a buyer will want to see.

---

### UC-04 — Outbound Caller ID Masking

**Product:** CBB Corporate
**Status:** Enabled automatically by UC-01 (no additional setup)

#### Level of Effort
**None** — this is a configuration of the UC-01 800 number, not a separate build. Outbound calls placed through the Twilio number display the 800 number as caller ID.

#### Cost
| Item | Cost |
|---|---|
| Outbound minutes | $0.014/min |
| At low corporate call volume | <$1/month |
| **Estimated monthly** | **~$0–1/month (incremental to UC-01)** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Customers and vendors see a consistent, professional business number on inbound calls |
| **Real** | Personal cell number stays private; all business call history is logged in Twilio (not on a personal device); call records are a business asset, not a personal one |

#### Acquisition Impact
**Moderate.** Reinforces the transferability argument from UC-01. Call history and contact records associated with the business number — not a personal cell — are cleaner in due diligence and don't create a "founder walks out with the Rolodex" concern.

---

### UC-05 — Match Day SMS Notifications

**Product:** Club & Match Management SaaS (Brief #02)
**Status:** Implement at Club SaaS build (~2,000–5,000 installs)

#### Level of Effort
**Medium.** Requires Club SaaS to be built first. Within Club SaaS:
- Collect shooter phone numbers at registration
- Trigger SMS on: registration confirmation, match reminders (T-24hr, T-1hr), score posting, cancellation/postponement
- Twilio Messaging Service (vs. raw phone number) for throughput and deliverability at scale
- STOP/HELP compliance handling (required by TCPA — Twilio handles automatically with Messaging Services)

#### Cost
| Item | Cost |
|---|---|
| Outbound SMS | $0.0079/message |
| Messaging Service fee | $0.0025/message (A2P 10DLC surcharge) |
| 10DLC brand registration (one-time) | $4.00 |
| 10DLC campaign registration (one-time) | $15.00/month |
| At 500 shooters, 4 messages/match, 2 matches/month | ~$11.70/month in SMS + ~$15 campaign fee |
| **Estimated monthly at moderate scale** | **~$27/month** |

**Note:** 10DLC (10-digit long code) registration is required by US carriers for A2P (application-to-person) SMS at any meaningful volume. Without it, messages are filtered as spam. This is a compliance requirement, not optional.

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Convenience — shooters get reminders and scores on their phones without checking an app or website |
| **Real** | Reduces no-shows (match directors' highest pain point); score notifications drive re-engagement with the app; cancellation SMS prevents wasted drives to the range — this is the single highest-value Twilio use case for end-user behavior change |

#### Acquisition Impact
**Very High.** SMS notification infrastructure for a SaaS product is a moat. It requires carrier registration, compliance setup, and sender reputation — all of which take time to establish and are non-trivial for a new owner to replicate. A buyer acquires a working, compliant, reputable SMS pipeline alongside the SaaS product. This directly increases the Club SaaS valuation multiple.

---

### UC-06 — Phone Verification (Verify API)

**Product:** Community Accounts (future)
**Status:** Implement when Community Accounts feature is built

#### Level of Effort
**Low.** Twilio Verify API is a purpose-built OTP service. Integration is ~20 lines of Python/Kotlin. No carrier registration required — Twilio handles routing.

#### Cost
| Item | Cost |
|---|---|
| Per OTP verification | $0.05 |
| At 200 new accounts/month | $10.00/month |
| **Estimated monthly at moderate scale** | **~$10/month** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Security signal — users feel the product is legitimate and their account is protected |
| **Real** | Prevents fake/bot account creation; protects community quality; enables account recovery; reduces support burden from duplicate or abandoned accounts |

#### Acquisition Impact
**Moderate–High.** Verified user accounts are a higher-quality asset than unverified ones. A buyer evaluating Community Accounts as a growth channel wants to know the user base is real. Phone-verified accounts also support ARPU analysis (one account = one person) and reduce fraud risk in any monetization model.

---

### UC-07 — Two-Way SMS Support ("Text HELP")

**Product:** ScopeDOPE
**Status:** Implement post-launch, when support volume justifies it (~500–1,000 installs)

#### Level of Effort
**Medium.** Options in increasing complexity:
1. **Basic:** Inbound SMS to the 800 number forwarded to Jason's cell — zero code, immediate
2. **Intermediate:** Twilio Studio no-code flow — keyword routing (HELP → auto-reply with support URL; BUG → Jira ticket creation webhook)
3. **Advanced:** Full webhook integration with `feedback-service` to log inbound SMS as support tickets

Recommend starting at Level 1, graduating to Level 2 at ~500 installs.

#### Cost
| Item | Cost |
|---|---|
| Inbound SMS to toll-free | $0.0075/message |
| Twilio Studio | Included in standard account |
| At 50 support SMS/month | ~$0.38/month |
| **Estimated monthly** | **<$1/month at early scale** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Accessibility — a published support SMS number signals that a real company is behind the product; lowers the barrier to reaching out vs. filling out a form |
| **Real** | Higher support conversion rate (users who would abandon a form will text); early user feedback channel that surfaces issues before they become App Store reviews |

#### Acquisition Impact
**Moderate.** A documented, operational support channel (even SMS-forwarded) is more attractive than "email only" or "submit a form." It shows the product is supported and the company is reachable — both relevant to a buyer's assessment of churn risk and brand reputation.

---

### UC-08 — Job Completion SMS

**Product:** Gunsmith Shop Management SaaS (Brief #13)
**Status:** Implement as part of Gunsmith SaaS build (after Club SaaS v1.0)

#### Level of Effort
**Low** (within the Gunsmith SaaS context). One trigger point: when a job status is set to "Ready for Pickup," fire an SMS to the customer's phone. ~10 lines of code once the SaaS has a job status model.

#### Cost
| Item | Cost |
|---|---|
| Outbound SMS | $0.0079/message |
| At 100 job completions/month per shop | ~$0.79/month per shop |
| **Estimated monthly per shop** | **<$1/month** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Modern, professional service — customers expect SMS notifications from any service business in 2026; its absence feels outdated |
| **Real** | Reduces inbound "is my gun ready?" calls (gunsmiths' most common interruption); faster customer pickup turnaround improves shop throughput; directly reduces the single most common complaint in gunsmith shop reviews |

#### Acquisition Impact
**Moderate.** Job completion SMS is a table-stakes feature for any shop management SaaS. Its presence is not a differentiator — its absence is a deficiency. Building it correctly (with 10DLC compliance) means a buyer doesn't inherit a carrier-filtering problem.

---

### UC-09 — Service Alerting / Outage Notifications

**Product:** CBB Infrastructure (all hosted services)
**Status:** Implement immediately after account creation

#### Level of Effort
**Low.** One outbound SMS triggered by a monitoring webhook (uptime monitor, Azure alert, or a simple cron health check against `feedback-service`). ~10 lines of Python or a no-code Twilio webhook. No carrier registration required at this volume.

#### Cost
| Item | Cost |
|---|---|
| Outbound SMS | $0.0079/message |
| At ~10 alerts/month (optimistic) | ~$0.08/month |
| **Estimated monthly** | **<$1/month** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | N/A — internal operational; customers don't see it |
| **Real** | Instant awareness of service degradation without needing to watch a dashboard; minutes saved in incident response directly reduces customer-facing downtime |

#### Acquisition Impact
**Moderate.** A buyer's due diligence will ask "how do you know when something breaks?" A documented, automated alerting pipeline — even a simple one — answers that question cleanly. Its absence signals operational immaturity.

---

### UC-10 — SendGrid Inbound Email Parsing

**Product:** `feedback-service` / all CBB products
**Status:** Implement after UC-03 (SendGrid) is live

#### Level of Effort
**Medium.** SendGrid Inbound Parse webhook forwards email received at a CBB domain address (e.g., `support@scope-dope.com`) to a `feedback-service` endpoint as a parsed JSON payload. Requires:
- MX record pointed to SendGrid on the target subdomain
- New Flask route in `feedback-service` to receive and log/route parsed email
- Optional: forward to Jira as a support ticket

#### Cost
| Item | Cost |
|---|---|
| SendGrid Inbound Parse | Included in all SendGrid plans (including free) |
| **Estimated monthly** | **$0** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Customers can email a real address and get a response — familiar, low-friction support channel |
| **Real** | Unifies all inbound support (web form, SMS, email) into a single intake pipeline; eliminates manual monitoring of a support inbox; every inbound email becomes a structured record |

#### Acquisition Impact
**Moderate–High.** A unified, logged support intake pipeline is a demonstrable operational asset. A buyer sees structured support history — volume trends, response time, issue categories — rather than a buried Gmail thread. This directly informs their post-acquisition support cost modeling.

---

### UC-11 — Match Registration Confirmation SMS

**Product:** Club & Match Management SaaS (Brief #02)
**Status:** Implement alongside UC-05 at Club SaaS build

#### Level of Effort
**Low** (within Club SaaS). Separate trigger from UC-05 reminders — fires immediately at registration completion. Same 10DLC pipeline and Messaging Service as UC-05; no additional compliance setup required.

#### Cost
| Item | Cost |
|---|---|
| Outbound SMS | $0.0079/message |
| Messaging Service surcharge | $0.0025/message |
| At 500 registrations/month | ~$5.20/month (shared 10DLC campaign with UC-05) |
| **Estimated monthly** | **~$5/month incremental to UC-05** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Instant confirmation that registration went through — eliminates the "did it work?" anxiety common with online registration |
| **Real** | Reduces duplicate registrations and support requests ("I'm not sure if I registered"); the confirmation SMS becomes the shooter's reference for match details (date, location, time) — they screenshot it |

#### Acquisition Impact
**High** (as part of the UC-05 pipeline). Confirmation + reminder + score + cancellation is a complete communication arc. A buyer sees a full-lifecycle SMS engagement model, not a one-off notification. Each message type adds to sender reputation and engagement data.

---

### UC-12 — Match Waitlist Notifications

**Product:** Club & Match Management SaaS (Brief #02)
**Status:** Implement as Club SaaS matures (post-v1.0)

#### Level of Effort
**Medium.** Requires Club SaaS to implement a waitlist model (ordered queue per match, capacity tracking). When a spot opens:
- Fire SMS to next person on waitlist
- Include a reply-YES or link-to-claim mechanic with a time window (e.g., 30 minutes)
- If not claimed, advance to next waitlist position

The SMS send itself is trivial; the waitlist state machine is the complexity.

#### Cost
| Item | Cost |
|---|---|
| Outbound SMS | $0.0079/message |
| Messaging Service surcharge | $0.0025/message |
| At 50 waitlist notifications/month | ~$0.52/month |
| **Estimated monthly** | **<$1/month** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Fairness and transparency — shooters trust that the waitlist is real and they'll be notified promptly |
| **Real** | Match directors fill cancellation spots without manual outreach; shooters who would otherwise miss a match get in — increases match fill rates and match director NPS; drives re-engagement with the app for waitlisted users |

#### Acquisition Impact
**High** (as part of the Club SaaS SMS ecosystem). Waitlist management is a feature match directors actively request — it solves a real operational pain point. For a buyer, it demonstrates product depth and stickiness beyond basic registration.

---

### UC-13 — Chronograph Session SMS Export

**Product:** ScopeDOPE (Brief #07 — Chronograph BLE Integration, v2.0)
**Status:** Implement at v2.0 chronograph integration

#### Level of Effort
**Low** (within the chronograph feature). After a velocity string is captured, offer an in-app option to SMS the summary to the shooter's own number. One outbound SMS, no Messaging Service required at this volume.

#### Cost
| Item | Cost |
|---|---|
| Outbound SMS | $0.0079/message |
| At 500 session exports/month | ~$3.95/month |
| **Estimated monthly** | **~$4/month at moderate use** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Novelty and convenience — "text me my velocity string" is a memorable, shareable feature that competing calculators don't have |
| **Real** | Gets session data off the device immediately without requiring the shooter to screenshot or remember to export; SMS lands in the shooter's message history as a permanent record even if the app is uninstalled |

#### Acquisition Impact
**Low–Moderate.** Not a moat individually, but contributes to the "ScopeDOPE does things calculators don't" narrative. Differentiators accumulate — a buyer sees a product that uses its communications infrastructure creatively across multiple features.

---

### UC-14 — Wholesale / Dealer Inquiry Routing

**Product:** CBB Corporate
**Status:** Implement when inbound dealer/wholesale inquiries begin (~1,000+ installs)

#### Level of Effort
**Low–Medium.** A dedicated Twilio number (or Studio flow on the existing 800 number) routes inbound "dealer inquiries" calls or SMS to a Twilio Studio flow that:
- Sends an auto-reply with next steps
- Creates a Jira CBB ticket via webhook
- Notifies Jason via SMS

No complex code — primarily Twilio Studio no-code configuration.

#### Cost
| Item | Cost |
|---|---|
| Additional local number (if separate from 800) | $1.15/month |
| Twilio Studio | Included |
| **Estimated monthly** | **~$1–2/month incremental** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Professional inquiry handling — dealers and distributors expect a structured process, not a personal cell |
| **Real** | Every inbound inquiry is captured as a structured record; none fall through the cracks; pipeline visibility for business development |

#### Acquisition Impact
**Moderate–High.** A documented, operational dealer/wholesale inquiry pipeline signals scale readiness. A buyer evaluating distribution strategy wants to see that inbound interest is captured and tracked — not dependent on Jason personally answering a call.

---

### UC-15 — Club SaaS Admin Two-Factor Authentication

**Product:** Club & Match Management SaaS (Brief #02)
**Status:** Implement at Club SaaS build (admin accounts only)

#### Level of Effort
**Low.** Uses the same Twilio Verify API as UC-06. Admin (match director) accounts get SMS 2FA on login. Shooter/participant accounts do not require 2FA — phone verification (UC-06) is sufficient at that tier.

#### Cost
| Item | Cost |
|---|---|
| Per OTP verification (admin logins) | $0.05 |
| At 50 admin logins/month | $2.50/month |
| **Estimated monthly** | **~$2–3/month** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Security and trust — match directors feel their club data and registration records are protected |
| **Real** | Prevents unauthorized access to match registration data, shooter contact information, and financial records (if Club SaaS handles payments); reduces liability exposure from a breach |

#### Acquisition Impact
**Moderate–High.** Any SaaS handling personal data (names, phone numbers, potentially payment info) is expected to have 2FA on administrative accounts. Its absence is a diligence flag — and a potential liability. Its presence, properly documented, is a clean checkbox in a security review.

---

### UC-16 — SMS DOPE Card Delivery

**Product:** ScopeDOPE / DOPE Card Generator (Brief #04)
**Status:** Evaluate at ~1,000 installs; low priority

#### Level of Effort
**High.** Requires:
- DOPE card generation pipeline capable of producing a shareable image (PNG/PDF)
- MMS attachment support (Twilio MMS — separate from SMS, higher cost)
- Inbound keyword parsing ("Text DOPE to 1-800-XXX-XXXX")
- Some mechanism to identify the shooter's profile/load (anonymous inbound SMS has no account context — requires a PIN or short code)

The core complexity is the stateless identity problem: an inbound SMS has no app context. Workarounds exist (PIN-based, link-to-claim) but add friction.

#### Cost
| Item | Cost |
|---|---|
| Outbound MMS | $0.0200/message (vs. $0.0079 for SMS) |
| At 200 MMS/month | $4.00/month |
| **Estimated monthly** | **~$4/month at moderate use** |

#### Customer Value
| Type | Value |
|---|---|
| **Perceived** | Novelty — "text for your DOPE card" is a memorable marketing hook; shareable on social media |
| **Real** | Limited without solving the identity problem cleanly; most shooters will use the in-app export; primary value is as a marketing/demo tool at matches and events |

#### Acquisition Impact
**Low.** Creative, but not a moat and not acquisition-relevant at this stage. Worth revisiting if the DOPE Card Generator (Brief #04) gains traction as a standalone web tool with its own user base.

---

## Summary Matrix

| UC | Use Case | Product | Effort | Est. Monthly Cost | Customer Value | Acquisition Impact | Recommended Timing |
|---|---|---|---|---|---|---|---|
| UC-01 | 800 Number | CBB Corporate | Low | ~$2–3 | Perceived: professional presence / Real: transferable asset | **High** | At account creation |
| UC-02 | Feedback SMS | feedback-service | Low | <$1 | Internal operational | Moderate | At account creation |
| UC-03 | SendGrid Email | All products | Low–Med | $0 (free tier) | Perceived: branded email / Real: deliverability | **High** | At account creation |
| UC-04 | Caller ID Masking | CBB Corporate | None | <$1 | Perceived: consistent number / Real: private cell + call records | Moderate | Automatic with UC-01 |
| UC-05 | Match Day SMS | Club SaaS | Medium | ~$27 | Perceived: convenience / Real: no-shows reduced, re-engagement | **Very High** | At Club SaaS build |
| UC-06 | Phone Verification | Community Accounts | Low | ~$10 | Perceived: security / Real: account quality | Moderate–High | At Community Accounts build |
| UC-07 | Two-Way Support SMS | ScopeDOPE | Medium | <$1 | Perceived: accessibility / Real: feedback channel | Moderate | ~500–1,000 installs |
| UC-08 | Job Completion SMS | Gunsmith SaaS | Low | <$1/shop | Perceived: modern service / Real: reduced interruptions | Moderate | At Gunsmith SaaS build |
| UC-09 | Service Alerting | CBB Infrastructure | Low | <$1 | Internal operational | Moderate | At account creation |
| UC-10 | Inbound Email Parsing | feedback-service | Medium | $0 | Perceived: familiar support channel / Real: unified intake | Moderate–High | After UC-03 live |
| UC-11 | Registration Confirmation | Club SaaS | Low | ~$5 | Perceived: confirmation / Real: reference artifact | **High** (part of UC-05 arc) | At Club SaaS build |
| UC-12 | Waitlist Notifications | Club SaaS | Medium | <$1 | Perceived: fairness / Real: fill rate + re-engagement | **High** | Club SaaS post-v1.0 |
| UC-13 | Chrono Session Export | ScopeDOPE | Low | ~$4 | Perceived: novelty / Real: persistent off-device record | Low–Moderate | At v2.0 chrono build |
| UC-14 | Dealer Inquiry Routing | CBB Corporate | Low–Med | ~$1–2 | Perceived: professional / Real: captured pipeline | Moderate–High | ~1,000+ installs |
| UC-15 | Admin 2FA | Club SaaS | Low | ~$2–3 | Perceived: security / Real: liability reduction | Moderate–High | At Club SaaS build |
| UC-16 | SMS DOPE Card Delivery | ScopeDOPE | High | ~$4 | Perceived: novelty / Real: limited without identity solution | Low | ~1,000 installs, low priority |

---

## Recommended Rollout Sequence

### Phase 1 — At Account Creation (Day 1)
1. Create Twilio account
2. Purchase 800 number → configure forwarding (UC-01, UC-04 automatic)
3. Activate SendGrid, authenticate domains (UC-03)
4. Wire feedback-service SMS notification (UC-02)
5. Wire service alerting webhook (UC-09)
6. Configure SendGrid Inbound Parse for `support@scope-dope.com` (UC-10)

**Total Phase 1 cost: ~$3–4/month**

### Phase 2 — Post-Launch (~500–1,000 installs)
7. Publish support SMS number, configure basic forwarding or Twilio Studio flow (UC-07)
8. Configure dealer inquiry routing via Twilio Studio (UC-14)

**Incremental cost: ~$1–2/month**

### Phase 3 — Club SaaS Build
9. 10DLC registration + match day SMS pipeline (UC-05)
10. Registration confirmation SMS (UC-11) — same pipeline, incremental trigger
11. Admin 2FA via Twilio Verify (UC-15)
12. Waitlist notifications (UC-12) — post-v1.0

**Incremental cost: ~$35/month (covered by SaaS subscription revenue)**

### Phase 4 — Community Accounts Build
13. Twilio Verify OTP integration for shooter accounts (UC-06)

**Incremental cost: ~$10/month at moderate scale**

### Phase 5 — v2.0 Chronograph Integration
14. Chronograph session SMS export (UC-13)

**Incremental cost: ~$4/month**

### Phase 6 — Gunsmith SaaS Build
15. Job completion SMS (UC-08)

**Incremental cost: <$1/month per shop (recoverable in subscription pricing)**

### Phase 7 — Evaluate at ~1,000 installs
16. SMS DOPE card delivery (UC-16) — only if DOPE Card Generator has standalone traction; identity problem must be solved first

---

## Compliance Notes

- **TCPA compliance** is required for any A2P SMS in the US. Twilio Messaging Services handle STOP/HELP/CANCEL opt-out automatically — always use a Messaging Service (not a raw phone number) for application-triggered bulk SMS (UC-05, UC-08).
- **10DLC registration** is required for domestic A2P SMS at any meaningful volume. Budget $4 brand registration (one-time) + $15/month campaign fee per use case. Required before UC-05 or UC-08 go live.
- **GDPR/CCPA** — if collecting phone numbers, include a consent disclosure at the point of collection (registration form). Retain opt-in records.

---

## Open Items

- [ ] 800 number selection — TBD (user researching separately)
- [ ] SendGrid domain authentication — requires DNS access to `coldboreballisticsllc.com` and `scope-dope.com` (Namecheap CBB account)
- [ ] 10DLC brand/campaign registration — execute before Club SaaS SMS goes live

---

## Document Control

| Field | Value |
|---|---|
| **Document owner** | `jschwefel@coldboreballisticsllc.com` |
| **Classification** | Confidential (03_-_Confidential/) |
| **Location** | `OneDrive/CBB_Corporate/03_-_Confidential/Infrastructure/Twilio/TWILIO_USE_CASE_ANALYSIS.md` |
| **Cross-references** | `Twilio_Architecture_Reference.md`; `Twilio_Operating_Runbook.md` |
| **Created** | 2026-06-05 |
| **Last updated** | 2026-06-05 |
| **Next full review due** | 2027-06-05 |

---

## Revision Control Block

| Rev | Date | Changed By | Reviewed By | Approved By | Summary |
|-----|------|------------|-------------|-------------|---------|
| 0.9 | 2026-06-05 | jschwefel | — | — | Initial release |
