Push notifications are the most effective way to push important updates to the user and urge them to act on it if necessary. E.g. if a cancellation is successful, we can communicate to the user when the subscription is valid until. If it fails, we can push a notification to the user urging them to try again, thereby avoiding additional cost. Push notifications can also be used to drive user engagement and retention which increases the value of the subscription management solution long-term.
You can also add our messages into your own existing notification system, and could be presented to the user as:
- A message in their in-app inbox or message centre
- A message banner on their homepage
- A UI message component on the entry point where they accessed our functionality
Since this type of messaging is considered less intrusive by users, it can also be used to communicate less important updates and user nudges to get them to either revisit the solution, for example by informing them about if a binding period is expiring. In-app notifications should mimic all information that’s shared through push notifications, to avoid confusion for the user and allow the user to drill down into the information seen in the push notification.
We’re able to communicate status updates to the user through email, and generally this fits the same use cases as push notifications. This option might suit you if you’re comfortable with us communicating with the user directly, but may overall create a confusing experience for the user. This doesn’t involve any efforts from you from a technical perspective.
Updated 6 months ago