An abandoned cart email is not arriving, and the flow looks live. The quickest useful question is not “which setting should I turn off?” It is “where did this specific customer journey stop?”
Use a controlled test and trace five stages: the event, the profile, entry into the flow, the email step and the recovery experience. That gives your VA or specialist evidence to investigate instead of a list of settings changed at random.
1. Confirm the event the flow expects
Read the actual trigger. Klaviyo distinguishes flows triggered by Added to Cart from those triggered by Started Checkout in its abandoned cart guide. Adding a product to the cart does not by itself test a Started Checkout flow.
Use the supported test approach for your store integration and a test address you control. Note the action, time, product and browser conditions. Avoid creating unnecessary real transactions just to see whether an email arrives.
Look for the expected event in the appropriate metric or profile activity. If it is absent, investigate the event collection and integration before changing the flow's content.
2. Check the profile and the event details
Identify which profile received the event. Check the test email address and whether the event contains the information expected by the flow.
An event existing somewhere in the account is not enough. It needs to be the relevant event connected to the intended test profile. Note the integration associated with the metric so a similarly named event is not mistaken for the correct one.
Keep test records clearly identifiable. If you use an existing profile, review its previous activity because that history may affect conditions in the flow. Document the test before involving any real customer record.
3. Find whether the profile entered the flow
Check the entry conditions and compare them with the event and profile. Read the filters as a description of who should qualify. Do not remove them merely because the test was excluded.
Klaviyo's metric-triggered flow troubleshooting guide explains how to inspect the trigger and relevant metric. Use the recipient activity and available reasons to distinguish a person who never entered from one who entered and was later skipped.
A test that correctly fails a condition is evidence that the condition is working. The next question is whether the condition matches your intended recovery strategy.
4. Inspect the specific email step
Review the message status, delay and recipient activity. A flow can contain email steps with different statuses. A person may be waiting, awaiting manual review, skipped or already sent.
Check the reason attached to the specific recipient. If Smart Sending explains the skip, consult Klaviyo's Smart Sending documentation. Do not assume a skipped message will automatically send later.
Keep the original settings in your change notes. Test one relevant adjustment at a time and record the resulting behaviour. This makes the investigation easier to review and prevents several unrelated changes from becoming the new unexplained setup.
5. Test the experience after delivery
If the email is recorded as sent, check the destination inbox and any available delivery information. Then inspect the actual recovery message using the test event.
Do the product details make sense? Does the recovery link lead to the expected place? Is the offer accurate? Are any dynamic fields missing? A static design preview may not reveal a problem with event-specific content.
Record the expected outcome and actual outcome. A message that arrives with an unusable link needs a different fix from a message that was never triggered.
Review the broader recovery setup
Check which other systems send recovery messages. Klaviyo's setup guide warns about duplicate store-platform recovery emails when using its flow. Map the existing messages before deciding which system should own each part of the journey.
Also check what should happen after a purchase. The flow's conditions should reflect the intended customer experience, and the test should include a review of that behaviour. Keep promotional copy aligned with current products, stock and offers.
This review is particularly useful before a busy promotion. Our Black Friday checklist covers the wider preparation around your emails.
A diagnostic brief you can hand over
Store integration and exact trigger metric.
Controlled test profile and event timestamp.
Expected behaviour at each of the five stages.
The first stage that differs from the expectation.
Recipient status and available skip or delivery reason.
Original settings and any changes already tested.
Links to the relevant flow and approved offer brief.
Use your approval rules to distinguish evidence gathering from changes to live automation. A trained VA can collect the test record and coordinate the investigation; decisions about targeting and live settings need the appropriate authority.
VAmazing connects email strategy with practical implementation and ongoing coordination. Explore our Klaviyo support or get in touch with the stage that needs attention.