Reach users on every channel
Section: DOC-CP-notifications#reach-users-on-every-channel.
Welcome a new user, tell them an update is ready, and keep that notice available when they return. Start with an in-app welcome message, then add the channels and preferences your application needs.
Choose the customer interaction
Section: DOC-CP-notifications#start-here.
| Build this feature | Recipe |
|---|---|
| Welcome a new user in your application | Prepare and deliver a welcome notification |
| Tell a user that a conversation update is ready | Send the completed update’s notice, with push enrollment when needed |
| Keep notices available after the user leaves the screen | Build an in-app inbox |
| Let users choose message types and channels | Build notification settings |
| Let users follow a recurring update | Build topic subscriptions |
Before you start
Section: DOC-CP-notifications#related.
Have an authenticated application user and a backend that authorizes who may configure or send notifications. Management routes do not enforce a separate administrator role, and subscriber operations still select their user through authentication; follow the administration prerequisites.
The in-app recipe needs no external email or push account. For another channel, prepare its provider and device or contact information using the linked recipe. Use the Notification API reference for exact request fields and the JSON contract for response presence rules.
Deliver the first welcome message
Section: DOC-CP-notifications#how-it-works.
- Prepare the welcome template and connect it to the intended recipient.
- Trigger it from your backend after the user’s application enrollment succeeds. Save the returned transaction reference.
- Load that user’s inbox and display the welcome message.
- Let the user open the intended screen, mark the notice read and archive it. Reopen the app to confirm its saved state.
- Add notification preferences, then connect extra delivery channels if the application needs them.
The feature works when the intended user can find the notice and complete its action. If it does not arrive, follow the original delivery before sending another: a trigger acknowledgement is not arrival. When the recipient is your backend rather than a person, use the webhook recipe.
Document ID: DOC-CP-notifications. Section identities and revisions.