Insurance & Risk
A small commercial insurance broker, an MGA underwriting desk, or an in-house risk team runs on the same handful of repeating cycles — the quote sent on Tuesday that has not been bound by Friday, the policy that renews in 42 days, the loss the client phoned in at 4pm, the SOV the underwriter asked for three weeks ago and is still waiting on. Each task is small in isolation. What costs money is the case that drops off the end of someone's mental list — the renewal that lapses because the chase letter sat in drafts over the bank holiday, the FNOL that did not reach the insurer until the next morning, the quote that converted to a competitor because we never followed up. These workflows take the repeating bits off the broker's desk so the time goes into the cases where a human judgment actually changes the outcome.
Nothing in this category auto-sends to a client, an insurer, or an underwriter. Every follow-up email, every FNOL notification, every renewal-terms covering letter, every endorsement request, and every document chase stops at a draft for the broker, account handler, or risk manager to review and send. The cost of a wrong renewal premium quoted in writing, an FNOL that misstates a material fact, or a chase letter sent to a client who paid the premium yesterday is far higher than the cost of one minute reviewing the queue. Slack is used for internal coordination — the Monday renewal-pipeline view, an FCA-deadline red alert, the daily claims status digest — and client names appear in those messages because the office team needs to act on them.
Use Cases
| Use Case | Description |
|---|---|
| Quote Follow-up Cycle | Each weekday, find quotes that have not converted, draft a follow-up email pitched to how long ago the quote went out, log every chase, and stop the moment the prospect replies or asks not to be contacted |
| Policy Renewal Cycle | Each Monday, find every policy renewing in the next 60 days, pull last year's premium and claims, draft the renewal-terms covering email, chase at 30 and 14 days, and red-alert anything still open inside 7 days |
| Claims First-Notification-of-Loss Intake | When a client reports a loss by email or web form, draft the insurer FNOL email with every field they need, send the client an acknowledgement explaining what happens next, and log the claim so it stays in the weekly client status digest until it closes |
| Underwriting Document Chase | When an insurer asks for more information on an application — claims history, statement of values, accountant's letter, risk survey — draft the request to the client, log what is outstanding, chase at sensible intervals, and red-alert anything still missing inside 7 days of the underwriter's deadline |
| Mid-Term Adjustment Endorsement Intake | When a client emails or phones in a change to a live policy, draft the endorsement request to the insurer, send the client an acknowledgement confirming the cover position pending the endorsement, log it on the MTA tracker, and chase the insurer if it does not come back inside the agreed turnaround |
| Broker Commission Reconciliation | Each month, read the insurer commission statements, match every line against the broker's policy register, flag missing, short-paid, and unpaid-overdue cases, and draft the chase notes to each insurer's accounts team |
| Complaint Acknowledgement and Resolution Tracker | When a client complaint email arrives, draft the same-day acknowledgement, log the complaint with the regulatory clock started, schedule milestone reminders, draft the final response when resolved, and red-alert anything still open as the deadline approaches |
| Sanctions and PEP Screening Cycle | Each week, run every active client and every director against the published sanctions and PEP lists, draft the escalation memo for any possible match, and red-alert the compliance officer if a possible match touches a policy on cover or up for renewal |
| Premium and Instalment Payment Chase | Each weekday, find clients whose premium or direct-debit instalment is overdue, draft a payment-chase email pitched to how overdue they are, log every chase, and red-alert the account handler when a policy is at risk of lapsing for non-payment |
| Risk Survey Scheduling and Follow-up | When an insurer requires a risk survey ahead of incept or renewal, book the surveyor, confirm with the client, chase the report, send it on to the underwriter when it comes back, and chase outstanding recommendations against the agreed completion dates |
| Claim Status Client Update Cycle | Each week, walk the open claims register, pull the latest status from the insurer and loss-adjuster updates, draft a per-client status note explaining where the claim has got to and what happens next, and red-alert any claim that has gone silent on the insurer's side for longer than the agreed service-level |