Page MenuHomePhabricator

U.S. Payments Wiki form variant with Phone Number and SMS opt-in
Open, Needs TriagePublic

Description

Hey fr-tech, filing this request that I've discussed with @AKanji-WMF:

Y'all have done amazing work getting us set up to start including SMS as a feature in our banners. We are going to trial it as an alternative to "Maybe Later" for people who might want to give us a cellphone number instead of email address.

But separate from that, one critical means of building our SMS list would be to see if we can actually integrate a Phone field + permission to SMS directly onto Payments Wiki, as a standard part of the checkout process.

I'm attaching a screenshot of how this might look > you can see the phone field and checkbox in the form.

If there is capacity to work on this, it could be put into immediate use whenever it's ready for the end of year Big English banner campaign.

image.png (1×948 px, 283 KB)

Event Timeline

@spatton spoke with FR-Tech and we recommend implementing RML flow first - let's talk

  • technical changes to form itself are relatively nominal
  • but integrating into Acoustic consent flow will be high lift - we'll need to understand and asses how API handling works for current scoped RML flow.

@Eileenmcnaughton @Ejegg - had a quick convo with Sam/Eric

  • we have collected phone numbers on our donate form before - but we'd have to figure out how to also send consent to Acoustic along with the phone number - as you've flagged. So this would need scoping.

*A campaign note: We'd want to confirm SMS with them pretty soon after sign up (i.e. you've opted into WMF texts).

  • This is a highly desired feature! Ideal in place by (in order of preference):
  • December
  • before TY in January 20
  • before Springlish

@bsisolak would appreciate your thoughts on what considerations need to be made around capturing consent data as we work to enable SMS opt-in in the PaymentsWiki form. CC @SKivlehan-WMF

My understanding is that when we capture consent information we need to push the date & source into Acoustic and we need to know that we have taken the correct steps / wording with the consent wording - I don't know if we want to track the wording that we use anywhere other than github - ie so if someone challenges what the wording was when they filled in the form on 20 March 2025 we can confirm that point in time

Capturing the exact consent wording is not likely necessary (though it surely doesn't hurt), so long as the consent date/time is recorded and maintained properly. For the wording, I would suggest replicating what has been done on the banners (screenshot below) (link to example banner --> Click "Maybe Later" link, then click "Send me a text message"). This language has been vetted by your legal counsel and the carriers who approved the short code.

I'll note that in addition to the consent and disclaimer language, you should label the input field "Mobile Phone Number" to reduce the number of landline numbers submitted.

image.png (770×924 px, 71 KB)

AKanji-WMF changed Risk Rating from N/A to Informational.Apr 16 2025, 6:18 PM

Note we should probably store IP address

From @SKivlehan-WMF :

a list: URL, name of checkbox/field (RML vs. Payments for example), date and time, IP address, useragent string. Follow up with Acoustic?

@Eileenmcnaughton - store in bar char, phone consent table

Whoa 'bar char' - sounds way more fun - but I did save varchar(255) :-) So we can store up to 255 characters there - eg. ip address, limited extra data

Steps:

  • frontend UI - make the page as variant
  • make collect the additional data acoustic needed (ip, user agent and date time)
  • Send the new data to a new queue
  • consume the queue to civi and eileen help with push those to Acoustic

Change #1193298 had a related patch set uploaded (by Cstone; author: Cstone):

[mediawiki/extensions/DonationInterface@master] WIP: Add variant for SMS optin

https://gerrit.wikimedia.org/r/1193298

@spatton Would we want to add front end validation on the consent check? Like if a donor types in their phone number but doesn't check the box it errors. Would we be able to do anything with the phone number if we didn't have the consent?

In discussing with @SKivlehan-WMF - we're fine to do either (providing we have legal okay to collect phone numbers without consent).

The reason we might to add the phone number without collecting consent would be to support later "round trip" data enrichment if they (for example) fill out an SMS RML form and opt in at that point.

  • unrelated - just making sure that folks who opt in via this form would have the same "SMS consent granted" activity generated (like the RML form does?). CC: @Lars

Talking to Lars and Eileen, for the first variant we are going to match the functionality to the acoustic numbers we have in civi, in that we only have them in civi if they have the consent. We can change this in the future.

We are also going to use the same phone location type as civi uses for acoustic but use the source to distinguish that they came from the payments form.

Change #1214236 had a related patch set uploaded (by Cstone; author: Cstone):

[wikimedia/fundraising/crm@master] WIP: Handle phone number from the payments form

https://gerrit.wikimedia.org/r/1214236

Change #1193298 merged by jenkins-bot:

[mediawiki/extensions/DonationInterface@master] Add variant for SMS optin

https://gerrit.wikimedia.org/r/1193298