Ideas

Global SMS Consent Checkboxes and Consent Detail Language

18

Login To Vote

Global SMS Consent Checkboxes and Consent Detail Language

Communication

Idea

Allow admins to set SMS Consent Checkbox Language (HTML Global Attribute) and SMS Consent details (HTML Global Attribute) in just one place that will then be automatically applied to any public form where Mobile phone number is collected. The SMS Consent detail would be an additional section of HTML that would be displayed at the bottom of forms where applicable as a disclaimer.

Ministry Need

Many churches heavily use texting to communicate with our communication. As 10DLC Campaign registry requirements evolve it will be impossible for churches to comply with 10DLC requirements and also follow Rock development best practices.

Context

According to our texting vendor Intulse,  A2P 10DLC registration are seeing more rejections related to missing, incomplete, or inaccurate SMS Consent language on forms. It is now expected that you will have an SMS consent checkbox and SMS Consent details on every form that contains a mobile phone number field.

Making this happen in Rock and doing it consistently is no small undertaking. There are multiple blocks to consider and their related templates and instances (i.e. registration templates, each page a block is included on, workflow types).

Here is a list of blocks that potentially collect mobile phone number and their configuration options as of Rock version 17.1.

Public Profile Edit

  • SMS Consent Checkbox Language: "I would like to receive important text messages"
  • SMS Consent Checkbox Language Configurable: No, but you can configure 'Mobile Highlight Text' above the Mobile field

Sign-Up Register

  • SMS Consent Checkbox Language: "Allow SMS Messages"
    SMS Consent Checkbox Language Configurable: No

Registration Entry

  • SMS Consent Checkbox Language: "Give your consent to receive SMS messages by simply checking the box."
  • SMS Consent Checkbox Language Configurable: No
  • Global Setting to default or lock Template field "Show SMS Opt-In": No

New Account

  • SMS Consent Checkbox Language: "SMS"
  • SMS Consent Checkbox Language Configurable: No

Connection Opportunity Signup

  •  SMS Consent Checkbox: No option exists to add a SMS Consent Checkbox

Family Pre Registration

  • SMS Consent Checkbox Language: "Give your consent to receive SMS messages by simply checking the box."
  • SMS Consent Checkbox Language Configurable: No

Workflow Entry Person Entry (With Form Action and Enable Person Entry)

  • SMS Consent Checkbox Language: "Give your consent to receive SMS messages by simply checking the box."
  • SMS Consent Checkbox Language Configurable: No
  • Global Setting to default or lock Template field "SMS Opt-In": No

We found it desirable to go with the following SMS Consent Checkbox Language HTML:

"I consent to receive important text messages from College Church. Unchecking this box will stop ALL text messages from College Church. For additional options manage your text preferences."

Based on our SMS usage, Intulse additionally suggested we add the following SMS Consent details to the bottom of every form collecting a mobile number:

SMS Consent Details

Photo of Tony ViscontiSubmitted by Tony Visconti, College Church  ·   ·  Communication
Remove Votes
Login to add a comment...

Submission Success Tips

Cultivate your ideas for maximum impact with these helpful submission tips that will increase the chances of your brilliant concepts becoming reality.

  • Clear Title: Craft a straightforward and descriptive title that instantly conveys the essence of your idea.
  • Concise Description: Provide an idea description that is succinct, ensuring it effectively communicates the concept without unnecessary verbosity.
  • Provide Additional Details: With a concise description complete, now provide any other details that are needed to better understand the requirements.
  • Thorough Ministry Need Review: Provide a comprehensive overview of the ministry need your idea addresses, emphasizing its significance.
  • Cover the WHY: Clearly articulate the rationale behind your idea, explaining why it's essential and how it aligns with the organization's goals and mission. Oftentimes a clear "why" sheds light into other possible options.