Org Web Adapter

Editing hungryroot/jira/be_7301_move_braze_sms_opt_out_from_address_endpoitn_to_dedicated_customer_endpoint.org

:PROPERTIES:
:ID:       f191ead4-fe45-479c-ae8b-64385de502ef
:END:
#+title: BE-7301 Move Braze SMS opt-out from address endpoitn to dedicated customer endpoint

- source :: https://hungryroot.atlassian.net/browse/BE-7301
- tags   :: [[id:3a477c02-e26d-40f7-a719-0aa1cd169dd8][Hungryroot API Project]]
- epic   :: [[id:86327fb4-0f66-4bc6-9068-c414cea77042][EP-411 Eng Parking Lot]]
- sprint :: [[id:211bb652-f918-4774-9611-ec6c3a77c72b][HR BE Sprint 105]]
- status :: [[id:4d41d978-e56f-45c1-88d1-e2c76510972e][Status - Complete]]

* Tasks
** DONE Add opt-out flow to the sms_consent app :work:feature:hungryroot:sprint105:be7301:ep411:smsconsent:
:PROPERTIES:
:ID:       9188098c-4477-bdd8-28db-bf4f093787d7
:END:
* Description
A fast-followup to adding our new SmsConsentRecord data model, we need to add
the ability to store opt-out values in the same records table. This should use
the same sms_consent model and enable sending “sms_opt_in” value as “false”
should result in an SmsConsentRecord table entry with the “consent_action” value
being “OPT-OUT”