Systems involved
| System | Role |
|---|---|
| Carrier billing / OSS | Source list of active DIDs and the registered address per DID. |
| Intrado / Bandwidth E911 / RedSky | E911 registration system and address validation API. |
| USPS / address validation API | Authoritative address normalization. |
| Splynx / Sonar / homegrown CRM | Subscriber contact lookup. |
| Gmail / Outlook | Subscriber re-attestation request. |
| Twilio SMS | Reminder for non-responding subscribers. |
| Studio Procedures | E911 validation campaign runbook. |
| Files / SharePoint | Compliance evidence pack. |
Walkthrough
Build the master DID + address join
Copilot pulls every active DID and joins to the registered E911 address from Intrado. The result is a row per DID with subscriber, location identifier, address-on-file, and last attestation date.
Validate addresses
Each address is sent through the USPS validation API in batches. Three classes come back: validated, validated-with-corrections, and unable-to-validate. Counts: 78,300 / 4,200 / 1,500.
Apply auto-corrections where safe
The 4,200 validated-with-corrections rows get a Markdown report listing the change. Routine corrections (zip-code +4, abbreviation expansion, casing) are auto-applied through Intrado after a sample review. Material changes go to subscriber re-attestation.
Subscriber re-attestation requests
For the 1,500 unable-to-validate and the material-change subset, Copilot drafts personalised emails through Gmail with the address on file, the proposed correction, and a one-click portal link to confirm. Sent in batches of 200 to avoid overwhelming support.
SMS reminders
After 7 days, Copilot finds subscribers who haven’t responded and sends a Twilio SMS reminder. After 14 days, support follows up by phone.
Track responses
Each response updates the master campaign table. Copilot maintains a live dashboard with response rate by region, by tier, by DID type.
Handle non-responders carefully
For subscribers who have not responded by the deadline, the carrier must not break their 911 — the procedure flags them for a phone call from compliance, not a service suspension.
Where Studio earns its keep
- The DID list, the E911 registrations, and the validation API live in one workspace — no sequential exports across three systems.
- Subscriber re-attestation goes out personalised, with the actual data on the line, instead of as a generic “please verify your address” email.
- The non-responder workflow respects emergency service — the system does not casually disable 911 for someone who didn’t open an email.
- The evidence pack is generated from the campaign state at any point in time, so the regulator’s question is answered with a current PDF.
Related
Procedures
E911 validation campaign runs every quarter against the current DID list.Connectors and MCP
Intrado, USPS validation, Twilio, and Gmail as Copilot tools.