LIFECYCLE CASE STUDY

Launch the flows, then keep checking the events.

IcyBear’s launch work connected lifecycle messages with the brand’s relaunch, followed by winback, cart and browse testing.

Selected delivery milestones: March–April 2026

LIFECYCLE CASE STUDY

Three decisions behind the work.

Selected delivery milestones: March–April 2026

01 · THE CONTEXT

The starting point

A website launch changes the context for automated messages. The project coordinated the lifecycle programme with launch communication, then continued testing the messages and monitoring the events that triggered them.

02 · THE WORK

The decisions behind the journey.

Coordinate the launch

A 3 March update confirmed the flows had gone live the previous night and customers were entering them. Email, SMS and WhatsApp launch communication was coordinated around the same milestone.

Extend the testing

By 10 April, winback, abandoned-cart and browse journeys were confirmed live. The update described content-structure and subject-line tests, including SMS in winback.

Keep operational checks visible

Later welcome-trigger problems required further investigation. The June close-out follow-up recorded a fallback to an older welcome flow while support work continued. A launch confirmation alone was not treated as proof of permanent reliability.

INSIDE THE DECISIONS

A launch is a moment. Reliability is an ongoing job.

IcyBear’s March relaunch connected automated journeys with email, SMS and WhatsApp communication. The first useful confirmation was that customers were entering the live flows. April then added a distinct testing stage around winback, cart and browse messages. Launch coordination and optimisation were separate parts of the work.

The later welcome-trigger issue makes this story more instructive. A flow can appear active in the platform without receiving the event it needs. The June fallback to an older welcome was a recorded operating response while support continued, rather than evidence that the new trigger had been permanently repaired.

Watch the relationship between traffic and entrants.

For another relaunch, compare customer activity with the events reaching the email platform. If signup activity continues while welcome entrants fall away, inspect the connection before rewriting the messages. Also check whether a customer who purchases leaves the appropriate recovery journey.

Keep the incident timeline beside the test timeline. A subject-line or content comparison is harder to interpret when one path has stopped receiving eligible customers. Record which version was running and why a fallback was introduced. This turns handover into a usable account history rather than a broad statement that everything was live.

03 · THE OUTCOME

What the work delivered.

The March and April updates confirm launched journeys and active testing. This case study covers those implementation milestones and the monitoring lesson; it does not claim a resolved welcome-trigger issue or an isolated commercial lift.

WHAT TO APPLY

Take the lesson into your own programme.

Follow a launch with real entrant and delivery checks. A flow can remain switched on while its trigger stops working. Keep the business event, entry count and fallback plan visible during handover.

Selected delivery milestones: March–April 2026. This case study covers the specific work described. Journey diagrams explain the approach.

QUESTIONS ABOUT THE WORK

What this case study shows.

Why keep checking triggers after flows go live?

IcyBear’s March–April 2026 work connected lifecycle messages with a brand relaunch, followed by winback, cart and browse testing. Launching the creative does not establish that events will continue arriving correctly. Monitor entries, eligibility and delivery after launch, especially when the storefront or checkout changes.

How do you verify that an automated customer journey actually works?

Test the path from the source event to the intended recipient and destination. Check the payload, customer state, eligibility, missing-data fallback and link after the click. Record creative approval, activation and observed delivery separately. A live switch alone does not establish that the right people receive the right message.

YOUR NEXT CHAPTER

What could your email programme do next?

Find the opportunities in your customer journey.

Browse all Thrivelia case studies

Discuss your customer journey with Thrivelia

Original campaign example

One offer, several routes into the range

The opening panel states the promotion and gives the reader a direct shopping action. Below it, individual product cards explain different jobs within a dental-care routine. That makes the catalogue easier to navigate than a list of product names alone. The founder-style message and rewards panel add separate reasons to consider the brand, while keeping the sale as the main campaign decision.

When adapting this structure, keep promotional eligibility and loyalty status distinct. Review delivered-email revenue and unsubscribes together.

IcyBear · Original campaign email · 2026-04-30

Explore the service and a related guide

For a similar customer journey, explore our retention marketing services and the beauty and skincare retention guide. Use the case's scope and measurement context to decide which lessons fit your account.

Review the available engagement scopes and pricing before choosing a delivery model.