Auto-Generated Decline Emails: How InsightUW Drafts, Reviews, and Sends Broker Notifications in One Workflow
How InsightUW selects from 9 category-specific email templates, auto-populates merge fields, and presents the draft for underwriter review — so every declination reaches the broker with accurate detail and professional tone, without a single auto-sent email.
The Problem
When a submission is declined, the broker needs to know — promptly, clearly, and with enough context to redirect the risk. But composing decline emails is one of the most tedious tasks in underwriting. The underwriter opens a blank email, types the insured name, copies the policy number from one system, looks up the broker contact in another, and writes a paragraph explaining why the submission was not accepted. The process takes 10-15 minutes per decline, and the language varies wildly between underwriters.
Worse, some declines never get communicated. A submission sits in "declined" status for weeks while the broker assumes it is still being reviewed. The broker calls, the underwriter scrambles to explain, and the relationship suffers. Carriers that track broker satisfaction consistently find that "no communication on decline" is the top complaint.
Standardizing decline emails through shared templates in Outlook or Word helps, but those templates are static. They cannot auto-populate submission-specific details, they cannot enforce review before send, and they cannot log the communication back to the submission record.
The InsightUW Approach
InsightUW maintains 9 category-specific email templates — 5 for new business declinations and 4 for renewal declinations — each with merge fields that auto-populate from the submission and decline records. When a decline is created, the system selects the matching template, fills in every field, and presents the draft in a review modal. The underwriter reads the email, edits the subject or body as needed, and authorizes the send. The broker receives the email, the underwriter is copied, and the communication is logged to the audit trail.
No email is ever sent without explicit underwriter approval.
The 9 Email Templates
InsightUW ships with 9 decline email templates organized by business type and decline reason:
New Business Templates (5)
| Template Key | Category | Subject Pattern | When Used |
|---|---|---|---|
| nb appetite | appetite | Submission Decline — {insured_name} — Outside Appetite | Appetite score below threshold or LOB mismatch |
| nb capacity | capacity | Submission Decline — {insured_name} — Capacity Constraints | Aggregate or per-risk capacity exhausted |
| nb territory | territory | Submission Decline — {insured_name} — Territory Restriction | State or country outside underwriting territory |
| nb sanctions | sanctions | Submission Decline — {insured_name} — Compliance Restriction | OFAC, SDN, or sanctions list match |
| nb default | default | Submission Decline — {insured_name} | Catch-all for declines without specific category |
Renewal Templates (4)
| Template Key | Category | Subject Pattern | When Used |
|---|---|---|---|
| rnl non renewal | non_renewal | Non-Renewal Notice — {insured_name} — Policy {policy_number} | Decision not to renew at expiration |
| rnl loss experience | loss_experience | Non-Renewal — {insured_name} — Adverse Loss Experience | Loss ratio or claim frequency exceeded threshold |
| rnl rate inadequacy | rate_inadequacy | Non-Renewal — {insured_name} — Rate Adequacy | Premium insufficient for risk profile |
| rnl default | renewal_default | Non-Renewal Notice — {insured_name} | Catch-all for renewal declines |
Merge Fields
Every template contains merge fields that auto-populate from the submission, decline, and user records:
| Merge Field | Source | Example Value |
|---|---|---|
{insured_name} |
Submission | BrightMart Retail Inc. |
{broker_name} |
Submission → Broker | Gallagher Specialty Group |
{broker_contact_email} |
Submission → Broker Contact | maria.santos@gallagher.com |
{lob} |
Submission | Cyber Liability |
{requested_limit} |
Submission | $10,000,000 |
{policy_number} |
Submission (renewals) | CYB-2025-00187 |
{decline_reason} |
Decline Record | Outside carrier appetite — prior breach history |
{decline_category} |
Decline Record | appetite |
{underwriter_name} |
Assigned UW | James Hartwell |
{underwriter_email} |
Assigned UW | james.hartwell@carrier.com |
{underwriter_phone} |
Assigned UW | (312) 555-0142 |
{submission_number} |
Submission | SUB-2026-CY-0091 |
{effective_date} |
Submission | 2026-08-15 |
The Review Modal
When a decline triggers an email draft, the underwriter sees a modal with:
- To — pre-filled with broker contact email (editable)
- CC — pre-filled with underwriter email (locked)
- Subject — pre-filled from template (editable)
- Body — pre-filled with merged template content (editable, rich text)
- Decline Category Badge — displayed but not editable
- Authorize Send button — primary action, requires confirmation
- Save as Draft button — saves without sending, returns to submission
- Cancel button — discards the draft
The underwriter can soften language, add context, or adjust tone before sending. The original template text is preserved in the audit trail alongside any edits.
Email Lifecycle States
| State | Description | UW Action Available |
|---|---|---|
draft |
Template merged, awaiting UW review | Edit, Send, Cancel |
reviewed |
UW opened and viewed the draft | Edit, Send, Cancel |
sent |
Email delivered to broker | View Only |
cancelled |
UW cancelled the draft | None |
Cyber Submission for BrightMart Retail
The Scenario: BrightMart Retail Inc. submits a Cyber Liability application through Gallagher Specialty Group requesting $10M in coverage. BrightMart suffered a PCI data breach 14 months ago affecting 2.3 million customer records. The breach resulted in $4.2M in notification and forensic costs. InsightUW's appetite engine scores the submission at 22/100 — well below the 30-point auto-decline threshold for Cyber.
What Happens:
- The auto-decline rule fires (appetite score 22 < threshold 30)
- Decline record created: category
appetite, reason "Prior breach within 24 months — PCI exposure" - Template nb appetite selected and merged
- Draft email appears in James Hartwell's review modal
The Draft Email:
Subject: Submission Decline — BrightMart Retail Inc. — Outside Appetite
Dear Maria,
Thank you for submitting BrightMart Retail Inc. (SUB-2026-CY-0091) for Cyber Liability coverage with a requested limit of $10,000,000 effective 08/15/2026.
After careful review, we are unable to offer terms on this submission. The risk falls outside our current underwriting appetite due to prior breach history and PCI exposure concerns.
We appreciate your continued partnership and encourage you to reach out with future opportunities.
James Hartwell | Senior Underwriter | Cyber & Technology
(312) 555-0142 | james.hartwell@carrier.com
James's Edits: James softens the language. He changes "we are unable to offer terms" to "we are unable to offer terms at this time" and adds: "Should BrightMart implement a comprehensive PCI DSS compliance program and complete 18 months without incident, we would welcome a resubmission." He also adds a personal note acknowledging the long-standing Gallagher relationship.
Result: Maria at Gallagher receives a professional, specific decline email within 20 minutes of submission. James is CC'd. The full communication — original draft, edits, and sent version — is logged to the submission audit trail.
What This Means for Underwriters
-
Every decline gets communicated — the system generates a draft automatically, so no submission sits in silence. Brokers always know where they stand.
-
Templates enforce consistency — whether a junior analyst or a senior VP declines a submission, the broker receives a professionally structured email with all relevant details.
-
Merge fields eliminate errors — insured names, policy numbers, limits, and broker contacts are pulled from the system, not typed by hand. No more "Dear [broker name]" emails.
-
UW retains full control — the email is always a draft first. The underwriter reads it, edits it, and explicitly authorizes the send. The system never sends a decline email without human approval.
-
Audit trail captures everything — the original template, the merged draft, any edits the underwriter made, the sent timestamp, and the recipient are all logged. Compliance and E&O teams have a complete record.
What's Next
The next blog explores the Configurable Auto-Decline Rules Engine — how InsightUW evaluates every submission against your underwriting guidelines using an 8-operator condition engine, 5 default rules, and 13 LOB-specific appetite rules to determine which submissions should be auto-declined.
InsightUW is an AI-powered underwriting workstation for P&C carriers. Request a demo to see auto-generated decline emails in action.