86 lines
3.2 KiB
Markdown
86 lines
3.2 KiB
Markdown
|
---
|
||
|
|
tags:
|
||
|
|
- reference
|
||
|
|
- sms
|
||
|
|
- pest-control
|
||
|
|
- pest-control-spring-2026
|
||
|
|
- niche-automation-prospecting
|
||
|
|
source: niche-automation-prospecting
|
||
|
|
date: 2026-03-31
|
||
|
|
---
|
||
|
|
|
||
|
|
# 10DLC ISV Setup Guide for OnCadence
|
||
|
|
|
||
|
|
**Date:** 2026-03-31
|
||
|
|
**Context:** Practical guide for managing 10DLC registration on behalf of pest control clients via Twilio ISV architecture.
|
||
|
|
|
||
|
|
## Architecture
|
||
|
|
- OnCadence = primary Twilio account (ISV/CSP)
|
||
|
|
- Each pest control client = Twilio subaccount
|
||
|
|
- Each subaccount gets: Secondary Customer Profile, Brand registration, Campaign registration, dedicated phone number(s)
|
||
|
|
- If one client gets flagged, others are unaffected
|
||
|
|
|
||
|
|
## What OnCadence Submits (via TrustHub API)
|
||
|
|
- ISV creates Primary Business Profile once
|
||
|
|
- Per client: Secondary Customer Profile with client's identity data
|
||
|
|
- Brand registration + Campaign registration per client
|
||
|
|
|
||
|
|
## What Each Client Provides (5-field intake form)
|
||
|
|
1. Legal business name (must match IRS EIN records exactly)
|
||
|
|
2. EIN
|
||
|
|
3. Business address (no P.O. boxes)
|
||
|
|
4. Website URL (Facebook Business page acceptable if no website)
|
||
|
|
5. Owner name, email, mobile number
|
||
|
|
|
||
|
|
## No-Website Edge Case
|
||
|
|
- Facebook Business page accepted by some carriers
|
||
|
|
- Google Business Profile URL sometimes works
|
||
|
|
- Page must "bear some relationship" to business name
|
||
|
|
- Companies with zero web presence = genuine friction point
|
||
|
|
|
||
|
|
## Sole Proprietors (No EIN)
|
||
|
|
- Lower throughput path: 1,000 msgs/day on T-Mobile
|
||
|
|
- Limited to one campaign, one number
|
||
|
|
- Requires mobile phone OTP verification
|
||
|
|
- Adequate for single-tech pest control shops
|
||
|
|
|
||
|
|
## Cost Per Client
|
||
|
|
|
||
|
|
| Item | Cost |
|
||
|
|
|---|---|
|
||
|
|
| Brand registration | $4.50 one-time |
|
||
|
|
| Campaign vetting | $15.00 one-time |
|
||
|
|
| Authentication verification | $12.50 one-time |
|
||
|
|
| **Total one-time** | **~$32** |
|
||
|
|
| Campaign monthly fee | $1.50-10/mo |
|
||
|
|
| Twilio number rental | ~$1.15/mo |
|
||
|
|
| Carrier surcharge/SMS | $0.003-0.005/msg |
|
||
|
|
| **Practical monthly (500 SMS)** | **~$10-20/mo** |
|
||
|
|
|
||
|
|
## Timeline
|
||
|
|
- Twilio announced direct carrier connections March 24, 2026 — registration now "days not weeks"
|
||
|
|
- Realistic: 5-10 business days for clean submission
|
||
|
|
- Tell clients 2 weeks, aim for 1
|
||
|
|
|
||
|
|
## Common Rejection Causes
|
||
|
|
- Legal name doesn't match IRS records (most common)
|
||
|
|
- Website down, parked, or doesn't mention business
|
||
|
|
- Vague campaign description
|
||
|
|
- Missing opt-out language in sample messages
|
||
|
|
|
||
|
|
## OnCadence Implementation
|
||
|
|
1. Build standardized intake form (5 fields)
|
||
|
|
2. Pre-write one campaign template for pest control: "Appointment Reminders / Customer Care" use case
|
||
|
|
3. Include sample messages with STOP opt-out language
|
||
|
|
4. Submit via Twilio TrustHub API using subaccount-per-client architecture
|
||
|
|
5. Budget ~$32 into setup fee (trivial at $3,500-5,000 implementation price)
|
||
|
|
|
||
|
|
## Key Rules
|
||
|
|
- Cannot use OnCadence's identity for client registrations — must use client's actual EIN/name
|
||
|
|
- Cannot share one number across multiple client brands (prohibited since Summer 2023)
|
||
|
|
- Each client gets dedicated Twilio long-code number registered to their brand
|
||
|
|
- Forward callbacks to client's actual business line
|
||
|
|
|
||
|
|
## ISV Legal
|
||
|
|
Yes, OnCadence can submit registrations on behalf of clients. This is the designed ISV path in Twilio's system. The registration attests the sending business identity, which must be the client's — but the ISV handles the submission process.
|