1. The Death of PHP Telephony
In traditional WordPress lead generation setups, when a customer dials a tracking number, Twilio makes an HTTP POST request to a WordPress REST API endpoint or webhook handler. That request must boot the entire WordPress core, connect to MySQL, execute theme plugins, and return TwiML XML.
This creates 1,200ms to 2,500ms of dead air before the call starts ringing. To the caller, it sounds like a dead line, causing up to 25% of emergency callers (e.g. towing, lockouts, water leaks) to hang up.
The Heatherverse Edge Solution: By moving call routing to Cloudflare Workers and Cloudflare D1 SQL, our webhook handles the call and returns valid TwiML in 15 milliseconds.
2. Zero Twilio SMS: Slack & Email Direct Dispatch
Twilio SMS has become expensive and burdened by complex carrier 10DLC registration requirements. Heatherverse enforces a clean channel separation:
- Voice Phone Calls: Routed exclusively via Twilio Voice straight to the contractor's cell in 15ms.
- Web Form Leads: Dispatched exclusively via private Slack webhooks and instant emails with rich interactive cards.
3. Multi-Tenant CRM Partitioning in D1
How do we handle dozens of contractors across multiple trades in the same county without mix-ups? We use a 4-point composite index in Cloudflare D1:
Composite Key: Site ID + Trade + City + Unique Tracking Phone
This guarantees that a plumbing lead in Waynesville never crosses wires with a concrete contractor in Johnson City or a towing call in Canton.