01
Step one: show one real alert first
Begin with a single sample alert rather than a feature tour. In a team example, the first screen might show a mock message reading that the supplier delivery has arrived, with a clear Acknowledge button. Let the user tap it and see the alert clear. That one action teaches the whole loop: something arrives, you notice it, you respond. Keep text to one line and avoid account forms at this stage. People should feel the benefit before they commit anything, and a short demonstration also reveals whether your wording, icon and button label are understandable at a glance.
02
Step two: ask permission with a reason
Request notification access only after the sample alert has shown its value, and explain the reason in plain words. In the example, the screen says that urgent delivery and shift messages will reach the phone, while everything else waits in the feed. Offer two choices: allow alerts now, or look around first. Never trap the user in a system dialog without context. If they decline, keep the app useful through an in-app feed and provide a gentle reminder later, after they have seen real value. Record which wording earns the most approvals and adjust it gradually.
03
Step three: let people set the volume
Finish onboarding with a short control screen that sets how loud the app should be. In the worked example, the user picks three levels: urgent rings immediately, normal groups into a digest, and low appears only in the feed. Add quiet hours with a sensible default, such as overnight. Show a preview of each level so choices feel concrete. Then end on the live feed with one waiting item, not a congratulation page. Review the flow after launch by watching where people stop, and trim any screen that does not help someone act on their first real alert.