Recall unrelated to user goals is attention taking

What it is

A re-engagement push is a notification whose content answers none of the recipient's goals — "we haven't seen you in three days," "everyone's watching." When recall is unrelated to user goals, what it takes is pure attention: the user's time and interrupted tasks are spent serving the sender's metrics. This is attention taking.

Why it happens

The legitimacy test has two channels: the information answers the recipient's need (goal relevance), or the user subscribed to this kind of recall (consent). Pure recall has neither, and what it exploits is the reflexivity of attention — sounds, banners, and badges capture attention without passing an intention review. Carrying no information (nothing happened that you need to know about), its entire effect is presence; what gets manufactured is the opening behavior, not any user value. The emptier and more frequent, the faster it slides from taking toward harassment — but harassment is the perception layer and taking is the structural one: even a user who is not annoyed is still being drained.

Where it stops holding

Goal relevance is time- and context-bound: the lunch deal a user wanted in the morning is noise at night. Pure content rules cannot cover that drift, so in practice it is handled by configurability and tiers — letting users define what counts as relevant rather than having the system guess once and forever. A few recalls sit in the gray zone (safety reminders with commercial intent) and are classified by their dominant effect. "Taking" is a design-ethics characterization, not a legal one; the two systems of judgment should not impersonate each other.

Applying it

Impose a double gate on recall notifications: goal relevance (a traceable preference or behavior expressing the need) and value density (opening lands on specific content, not a list page). If either fails, do not send. Frequency caps for recall are set independently of open rates — a high open rate is no license to send more, since opens may be badge-clearing. Verification: sample post-open behavior depth and task completion for recall notifications; the bounce-out share is a behavioral proxy for the share taken. Supplement with follow-ups asking users who disabled a category whether they are satisfied they did.

Related

• Same group: P3.06.1 Notifications can manufacture sessions the user never initiated · P3.06.3 Frequency judged by user value, not retention · P3.06.4 The cost of interruption lands on task resumption · P3.06.5 Badges are content-free recall signals · P3.06.6 Permission granularity determines whether users can refuse in part · P3.06.7 Timing more than frequency decides whether notifications read as harassment
• Adjacent: P2.08 The line between persuasion and manipulation · P3.03.1 Optimize for the user's long-term goals
• Search terms: attention taking · re-engagement push · notification ethics