Referral - Easy Rewards

Turn the existing base into an acquisition channel, and route referred leads to a branch.

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

Who it targets

Both sides of page 2: A1.4 refer (target 1000) on the retention side, and Referral (Easy Rewards) under ACQ.

Trigger

Post-positive-event on the referrer's side - disbursal, successful repayment, high satisfaction score.

Flow

identify referrers after a positive event
        |
generate referral ask + reward terms       [Creative Agent]
        |
compliance review - reward terms           [Compliance Agent]
        |
dispatch                                   [A5 dispatcher]
        |
referred lead captured  ->  IIFL BASE -> LEAD
        |
allocate to branch  ->  branch to connect  ->  C / NC
        |
reward fulfilment on qualifying conversion

Data it needs

Needs	Have
Referrer eligibility + event history	⬜
Lead capture and dedupe against existing base	⬜
Branch allocation rules	⬜
Reward ledger and fulfilment	⬜

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.

Also needs branch allocation and a reward ledger - neither is content infrastructure, and both are larger than the messaging.

Roadmap source

Page 2 - A1.4 -> Refer - 1000 and ACQ Referral (Easy Rewards) -> IIFL BASE -> LEAD -> allocate to branch -> branch to connect -> C - NC — see roadmap_ref_extracted.md.

Design notes

The whiteboard marks x Loyalty next to this flow - loyalty is drawn as the missing piece that would make referral repeatable rather than one-shot.
The hard part is fulfilment, not the ask. An unpaid referral reward generates complaints and kills the channel permanently.
Dedupe referred leads against the existing base before allocation, or branches end up working leads who are already customers.