re-file with twilio

barrettruth commented

2026-04-17 17:45:37 +00:00

Problem

Twilio remains the intended SMS transport, but the tracker needs the current Twilio work re-filed against reminders v1.

Scope

Review the existing Twilio adapter work from #196 and current config needs.
Re-file any remaining setup, credential, webhook, or delivery-status work as concrete child issues.
Keep credential names documented by name only; never put real values in issue text.

Acceptance criteria

Twilio SMS has an explicit path under #189 / v0.1.1.
Any required secret names are documented without secret values.

## Problem Twilio remains the intended SMS transport, but the tracker needs the current Twilio work re-filed against reminders v1. ## Scope - Review the existing Twilio adapter work from #196 and current config needs. - Re-file any remaining setup, credential, webhook, or delivery-status work as concrete child issues. - Keep credential names documented by name only; never put real values in issue text. ## Acceptance criteria - Twilio SMS has an explicit path under #189 / v0.1.1. - Any required secret names are documented without secret values.

barrettruth commented

2026-04-17 18:37:21 +00:00

The toll-free verification request for +leaked lol has been rejected for use by Barrett Ruth.

Reason code: 30509: Opt-In URL Not Accessible
Reason code: 30513: Opt-in - Consent for messaging is a requirement for service

What should I do next?
Edit the verification via the Messaging Compliance API or Console to fix the issue and resubmit
Note that you have 7 days to resubmit. Resubmissions within this window will go to a prioritized resubmission queue. After 7 days the submission will "expire", meaning it can still be re-submitted for review but will no longer be prioritized, so its turnaround time will be similar to a new submission.

Thank you,
Twilio Consumer Trust Team

Details:
Toll Free Verification Request SID: leaked lol
Account SID: leaked lol
Phone Number: +insert

The toll-free verification request for +leaked lol has been rejected for use by Barrett Ruth. Reason code: 30509: Opt-In URL Not Accessible Reason code: 30513: Opt-in - Consent for messaging is a requirement for service What should I do next? Edit the verification via the Messaging Compliance API or Console to fix the issue and resubmit Note that you have 7 days to resubmit. Resubmissions within this window will go to a prioritized resubmission queue. After 7 days the submission will "expire", meaning it can still be re-submitted for review but will no longer be prioritized, so its turnaround time will be similar to a new submission. Thank you, Twilio Consumer Trust Team Details: Toll Free Verification Request SID: leaked lol Account SID: leaked lol Phone Number: +insert

barrettruth commented

2026-04-20 22:51:09 +00:00

@harivansh-afk

barrettruth commented

2026-04-20 22:51:14 +00:00

this will enable reminders

barrettruth commented

2026-04-20 22:51:37 +00:00

i can give you my secrets later, just ask when you want to take action. i think i impled these but made them blocked behind having to login, not sure

barrettruth added the

labels

2026-05-10 20:16:27 +00:00

barrettruth added this to the v0.1.1 milestone

2026-05-10 20:16:27 +00:00

barrettruth referenced this issue

2026-05-11 15:54:42 +00:00

scope: retire reminders subsystem #286

barrettruth commented

2026-05-11 15:56:07 +00:00

Owner

Change of plan: Twilio/reminder work is no longer planned. Tracker #286 owns retiring the reminder subsystem, so this issue should close with that shutdown PR.

barrettruth referenced this issue from a pull request that will close it,

2026-05-11 16:07:36 +00:00

Retire reminders subsystem #288

barrettruth closed this issue

2026-05-11 16:21:32 +00:00

barrettruth referenced this issue from a commit

2026-05-11 16:21:33 +00:00

Retire reminders subsystem (#288)