Last week, we received feedback from Twilio on our A2P (Application-to-Person) registration. The message was clear: our SMS opt-in flow needed work. Rather than treat this as a compliance checkbox, we saw it as an opportunity to build something better.
What Changed
We rebuilt our SMS signup experience from the ground up. The new flow includes explicit opt-in language, clear frequency expectations, and easy opt-out instructions—all visible before a user submits their phone number. No hidden checkboxes, no buried terms.
We also created dedicated privacy and terms pages. These aren't afterthoughts—they're client-rendered Next.js pages with proper component structure and full test coverage. The content is honest and readable, not buried in legal jargon.
Why It Matters
Twilio's A2P compliance requirements exist because SMS spam is a real problem. Carriers need to verify that businesses sending messages have legitimate reasons and user consent. When we ship compliance features, we're not just checking a box—we're building trust with our users and ensuring our messages actually get delivered.
For Strug City, this work touches both our public website and the internal systems that power Strug Works. When an agent dispatches a notification or a user subscribes to updates, the entire flow now meets carrier standards. That means higher deliverability and fewer headaches for everyone.
The Technical Details
The implementation includes a new SMS signup form component tested with Vitest and React Testing Library. We added client-side privacy and terms pages using Next.js App Router conventions, complete with structured content and proper SEO metadata. The entire flow is backed by tests that verify both the user experience and the compliance requirements.
We updated our test setup to handle the Next.js environment properly, ensuring that every component renders correctly and that form validation works as expected. This isn't just about passing Twilio's review—it's about building infrastructure we can trust.
What's Next
We've resubmitted our A2P registration to Twilio with the updated compliance materials. Once approved, we'll be able to scale our SMS communications with confidence. In the meantime, we're exploring additional notification channels and building out the infrastructure to let users choose how they want to hear from us—SMS, email, or in-app.
This work also sets the stage for more sophisticated agent-to-user communication patterns. As Strug Works evolves, we want agents to notify users in ways that are timely, relevant, and respectful. Getting the compliance foundation right now means we can move fast later without breaking trust.