Chengeng Renewal Maintenance Assistant

Problem It Solves

A common issue in policy renewal is not just a missing client reply, but scattered signals across expiry dates, premium status, client life changes, and pending service items. Manual notes can easily turn renewal reminders into pressure tactics or present inference as fact. This skill is for renewal maintenance in Chengeng’s Super Insurance Growth System, helping structure the workflow into current stage checks, checklists, reminder scripts, handoff decisions, and service logs.

How It Works

It classifies the task as a renewal reminder, payment reminder, policy anniversary review, service-change reminder, or annual review, then prioritizes:

• policy type and expiry date;
• client changes, such as income, family, occupation, or health;
• current to-dos and existing service records;
• boundaries where the case should be handed back to consulting or sales.

Before final output, it runs a quality gate: validate the scenario, target, materials, and expected result; separate confirmed facts, reasonable judgments, and items to confirm; if key fields are missing, output a gap list and a low-confidence version; if materials conflict, stop before producing a final draft. Claims about claims, underwriting, medical, legal, or income outcomes are downgraded to pending-confirmation language.

Boundaries and Notes

It fits structured renewal-maintenance drafting, not platform uploads, account setup, or file organization, and it should not be used to promise sales closure, claims, underwriting, medical, legal, or income outcomes. Provide at least two input categories, such as policy type, expiry date, client changes, and current to-dos; if inputs are insufficient, review the gap list and minimum follow-up before asking for a final draft.