.png)
.png){kind=small}
Updated: 13 hours ago
Revel Nail: Email & SMS Recovery Case Study
LIFECYCLE CASE STUDY
One recovery conversation. Email and SMS in step.
Revel Nail’s recovery work coordinated Klaviyo and Attentive journeys, with audience splits designed to manage the migration between platforms.
Implementation milestones: June 2024
LIFECYCLE CASE STUDY
Three decisions behind the work.
Implementation milestones: June 2024
01 · THE CONTEXT
The starting point
Migrating email while retaining SMS can leave overlapping journeys. The project needed to keep the recovery conversation useful while the account moved through that transition.
THE CHALLENGE
Move the journeys without losing their meaning.
Revel Nail’s June 2024 work combined an email-platform migration with anniversary-sale preparation. Existing recovery journeys were running in Attentive while email activity moved into Klaviyo. Switching on a replacement flow was only one part of the change: the team needed to know which customers belonged in each system and whether the events driving those journeys were actually available.
The sale also depended on a customer base interested in particular new and returning shades. That shaped the creative brief. During the 12 June review, the client explained that manicure photography and swatches communicated the product better than closed jars, because the applied colour was what customers wanted to evaluate.
Thrivelia responded by updating the day’s emails and agreeing to replace jar images with manicure photography. The lesson from the exchange is specific to the purchase decision: show the result a customer is choosing, and let the offer support that choice. The reviewed discussion does not supply a quantified creative-test result.
02 · THE WORK
The decisions behind the journey.
Separate the migration audiences
A 12 June client update confirmed browse and checkout emails had moved into Klaviyo for customers outside the SMS list. The Attentive journey remained active for SMS subscribers.
Extend recovery coverage
On 18 June, Thrivelia confirmed the additional and Upstackified added-to-cart flows were configured. The client clarified that the tracking code would be deployed after the anniversary sale, so the added-to-cart journey would not fire until then.
Coordinate campaign timing
The campaign work included sale anticipation and an add-to-calendar invitation, with send planning tied to audience engagement. Further recovery tests were proposed as the next step.
THE MIGRATION AND SALE HANDOFF
Audience rules had to survive the move.
On 12 June, the client confirmed that browse-abandonment flows for starter-kit and non-starter-kit shoppers, plus checkout recovery, were live in Klaviyo. A split limited those sends to customers outside the SMS list. The Attentive journey remained active for customers on that list. This was a defined transitional audience rule, with implementation contributions from both the client and Thrivelia.
Added-to-cart recovery covered an earlier event than checkout. On 17 June, Thrivelia asked whether that stage was already covered in Attentive and discussed activating it alongside the migration. A shopper adding a product to a cart has taken a different action from someone starting checkout; naming the flow is not enough to confirm that its event is being captured.
On 18 June, Thrivelia reported the additional flow and Upstackified added-to-cart flow as ready and live. The client immediately clarified that the theme containing the tracking code would go live after the anniversary sale, so that journey would not fire until then. The accurate milestone is a configured flow with a pending site-tracking dependency, not demonstrated sends from the added-to-cart journey on that date.
The member-only sale preview revealed another data dependency. The client identified active Revelist members through a Shopify customer tag, but that tag was not appearing in Klaviyo during the review. The team investigated the sync, and the client offered an export for import. The thread records a proposed workaround, not confirmation that the missing-tag problem had already been resolved.
This mattered because an exclusive preview and a general sale announcement required different audiences and reveal times. An add-to-calendar invitation was discussed to remind customers when the sale started, while the team checked that offer details would not go to the broader audience prematurely. Copy, landing-page availability and segment readiness had to be reviewed together.
Send frequency was also discussed as a decision, not a blanket rule. The team recommended a pause before the daily anniversary-sale sequence and later proposed sending more frequently to the most engaged customers, with a broader first send and close deliverability monitoring. The sources show the recommendation; they do not establish a performance lift from increased frequency.
03 · THE OUTCOME
What the work delivered.
The clearest verified milestone is the 12 June client confirmation of live Klaviyo browse and checkout recovery for the non-SMS audience, with the Attentive journey retained for SMS-list customers. The creative review also records updates in response to the client’s product and photography guidance.
The 18 June added-to-cart milestone is narrower: the flow was configured, but its site-tracking code was due to be deployed after the anniversary sale. Keeping that dependency visible makes the case useful to another team planning a migration. A flow marked live in the platform and a journey receiving qualifying events are separate checks.
This project illustrates the coordination between creative, audience data and recovery infrastructure during a sale. The reviewed implementation records do not provide a controlled revenue comparison, a verified added-to-cart send result or a testimonial about those outcomes.
WHAT TO APPLY
Take the lesson into your own programme.
During a channel migration, define which platform owns each audience and event. Keep added-to-cart and checkout distinct, and verify that customers do not receive duplicated messages from parallel systems.
Implementation milestones: June 2024. This case study covers the specific work described. Journey diagrams explain the approach.
QUESTIONS ABOUT THE WORK
What this case study shows.
How can Klaviyo and Attentive avoid overlapping recovery messages?
Revel Nail’s recovery work coordinated Klaviyo and Attentive with audience splits based on SMS-list status. The lesson is to define which channel handles each eligible customer and to check the combined message sequence. Channel consent and journey eligibility are separate checks; appearing in an email audience does not establish permission for SMS.
How should welcome and abandonment flows avoid conflicting messages?
Give higher-intent events a clear place in the journey and review purchase exclusions, entry conditions and re-entry behaviour. Test a customer who subscribes, browses, starts checkout and then buys. The objective is a coherent sequence that changes with the customer’s actions, rather than several isolated automations competing for attention.
YOUR NEXT CHAPTER
What could your email programme do next?
Find the opportunities in your customer journey.
Comments