12 March 2026 · Method
Soft-ask before the system prompt
A soft-ask is an in-app screen that explains why notifications matter and offers Continue or Not now before the operating system dialog. Product teams like it because it feels kinder than a surprise OS prompt. Analytics teams should like it only when it changes the system decision, not when it merely inserts another funnel step to decorate.
What to log, or do not bother
You need four events with stable names across Thai and English UI: soft-ask shown, soft-ask continue, soft-ask dismiss, and OS result. If translators ship different labels, keep the event name identical. We have seen “Enable alerts” and “เปิดการแจ้งเตือน” treated as two experiments because someone hashed the visible string.
Shown must mean the screen was actually visible long enough to read, not that a view controller mounted behind a modal. If your analytics SDK fires on viewDidAppear while a paywall still covers the soft-ask, you will invent exposure.
The comparison that matters
Hold first-open users who reach a prompt-capable screen. Randomise: system prompt immediately versus soft-ask then prompt. Primary metric is OS Allow among that reachable group, not clicks on Continue. Secondary metric is later 7-day session quality among those who Allowed. A soft-ask that lifts Allow but tanks next-week retention is usually overselling the benefit of notifications.
Dismiss on the soft-ask is not a deny. Those users remain eligible for a later ask. Collapsing dismiss into Don’t Allow will make your recovery programme look larger than it is and will tempt someone to re-prompt people who only wanted more time.
When a soft-ask is the wrong medicine
Transactional apps that already explained notifications during KYC often do not need a second sermon. Adding a branded illustration between “account verified” and the OS dialog can drop exposure because users back out. In Permission Funnel Diagnostics we treat that drop as a product finding, not as a reason to shout louder on the illustration.
If you cannot randomise, at least time-box a before/after around a single code change and keep Songkran out of the window. A calendar effect will impersonate a soft-ask win faster than any copy test.