Insurance Renewal and Retention Official

Reads policies nearing expiry, determines the renewal stage, and drafts the touch into the Renewal Pipeline for licensed review. Draft only.

1. 01Select policies from the Policies table. If {{policyholder}} is provided, work only that policy. Otherwise find policies whose Expiry Date is within {{horizonInDays}} days (default 90) and whose Renewal Status is not Renewed or Lost. For each, compute days to expiry and map it to a stage: about 90 days out is the 90-Day touch, about 60 the 60-Day, about 30 the 30-Day, and inside 30 with no confirmation the Final touch.Output: The list of policies to work with days-to-expiry and the stage each should receive.
2. 02For each, draft the touch in the playbook tone for that stage. Follow the compliance rules exactly: do not quote, promise, or confirm a premium or that coverage is bound, and frame anything about amounts as subject to confirmation by a licensed agent. Ground the message in the policy record and the playbook.Output: For each policy, the drafted stage-appropriate touch, compliant with the guardrails.
3. 03Write each touch as a row in the Renewal Pipeline with the policyholder, policy type, sequence step, the draft, Drafted On today, Sent No, Reply Status None. Update the policy's Renewal Status to the current stage. Do not send anything.Output: Confirmation of the Renewal Pipeline rows created and policies updated, then a short readable summary using headings and bullet points: how many touches drafted by stage and total premium up for renewal. Never output JSON or raw data.

Produces a plain-English renewal summary and what-changed talking points for a policy, for a licensed agent. Draft only.

1. 01Read the policy for {{policyholder}} from the Policies table. Using the coverage explainers in the playbook, prepare a plain-English summary of what the policy covers, the term, and the renewal timing. Note anything that appears to be changing based on the record. Use only the record and the playbook.Output: The plain-English coverage summary and any apparent changes, grounded in the record.
2. 02Turn it into review talking points for a licensed agent: what to confirm with the client, likely questions, and any cross-sell worth raising as a review (not a pitch). Do not quote or confirm a premium, and note that amounts and coverage are subject to licensed confirmation.Output: A readable summary with headings: Coverage in plain English, What looks like it is changing, and Talking points to confirm. Never output JSON or code blocks.

Scans the Policies book for likely coverage gaps and logs internal cross-sell opportunities with rationale. Draft only.

1. 01Read the Policies table and, per policyholder, look at what lines they hold. Using the playbook's cross-sell guide, identify likely coverage gaps (for example a policyholder with Auto but no Umbrella, or Home but no complementary line). Consider only what the record supports.Output: A list of policyholders with a likely gap and the basis for each.
2. 02For each genuine gap not already tracked, create a Cross-sell Opportunities row with the policyholder, their current coverage, the gap, a recommended product, a Priority, and Status New. Frame everything as an internal suggestion for a licensed agent to evaluate. Do not draft client messages here and do not send anything.Output: Confirmation of the opportunities created, then a short readable summary using headings and bullet points: gaps found by type and the highest-priority ones. Never output JSON or raw data.

Drafts win-back messages for lapsed policyholders into the Win-back List for licensed review. Draft only.

1. 01Read the Win-back List for entries with Status New (and optionally cross-reference Policies with Renewal Status Lost), up to {{maxToProcess}} (default 10). For each, note the lapsed line, when it lapsed, and the reason if known.Output: The list of lapsed policyholders to draft win-back messages for, with context.
2. 02Draft a warm, respectful win-back message per the playbook retention tone that acknowledges the lapse, offers a no-pressure review, and invites a conversation. Do not quote a premium or promise coverage. Write the draft to the Win-back List row and set Status to Drafted. Do not send anything.Output: Confirmation of the rows updated, then a short readable summary using headings and bullet points: how many win-back drafts were prepared. Never output JSON or raw data.

Reads the renewal tables and produces a prioritized digest of upcoming renewals, stuck touches, premium at risk, and cross-sell.

1. 01Read the Policies, Renewal Pipeline, and Cross-sell Opportunities tables. Group policies by renewal window (expiring within 30, 60, and 90 days, excluding Renewed and Lost), total the premium in each window, find pipeline touches that are drafted but stuck without a reply, and pull the top open cross-sell opportunities.Output: The grouped renewals, premium at risk per window, stuck touches, and top cross-sell.
2. 02Write a prioritized daily digest for the owner.Output: A readable digest using headings and bullet points, with premium figures: renewals due in 30, 60, 90 days, premium at risk, touches needing attention, and top cross-sell. Lead with the headline numbers. Never output JSON or raw rows.