For Mobile-Based Services.. Even If the Mobile Grandfather Comes.. Push Policy Is Everything

Regardless of type or positioning, push policy is the core of mobile-based services.

Being able to design timing (sequence) means, on the service side, that you have user passion and a service blueprint; on the operations and delivery (CS) side, that you already have a funnel.

If you can measure timing like that, AI performance can improve and operations can be efficient. Scenarios in which the user asks first and scenarios in which AI proposes first differ — in design scope, expected performance, range of usable feedback, operations, maintenance — beyond comparison.
You end up recommending appropriate in-house or third-party services and goods to the customer, and the customer perceives the recommendation not as advertising but as interest and care, which raises their engagement with the service.
Customer engagement ultimately improves the service's quality and can form a so-called virtuous cycle with them.

But in reality, thinking back to practice using many apps, push often just plays the role of a notification or alarm, and even if you take precious time to click through, you aren't connected to the detail page, and often wander the service's entrance and leave.

Push is an environment possible only on mobile, especially since iPhone-era smartphones, and, starting next year, on mobile browsers including Apple's Safari.
Being able to speak first is tremendous power and opportunity.
Even more so if the user has your app installed.

People's everyday lives are like that too — situations where you can ask first or are in a position to ask.
Of course, asking a question includes many prerequisites, like the push policy I mentioned.

In the end, it's about people dealing with people.
The app (mobile) only assists.