Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow ActionNetwork upsert_person to not change mobile opt-in status #1212

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

austinweisgrau
Copy link
Collaborator

Prior behavior opted-in all phone numbers by default, and the only alternative would be to opt-out phone numbers sent to the API. This update allows for not changing the opt-in status of the number, and changes the default from opt-in to no change. This is a more reasonable and legally compliant default behavior than opting-in.

This causes a change in behavior! If users are currently relying on the default opt-in behavior of this connector's upsert_person method, this change will break their workflow. However, it is generally not legally compliant to opt-in by default, and more likely is that many users are unknowingly setting opt-in status to "subscribed" by default in a legally non-compliant way. The new configuration will require users to explicitly pass opt-in status if they want that status to be changed in ActionNetwork.

Prior behavior opted-in all phone numbers by default, and the only
alternative would be to opt-out phone numbers sent to the API. This
update allows for not changing the opt-in status of the number, and
changes the default from opt-in to no change. This is a more
reasonable and legally compliant default behavior than opting-in.
Copy link
Contributor

@matthewkrausse matthewkrausse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This all looks good to me.

Copy link
Collaborator

@shaunagm shaunagm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approving on behalf of MK

@shaunagm shaunagm added the breaking change applied only to PRs, indicates when something has a breaking change to be flagged in release notes label Dec 12, 2024
@shaunagm shaunagm merged commit b943598 into move-coop:main Dec 12, 2024
57 checks passed
@shaunagm
Copy link
Collaborator

This link can be used in the release notes: https://www.strivemessaging.org/article/tcpa-compliance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change applied only to PRs, indicates when something has a breaking change to be flagged in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants