AD SPACE AVAILABLE · BRAND PARTNERS WELCOME

How to Configure Klaviyo AI's Send Time Optimization and Predictive Recommendations for Automated Flows

365Finds Editorial
Indexed 11,430 Wiki articles

Put 365 Wiki to work with your AI

Copy the prompt below, paste it into the AI you already use, then ask your question.

Download full Skill

Try it with the prompt first. If you use 365 Wiki often, install the full 365Wiki Skill so you do not have to paste it again. No regular AI? Gemini or Microsoft Copilot on the web will work.

365Wiki Skill

Automated email flows—such as abandoned checkout sequences, post-purchase follow-ups, and replenishment reminders—drive a disproportionate share of e-commerce revenue compared to broadcast campaigns. However, standard automation flows often suffer from two major shortcomings: rigid time delays that deliver emails when customers are asleep or distracted, and generic product grids that fail to reflect individual shopping preferences.

Klaviyo addresses both issues by combining machine learning models with native customer data. To get the maximum return on investment from these tools, merchants must understand how Klaviyo's send time algorithms operate across campaigns and flows, how dynamic product recommendation engines curate catalog items, and how to configure them inside the Klaviyo flow builder.


1. Understanding Klaviyo AI's Send Time Optimization: Campaigns vs. Flows

A common source of confusion among merchants is the difference between Klaviyo's timing optimization tools. Klaviyo offers two distinct AI timing mechanisms, and understanding how they interact with automated flows is essential for effective setup.

Smart Send Time vs. Personalized Send Time

How Timing Works in Automated Flows

Neither Smart Send Time nor Personalized Send Time functions as a simple drag-and-drop node inside automated event-triggered flows. Automated flows are inherently triggered by real-time customer behavior (such as Started Checkout, Added to Cart, or Placed Order). Klaviyo manages flow timing through Time Delay components, Quiet Hours, and Predictive Analytics properties:

  1. Flow Time Delays with Local Time Restrictions: In any flow, merchants can set a delay (e.g., 2 hours, 1 day) and restrict delivery to specific hours in the recipient's local time zone (e.g., "Send only between 9:00 AM and 8:00 PM in recipient's local time").
  2. Applying Campaign Timing Insights to Flow Delays: Data gathered from Smart Send Time and campaign reports provides the baseline conversion hours for your store. If exploratory sends show peak purchasing between 7:00 PM and 9:00 PM local time, your second abandoned checkout reminder or winback email can be scheduled to hold until that peak window.
  3. Predictive Analytics Timing: For retention and repeat purchase flows, Klaviyo AI calculates profile-level attributes:
    • Expected date of next order: Machine learning forecasts when a specific shopper is due to buy again based on historical order cadence.
    • Predicted Customer Lifetime Value (CLV): Categorizes profiles into high, medium, and low expected spenders.
    • Churn Risk: Identifies whether a customer is active, at risk, or dormant.

2. Configuring Predictive Product Recommendations in Klaviyo

Predictive product recommendations in Klaviyo rely on synced catalog data (via Shopify, BigCommerce, WooCommerce, or custom API feeds) and individual browsing and purchasing events.

Step 1: Create and Configure Dynamic Product Feeds

Before embedding recommendations into flow templates, set up dedicated feeds in the Klaviyo dashboard:

  1. Navigate to Content > Products in the left-hand navigation.
  2. Select the Product feeds tab and click Create Product Feed.
  3. Name your feed based on its strategic purpose (e.g., Post-Purchase Cross-Sell, Cart Abandonment Alternatives, or Trending Fallback).
  4. Select the recommendation algorithm:
    • What customers have purchased (Customers Also Bought): Evaluates co-purchase patterns across your catalog. If a customer bought Product A, the feed surfaces Products B and C that other shoppers frequently bought in subsequent or bundled orders. Best for post-purchase and repeat-purchase flows.
    • Recently viewed products: Dynamically surfaces items the customer browsed during recent web sessions. Best for browse abandonment and high-intent recovery flows.
    • Popular / Best-selling products: Displays top revenue-generating items across the store or within selected categories. Essential as fallback logic.
  5. Set filtering and exclusion rules:
    • Filter by collections or categories to avoid irrelevant cross-sells (e.g., excluding gift cards, clearance parts, or apparel sizes).
    • Confirm that out-of-stock items are automatically excluded.
    • Enable the suppression of items already purchased by the recipient so customers are never shown items they already own (ideal for non-consumable goods).
  6. Configure Fallback Logic: When a shopper has insufficient behavioral history for personalized recommendations, Klaviyo automatically falls back to your best-selling catalog items. Ensure your fallback sort order is defined.

Step 2: Insert Dynamic Product Blocks into Flow Emails

  1. Open your target flow in the Flow Builder (e.g., Abandoned Cart or Post-Purchase Series).
  2. Click the email action node and select Edit.
  3. In the email template editor, drag the Product block from the left panel into your layout.
  4. In the block configuration panel, change the mode from Static to Dynamic.
  5. Select your newly created Product Feed from the dropdown menu.
  6. Customize the display attributes:
    • Set the layout (1 to 4 columns).
    • Toggle product title, image, price, and "Shop Now" buttons.
    • Ensure links dynamically append tracking parameters to measure flow-driven revenue.

3. Implementation Playbook for Core Customer Flows

Flow TypeTrigger EventOptimal Timing ConfigurationRecommended Product Feed Strategy
Abandoned CheckoutStarted CheckoutWait 1-2 hours for Email 1; wait 20-24 hours for Email 2; delay to daytime local hoursPrimary block: Dynamic checkout event table; Secondary block: Related best sellers in category
Post-Purchase Cross-SellPlaced OrderWait 7 to 14 days; aligned with fulfillment delivery confirmation"Customers Also Bought" feed excluding current order items
Predictive ReplenishmentExpected Next Order Date or Segment TriggerWait until 7-10 days before Expected Next Order DateConsumable re-order reminder with refill or adjacent line recommendations
Customer WinbackChurn Risk = HighTriggered when customer enters churn segment; quiet hours enforcedTrending storewide best-sellers combined with targeted promotional incentive

4. Detailed Configuration for Key Flows

A. Abandoned Checkout Recovery

B. Post-Purchase and Repeat Purchase Retention

C. Predictive Winback & Churn Prevention


5. Best Practices, Pitfalls, and Deliverability Safeguards

  1. Verify Minimum Data Thresholds: Klaviyo's predictive models (CLV, Churn Risk, Expected Order Date) require sufficient transaction volume. If your store has fewer than several hundred completed orders, predictive properties may remain unpopulated. Allow historical data to sync thoroughly after initial store integration.
  2. Always Configure Fallbacks: Never assume every visitor has a populated browsing profile. If a new subscriber enters a flow, an unconfigured recommendation feed can show blank spaces. Always set a fallback rule to display best-selling catalog items.
  3. Respect Quiet Hours: Ensure your flow delays do not release automated emails or SMS during late-night or early-morning windows. Use Klaviyo's "Quiet Hours" and "Only send during specific hours" settings to align delivery with waking hours.
  4. Avoid Duplicate Purchases on Non-Consumable Catalogs: In furniture, electronics, and apparel, selling a customer an identical item rarely works. Ensure the "Exclude already purchased products" setting is toggled on in your dynamic product feed settings.
  5. Monitor Revenue Lift via Flow A/B Testing: Use Klaviyo's Flow Branching A/B test feature to compare an email containing only static copy against one with a Dynamic Product Recommendations block. Track placed order rate, click rate, and revenue per recipient to validate performance gains.

References