01
Abandoned order from a custom store
Before the store runs on a custom engine, and Klaviyo saw nothing — abandoned carts were lost.
After the store sends a 'cart started' event to Klaviyo, and the reminder flow starts by itself with the exact products left in the cart.
02
CRM customers become Klaviyo segments
Before the marketer exported the customer base from the CRM once a month and uploaded it to Klaviyo; segments were always out of date.
After profiles update as soon as a manager changes a deal stage, and segments such as 'bought in the last 30 days' rebuild themselves.
03
Order status messages
Before the warehouse changed the status in the accounting system, and the client found out about shipping only by calling.
After 'shipped' and 'ready for pickup' events go to Klaviyo, and the client receives an email or SMS with the tracking number within the flow.
04
Subscription consent in one place
Before a client unsubscribed in Klaviyo but kept getting messages from the CRM, and vice versa.
After subscribe and unsubscribe actions sync both ways, and the client's choice is respected everywhere.