I would suggest a notification inbox feature as a separate channel with WebEngage Customer Data Platform. Let's assume that a user is getting a push notification through an app and you want that particular notification that was triggered a while ago, yesterday, a week back, two days back, or whenever, to be stored in your app's notifications. I think that should be a separate channel rather than a particular feature inside another channel. Notification inbox is not actually a separate feature, though it has been mentioned in the documentation guide as a separate channel. However, it has been treated as an in-house feature of push and web push. If this feature were available as a separate channel with WebEngage, I would have stuck with WebEngage entirely rather than going to any other solution. Regarding metrics, I am able to reach my targets with WebEngage Customer Data Platform. Obviously, it depends on user activity, as some users would be active during certain months and there would be some idle or dull months. During dull months, WebEngage makes sure that I meet my targets at least 85 to 90 percent of the time, which means I have the best service providers and channels coming in. Regarding attendance, there was a lesson drop where the benchmark for lesson one was around 60 percent and for lesson two was around 50 to 55 percent. For lesson three, it was around 50 percent. When we understood the metrics with WebEngage, we discovered that lesson three was falling short by 5 to 10 percent, which was concerning. Since WebEngage was able to share these metrics with me, I was able to create campaigns to ensure people came back and took their lessons for lesson three, getting my attendance back to 50 to 55 percent. From an operations perspective regarding WebEngage Customer Data Platform, I do not find many issues. However, if you do not make up your payments, they keep on pointing out popups that annoy you on every click. If you have not made a payment for WebEngage services and it is overdue, payment reminders will keep popping up, which is annoying. I am not sure if WebEngage can come up with some alternative options to ensure this is not impacting users or organizations.
