Business texting
Texttive
Business texting for reminders, order updates, two-way conversations and promotions from local or toll-free numbers. Texttive handles opt-outs, quiet hours and carrier registration, and customers pay only for what they send.

The problem
Business texting is governed by carrier registration (10DLC) and TCPA rules, and the launch depended on outside parties: Twilio, carrier approval, Stripe and Mailgun. Any one of them could block go-live.
My role
- Mapped each vendor dependency and its risk up front and planned around the approval path.
- Built compliance into the product before applying: TCPA opt-out handling and quiet hours.
- Led carrier 10DLC registration through to approval.
Key decisions
| # | Decision | Why |
|---|---|---|
| 1 | Prepaid wallet instead of monthly plans | Customers pay only for what they send |
| 2 | Compliance in the product, not the customer's hands | Opt-outs and quiet hours enforced automatically |
| 3 | Separate queues for messages, lookups and webhooks | One slow job type cannot block the others |
Results
- Carrier 10DLC approval received; live with SMS, MMS, carrier lookup, API and webhooks.
- AI Smart Replies add-on suggests replies for the business to approve.
- Texting is reused by RepComet, so its carrier registration and opt-out handling serve two products.
- Role
- Project manager and lead developer
- Users
- Small businesses
- Pricing
- Prepaid, pay per message
- Stack
- Laravel, Redis queues, Twilio, Stripe
- Status
- Live, carrier 10DLC approved
- Live
- texttive.com
- Employer
- Social Points Media