Reactive alert. Listens to connection.api.salesforce.contact updated bus events; for each fired contact reads the cross-vendor `engagement_score_per_contact` enrichment (filled by the kernel housekeeping producer from D-129 P6 + D-130 P6 widening) and the Salesforce-flavored `lifecycle_stage_inferred_salesforce` topic (filled by the D-130 P6 kernel producer). Dispatches a notification when the contact is `customer`-stage AND engagement trajectory is `falling` AND last meaningful touch is older than a configurable threshold. The reconciler's poll cadence + CometD streaming drive the practical 'daily watcher' frequency. Salesforce parallel of `surface-low-engagement-contacts-hubspot`; both share `variant_group: surface-low-engagement-contacts`.

How it works 13 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Data fetch

▼ contact ?

▼ engagement_rows ?

▼ lifecycle_rows ?

▼

Process (10 steps)

■ trajectory default

Apply default

■ last_touch_at default

Apply default

■ lifecycle_stage default

Apply default

■ days_since_touch date_diff

Calculate days between last touch at and event payload at

■ is_customer compare

Check if lifecycle stage equals customer

■ is_falling compare

Check if trajectory equals falling

■ is_stale compare

Check if days since touch is greater than setting stale touch days

■ should_alert all

Check if all conditions are true

■ notify ?

skip: step.should_alert equal false

■ card to_summary

Format results as a summary card

Settings 3 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

channels setting = in_app

salesforce setting =

stale touch days setting = 30