The Connection Opportunity Signup block collects mobile phone numbers but does not provide an option for the individual to grant SMS consent.

Other public-facing Rock experiences—including Registration Entry, Group Registration, Family Pre-Registration, and workflow person entry forms—can display Rock’s standard SMS opt-in control. The Connection Opportunity Signup block should support the same consent experience.

Current Behavior

• The block can collect a mobile phone number.
• The current Obsidian implementation explicitly hides the SMS opt-in control using hideSms="true" in the block source .
• A Connection Request Boolean attribute can be displayed as a workaround, but it only saves an attribute value. It does not update PhoneNumber.IsMessagingEnabled.
• Correctly recording consent currently requires custom JavaScript, Lava, a workflow, or a plugin.

Suggested Behavior

Add a block setting named Show SMS Opt-In.

When enabled:

• Display Rock’s standard SMS consent checkbox with the mobile phone field.
• Use the centrally configured SMS opt-in message.
• Save the submitted choice to PhoneNumber.IsMessagingEnabled on the matching or newly created mobile phone number.
• Support both new-person creation and existing-person matching.

The setting should default to disabled so existing block behavior remains unchanged.

When the SMS option is hidden, submitting the form must not modify an existing phone number’s messaging-enabled status.

Acceptance Criteria

1. Existing blocks remain unchanged after upgrading.
2. Enabling Show SMS Opt-In displays the consent checkbox when the mobile phone field is displayed.
3. The checkbox is not displayed when the mobile phone field is hidden.
4. Checking the option saves PhoneNumber.IsMessagingEnabled = true.
5. An explicit unchecked response is saved appropriately when the consent option was displayed.
6. Hiding the option does not silently set an existing phone number’s messaging status to false.
7. The standard globally configured SMS consent label is used.
8. New-person and existing-person matching scenarios are covered by tests.
9. Existing Connection Request attributes, CAPTCHA behavior, and confirmation/redirect behavior remain unaffected.

Ministry Use Case

Connection opportunities are a common entry point for serving, volunteering, care, and other ministry engagement. These forms often collect a mobile number, but they currently provide no native way to capture SMS consent at the same time.

Adding the standard consent control would:

• Provide a consistent experience across Rock’s public forms.
• Reduce custom implementation requirements.
• Help organizations maintain clear 10DLC/TCR consent records.
• Avoid having to contact individuals again solely to obtain texting permission.

Related Idea

This is a focused implementation request related to Global SMS Consent Checkboxes and Consent Detail Language — Idea #2124 . That idea identifies Connection Opportunity Signup as one of the places where no SMS consent option currently exists.

Technical Note

The Obsidian block already renders PhoneNumberBoxWithSms; it currently hard-codes the SMS portion as hidden. The existing shared control and implementations in other Rock entry blocks provide