Winback-Outreach.md

02-Outreach/Winback-Outreach.md

1. ---
2. type: outreach-play
3. scope: 02-Outreach
4. outreach_type: "Winback"
5. tags: [outreach, winback]
6. created: 2026-06-16
7. updated: 2026-09-28
8. aliases: ["Winback"]
9. ---
11. # Winback Outreach
13. The purpose: re-activate lapsed clients who have not ordered recently (no order in 12+ months). **No vault email copy is needed: the Winback outreach is automated inside Bitrix** (Matt, 2026-08-06), with one important nuance. A deal routed into cat 26 lands in the **Client bucket (the first stage), which is NOT automated**. The automation fires only when **Nora moves the deal to a later stage**: her stage move is the send, and she controls the pace. Routing rules: [[pipeline-routing-rules]].
15. ~~[TBD: Winback email copy]~~ Moot: the copy lives in Bitrix's cat-26 automation, not the vault. [TBD: document the automation's actual sequence here (stages that fire, email count, stop conditions) once confirmed in Bitrix. The stage names the driver knows are in `STAGE_NAMES["26"]` in `07-Automation/partner_pipeline/stages.py`.]
17. One automated pass per dormancy spell, never a second while still dormant. The driver's route step enforces this: a partner whose census already carries a `winback` block entered on or after their last order is excluded ("winback already done this dormancy spell"), and that evidence is inherited across identity twins.
19. ## Target list
21. Every stub with a Winback block in `outreach_pipelines`, showing the block's live fields. Longest-lapsed first.
23. ```dataview
24. TABLE WITHOUT ID file.link AS "Client", company AS "Company", user_group_correct AS "Tier", outreach_pipelines.winback.stage AS "Stage", outreach_pipelines.winback.status AS "Status", outreach_pipelines.winback.entered AS "Entered", outreach_pipelines.winback.last_touch AS "Last Touch", last_order_date AS "Last Order"
25. FROM "03-Clients/client-stubs"
26. WHERE outreach_pipelines.winback
27. SORT last_order_date ASC
28. ```