Relance Pilot

Context

A design target, not a delivered mission: the figures below are design objectives and sector orders of magnitude, to be confirmed on your real volumes. The pattern covers three flows that behave alike: unanswered quotes, overdue invoices and missing case documents. In all three, the agent reads the case state, drafts a dated message and puts it in a validation queue.

Challenge

Follow-ups lose to the day's fires, so they happen late, unevenly, and nobody knows what has already gone out.

Solution

Reads states from the billing tool and CRM, applies case-age rules, drafts the message with the right tone for the age, routes it to a human validation queue, and freezes automatically as soon as a dispute or contested payment is detected.

Results

• Every waiting case carries a dated next action
• The message goes out at the right age, not when someone remembers
• Readable history of what was sent and by whom
• No follow-up on a case flagged as disputed

Limits

• Without reliable case state in the billing tool, sorting is wrong and the pattern is useless
• Legal collection is out of scope: the freeze stops at dispute detection
• The figures above have not been observed in production, they exist to frame a conversation