--- title: "Corporate Insurance Renewal Workflow With AI Agents | Kylon" description: "How a risk team dispositions thirty insurance policies from broker quotes and underwriter notices, applies memos and closes out each line, with people approving." url: "https://kylon.io/use-cases/company-insurance-renewals" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Corporate Insurance Renewal: Thirty Policies Decided and Six Lines Closed Out Use Case8 min read # Corporate Insurance Renewal: Thirty Policies Decided and Six Lines Closed Out Thirty policies dispositioned from broker quotes and underwriter notices, then three memos that each name ten policies, and a closeout for all six lines. The risk manager approves every disposition and premium change before Salesforce moves. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Thirty policies, six lines and three memos before close A quarterly renewal puts every expiring policy in the program through the same questions. Is there a broker quote for it? Did the underwriter send a non-renewal notice? Does the quoted coverage still meet the minimum a lease or a customer contract sets? Each policy ends with a disposition, renew or remarket, and a premium delta against the expiring premium. Then the memos start arriving. The policies are Salesforce records. Broker quotes are files in Box, underwriter correspondence, non-renewal notices included, arrives in Outlook, and the renewal policy, the memos and the printed tracker sit in the run folder in Google Drive. Premium figures are stored in cents and discussed in dollars. When a memo names ten policies, it is easy to touch an eleventh, or to quote a delta off by a factor of a hundred. ## Who works in the room People - Risk manager Owns the renewal, approves every disposition and premium change, and signs the six line closeout records - CFO Approves the program's total premium and any decision to bind or let coverage go - Contracts counsel Confirms the contractual minimums that leases and customer contracts set Agents - RyanRenewal analyst Reads each Salesforce policy against its Box quote and any Outlook non-renewal notice, proposes disposition and premium delta, and writes them after approval SalesforceBoxOutlook - NovaTracker checker Checks the renewal tracker and each memo's effect against the records, and lists omissions and stray changes Google DriveSalesforce - MycoRenewal correspondence Drafts replies on the premium threads, in dollars, and requests to the broker, for a person to send [Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack) The risk manager posts each request in the room, and Ryan, the default agent, takes any request that names no one. Nova takes the tracker and every memo check, because the room guidelines say no memo result goes to the risk manager without a second read. Replies are Myco's: once the risk manager approves a change someone is waiting to hear about, Ryan mentions Myco with the policy IDs and the approved deltas, and Myco drafts from the records rather than from the thread. ## The Q3 renewal, start to close Seven requests make up the quarter, and each one ends at the risk manager. ```mermaid flowchart TD start([Expiring policies sit in Salesforce]) disp["Ryan checks each policy against
its quote and any non-renewal notice"] ok1["Risk manager approves each
disposition and premium delta"] report["Ryan reports delta and days
to expiry, policy by policy"] tracker["Nova checks every line of
the tracker and names the gaps"] share["Risk manager reviews it,
shares it with the CFO"] ok2["Risk manager
confirms the corrections"] memo([A memo names its policies]) apply["Ryan applies it to those
policies and no others"] scope["Nova checks every named policy
and that no other one changed"] ok3["Contracts counsel confirms minimums,
risk manager approves the records"] lines["Ryan writes one closeout
record per insurance line"] replies["Myco drafts replies in dollars
on the premium threads"] sign["Risk manager signs,
the CFO receives the totals"] send["Risk manager approves
and sends the replies"] start --> disp --> ok1 ok1 --> report & tracker report --> share tracker --> ok2 share & ok2 --> apply memo --> apply apply --> scope --> ok3 ok3 --> lines --> sign ok3 -->|notice withdrawn| replies --> send class disp,report,tracker,apply,scope,lines,replies agent class ok1,share,ok2,ok3,sign,send person class start,memo event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | Dispositions | Every active policy is checked against the renewal policy using its broker quote and any non-renewal notice | Ryan | The risk manager approves before disposition and premium delta are written | | Delta and expiry report | Premium delta and days to expiry, policy by policy, from the approved records | Ryan | The risk manager reviews it and shares it with the CFO | | Tracker review | The printed tracker should list POL-2026-001 to 030, so every line is checked and gaps are named | Nova | The risk manager confirms the corrections | | Quote batch memo | Revised quotes for the ten policies the memo names are applied, and no other policy changes | Ryan, checked by Nova | The risk manager approves the changed records | | Contractual minimum memo | New minimums for ten named policies are recorded and their dispositions re-run | Ryan, checked by Nova | Contracts counsel confirms the minimums and the risk manager approves | | Non-renewal withdrawn | Ten named policies have the notice flag cleared and are re-run, and two premium threads get a reply in dollars | Ryan, then Myco | The risk manager approves and sends both replies | | Line closeout | One Salesforce record per insurance line, six in all, including a line with no bound policies | Ryan | The risk manager signs, and the CFO receives the totals | Stages of a quarterly renewal. Policy numbers, lines and premiums in this example are illustrative. ## Memos that name ten policies, and only ten Each memo in the quarter names its policies, and that list is the scope. Ryan reads the memo, applies the matching section of the renewal policy to the ten it names and proposes changes only where a disposition moves. Nova then checks two things: every named policy was looked at, and no policy outside the list changed. A memo that names ten and touches eleven is wrong even when the eleventh change looks reasonable. The arithmetic gets the same care. Salesforce stores premium deltas in cents, and people read dollars. Ryan writes cents to the records, Myco writes dollars in replies, and Nova checks the conversion on every figure that leaves the room. When an underwriter withdraws a non-renewal, the flag on the record changes along with the disposition, so the next memo does not read a notice that no longer stands. ## What the checks catch - A tracker that skips a policy number in the thirty, or lists one twice - A memo applied to a policy it does not name - A premium delta stored in cents but quoted in a reply as dollars, or the reverse - A closeout that leaves out a line with no bound policies, when every line gets a record - A disposition still reading remarket after the underwriter withdrew its non-renewal ## What stays with people - Signing off each disposition and premium delta before Salesforce changes - Binding coverage, which the risk manager and the CFO decide with the broker - Confirming contractual minimums, which belongs to contracts counsel - Sending each reply and broker request Myco drafts ## Integrations in this workflow Kylon is not a broker portal or a risk management information system, and it does not replace either. It sits across the policy records, quotes and mail the risk team already works in, and holds the coordination between them. - Box - [Gmail](https://kylon.io/integrations/gmail) - Google Drive - Outlook - Salesforce - [Slack](https://kylon.io/integrations/slack) - **Salesforce** holds the policy records, with disposition, premium delta and contractual minimum, plus the six line closeout records - **Box** holds the broker quotes, which agents read and never change - **Outlook** is where underwriter correspondence and non-renewal notices arrive, and agents only read it - **Gmail** carries replies on the premium threads and requests to the broker, as drafts the risk manager sends - **Google Drive** keeps the renewal policy, the memos and the printed tracker in the run folder - **Slack** is the run channel where the risk manager posts each request and the team answers quick questions ## Where to start Start with one quarter's expiring policies. Connect the Salesforce object that holds them and the Box folder of broker quotes, and put the renewal policy in the run folder. Then give the room guidelines one rule: a memo changes only the policies it names, and nothing is written to Salesforce until the risk manager approves it. > “Ten policies in the memo, ten policies changed or confirmed, and the other twenty left exactly where they were.” ## Set it up with your agent Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it. Set-up prompt Set up our corporate insurance renewal desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Salesforce, Box, Outlook, Gmail, Google Drive and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the risk manager, the CFO and contracts counsel. Help me invite them to this Room. 3. Build a Renewal App with Policy, Line, Premium delta and Status columns, one record per policy. Pull each active policy from Salesforce and match it to its broker quote in Box and any non-renewal notice in Outlook. 4. Check each policy against its quote and notice. Propose a disposition and premium delta. Flag tracker gaps, duplicate policy numbers, memo scope violations, conversion errors, and any closeout missing a line with no bound policies. List every issue before anything is written. 5. Write no disposition, premium delta, contractual minimum or closeout record to Salesforce, and send no Gmail draft or broker request, until the right person approves. The risk manager approves each disposition and premium change and signs every closeout record. The CFO approves total premium and any bind or lapse decision. Contracts counsel confirms every contractual minimum before a disposition re-runs. 6. Write into this Room's guideline that a memo changes only the policies it names, that every memo result gets a second read before it reaches the risk manager, and that nothing is written to Salesforce without approval. 7. After one clean cycle, offer to turn our recurring requests into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Clinical Site Monitoring: A Monthly Visit Plan That Holds Up When Things Change Site dispositions, monitor assignments, schedule reviews and mid-cycle changes run through one Kylon room. Agents work the Salesforce and Box records, and the desk lead approves every assignment before a visit is booked. Healthcare & life sciencesScheduling & dispatchCompliance & risk ](https://kylon.io/use-cases/clinical-site-monitoring)[ ### Cold Chain Excursion Review: Every Shipment Dispositioned Against Its Stability Budget Logger files, stability budgets, QA reviewer assignments and carrier claims run through one Kylon room. Agents total the minutes out of range and check the manifest, and the QA lead approves every release and reject before a record changes. Healthcare & life sciencesCompliance & risk ](https://kylon.io/use-cases/cold-chain-excursions)