Request

Rock’s phone-number fields currently use one system-wide default country code—the first ordered value in the Communication Phone Country Code defined type.

For churches using shared forms across multiple countries or international campuses, this creates unnecessary friction. For example, our primary/default code is Australia, but a person completing the same form from another country is initially shown Australia’s code and must manually change it before entering their phone number.

Proposed enhancement

Add configurable country-code defaulting for Rock phone fields, with a priority order such as:

1. Explicit field/block configuration — an administrator-selected country code, where applicable.
2. Campus or site context — use a country code configured for the campus/site associated with the form.
3. Visitor IP geolocation — use the visitor’s detected country when a matching country code is available.
4. Browser/device locale — optionally use the visitor’s locale as an additional fallback.
5. System default — continue using the first ordered country code in the defined type when no other value can be determined.

The country-code selector should remain visible and editable so visitors can always correct the selection.

Configuration considerations

• Allow administrators to enable or disable location-aware defaulting globally and/or per block/form.
• Do not require browser location permission; IP geolocation and/or locale should work silently when enabled.
• Do not persist location data solely to determine the phone default.
• Use the existing system default when a detected country does not have a configured phone-code entry.
• Ensure the behavior is available consistently across standard Rock phone controls, including public forms, workflow entry, registration, account entry, and person/family editing.

Why this matters

This would improve form completion and phone-number accuracy for churches operating in multiple countries while preserving today’s simple single-default behavior for churches that only serve one region. It would be especially useful where international campuses use identical shared forms and workflows.