Preference preview

CivicPal notice preferences

Review how CivicPal can explain notice preference choices in public, launch-preview form. This surface is deterministic and does not store contact settings, create member-specific records, or claim that live delivery is active.

Launch-preview guidance only

These preference rows explain launch intent, consent boundaries, and currently deferred delivery behavior in plain language. They do not submit or retain any preference values.

Consent stays explicit

CivicPal can explain when consent or verification is needed without collecting or storing anything on this route.

Flags stay readable

Launch flags and reason-code framing are shown as public-safe labels, not runtime claims.

Private action waits

When someone needs help beyond public browsing, CivicPal still hands off into private support paths.

SMScivicpal.sms.enabledConsent required

Consent-gated launch path planned

SMS updates stay preview-only here. CivicPal shows the launch path without claiming any retained phone choice or live delivery runtime.

Emailcivicpal.email.enabledEmail verification required

Verification and consent path planned

Email preference copy remains public-safe and explanatory only. This preview does not create member-linked records or retain an email choice.

App / PWAcivicpal.app_inbox.enabledChannel unavailable

Public route visible now, inbox runtime deferred

People can browse public notices today, but the app inbox preference path remains deferred until a later bounded packet.

Voice supportcivicpal.voice_callback.enabledVoice callback only

Support-assisted callback path planned

Voice support remains a guided support path in launch preview and does not imply automated callback campaigns or live voice delivery.

Language and support remain review-safe

If language coverage or delivery availability changes later, CivicPal will need a separately approved runtime slice. This preview keeps those states explanatory and public-safe.