Renewal

Retain customers approaching the end of a term. Target: Rs 500-700 cr.

Vertical: Program · Status: ⬜ Planned Back to Program · workflows index

Who it targets

A1 active base with a dated maturity - the only Program workflow with a genuinely known deadline.

Trigger

Time-based and predictable. Maturity date minus a lead window. The easiest trigger in the whole set.

Flow

select facilities maturing in the lead window
        |
tier by value and churn risk
        |
generate renewal offer                [Creative Agent]
        |
compliance review                     [Compliance Agent]
        |
multi-touch sequence, escalating      [A5 dispatcher]
        |
unconverted at T-minus-N  ->  route to branch for human contact

Data it needs

Needs	Have
Maturity dates	⬜
Renewal terms available	⬜
Churn-risk signal	⬜
Branch mapping for escalation	⬜

Agents involved

Creative Agent - Compliance Agent.

Blocked on

CRM integration - not started. Without customer records there is no base to select from.

See Program dependencies.

Roadmap source

Page 2 - A1 -> Renew - 500-700 cr — see roadmap_ref_extracted.md.

Design notes

Start here when the CRM lands. A known future date, a defined outcome and a measurable baseline make this the cleanest workflow to prove the whole Program stack end to end.
Multi-touch with escalation to human contact is the pattern; a single message fired at a maturity date under-performs badly.