Dashboard → Settings → Notifications → Email Delivery

Get started with Umbrella and Klaviyo in four steps

Connect Klaviyo and Umbrella’s customer emails — policy confirmations, claim updates, warranty offers — send from your Klaviyo account instead of Umbrella’s. They use the sending domain you have already verified there, your designs, and your unsubscribe handling.

That also means you can skip the DNS setup on the Email Domain tab for customer email. Umbrella still decides who gets notified and when; Klaviyo does the sending.

1 Connect Klaviyo

2 Build a flow

3 Turn on routing

4 Check readiness

Step 1 — Connect Klaviyo

Go to Settings → Notifications → Email Delivery and select Connect with Klaviyo. Sign in, approve the permissions, and you are returned to Umbrella. There is nothing to copy or paste.

When you connect, Umbrella sets up your account automatically:

Creates the flow triggers. Fifteen metrics appear in Klaviyo, one per notification, each named like Umbrella: Policy Purchased. They have to exist before Klaviyo will offer them as a trigger.
Adds fifteen email designs to your template library, matching your Umbrella templates and named after the same metrics. They are a starting point, not a cage — see below.

Note The setup events Umbrella sends to create those metrics are backdated by a month, so they cannot trigger a flow or reach a real customer.

You can revoke Umbrella’s access at any time from Klaviyo, or disconnect from this tab.

Step 2 — Build a flow in Klaviyo

Klaviyo sends the email, so each notification you want it to handle needs a flow listening for that notification’s metric.

In Klaviyo: Flows → Create Flow → Metric, choose a trigger such as Umbrella: Policy Purchased, add an Email action, and start from the saved template of the same name. Then set the flow Live.

Important A flow that is left in Draft or Manual looks connected but never sends. Only Live flows deliver.

Start with one notification — Policy Purchased is the usual first — and add the rest once you have seen it work end to end.

Using the event data

Each event carries the details for that email, so your design can reference them directly:

{{ event.customerName }}, {{ event.policyNumber }}, {{ event.productName }}, {{ event.orderName }}
{{ event.policies }} — a list, for orders with more than one policy, so you can loop over it in your own markup

The templates Umbrella pushes already reference these. Edit one inside Klaviyo and it becomes yours: Umbrella detaches it and stops overwriting it, and the trigger list marks it Edited in Klaviyo. Use Sync designs on this tab to pull Umbrella’s version back down for anything you have not touched.

Step 3 — Turn on routing

Connecting does not move any email on its own — you choose what goes where.

All customer email: turn on Send customer emails through Klaviyo on the Email Delivery tab.
One notification at a time: on the Notification Preferences tab, each customer notification has a destination next to its on/off control — Default, Umbrella, or Klaviyo.

Nothing is lost while you build. If you route a notification to Klaviyo before its flow is live, Umbrella sends that email through its own service instead. Customers keep receiving everything; you just do not get your branding on it yet.

Merchant alerts and scheduled reports — new claim notifications, daily and monthly summaries — always send through Umbrella. They are internal operations mail, not customer marketing.

Step 4 — Check readiness

The Flow triggers list on the Email Delivery tab shows the state of each notification:

Live — a flow is running and Klaviyo will send it
No flow — nothing is listening; Umbrella is sending it instead
Not set up — the metric has not been created yet

Select Re-check flows after building a flow in Klaviyo to refresh the list. Umbrella also re-checks on its own while sending, so a paused or deleted flow is noticed rather than silently swallowing email.

Optional: sync warranty activity

Send warranty activity to Klaviyo adds policy and claim events to your customers’ Klaviyo profiles overnight — coverage activated, expiring in 90 / 60 / 30 days, expired, claim filed, claim resolved. No emails are sent by this on its own.

It exists for segmentation and campaigns: customers whose coverage lapses next month is a renewal audience you can build and target. It is off until you turn it on.

Billing Klaviyo charges by active profile. Most warranty customers are already in your account from your store sync, so the difference is usually small — but adding new ones can affect your Klaviyo plan.

Troubleshooting

Emails still arrive with Umbrella branding. The flow is not Live, or routing is still set to Umbrella. Check the Flow triggers list — anything not Live is being sent by Umbrella.

“Reconnect required”. Umbrella’s access was revoked in Klaviyo, or went unused for 90 days. Select Connect with Klaviyo again; your routing choices and flows are preserved.

A design will not update from Umbrella. It is marked Edited in Klaviyo, which is deliberate — your edits are never overwritten.

Notification Settings — which notifications are sent, and to whom
Email Templates — editing the content Umbrella pushes to Klaviyo
Email Domain — sending through Umbrella on your own domain instead