renewal-automator
Design automated renewal workflows with retention scoring and proactive outreach sequences. Use when building renewal automation for insurance agencies to reduce lapse rates and improve client retention.
What this skill does
# Renewal Automator Workflow Design Design a complete automated renewal workflow that scores client retention risk, triggers proactive outreach sequences, manages quote generation, and handles exception cases — all designed to maximize retention rates and reduce the manual burden on agency staff. ## Renewal Pipeline Architecture The renewal automation runs as a background process that continuously monitors upcoming expirations and triggers the appropriate actions based on days-to-expiration and client retention score. **Pipeline overview:** ``` Daily: Scan for upcoming expirations → 90 days: Enter renewal pipeline → Score retention risk → Route by tier → 60 days: Quote generation trigger → Deliver quote to agent → 30 days: Agent review flag → Client outreach → 14 days: Escalation if not resolved → 7 days: Final alert → Expiration: Lapse handling ``` --- ## Component 1: Renewal Pipeline Setup **Scanning criteria:** Run nightly. Pull all policies from AMS where: - `expiration_date` is between today and today + 90 days - `policy_status` = 'Active' - Not already in renewal pipeline (deduplicate) **Pipeline entry data captured:** | Field | Source | |-------|--------| | Policy number | AMS | | Named insured | AMS | | LOB | AMS | | Carrier | AMS | | Current premium | AMS | | Expiration date | AMS | | Agent of record | AMS | | Client retention score | Calculated (see Component 2) | | Renewal tier | Derived from retention score | | Pipeline entry date | System timestamp | | Status | New / Contacted / Quoted / Renewed / Non-renewed / Lapsed | --- ## Component 2: Retention Scoring Model Score each client 0–100 at renewal pipeline entry. Higher score = higher retention risk. **Scoring factors:** | Factor | Condition | Risk Points | |--------|-----------|------------| | Claims history — frequency | 0 claims in 3 years | 0 | | Claims history — frequency | 1 claim in 3 years | +5 | | Claims history — frequency | 2+ claims in 3 years | +15 | | Claims history — severity | Claims totaling > $[X] | +10 | | Payment record | No late payments in 12 months | 0 | | Payment record | 1–2 late payments | +8 | | Payment record | 3+ late payments or NSF | +20 | | Coverage changes last term | No mid-term changes | 0 | | Coverage changes last term | Reduced coverage | +10 | | Coverage changes last term | Cancelled endorsement | +8 | | Relationship tenure | 5+ years with agency | −15 (protective) | | Relationship tenure | 3–5 years | −8 | | Relationship tenure | 1–3 years | 0 | | Relationship tenure | < 1 year (first renewal) | +10 | | Competitor pricing indicator | Premium increase > 15% at renewal | +20 | | Competitor pricing indicator | Premium increase 5–15% | +10 | | Multi-policy household/account | 3+ policies | −10 | | Multi-policy household/account | 2 policies | −5 | | Agent relationship quality | Agent-rated relationship score (1–5, entered in AMS) | −[5−score] × 3 | **Retention risk tiers:** | Score | Tier | Designation | Handling | |-------|------|-------------|---------| | 0–25 | A | Low risk | Automated outreach sequence | | 26–50 | B | Medium risk | Automated + agent phone call at 30 days | | 51–75 | C | High risk | Agent personal outreach starting at 90 days | | 76–100 | D | Critical risk | Senior agent / principal involvement from pipeline entry | --- ## Component 3: Outreach Sequence Design Sequences are triggered automatically based on days-to-expiration and retention tier. **Tier A — Low risk automated sequence:** | Day | Trigger | Channel | Content | |-----|---------|---------|---------| | −90 | Auto | Email | Renewal notice: policy expiring [date], we're already working on your renewal, no action needed | | −60 | Auto | Email | Quote ready: [Carrier] has offered renewal at $[premium]; or: here are your options with premium comparison | | −30 | Auto | Email | Action requested: confirm renewal by [date] to avoid a lapse in coverage | | −14 | Auto | Email | Reminder: renewal in 14 days; one-click confirm link | | −7 | Auto | Email + SMS (if opted in) | Final reminder: your policy expires in 7 days | **Tier B — Medium risk with agent touchpoint:** | Day | Trigger | Channel | Content | |-----|---------|---------|---------| | −90 | Auto | Email | Renewal notice (same as Tier A) | | −60 | Auto | Email | Quote ready | | −30 | Agent task | Phone call required | Agent calls to review coverage and confirm renewal; document outcome in AMS | | −30 | Auto (if no call logged) | Email | Backup if agent has not called | | −14 | Auto | Email | Reminder | | −7 | Auto | Email + SMS | Final reminder | **Tier C — High risk proactive outreach:** | Day | Trigger | Channel | Content | |-----|---------|---------|---------| | −90 | Agent task | Phone call required | Agent calls to establish contact, discuss any changes, explain renewal process | | −90 | Auto (backup) | Email | Renewal notice if agent call not completed by day −85 | | −60 | Auto | Email | Quote options with premium comparison; agent copies on all communications | | −45 | Agent task | Phone call | Agent follows up on quote; addresses any concerns about premium increase | | −30 | Auto | Email | Confirm renewal or request meeting | | −14 | Agent task | Phone call | Final personal outreach | | −7 | Auto | Email + SMS | Final reminder | **Tier D — Critical risk escalation:** | Day | Trigger | Channel | Content | |-----|---------|---------|---------| | −90 | Escalation alert | Task to principal/senior agent | Flag for immediate personal attention | | −90 | Agent task | Phone call required | Senior agent / principal calls personally | | −60 | Auto | Email | Quote with cover letter from principal | | −60 | Agent task | Optional: in-person or video meeting | Review relationship, address concerns, negotiate if applicable | | −45 | Agent task | Phone call | Follow-up on quote decision | | −30 | Agent task | Phone call | Status check | | −14 | Agent task | Phone call | Final outreach | | −7 | Auto | Email + SMS | Final reminder | --- ## Component 4: Quote Generation **Automatic re-marketing rules:** | Condition | Action | |-----------|--------| | Carrier offering renewal (no non-renewal notice) + premium increase < 5% | Auto-generate renewal quote from current carrier; present to agent for review | | Premium increase 5–15% | Trigger market comparison: current carrier + [N] alternative carriers | | Premium increase > 15% | Trigger full market sweep: all appointed carriers for this LOB | | Carrier issuing non-renewal | Trigger immediate full market sweep; notify agent and client | | Client credit score dropped significantly (if available) | Flag for agent review before quoting; some carriers will increase or non-renew | **Carrier selection logic:** For market comparisons, submit to carriers in this priority order: 1. Carriers with active binding authority for this LOB and risk profile 2. Carriers with preferred appointments (higher commission or volume commitment) 3. All remaining appointed carriers 4. E&S markets (only if admitted market cannot accommodate the risk) **Quote comparison delivery to agent:** - Quote comparison table (carrier, premium, key coverage differences, AM Best rating) - Recommended carrier (system recommendation based on premium and coverage quality score) - Flag any coverage differences between current and proposed (always highlight if proposed offers less coverage) - Agent reviews and selects; selection logged --- ## Component 5: Client Communication Templates **Renewal notification email (Day −90, all tiers):** > Subject: Your [LOB] policy renews [date] — we're already working on it > > Dear [Client First Name], > > Your [LOB] policy with [Carrier] (policy #[number]) renews on [date]. We wanted you to know early so you have plenty of time to review your coverage and options. > > Over the next few weeks, we'll: > - Review your current coverage to make sure it still fits your needs > - Check market pricing so you always know you're getting a competitive ra
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.