Communication Templates
On-brand HTML email, plain-text email, SMS, in-app messages, push notifications, and support macros ready to copy into the Olli application or any sending system. Pick the audience, pick the format, copy the source.
Deliverability & adoption
Every template below is designed to land in the inbox or notification tray, not the spam folder. These are the cross-channel rules from Gmail / Yahoo / Apple Mail / Outlook bulk-sender requirements, mobile carrier A2P 10DLC rules, and APNs / FCM push guidelines. Each individual template card surfaces the specific items it must satisfy.
Email (Gmail / Yahoo / Apple / Outlook)
- Subject lines under 50 chars · no ALL CAPS · no spammy punctuation
- Preheader text 60–90 chars · written intentionally
- Plain-text alternative for every HTML send (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text on every image
- <100KB HTML to avoid Gmail clipping · table layout · no JavaScript · no embedded forms
- List-Unsubscribe header + List-Unsubscribe-Post: List-Unsubscribe=One-Click
- Working unsubscribe in visible footer + physical mailing address (CAN-SPAM)
- 'Why you're getting this' line in every marketing email
- SPF, DKIM, DMARC aligned on the Olli sending domain
- Consistent From name + monitored reply-to · never noreply@
- Links use olli.insure or a branded tracking subdomain · no bit.ly
- Dark-mode safe colors · dark-bg logo where appropriate
- Honor sunset policies · warm up new sending domains/IPs gradually
SMS (A2P 10DLC / TCPA / CTIA)
- A2P 10DLC registered sender + brand/campaign vetting
- Marketing SMS requires prior express consent (TCPA)
- Brand name on every message · 'Reply STOP to opt out, HELP for help' on first marketing message
- Honor STOP / UNSTOP / HELP keywords automatically
- Target ≤ 160 GSM-7 chars to avoid segmentation
- Branded short domain only — no bit.ly or t.co
- Marketing quiet hours: no sends 9pm–8am recipient local time
- Transactional SMS is opt-out exempt — include the exemption notice
Push (APNs / FCM)
- Title ≤ 30 chars · body ≤ 100 chars
- Deep link to the exact in-app destination — never the home screen
- Use OS notification categories / channels so users can mute marketing without muting transactional
- No marketing push without explicit opt-in
- Transactional push only for events the user actually acted on
- No PII or one-time codes in the visible body (lock-screen visible)
In-app
- Frequency cap documented · always dismissible (unless legally required to acknowledge)
- Never blocks the user's primary task
- Targeted by segment (DTC vs B2B2C) — never broadcast to everyone
- One in-app message per screen at a time
DNS records to set up on olli.insure
- · SPF: include olli.insure ESP + any partner-relay sender
- · DKIM: 2048-bit key on the sending subdomain, rotated annually
- · DMARC: p=quarantine minimum, rua + ruf reports to dmarc@olli.insure
- · BIMI: optional, requires VMC + DMARC enforcement (p=quarantine or stricter)
- · MX + return-path align with the sending domain for full alignment
Words / patterns to avoid in subjects + body
- ×FREE, ACT NOW, 100% guaranteed, no obligation, risk-free
- ×All caps subjects, exclamation marks (!!!), $$$
- ×'Click here', 'open immediately', 'final notice' framing
- ×'Congratulations!' as a greeting · clickbait subject lines
Customer Users (DTC)
Solo entrepreneurs buying and managing insurance directly from Olli.
Tone (applies to all formats)
Friendly, direct, plain-English. The smartest friend who knows insurance.
Subject
Welcome to Olli, [First Name].
Preview uses local logo assets for display. The copied/downloaded HTML keeps the production https://olli.insure/... URLs so emails resolve correctly once sent.
View raw HTML
<!DOCTYPE html>
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xmlns:o="urn:schemas-microsoft-com:office:office">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<meta name="x-apple-disable-message-reformatting">
<meta name="color-scheme" content="light only">
<meta name="supported-color-schemes" content="light only">
<title>Olli</title>
<!--[if mso]>
<style>table,td,div,p,a{font-family:Arial,Helvetica,sans-serif !important;}</style>
<![endif]-->
<style>
@media (prefers-color-scheme: dark) { :root { color-scheme: light only; } }
@media only screen and (max-width: 620px) {
.container { width:100% !important; }
.px { padding-left:20px !important; padding-right:20px !important; }
.h1 { font-size:22px !important; line-height:30px !important; }
}
</style>
</head>
<body style="margin:0;padding:0;background:#F0F0F0;-webkit-font-smoothing:antialiased;">
<div style="display:none;font-size:1px;color:#F0F0F0;line-height:1px;max-height:0;max-width:0;opacity:0;overflow:hidden;">Welcome to Olli. Here is what happens next.</div>
<table role="presentation" cellpadding="0" cellspacing="0" border="0" width="100%" style="background:#F0F0F0;">
<tr>
<td align="center" style="padding:24px 12px;">
<table role="presentation" class="container" cellpadding="0" cellspacing="0" border="0" width="600" style="width:600px;max-width:600px;background:#FFFFFF;border-radius:8px;overflow:hidden;">
<tr>
<td align="right" class="px" style="padding:8px 32px 0 32px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:11px;color:#949291;">
<a href="https://olli.insure/view-in-browser" style="color:#949291;text-decoration:none;">View in browser</a>
</td>
</tr>
<tr>
<td align="left" class="px" style="padding:20px 32px 24px 32px;">
<img src="https://olli.insure/olli-logo.png" width="64" height="auto" alt="Olli" style="display:block;border:0;outline:none;text-decoration:none;height:auto;width:64px;">
</td>
</tr>
<tr><td style="padding:0 32px;"><div style="height:1px;background:#F0F0F0;line-height:1px;font-size:1px;"> </div></td></tr>
<tr>
<td class="px" style="padding:32px 32px 8px 32px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;">
<h1 class="h1" style="margin:0 0 16px 0;font-size:26px;line-height:34px;color:#050505;font-weight:700;letter-spacing:-0.01em;">Welcome to Olli, [First Name].</h1>
<p style="margin:0 0 24px 0;font-size:16px;line-height:24px;color:#050505;">You are set up. Your policy is active and your documents are in your account. Here is the link to everything in one place.</p>
<table role="presentation" cellpadding="0" cellspacing="0" border="0">
<tr>
<td bgcolor="#CC33CC" style="border-radius:9999px;">
<a href="https://olli.insure/account" style="display:inline-block;padding:12px 28px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:15px;line-height:20px;font-weight:600;color:#FFFFFF;text-decoration:none;border-radius:9999px;">Open my account</a>
</td>
</tr>
</table>
<p style="margin:24px 0 0 0;font-size:15px;line-height:22px;color:#050505;">If anything looks off or you have a question, just reply to this email. A real person on our team will get back to you the same business day.</p>
<p style="margin:24px 0 0 0;font-size:15px;line-height:22px;color:#050505;">- The Olli Team</p>
</td>
</tr>
<tr><td class="px" style="padding:32px 32px 0 32px;"><div style="height:1px;background:#F0F0F0;line-height:1px;font-size:1px;"> </div></td></tr>
<tr>
<td class="px" style="padding:24px 32px 28px 32px;background:#050505;color:#C5C3C0;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:12px;line-height:18px;">
<table role="presentation" cellpadding="0" cellspacing="0" border="0" width="100%">
<tr>
<td align="left" style="padding-bottom:12px;">
<a href="https://olli.insure" style="color:#FFFFFF;text-decoration:none;font-weight:600;font-size:13px;">olli.insure</a>
</td>
<td align="right" style="padding-bottom:12px;">
<a href="https://linkedin.com/company/olli" style="display:inline-block;width:28px;height:28px;background:#FFFFFF;color:#050505;border-radius:50%;text-align:center;line-height:28px;font-size:12px;font-weight:700;text-decoration:none;margin-left:6px;" aria-label="LinkedIn">in</a>
<a href="https://instagram.com/olli" style="display:inline-block;width:28px;height:28px;background:#FFFFFF;color:#050505;border-radius:50%;text-align:center;line-height:28px;font-size:12px;font-weight:700;text-decoration:none;margin-left:6px;" aria-label="Instagram">IG</a>
<a href="https://x.com/olli" style="display:inline-block;width:28px;height:28px;background:#FFFFFF;color:#050505;border-radius:50%;text-align:center;line-height:28px;font-size:12px;font-weight:700;text-decoration:none;margin-left:6px;" aria-label="X">X</a>
</td>
</tr>
</table>
<p style="margin:0 0 8px 0;color:#C5C3C0;">Olli Insurance, 123 Market Street, Suite 400, San Francisco, CA 94103</p>
<p style="margin:0 0 8px 0;color:#949291;">Olli Technologies, Inc. Olli is a technology platform and insurance operating system. Olli does not underwrite, issue, or sell insurance.</p>
<p style="margin:0 0 16px 0;color:#949291;">Insurance products are provided by licensed insurance carriers, coverholders, and underwriters. Coverage is subject to underwriting, eligibility, and the terms of the issued policy. Availability varies by state. This message is for informational purposes only and is not a binding offer of insurance.</p>
<p style="margin:0;color:#C5C3C0;">
<a href="https://olli.insure/unsubscribe?id=%%RECIPIENT_ID%%" style="color:#FFFFFF;text-decoration:underline;">Unsubscribe</a>
<span style="color:#949291;"> · </span>
<a href="https://olli.insure/preferences?id=%%RECIPIENT_ID%%" style="color:#FFFFFF;text-decoration:underline;">Manage preferences</a>
<span style="color:#949291;"> · </span>
<a href="https://olli.insure/preferences?id=%%RECIPIENT_ID%%&opt_out=all" style="color:#FFFFFF;text-decoration:underline;">Opt out of all marketing</a>
</p>
</td>
</tr>
</table>
<table role="presentation" cellpadding="0" cellspacing="0" border="0" width="600" style="width:600px;max-width:600px;">
<tr><td align="center" class="px" style="padding:16px 32px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:11px;color:#949291;line-height:16px;">
Olli Insurance, 123 Market Street, Suite 400, San Francisco, CA 94103
</td></tr>
</table>
</td>
</tr>
</table>
</body>
</html>When to use this HTML email
Onboarding emails, policy confirmations, renewal reminders, product launches, and monthly newsletters. Send when the message benefits from a CTA button, formatting, or branded layout.
Do (HTML)
- Use the first name and keep paragraphs short
- One primary CTA button per email - magenta pill, action verb
- Invite a reply - mention that a real person responds
Don't (HTML)
- Don't use fear-based language about claims or risk
- Don't add a secondary CTA that competes with the main action
- Don't use industry jargon without a plain-English translation
Subject
Welcome to Olli, [First Name].
Subject: Welcome to Olli, [First Name]. Welcome to Olli, [First Name]. You are set up. Your policy is active and your documents are in your account. Here is the link to everything in one place: https://olli.insure/account If anything looks off or you have a question, just reply to this email. A real person on our team will get back to you the same business day. - The Olli Team ---------------------------------------------------------- olli.insure | LinkedIn: linkedin.com/company/olli Instagram: instagram.com/olli | X: x.com/olli Olli Insurance, 123 Market Street, Suite 400, San Francisco, CA 94103 Olli Technologies, Inc. Olli is a technology platform and insurance operating system. Olli does not underwrite, issue, or sell insurance. Insurance products are provided by licensed insurance carriers, coverholders, and underwriters. Coverage is subject to underwriting, eligibility, and the terms of the issued policy. Availability varies by state. This message is for informational purposes only and is not a binding offer of insurance. Unsubscribe: https://olli.insure/unsubscribe?id=%%RECIPIENT_ID%% Manage preferences: https://olli.insure/preferences?id=%%RECIPIENT_ID%% Opt out of all marketing: https://olli.insure/preferences?id=%%RECIPIENT_ID%%&opt_out=all
Use as the text/plain alternate alongside the HTML version. Wrapped at ~72 characters.
When to use this plain-text email
Required text/plain alternate for every HTML send so it renders in clients that block HTML and improves deliverability.
Do (Plain text)
- Mirror the HTML subject, headline, and CTA URL exactly
- Wrap at ~72 characters and use ASCII characters only
- Spell out URLs in full - no link text
Don't (Plain text)
- Don't use Unicode bullets, smart quotes, em dashes, or emoji
- Don't reformat or rewrite content - it must match the HTML version
- Don't omit the footer block (address, legal, unsubscribe)
SMS
Olli
Olli: You are all set, [First Name]. Your policy is active. Open your account: https://olli.insure/a/xxx Reply HELP for help, STOP to opt out.
Raw source
Olli: You are all set, [First Name]. Your policy is active. Open your account: https://olli.insure/a/xxx Reply HELP for help, STOP to opt out.
Paste directly into your SMS provider. Replace bracketed placeholders ([First Name], xxx) before sending.
When to use this SMS
Time-sensitive nudges to existing DTC customers: payment past due, document needed, renewal in 7 days. Use sparingly - one or two a quarter outside transactional events.
Do (SMS)
- Lead with the sender prefix 'Olli:' on the first line
- Keep under 160 characters for single-segment delivery
- End every marketing SMS with 'Reply STOP to opt out'
Don't (SMS)
- Don't send marketing SMS without explicit opt-in on file
- Don't use shortlinks from untrusted domains - use olli.insure short paths
- Don't send before 9am or after 9pm in recipient local time
Clients & Partners (B2B2C)
Platform partners who embed or distribute Olli insurance to their own users.
Tone (applies to all formats)
Business-to-business, structured, respectful of their time. Confident, not chummy.
Subject
Your Q[N] partner summary is ready.
Preview uses local logo assets for display. The copied/downloaded HTML keeps the production https://olli.insure/... URLs so emails resolve correctly once sent.
View raw HTML
<!DOCTYPE html>
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xmlns:o="urn:schemas-microsoft-com:office:office">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<meta name="x-apple-disable-message-reformatting">
<meta name="color-scheme" content="light only">
<meta name="supported-color-schemes" content="light only">
<title>Olli</title>
<!--[if mso]>
<style>table,td,div,p,a{font-family:Arial,Helvetica,sans-serif !important;}</style>
<![endif]-->
<style>
@media (prefers-color-scheme: dark) { :root { color-scheme: light only; } }
@media only screen and (max-width: 620px) {
.container { width:100% !important; }
.px { padding-left:20px !important; padding-right:20px !important; }
.h1 { font-size:22px !important; line-height:30px !important; }
}
</style>
</head>
<body style="margin:0;padding:0;background:#F0F0F0;-webkit-font-smoothing:antialiased;">
<div style="display:none;font-size:1px;color:#F0F0F0;line-height:1px;max-height:0;max-width:0;opacity:0;overflow:hidden;">Quarterly performance summary and platform updates.</div>
<table role="presentation" cellpadding="0" cellspacing="0" border="0" width="100%" style="background:#F0F0F0;">
<tr>
<td align="center" style="padding:24px 12px;">
<table role="presentation" class="container" cellpadding="0" cellspacing="0" border="0" width="600" style="width:600px;max-width:600px;background:#FFFFFF;border-radius:8px;overflow:hidden;">
<tr>
<td align="right" class="px" style="padding:8px 32px 0 32px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:11px;color:#949291;">
<a href="https://olli.insure/view-in-browser" style="color:#949291;text-decoration:none;">View in browser</a>
</td>
</tr>
<tr>
<td class="px" style="padding:20px 32px 24px 32px;">
<img src="https://olli.insure/partner-logo-placeholder.png" height="32" alt="[Partner Name]" style="display:block;border:0;outline:none;text-decoration:none;height:32px;width:auto;">
</td>
</tr>
<tr><td style="padding:0 32px;"><div style="height:1px;background:#F0F0F0;line-height:1px;font-size:1px;"> </div></td></tr>
<tr>
<td class="px" style="padding:32px 32px 8px 32px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;">
<h1 class="h1" style="margin:0 0 16px 0;font-size:26px;line-height:34px;color:#050505;font-weight:700;letter-spacing:-0.01em;">Your Q[N] partner summary is ready.</h1>
<p style="margin:0 0 24px 0;font-size:16px;line-height:24px;color:#050505;">[Partner Name]: here is a snapshot of how your embedded insurance offering performed last quarter, plus what is shipping next on the Olli platform.</p>
<table role="presentation" cellpadding="0" cellspacing="0" border="0">
<tr>
<td bgcolor="#CC33CC" style="border-radius:9999px;">
<a href="https://olli.insure/partners/reports" style="display:inline-block;padding:12px 28px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:15px;line-height:20px;font-weight:600;color:#FFFFFF;text-decoration:none;border-radius:9999px;">View the report</a>
</td>
</tr>
</table>
<p style="margin:24px 0 0 0;font-size:15px;line-height:22px;color:#050505;">Want to talk through it? Your dedicated partner manager, [Manager Name], has time on the calendar this week.</p>
<p style="margin:24px 0 0 0;font-size:15px;line-height:22px;color:#050505;">- The Olli Team</p>
</td>
</tr>
<tr><td class="px" style="padding:32px 32px 0 32px;"><div style="height:1px;background:#F0F0F0;line-height:1px;font-size:1px;"> </div></td></tr>
<tr>
<td class="px" style="padding:24px 32px 28px 32px;background:#050505;color:#C5C3C0;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:12px;line-height:18px;">
<table role="presentation" cellpadding="0" cellspacing="0" border="0" width="100%">
<tr>
<td align="left" style="padding-bottom:12px;">
<a href="https://olli.insure" style="color:#FFFFFF;text-decoration:none;font-weight:600;font-size:13px;">olli.insure</a>
</td>
<td align="right" style="padding-bottom:12px;">
<a href="https://linkedin.com/company/olli" style="display:inline-block;width:28px;height:28px;background:#FFFFFF;color:#050505;border-radius:50%;text-align:center;line-height:28px;font-size:12px;font-weight:700;text-decoration:none;margin-left:6px;" aria-label="LinkedIn">in</a>
<a href="https://instagram.com/olli" style="display:inline-block;width:28px;height:28px;background:#FFFFFF;color:#050505;border-radius:50%;text-align:center;line-height:28px;font-size:12px;font-weight:700;text-decoration:none;margin-left:6px;" aria-label="Instagram">IG</a>
<a href="https://x.com/olli" style="display:inline-block;width:28px;height:28px;background:#FFFFFF;color:#050505;border-radius:50%;text-align:center;line-height:28px;font-size:12px;font-weight:700;text-decoration:none;margin-left:6px;" aria-label="X">X</a>
</td>
</tr>
</table>
<p style="margin:0 0 8px 0;color:#C5C3C0;">Olli Insurance, 123 Market Street, Suite 400, San Francisco, CA 94103</p>
<p style="margin:0 0 8px 0;color:#949291;">Olli Technologies, Inc. Olli is a technology platform and insurance operating system. Olli does not underwrite, issue, or sell insurance.</p>
<p style="margin:0 0 16px 0;color:#949291;">Insurance products are provided by licensed insurance carriers, coverholders, and underwriters. Coverage is subject to underwriting, eligibility, and the terms of the issued policy. Availability varies by state. This message is for informational purposes only and is not a binding offer of insurance.</p>
<p style="margin:0;color:#C5C3C0;">
<a href="https://olli.insure/unsubscribe?id=%%RECIPIENT_ID%%" style="color:#FFFFFF;text-decoration:underline;">Unsubscribe</a>
<span style="color:#949291;"> · </span>
<a href="https://olli.insure/preferences?id=%%RECIPIENT_ID%%" style="color:#FFFFFF;text-decoration:underline;">Manage preferences</a>
<span style="color:#949291;"> · </span>
<a href="https://olli.insure/preferences?id=%%RECIPIENT_ID%%&opt_out=all" style="color:#FFFFFF;text-decoration:underline;">Opt out of all marketing</a>
</p>
</td>
</tr>
</table>
<table role="presentation" cellpadding="0" cellspacing="0" border="0" width="600" style="width:600px;max-width:600px;">
<tr><td align="center" class="px" style="padding:16px 32px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:11px;color:#949291;line-height:16px;">
Olli Insurance, 123 Market Street, Suite 400, San Francisco, CA 94103
</td></tr>
</table>
</td>
</tr>
</table>
</body>
</html>When to use this HTML email
Quarterly performance summaries, platform releases, contract renewals, partner enablement. Anything where a co-branded header and a single primary CTA help frame the update.
Do (HTML)
- Partner logo in the header; keep Olli out of the header for partner-branded sends
- Lead with results or what changed - no warm-up paragraph
- Always name a specific person (partner manager) as the next step
Don't (HTML)
- Don't use casual/social-media tone or emoji
- Don't bury the action - put the CTA in the first screen
- Don't mix DTC offer language ('insurance made easy for you') into partner email
Subject
Your Q[N] partner summary is ready.
Subject: Your Q[N] partner summary is ready. [Partner Name]: here is a snapshot of how your embedded insurance offering performed last quarter, plus what is shipping next on the Olli platform. View the report: https://olli.insure/partners/reports Want to talk through it? Your dedicated partner manager, [Manager Name], has time on the calendar this week. - The Olli Team ---------------------------------------------------------- olli.insure | LinkedIn: linkedin.com/company/olli Instagram: instagram.com/olli | X: x.com/olli Olli Insurance, 123 Market Street, Suite 400, San Francisco, CA 94103 Olli Technologies, Inc. Olli is a technology platform and insurance operating system. Olli does not underwrite, issue, or sell insurance. Insurance products are provided by licensed insurance carriers, coverholders, and underwriters. Coverage is subject to underwriting, eligibility, and the terms of the issued policy. Availability varies by state. This message is for informational purposes only and is not a binding offer of insurance. Unsubscribe: https://olli.insure/unsubscribe?id=%%RECIPIENT_ID%% Manage preferences: https://olli.insure/preferences?id=%%RECIPIENT_ID%% Opt out of all marketing: https://olli.insure/preferences?id=%%RECIPIENT_ID%%&opt_out=all
Use as the text/plain alternate alongside the HTML version. Wrapped at ~72 characters.
When to use this plain-text email
Required text/plain alternate for every partner HTML send. Partners often whitelist or forward via systems that prefer text/plain.
Do (Plain text)
- Keep the same structure as the HTML: headline, summary, CTA URL, manager name
- Wrap at ~72 characters and use ASCII characters only
- Spell out the report URL on its own line for easy copy/paste
Don't (Plain text)
- Don't compress to a one-liner - partners read the full text alternate
- Don't include sales pitches - this is account communication
- Don't omit the footer block (address, legal, unsubscribe)
SMS
Olli
Olli: [Partner Name] Q[N] summary is ready. View: https://olli.insure/p/xxx Reply STOP to opt out.
Raw source
Olli: [Partner Name] Q[N] summary is ready. View: https://olli.insure/p/xxx Reply STOP to opt out.
Paste directly into your SMS provider. Replace bracketed placeholders ([First Name], xxx) before sending.
When to use this SMS
Rare. Use only for time-critical operational alerts where the partner contact has opted in to SMS (e.g. an integration outage notice).
Do (SMS)
- Use 'Olli:' prefix and name the partner inside the message body
- Keep messages under 160 characters
- End marketing/notification SMS with 'Reply STOP to opt out'
Don't (SMS)
- Don't send marketing or summary nudges over SMS to partner contacts
- Don't use casual language - keep it operational and clear
- Don't send to partner staff who haven't explicitly opted in
Customers of Clients (B2B2C End User)
End users who get insurance through a partner platform, delivered under the partner brand.
Tone (applies to all formats)
Warm, simple, reassuring. Partner brand is primary - Olli is the trusted provider in the background.
Subject
Your [Partner Name] coverage is confirmed.
Preview uses local logo assets for display. The copied/downloaded HTML keeps the production https://olli.insure/... URLs so emails resolve correctly once sent.
View raw HTML
<!DOCTYPE html>
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xmlns:o="urn:schemas-microsoft-com:office:office">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<meta name="x-apple-disable-message-reformatting">
<meta name="color-scheme" content="light only">
<meta name="supported-color-schemes" content="light only">
<title>Olli</title>
<!--[if mso]>
<style>table,td,div,p,a{font-family:Arial,Helvetica,sans-serif !important;}</style>
<![endif]-->
<style>
@media (prefers-color-scheme: dark) { :root { color-scheme: light only; } }
@media only screen and (max-width: 620px) {
.container { width:100% !important; }
.px { padding-left:20px !important; padding-right:20px !important; }
.h1 { font-size:22px !important; line-height:30px !important; }
}
</style>
</head>
<body style="margin:0;padding:0;background:#F0F0F0;-webkit-font-smoothing:antialiased;">
<div style="display:none;font-size:1px;color:#F0F0F0;line-height:1px;max-height:0;max-width:0;opacity:0;overflow:hidden;">Your [Partner Name] coverage is confirmed.</div>
<table role="presentation" cellpadding="0" cellspacing="0" border="0" width="100%" style="background:#F0F0F0;">
<tr>
<td align="center" style="padding:24px 12px;">
<table role="presentation" class="container" cellpadding="0" cellspacing="0" border="0" width="600" style="width:600px;max-width:600px;background:#FFFFFF;border-radius:8px;overflow:hidden;">
<tr>
<td align="right" class="px" style="padding:8px 32px 0 32px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:11px;color:#949291;">
<a href="https://olli.insure/view-in-browser" style="color:#949291;text-decoration:none;">View in browser</a>
</td>
</tr>
<tr>
<td class="px" style="padding:20px 32px 24px 32px;">
<img src="https://olli.insure/partner-logo-placeholder.png" height="32" alt="[Partner Name]" style="display:block;border:0;outline:none;text-decoration:none;height:32px;width:auto;">
</td>
</tr>
<tr><td style="padding:0 32px;"><div style="height:1px;background:#F0F0F0;line-height:1px;font-size:1px;"> </div></td></tr>
<tr>
<td class="px" style="padding:32px 32px 8px 32px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;">
<h1 class="h1" style="margin:0 0 16px 0;font-size:26px;line-height:34px;color:#050505;font-weight:700;letter-spacing:-0.01em;">Your [Partner Name] coverage is confirmed.</h1>
<p style="margin:0 0 24px 0;font-size:16px;line-height:24px;color:#050505;">Hi [First Name], your insurance through [Partner Name] is active. Your policy documents and ID card are ready in your account.</p>
<table role="presentation" cellpadding="0" cellspacing="0" border="0">
<tr>
<td bgcolor="#CC33CC" style="border-radius:9999px;">
<a href="https://olli.insure/account" style="display:inline-block;padding:12px 28px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:15px;line-height:20px;font-weight:600;color:#FFFFFF;text-decoration:none;border-radius:9999px;">View my coverage</a>
</td>
</tr>
</table>
<p style="margin:24px 0 0 0;font-size:15px;line-height:22px;color:#050505;">Questions about your policy? Reply to this email or visit the [Partner Name] help center.</p>
<p style="margin:24px 0 0 0;font-size:15px;line-height:22px;color:#050505;">- The Olli Team</p>
</td>
</tr>
<tr><td class="px" style="padding:32px 32px 0 32px;"><div style="height:1px;background:#F0F0F0;line-height:1px;font-size:1px;"> </div></td></tr>
<tr>
<td class="px" style="padding:24px 32px 28px 32px;background:#050505;color:#C5C3C0;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:12px;line-height:18px;">
<p style="margin:0 0 12px 0;color:#FFFFFF;font-size:13px;">
<span style="color:#C5C3C0;">Powered by</span>
<img src="https://olli.insure/olli-logo.png" height="14" alt="Olli" style="vertical-align:middle;margin-left:4px;display:inline-block;border:0;outline:none;text-decoration:none;height:14px;width:auto;filter:invert(1) brightness(2);">
</p>
<table role="presentation" cellpadding="0" cellspacing="0" border="0" width="100%">
<tr>
<td align="left" style="padding-bottom:12px;">
<a href="https://olli.insure" style="color:#FFFFFF;text-decoration:none;font-weight:600;font-size:13px;">olli.insure</a>
</td>
<td align="right" style="padding-bottom:12px;">
<a href="https://linkedin.com/company/olli" style="display:inline-block;width:28px;height:28px;background:#FFFFFF;color:#050505;border-radius:50%;text-align:center;line-height:28px;font-size:12px;font-weight:700;text-decoration:none;margin-left:6px;" aria-label="LinkedIn">in</a>
<a href="https://instagram.com/olli" style="display:inline-block;width:28px;height:28px;background:#FFFFFF;color:#050505;border-radius:50%;text-align:center;line-height:28px;font-size:12px;font-weight:700;text-decoration:none;margin-left:6px;" aria-label="Instagram">IG</a>
<a href="https://x.com/olli" style="display:inline-block;width:28px;height:28px;background:#FFFFFF;color:#050505;border-radius:50%;text-align:center;line-height:28px;font-size:12px;font-weight:700;text-decoration:none;margin-left:6px;" aria-label="X">X</a>
</td>
</tr>
</table>
<p style="margin:0 0 8px 0;color:#C5C3C0;">Olli Insurance, 123 Market Street, Suite 400, San Francisco, CA 94103</p>
<p style="margin:0 0 8px 0;color:#949291;">Olli Technologies, Inc. Olli is a technology platform and insurance operating system. Olli does not underwrite, issue, or sell insurance.</p>
<p style="margin:0 0 16px 0;color:#949291;">Insurance products are provided by licensed insurance carriers, coverholders, and underwriters. Coverage is subject to underwriting, eligibility, and the terms of the issued policy. Availability varies by state. This message is for informational purposes only and is not a binding offer of insurance.</p>
<p style="margin:0;color:#C5C3C0;">
<a href="https://olli.insure/unsubscribe?id=%%RECIPIENT_ID%%" style="color:#FFFFFF;text-decoration:underline;">Unsubscribe</a>
<span style="color:#949291;"> · </span>
<a href="https://olli.insure/preferences?id=%%RECIPIENT_ID%%" style="color:#FFFFFF;text-decoration:underline;">Manage preferences</a>
<span style="color:#949291;"> · </span>
<a href="https://olli.insure/preferences?id=%%RECIPIENT_ID%%&opt_out=all" style="color:#FFFFFF;text-decoration:underline;">Opt out of all marketing</a>
</p>
</td>
</tr>
</table>
<table role="presentation" cellpadding="0" cellspacing="0" border="0" width="600" style="width:600px;max-width:600px;">
<tr><td align="center" class="px" style="padding:16px 32px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:11px;color:#949291;line-height:16px;">
Olli Insurance, 123 Market Street, Suite 400, San Francisco, CA 94103
</td></tr>
</table>
</td>
</tr>
</table>
</body>
</html>When to use this HTML email
Policy confirmations, claim updates, renewal notices, and service messages delivered under a partner brand. Header is partner-only. 'Powered by Olli' plus the carrier disclaimer live in the footer.
Do (HTML)
- Partner logo only in the header - Olli does not appear up top
- Always phrase coverage as 'your [Partner Name] coverage'
- Footer must include 'Powered by Olli' AND the disclaimer that insurance is provided by licensed carriers, coverholders, and underwriters
Don't (HTML)
- Don't claim 'insurance by Olli' or 'provided by Olli' - Olli is the tech platform, not the insurer
- Don't lead with Olli branding - the user knows the partner, not us
- Don't promote Olli products or upsells inside a partner email
Subject
Your [Partner Name] coverage is confirmed.
Subject: Your [Partner Name] coverage is confirmed. Hi [First Name], your insurance through [Partner Name] is active. Your policy documents and ID card are ready in your account. View my coverage: https://olli.insure/account Questions about your policy? Reply to this email or visit the [Partner Name] help center. - The [Partner Name] Team ---------------------------------------------------------- Powered by Olli | olli.insure LinkedIn: linkedin.com/company/olli Instagram: instagram.com/olli | X: x.com/olli Olli Insurance, 123 Market Street, Suite 400, San Francisco, CA 94103 Olli Technologies, Inc. Olli is a technology platform and insurance operating system. Olli does not underwrite, issue, or sell insurance. Insurance products are provided by licensed insurance carriers, coverholders, and underwriters. Coverage is subject to underwriting, eligibility, and the terms of the issued policy. Availability varies by state. This message is for informational purposes only and is not a binding offer of insurance. Unsubscribe: https://olli.insure/unsubscribe?id=%%RECIPIENT_ID%% Manage preferences: https://olli.insure/preferences?id=%%RECIPIENT_ID%% Opt out of all marketing: https://olli.insure/preferences?id=%%RECIPIENT_ID%%&opt_out=all
Use as the text/plain alternate alongside the HTML version. Wrapped at ~72 characters.
When to use this plain-text email
Required text/plain alternate for every end-user HTML send. Often forwarded to family members or saved as proof of coverage.
Do (Plain text)
- Mirror the headline and CTA URL from the HTML
- Include 'Powered by Olli' on its own line in the footer
- Wrap at ~72 characters and use ASCII characters only
Don't (Plain text)
- Don't switch to Olli-first phrasing in the text version
- Don't add a marketing P.S. - end users did not opt into Olli marketing
- Don't omit the footer block (address, legal, unsubscribe)
SMS
[Partner Name]
[Partner Name]: Your coverage is active, [First Name]. View ID card: https://olli.insure/u/xxx Reply HELP for help, STOP to opt out. Powered by Olli.
Raw source
[Partner Name]: Your coverage is active, [First Name]. View ID card: https://olli.insure/u/xxx Reply HELP for help, STOP to opt out. Powered by Olli.
Paste directly into your SMS provider. Replace bracketed placeholders ([First Name], xxx) before sending.
When to use this SMS
Transactional updates the partner has authorized: coverage active, claim status changed, document ready. Marketing SMS to end users is not allowed without explicit partner consent.
Do (SMS)
- Use '[Partner Name]:' as the prefix; close with 'Powered by Olli.' if space allows
- Reference partner-named coverage, not 'Olli coverage'
- End every marketing SMS with 'Reply STOP to opt out'
Don't (SMS)
- Don't strip the partner name from the sender prefix
- Don't send Olli-branded marketing to partner end users
- Don't send before 9am or after 9pm in recipient local time
System / Automated Messages
Any user receiving a transactional message: sign-in codes, password resets, security alerts, receipts.
Tone (applies to all formats)
Direct, neutral, security-toned. No marketing language. No emoji. No soft language for security events.
Subject
Your one-time sign-in code: 123456
Preview uses local logo assets for display. The copied/downloaded HTML keeps the production https://olli.insure/... URLs so emails resolve correctly once sent.
View raw HTML
<!DOCTYPE html>
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xmlns:o="urn:schemas-microsoft-com:office:office">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<meta name="x-apple-disable-message-reformatting">
<meta name="color-scheme" content="light only">
<meta name="supported-color-schemes" content="light only">
<title>Olli</title>
<!--[if mso]>
<style>table,td,div,p,a{font-family:Arial,Helvetica,sans-serif !important;}</style>
<![endif]-->
<style>
@media (prefers-color-scheme: dark) { :root { color-scheme: light only; } }
@media only screen and (max-width: 620px) {
.container { width:100% !important; }
.px { padding-left:20px !important; padding-right:20px !important; }
.h1 { font-size:22px !important; line-height:30px !important; }
}
</style>
</head>
<body style="margin:0;padding:0;background:#F0F0F0;-webkit-font-smoothing:antialiased;">
<div style="display:none;font-size:1px;color:#F0F0F0;line-height:1px;max-height:0;max-width:0;opacity:0;overflow:hidden;">Use the code below to finish signing in.</div>
<table role="presentation" cellpadding="0" cellspacing="0" border="0" width="100%" style="background:#F0F0F0;">
<tr>
<td align="center" style="padding:24px 12px;">
<table role="presentation" class="container" cellpadding="0" cellspacing="0" border="0" width="600" style="width:600px;max-width:600px;background:#FFFFFF;border-radius:8px;overflow:hidden;">
<tr>
<td align="right" class="px" style="padding:8px 32px 0 32px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:11px;color:#949291;">
<a href="https://olli.insure/view-in-browser" style="color:#949291;text-decoration:none;">View in browser</a>
</td>
</tr>
<tr>
<td align="left" class="px" style="padding:20px 32px 24px 32px;">
<img src="https://olli.insure/olli-logo.png" width="64" height="auto" alt="Olli" style="display:block;border:0;outline:none;text-decoration:none;height:auto;width:64px;">
</td>
</tr>
<tr><td style="padding:0 32px;"><div style="height:1px;background:#F0F0F0;line-height:1px;font-size:1px;"> </div></td></tr>
<tr>
<td class="px" style="padding:32px 32px 8px 32px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;">
<h1 class="h1" style="margin:0 0 16px 0;font-size:22px;line-height:30px;color:#050505;font-weight:700;letter-spacing:-0.01em;">Your one-time sign-in code</h1>
<p style="margin:0 0 24px 0;font-size:15px;line-height:22px;color:#050505;">Enter this code in the Olli sign-in screen to continue. It expires in 10 minutes.</p>
<div style="font-family:'SF Mono',Menlo,Consolas,monospace;font-size:32px;letter-spacing:6px;color:#050505;background:#F0F0F0;padding:16px 24px;border-radius:8px;text-align:center;font-weight:700;">123 456</div>
<p style="margin:24px 0 0 0;font-size:13px;line-height:20px;color:#949291;">If you did not try to sign in, ignore this email. Your account is safe - no changes were made. Olli will never ask you for this code outside the sign-in screen.</p>
</td>
</tr>
<tr><td class="px" style="padding:24px 32px 0 32px;"><div style="height:1px;background:#F0F0F0;line-height:1px;font-size:1px;"> </div></td></tr>
<tr>
<td class="px" style="padding:20px 32px 24px 32px;background:#F0F0F0;color:#949291;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:12px;line-height:18px;">
<p style="margin:0 0 8px 0;color:#050505;font-weight:600;">Security notice</p>
<p style="margin:0 0 8px 0;">If you did not request this, contact <a href="mailto:security@olli.insure" style="color:#050505;text-decoration:underline;">security@olli.insure</a> immediately. Olli will never ask for your password or one-time code over email or phone.</p>
<p style="margin:0 0 8px 0;">This is a transactional service message related to your account. You cannot unsubscribe from these messages while your account is active.</p>
<p style="margin:0;">Olli Technologies, Inc. Olli is a technology platform and insurance operating system. Olli does not underwrite, issue, or sell insurance.</p>
</td>
</tr>
</table>
<table role="presentation" cellpadding="0" cellspacing="0" border="0" width="600" style="width:600px;max-width:600px;">
<tr><td align="center" class="px" style="padding:16px 32px;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Helvetica,Arial,sans-serif;font-size:11px;color:#949291;line-height:16px;">
Olli Insurance, 123 Market Street, Suite 400, San Francisco, CA 94103
</td></tr>
</table>
</td>
</tr>
</table>
</body>
</html>When to use this HTML email
One-time codes, password resets, account security alerts, payment receipts, policy document delivery. Anything purely service-related where marketing CTAs are not permitted.
Do (HTML)
- State the action and the expiration window in the first sentence
- Use a monospaced block for codes
- Include a one-line 'what to do if this wasn't you' instruction
Don't (HTML)
- Don't include marketing CTAs, banners, or product upsells
- Don't include an unsubscribe link - transactional messages are exempt; use the security-notice footer instead
- Don't use emoji, casual greetings, or 'fun' tone in security messages
Subject
Your one-time sign-in code: 123456
Subject: Your one-time sign-in code: 123456 Your one-time sign-in code Enter this code in the Olli sign-in screen to continue. It expires in 10 minutes. 123 456 If you did not try to sign in, ignore this email. Your account is safe - no changes were made. Olli will never ask you for this code outside the sign-in screen. ---------------------------------------------------------- SECURITY NOTICE If you did not request this, contact security@olli.insure immediately. Olli will never ask for your password or one-time code over email or phone. This is a transactional service message related to your account. You cannot unsubscribe from these messages while your account is active. Olli Technologies, Inc. Olli is a technology platform and insurance operating system. Olli does not underwrite, issue, or sell insurance.
Use as the text/plain alternate alongside the HTML version. Wrapped at ~72 characters.
When to use this plain-text email
Required text/plain alternate for every transactional HTML send. Some security mail filters block HTML for codes and only render the text version.
Do (Plain text)
- Put the code on its own line, indented, easy to copy
- Include the SECURITY NOTICE block verbatim
- State explicitly that the message is opt-out exempt
Don't (Plain text)
- Don't add an unsubscribe link in the text alternate
- Don't paraphrase the security notice - keep the exact wording
- Don't include URLs that aren't required to complete the action
SMS
Olli
Olli: Your one-time code is 123456. Expires in 10 min. Do not share. Account-service msg - opt-out exempt; reply HELP for help.
Raw source
Olli: Your one-time code is 123456. Expires in 10 min. Do not share. Account-service msg - opt-out exempt; reply HELP for help.
Paste directly into your SMS provider. Replace bracketed placeholders ([First Name], xxx) before sending.
When to use this SMS
One-time codes, two-factor auth, fraud alerts, and other security/account-service messages. Transactional SMS is opt-out exempt under TCPA/CTIA - the message must say so.
Do (SMS)
- Lead with 'Olli:' and put the code in the first sentence
- State the expiration window in plain numbers
- Include the opt-out-exempt notice (e.g. 'Account-service msg - opt-out exempt')
Don't (SMS)
- Don't include 'Reply STOP to opt out' - it implies marketing and creates a false expectation
- Don't mix marketing content into a transactional security SMS
- Don't repeat or resend codes - generate a new one if the user asks
In-app messages
Banners and modals shown to signed-in users inside the Olli app or a partner app where Olli is embedded.
Solo entrepreneurs signed in to the Olli app.
Tone (this audience)
Friendly, direct, plain-English. Acknowledges the user is mid-task.
Title / Body / CTA
One doc left, [First Name].
In-app banner
×One doc left, [First Name].
Upload your business license so we can finalize your coverage. Takes about 30 seconds.
Raw source
Title: One doc left, [First Name]. Body: Upload your business license so we can finalize your coverage. Takes about 30 seconds. CTA: Upload now
Replace bracketed placeholders ([First Name], [Partner Name]) before shipping. Use one in-app message per screen at a time.
When to use this in-app
Surface a single next-best-action while the user is signed in: missing document, expiring card, coverage gap. Use the in-app banner or modal pattern, not a toast, when the user must act.
Do (in-app)
- Lead with a first name and the specific action
- One CTA, action verb, magenta pill
- Offer a dismiss option unless action is blocking
Don't (in-app)
- Don't reuse marketing copy - the user is already in the product
- Don't stack multiple in-app messages on the same screen
- Don't write more than 2 short sentences
Partner admins signed in to the Olli partner dashboard.
Tone (this audience)
Business-to-business, structured. Respects their time.
Title / Body / CTA
Your Q[N] report is ready.
In-app banner
×Your Q[N] report is ready.
Last quarter's embedded insurance performance and the upcoming platform release notes are in your reports tab.
Raw source
Title: Your Q[N] report is ready. Body: Last quarter's embedded insurance performance and the upcoming platform release notes are in your reports tab. CTA: Open report
Replace bracketed placeholders ([First Name], [Partner Name]) before shipping. Use one in-app message per screen at a time.
When to use this in-app
Notify partner admins of new reports, contract events, or platform releases on first sign-in after publication. Show in the dashboard header banner, not as a toast.
Do (in-app)
- Lead with what changed, not a warm-up
- Link directly to the report or release notes
- Show once per admin, then move to the activity feed
Don't (in-app)
- Don't use casual/social-media tone
- Don't show the same banner every sign-in - dismiss after first view
- Don't mix DTC offer language into partner banners
End users signed in to a partner app where Olli is embedded.
Tone (this audience)
Warm, simple, reassuring. Partner brand primary, Olli in the background.
Title / Body / CTA
Your [Partner Name] coverage is active.
In-app banner
×Your [Partner Name] coverage is active.
Tap below to view your policy and ID card inside [Partner Name].
Raw source
Title: Your [Partner Name] coverage is active. Body: Tap below to view your policy and ID card inside [Partner Name]. CTA: View coverage
Replace bracketed placeholders ([First Name], [Partner Name]) before shipping. Use one in-app message per screen at a time.
When to use this in-app
Coverage activation, claim status changes, and renewal nudges shown inside the partner experience. Use the partner's native banner/modal pattern with co-branded styling.
Do (in-app)
- Phrase coverage as 'your [Partner Name] coverage'
- Keep 'Powered by Olli' subtle and small
- Match the partner app's existing component style
Don't (in-app)
- Don't lead with Olli branding
- Don't add Olli marketing or upsells
- Don't break the partner's tone or component spacing
Any signed-in user receiving a service-level notice (status, maintenance, security).
Tone (this audience)
Direct, neutral, factual. No marketing language. No emoji.
Title / Body / CTA
We're updating the payments service.
In-app banner
×We're updating the payments service.
You may see a brief delay when adding a payment method between 9:00-9:15 PM PT tonight. Your existing payments are unaffected.
Raw source
Title: We're updating the payments service. Body: You may see a brief delay when adding a payment method between 9:00-9:15 PM PT tonight. Your existing payments are unaffected. CTA: Got it
Replace bracketed placeholders ([First Name], [Partner Name]) before shipping. Use one in-app message per screen at a time.
When to use this in-app
Planned maintenance windows, degraded service notices, forced sign-outs, and security warnings. Use the system-banner style (black background) and pin until acknowledged.
Do (in-app)
- State the impact, the time window, and what is unaffected
- Use 24-hour clock or explicit timezone
- Acknowledge dismissal explicitly ('Got it' or 'Sign in again')
Don't (in-app)
- Don't soften security messages with emoji or casual phrasing
- Don't include marketing CTAs in a service notice
- Don't auto-dismiss security or forced-action banners
Push notifications
Lock-screen and notification-tray pushes. Visible body has a hard limit: iOS 178 chars, Android 240 chars (title + body).
Solo entrepreneurs who opted in to push notifications from the Olli mobile app.
Tone (this audience)
Friendly, direct, action-led. No filler words.
Lock screen
Olli
now
Renewal in 7 days
Your general liability policy renews March 14. Tap to review or update coverage before it does.
Raw source
Title: Renewal in 7 days Body: Your general liability policy renews March 14. Tap to review or update coverage before it does.
Limit is title + body characters combined. Replace bracketed placeholders before sending. Deep link the tap target to the exact screen.
When to use this push
Time-sensitive nudges: renewal coming up, payment failed, document needed, claim status changed. Send to opted-in users only, one push per event max.
Do (push)
- Lead the title with the event, not the brand ('Renewal in 7 days', not 'Olli update')
- Put the actionable detail in the first sentence of the body
- Deep link to the exact screen, not the app home
Don't (push)
- Don't send marketing pushes - reserve for transactional and account events
- Don't use ALL CAPS or excessive punctuation
- Don't send before 9am or after 9pm in recipient local time
Partner admins using the Olli partner mobile dashboard with push enabled.
Tone (this audience)
Business-to-business, operational, terse.
Lock screen
Olli
now
[Partner Name]: Q[N] report ready
Embedded insurance summary and platform release notes are available now in your dashboard.
Raw source
Title: [Partner Name]: Q[N] report ready Body: Embedded insurance summary and platform release notes are available now in your dashboard.
Limit is title + body characters combined. Replace bracketed placeholders before sending. Deep link the tap target to the exact screen.
When to use this push
Operational events partner admins need quickly: report published, integration alert, contract renewal due. Use rarely - partner email is the default.
Do (push)
- Prefix the title with the partner name in brackets
- Keep body operational - what shipped, what to do
- Send during business hours in the partner's primary timezone
Don't (push)
- Don't push marketing or sales content to partner contacts
- Don't send pushes to partner end users from the partner channel
- Don't send outside business hours unless the alert is an outage
End users of a partner app who opted in to that app's push notifications.
Tone (this audience)
Warm, simple, reassuring. Partner branded - Olli is invisible at the push layer.
Lock screen
Partner App
now
[Partner Name]: Coverage active
Your policy is confirmed and your ID card is ready. Tap to view it in [Partner Name].
Raw source
Title: [Partner Name]: Coverage active Body: Your policy is confirmed and your ID card is ready. Tap to view it in [Partner Name].
Limit is title + body characters combined. Replace bracketed placeholders before sending. Deep link the tap target to the exact screen.
When to use this push
Coverage activation, claim updates, document ready, renewal reminders - sent under the partner's APNs/FCM credentials so the partner brand appears on the lock screen.
Do (push)
- Lead the title with the partner name, not 'Olli'
- Reference 'your [Partner Name] coverage' in the body
- Deep link into the partner app's policy screen
Don't (push)
- Don't push from Olli credentials - it breaks the partner experience
- Don't include 'Powered by Olli' in the visible push body
- Don't send Olli marketing through the partner push channel
Any opted-in user receiving a security or service push.
Tone (this audience)
Direct, neutral, security-toned. No marketing. No emoji.
Lock screen
Olli
now
New sign-in to your account
We saw a sign-in from a new device in San Francisco, CA. If this wasn't you, tap to secure your account.
Raw source
Title: New sign-in to your account Body: We saw a sign-in from a new device in San Francisco, CA. If this wasn't you, tap to secure your account.
Limit is title + body characters combined. Replace bracketed placeholders before sending. Deep link the tap target to the exact screen.
When to use this push
Security and account-service events: new device sign-in, password change, MFA enrollment, suspected fraud. Always pair with an in-app or email confirmation.
Do (push)
- State the event and the place/time in the first sentence
- Offer a one-tap path to secure the account
- Deliver immediately - no batching, no quiet hours
Don't (push)
- Don't include one-time codes in push body (visible on lock screen)
- Don't use emoji or marketing language in security pushes
- Don't suppress for quiet hours - security pushes override schedules
Support macros
Canned support replies. Every macro has a customer-facing variant and an internal-note variant that stays on the conversation.
Solo entrepreneurs contacting Olli support directly.
Tone (this audience)
Friendly, direct, plain-English. Smartest friend who knows insurance.
Subject
Re: your coverage question
Hi [First Name], Thanks for the note. Quick answer first: yes, your general liability policy covers the situation you described, up to your [Limit] limit per occurrence. Here is what I checked: - Your policy is active and in good standing. - The incident date falls inside your coverage period. - The activity you described is listed in your covered operations. If you want to file a claim, the fastest path is the claims tab in your account: https://olli.insure/account/claims. It takes about 5 minutes. If you'd rather talk it through first, reply to this email with a good time and I'll send a calendar link. - [Agent First Name] Olli Support
Paste into the customer reply. Personalize bracketed placeholders before sending.
When to use this customer reply
Tier 1 coverage-confirmation replies for DTC customers. Use when the answer is yes and you have already verified the policy is active and the activity is covered.
Do (customer reply)
- Lead with the answer in the first sentence
- List what you checked - it builds trust
- Offer a real next step (claims link or a call)
Don't (customer reply)
- Don't quote policy language without translating it
- Don't promise coverage before verifying the policy is active
- Don't send without personalizing the first name and limit
Solo entrepreneurs contacting Olli support directly.
Tone (this audience)
Friendly, direct, plain-English. Smartest friend who knows insurance.
Variant
Internal note (not sent to customer)
[Internal note - not visible to customer] Macro: dtc_coverage_question_confirmed Verified before sending: - Policy [Policy Number] active, no lapse - Incident date [DATE] within coverage period [START] - [END] - Activity [ACTIVITY] listed in declarations page section II - GL limit confirmed: [LIMIT] per occurrence / [AGG] aggregate Next steps if customer files: - Tag conversation: claims-intent, gl, dtc - Move to Tier 2 if claim opened, link the claim ID - If customer asks about premium impact, route to underwriting
Stays on the conversation as an internal note. Never sent to the customer - drives routing, escalation, and the audit trail.
When to use this internal note
Pair every customer-facing macro with an internal note documenting what was checked and what to do next. Stays on the conversation, never sent to the customer.
Do (internal note)
- List the exact records you verified (policy number, dates, limits)
- Tag the conversation so it routes correctly
- Note escalation conditions explicitly
Don't (internal note)
- Don't paste internal notes into the customer reply
- Don't use abbreviations a new agent won't recognize
- Don't skip the verification list - it's the audit trail
Partner team members contacting Olli partner support.
Tone (this audience)
Business-to-business, structured, respectful of their time.
Subject
Re: [Partner Name] integration question
Hi [First Name], Confirming what we discussed: the rate-limit issue your team flagged on the /quotes endpoint was caused by a stale API key on your staging environment. Rotating the key cleared the 429s. For your records: - Affected endpoint: POST /v2/quotes - Window: [START] UTC to [END] UTC - Resolution: API key rotated, new key delivered via your secrets manager Next on our side: - We're shipping a clearer 429 response body next sprint (eta [DATE]) so this is easier to diagnose in your logs. - Your dedicated partner manager, [Manager Name], will follow up on Friday with the release notes. If you hit anything else, reply here or page us in the shared partner Slack channel. - [Agent First Name] Olli Partner Support
Paste into the customer reply. Personalize bracketed placeholders before sending.
When to use this customer reply
Resolution replies to partner integration tickets. Use after the issue is fixed and verified, when summarizing what happened and what's next.
Do (customer reply)
- Lead with what was wrong and what fixed it
- Cite endpoints, timestamps, and ticket IDs
- Always name the partner manager as the next contact
Don't (customer reply)
- Don't use casual tone or emoji - partners read this in tickets
- Don't promise a release date without confirming with eng
- Don't close the ticket without the resolution paragraph
Partner team members contacting Olli partner support.
Tone (this audience)
Business-to-business, structured, respectful of their time.
Variant
Internal note (not sent to customer)
[Internal note - not visible to partner] Macro: partner_integration_resolution_apikey Verified before sending: - Partner: [Partner Name] (account [ACCOUNT_ID]) - Endpoint: POST /v2/quotes - Error window: [START] - [END] UTC - Root cause: stale API key on partner staging env - Resolution: key rotated [TIMESTAMP], confirmed 200s resumed Follow-ups: - Tag conversation: partner-integration, resolved, api-keys - Loop in partner manager [Manager Name] on the conversation - File platform ticket [TICKET] for clearer 429 response body - Add to weekly partner ops report
Stays on the conversation as an internal note. Never sent to the customer - drives routing, escalation, and the audit trail.
When to use this internal note
Internal handoff and audit log for every partner ticket. Captures the root cause and the platform follow-ups so partner manager and eng stay in sync.
Do (internal note)
- Record root cause, timestamps, and the ticket ID
- Tag the conversation for partner ops reporting
- Loop in the named partner manager
Don't (internal note)
- Don't leak internal ticket numbers into the customer reply
- Don't close the conversation before partner manager is looped in
- Don't use shorthand a new ops hire won't understand
End users of a partner platform contacting support about their partner-branded coverage.
Tone (this audience)
Warm, simple, reassuring. Partner brand primary - Olli is the provider in the background.
Subject
Re: your [Partner Name] coverage
Hi [First Name], Thanks for reaching out about your [Partner Name] coverage. Quick answer: your policy is active and the incident you described is covered. Here is what I confirmed: - Your [Partner Name] policy is in good standing. - The date of the incident is inside your coverage period. - The covered amount is up to your [Limit] limit. To open a claim, the fastest path is the help section of your [Partner Name] account. It takes about 5 minutes and you can upload photos directly from your phone. If you have any questions while filing, just reply to this email. A real person on the [Partner Name] support team will read your reply. - [Agent First Name] [Partner Name] Support Powered by Olli. Insurance is provided by licensed carriers, coverholders, and underwriters; Olli is the technology platform that powers [Partner Name] coverage.
Paste into the customer reply. Personalize bracketed placeholders before sending.
When to use this customer reply
Coverage-confirmation replies to end users contacting support inside a partner program. Sent under the partner-branded signoff. Olli appears only as a 'Powered by Olli' line with the carrier disclaimer at the bottom.
Do (customer reply)
- Phrase everything as 'your [Partner Name] coverage'
- Sign off as '[Partner Name] Support'; put 'Powered by Olli' + carrier disclaimer on a separate line below
- Route the customer back into the partner app for claims
Don't (customer reply)
- Don't claim 'insurance provided by Olli' - Olli is the tech platform, not the insurer
- Don't lead with Olli branding
- Don't suggest the customer switch to a direct-Olli product
End users of a partner platform contacting support about their partner-branded coverage.
Tone (this audience)
Warm, simple, reassuring. Partner brand primary - Olli is the provider in the background.
Variant
Internal note (not sent to customer)
[Internal note - not visible to end user] Macro: enduser_coverage_confirmed_partner Verified before sending: - Partner: [Partner Name] (program [PROGRAM_ID]) - End-user policy [POLICY_NUMBER] active, no lapse - Incident date [DATE] within coverage period - Coverage limit [LIMIT] confirmed against program terms - Co-branding rules: lead Partner; Olli only as "Powered by" + carrier disclaimer at the bottom Routing: - Tag conversation: enduser, partner-[Partner ID], coverage-confirmed - Do not surface Olli marketing or upsells - Escalate to Tier 2 + partner manager if claim opened
Stays on the conversation as an internal note. Never sent to the customer - drives routing, escalation, and the audit trail.
When to use this internal note
Audit log for end-user tickets that documents co-branding compliance and routing. Critical for partner reporting and to keep upsells out of partner conversations.
Do (internal note)
- Note the partner and program IDs explicitly
- Record the co-branding rule applied
- Tag for partner reporting
Don't (internal note)
- Don't add Olli upsell suggestions to the internal note
- Don't paste partner program terms into the customer reply
- Don't skip the co-branding rule line - compliance reviews it
Any user who triggered an automated support flow (failed sign-in, suspected fraud, account lockout).
Tone (this audience)
Direct, neutral, security-toned. No marketing. No emoji. No soft language.
Subject
Your Olli account is temporarily locked
Hi [First Name], We temporarily locked your Olli account after multiple failed sign-in attempts. This is a security precaution. To regain access: 1. Reset your password: https://olli.insure/reset 2. Sign in with the new password 3. If prompted, complete the one-time code sent to your email If you did not try to sign in, your account is safe - no changes were made. Reply to this email or contact security@olli.insure right away and we will investigate. This is a transactional account-service message. It is not subject to marketing unsubscribe. - Olli Support
Paste into the customer reply. Personalize bracketed placeholders before sending.
When to use this customer reply
Automated security replies sent when a system event (lockout, suspected fraud, MFA failure) generates a support touchpoint. Customer-facing copy is fixed - do not soften.
Do (customer reply)
- State the event and the remediation steps in numbered order
- Always include the 'wasn't me' escalation path
- Include the transactional-exemption line
Don't (customer reply)
- Don't add marketing or product CTAs to a security message
- Don't use emoji or 'friendly' phrasing in a lockout reply
- Don't include one-time codes in the customer-visible body
Any user who triggered an automated support flow (failed sign-in, suspected fraud, account lockout).
Tone (this audience)
Direct, neutral, security-toned. No marketing. No emoji. No soft language.
Variant
Internal note (not sent to customer)
[Internal note - not visible to customer] Macro: system_account_locked_failed_signin Triggering event: - User [USER_ID] - 5 failed sign-in attempts in [WINDOW] minutes - Source IPs: [IPS] - Lockout duration: [DURATION] minutes (auto-release) or until password reset Verified before sending: - No active fraud case on the account - Email on file confirmed - reset link is safe to send - No partner-program co-branding required (this is direct-Olli) Next steps: - Tag conversation: security, account-locked, automated - If user replies "wasn't me", escalate to security@olli.insure within 1 hour - Log to security audit trail [LINK]
Stays on the conversation as an internal note. Never sent to the customer - drives routing, escalation, and the audit trail.
When to use this internal note
Audit log for automated security flows. Required for every security-triggered conversation so on-call can reconstruct the event.
Do (internal note)
- Record user ID, source IPs, and the lockout window
- Cite the security audit log link
- Set the escalation SLA in plain numbers
Don't (internal note)
- Don't expose source IPs or audit links in the customer reply
- Don't close a security conversation without on-call review
- Don't omit the SLA - it drives on-call routing
Every customer-facing message Olli sends
Templates for every lifecycle, policy, billing, claims, compliance, partner, growth, and operational moment — on-brand, copy-paste ready, with the specific deliverability guardrails each one must satisfy.
Lifecycle & Onboarding
Account creation through first policy bound.
Welcome
Subject: Welcome to Olli, [First Name]
Preheader: Your account is ready. Here's the one link that opens everything.
Hi [First Name], You're in. Your Olli account is ready and your dashboard is where every policy, document, and claim will live from here on out. If you have a question, just reply to this email. A real person on our team responds — same business day. — The Olli Team
https://olli.insure/accountDeliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
Email verification
Subject: Confirm your email for Olli
Preheader: One tap to verify. Expires in 24 hours.
Confirm this email is yours so we can send your policy documents and account updates here. This link expires in 24 hours. If you didn't create an Olli account, ignore this email — nothing will happen. — Olli
https://olli.insure/verify?t=xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Password reset
Subject: Reset your Olli password
Preheader: Tap to set a new password. Link expires in 30 minutes.
Set a new password to get back into your Olli account. This link expires in 30 minutes. If you didn't request this, ignore the email — your password stays the same. If you're worried, write to security@olli.insure and we'll take a look. — Olli
https://olli.insure/reset?t=xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Profile completion nudge
Title: One step to a quote
Add your business type and state and we'll show you the right coverage in under a minute.
/account/profileDeliverability guardrails for this card
- Frequency cap documented · dismissible
- Does not block the primary task
- Targeted by segment (never broadcast-to-all)
- Single CTA · plain-English action verb
Quote saved
Subject: Your Olli quote is saved
Preheader: Pick up where you left off — your quote is locked for 30 days.
We saved your quote. It's locked at the price you saw for the next 30 days, so you can come back whenever you're ready. Questions before you buy? Reply to this email — a licensed person on our team will walk you through it. — The Olli Team
https://olli.insure/quote/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
Quote expiring in 3 days
Subject: Your Olli quote expires in 3 days
Preheader: Lock today's price before it refreshes.
Heads up — the quote we saved for you expires in 3 days. After that the price may change with the market. If the quote still works, you can bind coverage in a couple of minutes. If not, reply and we'll adjust it. — The Olli Team
https://olli.insure/quote/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
Quote expiring (SMS)
Olli: Your quote expires in 3 days. Lock today's price: https://olli.insure/q/xxx Reply STOP to opt out, HELP for help.
Deliverability guardrails for this card
- A2P 10DLC registered sender + campaign vetted
- Prior express consent on file (TCPA)
- Sender prefix 'Olli:' · single segment preferred
- 'Reply STOP to opt out, HELP for help' on first message
- No URL shorteners · branded olli.insure short path only
- Quiet hours respected (9pm–8am recipient local time)
Abandoned application
Subject: Pick up where you left off
Preheader: Your application is saved. Two minutes finishes it.
You started an application and got pulled away — totally normal. Your answers are saved and you're about two minutes from a bindable quote. If something tripped you up, reply to this email and we'll unstick it. — The Olli Team
https://olli.insure/apply/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
Policy Lifecycle
Bind, endorse, renew, cancel, non-renew.
DTC variants
Policy bound + declarations
Subject: Your policy is active — declarations attached
Preheader: Coverage starts [Effective Date]. Documents are in your account.
Your [Coverage Type] policy is active. The declarations page, ID card, and full policy form are saved to your account and attached to this email as PDFs. Effective [Effective Date] through [Expiration Date]. Policy number [Policy Number]. Keep this email for your records — most landlords, clients, and platforms will accept the attached COI. — The Olli Team
https://olli.insure/account/documentsDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Certificate of Insurance (COI) issued
Subject: Your Certificate of Insurance is ready
Preheader: COI for [Certificate Holder] attached and saved to your account.
Your Certificate of Insurance is ready. The PDF is attached and a copy is saved in your account. Certificate holder: [Certificate Holder] Effective: [Effective Date] Policy: [Policy Number] Need it sent directly to the holder, or a different format? Reply to this email and we'll handle it. — The Olli Team
https://olli.insure/account/coi/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Endorsement confirmation
Subject: Your policy change is in effect
Preheader: Endorsement effective [Effective Date]. Updated documents attached.
Your policy change is in effect as of [Effective Date]. What changed: [Plain-English summary of endorsement] Premium impact: [+/-$X annualized] The updated declarations page is attached and saved to your account. — The Olli Team
https://olli.insure/accountDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Mid-term cancellation confirmation
Subject: Your policy is cancelled — confirmation
Preheader: Effective [Cancellation Date]. Refund details below.
Your [Coverage Type] policy is cancelled, effective [Cancellation Date] at 12:01 AM. Refund: [Refund Amount], back to the card on file within 5–10 business days. Reason on file: [Reason] If this isn't right, reply within 10 days and we'll review it. Otherwise, this confirms the change. — Olli
Deliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Reinstatement
Subject: Your policy is reinstated
Preheader: Coverage is active again, effective [Reinstatement Date].
Good news — your [Coverage Type] policy is reinstated, effective [Reinstatement Date]. There was a gap between [Lapse Date] and [Reinstatement Date]. Anything that happened during that gap isn't covered. Going forward, you're back in force. — The Olli Team
https://olli.insure/accountDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Non-renewal notice (letter)
[Date] [Customer Name] [Address] Re: Notice of Non-Renewal — Policy [Policy Number] Dear [Customer Name], This letter is your formal notice that your [Coverage Type] policy with Olli, effective [Effective Date] through [Expiration Date], will not be renewed on the expiration date. Reason for non-renewal: [State-permissible reason in plain English]. This notice is provided in compliance with [State] Insurance Code § [Citation], which requires [N] days' advance notice. You have the right to request a written explanation of the underwriting decision, and the right to appeal to your state Department of Insurance. Contact information is on the next page. We can help you find replacement coverage — reply to this letter or email support@olli.insure within 14 days. Sincerely, Olli Insurance Services, LLC Licensed in [State], License #[License]
Why this is legally required: Required by state insurance code. Days of advance notice vary by state and line of business — check your filings.
Deliverability guardrails for this card
- Mailed first-class with proof of delivery where required by state
- Includes policy number, effective date, and the legal cite
- Plain-English summary at top · legal text below
- Copy retained in customer account documents
- Olli return address + licensed-producer line in footer
Renewal reminder — 60 days
Subject: Your renewal is 60 days out
Preheader: Here's what's changing and what you can do now.
Your [Coverage Type] policy renews on [Renewal Date], 60 days from now. At today's pricing, your new annual premium would be [$New Premium] (was [$Current]). If you want to look at higher or lower limits before then, now's a good time. Nothing to do today unless you want changes — autopay will handle the renewal. — The Olli Team
https://olli.insure/account/renewalDeliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
Renewal reminder — 30 days
Subject: Renewal in 30 days — anything to change?
Preheader: Confirm your renewal or adjust coverage before [Renewal Date].
Your renewal is 30 days out. New annual premium: [$New Premium], effective [Renewal Date]. If nothing's changed in your business — same revenue, same operations, same address — autopay handles it. If something has changed, update us so the coverage matches. — The Olli Team
https://olli.insure/account/renewalDeliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
Renewal reminder — 7 days
Subject: Renewal in 7 days
Preheader: [$New Premium] charges on [Renewal Date] unless you change it.
Last reminder before renewal. On [Renewal Date] we'll charge [$New Premium] to the card on file and your new policy term starts the same day. If you want to cancel, downgrade, or upgrade, do it before [Renewal Date – 1]. — The Olli Team
https://olli.insure/account/renewalDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Renewal in 7 days (push)
Title: Renewal in 7 days
[$New Premium] charges [Renewal Date]. Tap to review or change coverage.
/account/renewalDeliverability guardrails for this card
- Title ≤ 30 chars · body ≤ 100 chars
- Deep link to the exact in-app destination
- Sent under correct notification category/channel
- Transactional only unless explicit marketing opt-in
- No PII or codes in visible body
Renewed — confirmation
Subject: You're renewed — new term starts today
Preheader: Updated declarations attached. Coverage continues uninterrupted.
Your [Coverage Type] policy is renewed. New term: [Effective Date] through [Expiration Date]. Premium: [$Amount], charged to the card ending in [last4]. Updated declarations and ID card are attached and saved to your account. — The Olli Team
https://olli.insure/accountDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Rate change explanation
Subject: Your renewal price changed — here's why
Preheader: Plain-English breakdown of what moved your premium.
Your renewal premium changed from [$Old] to [$New]. We don't like surprise pricing, so here's what moved it: • [Driver 1, e.g. updated revenue]: [$ impact] • [Driver 2, e.g. state-approved rate change]: [$ impact] • [Driver 3, e.g. claims history]: [$ impact] If any of those numbers are wrong, reply to this email and we'll requote. — The Olli Team
https://olli.insure/account/renewalDeliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
B2B2C variants
Policy bound (B2B2C end user)
Subject: Your [Partner Name] coverage is active
Preheader: Policy and ID card are ready inside [Partner Name].
Your [Partner Name] coverage is active. Your policy documents and ID card are ready in your [Partner Name] account. Effective [Effective Date] through [Expiration Date]. Policy number [Policy Number]. Insurance for [Partner Name] is provided by Olli. Questions? Reply here — a real person reads it. — [Partner Name] Support, provided by Olli
https://olli.insure/accountDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Billing & Payments
Receipts, autopay, failures, refunds.
Payment receipt
Subject: Receipt: [$Amount] payment to Olli
Preheader: Paid [Date] · card ending [last4] · policy [Policy Number]
Thanks — we received your payment. Amount: [$Amount] Date: [Date] Method: card ending [last4] Policy: [Policy Number] A PDF receipt is attached for your records. — Olli
https://olli.insure/account/billingDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Upcoming autopay charge
Subject: Heads up: [$Amount] autopay on [Date]
Preheader: Card ending [last4] · policy [Policy Number]
Your autopay charge is scheduled. Amount: [$Amount] Date: [Date] Method: card ending [last4] If the card needs updating, do it before [Date – 1] to avoid a failed payment. — Olli
https://olli.insure/account/billingDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Payment failed
Subject: We couldn't process your payment
Preheader: Update your card to keep your coverage active.
The [$Amount] charge to the card ending [last4] didn't go through. Reason from the bank: [Reason]. Fix it in your billing settings and we'll retry within 24 hours. If we can't collect, your policy may lapse on [Cancellation Date] — we'll send a separate notice before that happens. — Olli
https://olli.insure/account/billingDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Payment failed (SMS)
Olli: Your [$Amount] payment didn't go through. Update card to keep coverage active: https://olli.insure/b/xxx Account-service msg — opt-out exempt; reply HELP for help.
Deliverability guardrails for this card
- A2P 10DLC registered sender + campaign vetted
- Sender prefix 'Olli:' on first line
- Single segment (≤ 160 GSM-7 chars) preferred
- No URL shorteners · branded olli.insure short path only
- Transactional — opt-out exempt notice included
- HELP / STOP keywords auto-handled
Payment failed (in-app)
Title: Update your payment method
Your [$Amount] charge didn't go through. Fix the card on file to keep your coverage active.
/account/billingDeliverability guardrails for this card
- Frequency cap documented · dismissible
- Does not block the primary task
- Targeted by segment (never broadcast-to-all)
- Single CTA · plain-English action verb
Past-due / pending cancellation
Subject: Your policy may cancel on [Cancellation Date]
Preheader: Pay [$Amount Due] to keep your coverage in force.
Your account is past due. Without payment of [$Amount Due] by [Cancellation Date], your [Coverage Type] policy will cancel for non-payment. If cancelled, anything that happens after [Cancellation Date] won't be covered. Pay or update your card today to avoid a gap. — Olli
https://olli.insure/account/billingDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Notice of cancellation for non-payment (letter)
[Date] [Customer Name] [Address] Re: Notice of Cancellation for Non-Payment — Policy [Policy Number] Dear [Customer Name], This letter is your formal notice that your [Coverage Type] policy will be cancelled effective [Cancellation Date] at 12:01 AM for non-payment of premium in the amount of [$Amount Due]. To prevent cancellation, payment must be received by [Cure Date]. Pay online at https://olli.insure/account/billing, by phone at [Phone], or by mail to the address below. This notice is provided in compliance with [State] Insurance Code § [Citation], which requires [N] days' advance notice for cancellation for non-payment. If coverage is cancelled, you may reapply, but reinstatement is not guaranteed and a coverage gap will exist. Sincerely, Olli Insurance Services, LLC Licensed in [State], License #[License]
Why this is legally required: Notice period for non-payment cancellation is state-specific (commonly 10 days). Confirm against your state filings.
Deliverability guardrails for this card
- Mailed first-class with proof of delivery where required by state
- Includes policy number, effective date, and the legal cite
- Plain-English summary at top · legal text below
- Copy retained in customer account documents
- Olli return address + licensed-producer line in footer
Refund issued
Subject: Refund of [$Amount] is on its way
Preheader: Posted to card ending [last4]. 5–10 business days.
Your refund of [$Amount] is processed and on its way back to the card ending [last4]. Most banks post it within 5–10 business days. Reason: [Plain-English reason, e.g. mid-term cancellation, premium adjustment]. — Olli
https://olli.insure/account/billingDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Payment method expiring
Subject: Your card on file expires this month
Preheader: Add a new card to keep autopay running.
The card ending [last4] expires [MM/YY]. Add a new card before your next charge on [Next Charge Date] so autopay keeps your coverage in force. — Olli
https://olli.insure/account/billingDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Card expiring (push)
Title: Card on file expires soon
Card ending [last4] expires this month. Tap to update.
/account/billingDeliverability guardrails for this card
- Title ≤ 30 chars · body ≤ 100 chars
- Deep link to the exact in-app destination
- Sent under correct notification category/channel
- Transactional only unless explicit marketing opt-in
- No PII or codes in visible body
Claims
Intake to close, every customer-facing touchpoint.
DTC variants
Claim received
Subject: We received your claim — #[Claim Number]
Preheader: An adjuster will be assigned within 1 business day.
We have your claim. Here's what happens next. Claim number: [Claim Number] Received: [Date] Incident date: [Incident Date] An adjuster will be assigned within 1 business day and reach out to you directly. You can track status anytime in your account. — Olli Claims
https://olli.insure/account/claims/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Adjuster assigned
Subject: [Adjuster Name] is on your claim
Preheader: Direct line and email below. Expect contact within 24 hours.
[Adjuster Name] is your claims adjuster for claim #[Claim Number]. Direct: [Phone] Email: [Adjuster Email] They'll reach out within 24 hours to walk through the next steps. If you don't hear from them by then, reply here and we'll escalate. — Olli Claims
Deliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Documents requested
Subject: We need a few documents to move your claim forward
Preheader: Upload directly from your phone — takes about 5 minutes.
To keep claim #[Claim Number] moving, we need: • [Document 1] • [Document 2] • [Document 3] Upload directly from your account — photos from your phone are fine. We'll review within 1 business day of receiving everything. — Olli Claims
https://olli.insure/account/claims/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Documents requested (SMS)
Olli: Claim #[Claim Number] needs docs to proceed. Upload from your phone: https://olli.insure/c/xxx Account-service msg — opt-out exempt.
Deliverability guardrails for this card
- A2P 10DLC registered sender + campaign vetted
- Sender prefix 'Olli:' on first line
- Single segment (≤ 160 GSM-7 chars) preferred
- No URL shorteners · branded olli.insure short path only
- Transactional — opt-out exempt notice included
- HELP / STOP keywords auto-handled
Claim status update
Subject: Claim #[Claim Number] update
Preheader: Now in [Status]. Next step: [Next Step].
Quick update on claim #[Claim Number]. Status: [Status] What just happened: [Plain-English summary] What's next: [Next Step], expected by [Date] You don't need to do anything right now unless we ask. Track anytime in your account. — Olli Claims
https://olli.insure/account/claims/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Claim status (push)
Title: Claim update
Claim #[Claim Number] is now [Status]. Tap for details.
/account/claims/xxxDeliverability guardrails for this card
- Title ≤ 30 chars · body ≤ 100 chars
- Deep link to the exact in-app destination
- Sent under correct notification category/channel
- Transactional only unless explicit marketing opt-in
- No PII or codes in visible body
Claim decision
Subject: Decision on claim #[Claim Number]
Preheader: [Approved / Partially approved / Denied] — details inside.
We've made a decision on claim #[Claim Number]. Decision: [Approved / Partially approved / Denied] Covered amount: [$Amount] Reason: [Plain-English explanation] If approved, payment will be issued per the next message. If denied or partially approved, you have the right to appeal — instructions are attached and in your account. — Olli Claims
https://olli.insure/account/claims/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Claim payment issued
Subject: Payment of [$Amount] for claim #[Claim Number]
Preheader: Sent to [Method]. Arrives within [Window].
Your claim payment is on its way. Amount: [$Amount] Method: [ACH / check / card] Expected arrival: [Window] Less any deductible or coinsurance you owed: [$Deductible]. — Olli Claims
https://olli.insure/account/claims/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Claim closed
Subject: Claim #[Claim Number] is closed
Preheader: Final summary attached. Reopen anytime within [N] days.
Claim #[Claim Number] is now closed. A full summary PDF is attached and saved to your account. If something new comes up related to this claim, you can reopen it within [N] days by replying to this email. Thanks for working with us through this. — Olli Claims
Deliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
B2B2C variants
Claim received (B2B2C end user)
Subject: Your [Partner Name] claim is open — #[Claim Number]
Preheader: An adjuster will reach out within 1 business day.
Your claim under your [Partner Name] coverage is open. An adjuster will be assigned within 1 business day. Claim number: [Claim Number] Incident date: [Incident Date] Insurance for [Partner Name] is provided by Olli. Track status anytime in your [Partner Name] account. — [Partner Name] Support, provided by Olli
https://olli.insure/accountDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Compliance & Legal
State-required notices and regulatory disclosures.
DTC variants
State-required cancellation notice (letter)
[Date] [Customer Name] [Address] Re: Notice of Cancellation — Policy [Policy Number] Dear [Customer Name], This letter serves as formal notice that your [Coverage Type] policy is being cancelled, effective [Cancellation Date] at 12:01 AM. Reason for cancellation: [State-permissible reason] Statutory citation: [State] Insurance Code § [Citation] Advance notice provided: [N] days You have the right to: • Request a written explanation of the cancellation decision • Appeal to the [State] Department of Insurance: [DOI Phone / URL] • Receive any unearned premium refund within [N] days Sincerely, Olli Insurance Services, LLC Licensed in [State], License #[License]
Why this is legally required: Required by state insurance code for any non-payment or underwriting cancellation. Notice period and content requirements vary by state.
Deliverability guardrails for this card
- Mailed first-class with proof of delivery where required by state
- Includes policy number, effective date, and the legal cite
- Plain-English summary at top · legal text below
- Copy retained in customer account documents
- Olli return address + licensed-producer line in footer
Adverse action notice (letter)
[Date] [Customer Name] [Address] Re: Notice of Adverse Action Dear [Customer Name], This notice informs you that an adverse action has been taken on your application or policy with Olli, based in whole or in part on information contained in a consumer report. Action taken: [Declined / Rated up / Non-renewed] Consumer reporting agency used: [CRA Name], [CRA Address], [CRA Phone], [CRA URL] The CRA did not make the decision and cannot explain it. Under the Fair Credit Reporting Act, you have the right to: • Obtain a free copy of your consumer report from the CRA within 60 days • Dispute the accuracy or completeness of any information in the report directly with the CRA If you have questions about the underwriting decision itself, contact us at support@olli.insure. Sincerely, Olli Insurance Services, LLC
Why this is legally required: Required under the Fair Credit Reporting Act (FCRA) and state equivalents whenever a consumer report contributes to declining, rating, or non-renewing.
Deliverability guardrails for this card
- Mailed first-class with proof of delivery where required by state
- Includes policy number, effective date, and the legal cite
- Plain-English summary at top · legal text below
- Copy retained in customer account documents
- Olli return address + licensed-producer line in footer
Privacy / terms update
Subject: Updates to our Privacy Policy and Terms
Preheader: Plain-English summary of what changed and what it means for you.
We updated our Privacy Policy and Terms of Service, effective [Effective Date]. What changed, in plain English: • [Change 1] • [Change 2] • [Change 3] Nothing you need to do — your account and coverage continue as normal. Full text of both documents is on our site. — Olli
https://olli.insure/legalDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
B2B2C variants
1099 tax document available (partner)
Subject: Your [Tax Year] 1099 from Olli is ready
Preheader: Download from your partner dashboard. Filed with the IRS.
[Partner Name]: your [Tax Year] Form 1099-NEC from Olli is ready in your partner dashboard. We filed the same form with the IRS on [Filing Date]. Total commissions reported: [$Amount] If anything looks wrong, reply to this email by [Correction Deadline] so we can issue a correction. — Olli Partner Operations
https://olli.insure/partners/tax-documentsDeliverability guardrails for this card
- Subject ≤ 50 chars · plain-English
- Preheader 60–90 chars
- Plain-text alternative shipped
- List-Unsubscribe header + visible link
- Physical address + company legal line in footer
- SPF / DKIM / DMARC aligned · From: partners@olli.insure
- Co-branded header: partner logo left, 'Insurance by Olli' right
- Named partner manager as next contact
Partner / B2B2C
Partner-facing and co-branded end-user messages.
Partner invite
Subject: [Inviter Name] invited you to Olli for [Partner Name]
Preheader: Accept to access your partner dashboard and API keys.
[Inviter Name] added you to the [Partner Name] Olli workspace. What you get: partner dashboard access, API keys, embedded-flow controls, and the partner performance report. Accept the invite to set your password and sign in. — Olli Partner Team
https://olli.insure/partners/invite/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · plain-English
- Preheader 60–90 chars
- Plain-text alternative shipped
- List-Unsubscribe header + visible link
- Physical address + company legal line in footer
- SPF / DKIM / DMARC aligned · From: partners@olli.insure
- Co-branded header: partner logo left, 'Insurance by Olli' right
- Named partner manager as next contact
Partner onboarding
Subject: Welcome to Olli, [Partner Name] — here's your launch path
Preheader: Three steps to your first embedded quote.
Welcome aboard. Three steps to your first embedded quote: 1. Grab your sandbox API keys from the dashboard. 2. Drop our embed snippet into your application flow. 3. Run a test quote and ping your partner manager [Manager Name] for review. Most partners are live in under two weeks. We're here for any of it. — [Manager Name], Olli Partner Team
https://olli.insure/partnersDeliverability guardrails for this card
- Subject ≤ 50 chars · plain-English
- Preheader 60–90 chars
- Plain-text alternative shipped
- List-Unsubscribe header + visible link
- Physical address + company legal line in footer
- SPF / DKIM / DMARC aligned · From: partners@olli.insure
- Co-branded header: partner logo left, 'Insurance by Olli' right
- Named partner manager as next contact
Embedded handoff confirmation (co-branded)
Subject: Your [Partner Name] coverage is ready to review
Preheader: Coverage details and binding are inside [Partner Name].
Hi [First Name], Your quote from [Partner Name] is ready. The coverage was built for what you do — review the details and bind directly inside [Partner Name]. Insurance for [Partner Name] is provided by Olli, a licensed insurance services company. — [Partner Name], with Olli
https://olli.insure/handoff/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · plain-English
- Preheader 60–90 chars
- Plain-text alternative shipped
- List-Unsubscribe header + visible link
- Physical address + company legal line in footer
- SPF / DKIM / DMARC aligned · From: partners@olli.insure
- Co-branded header: partner logo left, 'Insurance by Olli' right
- Named partner manager as next contact
Monthly performance / commission statement
Subject: [Partner Name] [Month] statement is ready
Preheader: Policies, premium, and commission for the month.
[Partner Name]: your [Month] statement is in the dashboard. New policies: [N] Written premium: [$Premium] Commission earned: [$Commission] Payout date: [Date] Full breakdown and CSV export are in the partner dashboard. — [Manager Name], Olli Partner Team
https://olli.insure/partners/statementsDeliverability guardrails for this card
- Subject ≤ 50 chars · plain-English
- Preheader 60–90 chars
- Plain-text alternative shipped
- List-Unsubscribe header + visible link
- Physical address + company legal line in footer
- SPF / DKIM / DMARC aligned · From: partners@olli.insure
- Co-branded header: partner logo left, 'Insurance by Olli' right
- Named partner manager as next contact
API key / webhook failure alert
Subject: Webhook delivery failing for [Partner Name]
Preheader: [N] failed attempts in the last hour. Action may be needed.
Heads up — webhook deliveries to [Partner Name] are failing. Endpoint: [URL] Failure window: [Start UTC] to [End UTC] Attempts: [N] Last response: [Status code] [Message] We're retrying with exponential backoff for the next 24 hours. If the endpoint isn't fixed by then, events will be marked failed and we'll page your partner manager. — Olli Platform
https://olli.insure/partners/webhooksDeliverability guardrails for this card
- Subject ≤ 50 chars · plain-English
- Preheader 60–90 chars
- Plain-text alternative shipped
- List-Unsubscribe header + visible link
- Physical address + company legal line in footer
- SPF / DKIM / DMARC aligned · From: partners@olli.insure
- Co-branded header: partner logo left, 'Insurance by Olli' right
- Named partner manager as next contact
Webhook failing (SMS, on-call)
Olli: [Partner Name] webhook failing — [N] errors in the last hour. Logs: https://olli.insure/p/wh Account-service msg — opt-out exempt.
Deliverability guardrails for this card
- A2P 10DLC registered sender + campaign vetted
- Sender prefix 'Olli:' on first line
- Single segment (≤ 160 GSM-7 chars) preferred
- No URL shorteners · branded olli.insure short path only
- Transactional — opt-out exempt notice included
- HELP / STOP keywords auto-handled
Growth & Engagement
Referrals, education, NPS, win-back.
Referral invite
Subject: Know another solo who needs insurance?
Preheader: You both get [$Reward] when they bind their first policy.
If you know another freelancer or solo who's winging it without coverage, send them your referral link. When they bind their first policy, you both get [$Reward]. No limits, no fine print beyond what's on the link. — The Olli Team
https://olli.insure/account/referDeliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
Referral reward earned
Subject: [$Reward] is yours — [Friend First Name] is covered
Preheader: Reward credited to your account. Thanks for the introduction.
[Friend First Name] just bound their first policy with Olli. Your [$Reward] credit is on your account and will apply to your next renewal. Genuinely — thanks for sending them our way. — The Olli Team
https://olli.insure/account/billingDeliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
Referral reward earned (in-app)
Title: You earned [$Reward]
[Friend First Name] bound their first policy. Your credit is live and applies to your next renewal.
/account/billingDeliverability guardrails for this card
- Frequency cap documented · dismissible
- Does not block the primary task
- Targeted by segment (never broadcast-to-all)
- Single CTA · plain-English action verb
Cross-sell suggestion
Subject: You might want [Coverage Type] too
Preheader: Why we think it fits — and how to skip if it doesn't.
You're covered for [Existing Coverage]. Based on what you do, [Suggested Coverage] usually pairs with it because [Plain-English reason]. Not interested? No problem — ignore this email and we won't keep nudging. — The Olli Team
https://olli.insure/products/[suggested]Deliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
Cross-sell suggestion (in-app)
Title: Consider [Suggested Coverage]
Most solos doing [Activity] add this alongside their [Existing Coverage]. Worth a 60-second look.
/products/[suggested]Deliverability guardrails for this card
- Frequency cap documented · dismissible
- Does not block the primary task
- Targeted by segment (never broadcast-to-all)
- Single CTA · plain-English action verb
Insurance 101 drip (solo edition)
Subject: Insurance, in plain English — Part 1
Preheader: What 'general liability' actually covers, in 3 minutes.
Most insurance writing is built for insurance people. This series isn't. Today: general liability. What it actually covers, what it doesn't, and when a solo entrepreneur needs it. [Short, plain-English explanation, ~150 words.] Next week: professional liability vs. E&O. If you want to skip the series, the link is at the bottom. — The Olli Team
https://olli.insure/learn/general-liabilityDeliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
NPS / review request
Subject: Two questions, 10 seconds
Preheader: How did we do? Your answer changes what we build next.
Two questions, no tricks: 1. On a 0–10 scale, would you recommend Olli to another solo? 2. Why? Reply to this email or tap below. Real humans read every answer — and they shape what we build next. — The Olli Team
https://olli.insure/feedback/npsDeliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
Win-back for churned users
Subject: If anything's changed, we can take another look
Preheader: Your account is still here. Requote anytime.
You cancelled your Olli coverage a while back. If anything's changed about your business — new revenue, new clients, a contract that requires coverage — we can requote in a couple of minutes. No pressure. Your account is still here when you need it. — The Olli Team
https://olli.insure/quoteDeliverability guardrails for this card
- Subject ≤ 50 chars · no ALL CAPS · no spammy punctuation
- Preheader 60–90 chars · written intentionally
- Plain-text alternative shipped (multipart/alternative)
- ≥ 60% text-to-image ratio · descriptive alt text
- List-Unsubscribe header + one-click + visible footer link
- Physical mailing address + 'why you're getting this' line
- SPF / DKIM / DMARC aligned on olli.insure
- From: hello@olli.insure (monitored) · never noreply@
- Links on olli.insure or branded tracking subdomain
- Dark-mode safe colors · honors sunset/suppression policy
Operational / Transactional
2FA, appointments, signatures.
2FA code (SMS)
Olli: Your sign-in code is 123456. Expires in 10 min. Do not share. Account-service msg — opt-out exempt; reply HELP for help.
Deliverability guardrails for this card
- A2P 10DLC registered sender + campaign vetted
- Sender prefix 'Olli:' on first line
- Single segment (≤ 160 GSM-7 chars) preferred
- No URL shorteners · branded olli.insure short path only
- Transactional — opt-out exempt notice included
- HELP / STOP keywords auto-handled
Appointment reminder with licensed agent
Subject: Your call with [Agent Name] is tomorrow
Preheader: [Date] at [Time, Timezone] · [Duration] minutes
Quick reminder — you have a call with [Agent Name], one of our licensed insurance pros, tomorrow. When: [Date] at [Time, Timezone] Length: [Duration] minutes Where: [Meeting Link] If you need to reschedule, the link below has open times. Otherwise, see you then. — Olli
https://olli.insure/account/appointments/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
Appointment reminder (SMS)
Olli: Reminder — call with [Agent First Name] tomorrow at [Time TZ]. Join: https://olli.insure/a/xxx Account-service msg — opt-out exempt.
Deliverability guardrails for this card
- A2P 10DLC registered sender + campaign vetted
- Sender prefix 'Olli:' on first line
- Single segment (≤ 160 GSM-7 chars) preferred
- No URL shorteners · branded olli.insure short path only
- Transactional — opt-out exempt notice included
- HELP / STOP keywords auto-handled
E-signature document request
Subject: [Document Name] is ready for your signature
Preheader: About 2 minutes. No printer needed.
[Document Name] is ready for your signature. It takes about two minutes from your phone — no printing, no scanning. If you'd like to read it first, the unsigned PDF is attached. Sign-here tags are clearly marked when you open the link. — Olli
https://olli.insure/sign/xxxDeliverability guardrails for this card
- Subject ≤ 50 chars · states the action clearly
- Preheader explains what changed · 60–90 chars
- Plain-text alternative shipped (multipart/alternative)
- Footer: physical address + security notice (no marketing unsubscribe)
- SPF / DKIM / DMARC aligned on olli.insure
- From: no-reply@olli.insure with monitored reply-to
- Links on olli.insure · no third-party shorteners
- No marketing CTAs · no upsells
