Story: As a user, I want to subscribe for notifications about a piece of legislation I am interested in

[kwhinnery]

See this doc for more background.

Subscription Flow

1. User texts hello to a Twilio number for the notification system
2. User receives a welcome message detailing the commands that can be sent to the system
3. User texts list to see the types of data they can subscribe to
4. User texts subscribe bill to subscribe for notifications on a specific piece of legislation. The system responds by asking for their state of residence.
5. User texts in "mn"
6. System prompts for the name of the piece of legislation
7. User texts "HF 20210"
8. User is now subscribed for updates on House File 90210 in the MN state legislature
9. (meta) - A Notify binding is created with a tag bill;mn;hf90210

[kwhinnery]

The key element here is that we are using Notify as the storage mechanism for a user's subscriptions, in addition to the transport mechanism for Notifications.

The Notify tag we use must be built with a common convention that will allow us to dynamically create a tag that will be used for notifications later. For anyone who wants to work on this issue and has questions, hit me up in Slack.

[philnash]

A maximum of 20 tags are allowed per binding. To solely use tags for this would limit the number of subscriptions a user could have. This limit appears to be throughout the system (you could add users to a segment, but then a user can only have a maximum of 20 segments).

Is a limit of 20 subscriptions, by tag, reasonable for this MVP?