> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digifist.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation Recipes

> Pre-built flow examples for the most common WhatsApp automation use cases in Galantis.

Recipes are fully documented automation flows built around the most common Shopify merchant use cases. Each recipe shows the complete node sequence — trigger, delays, conditions, and actions — with the reasoning behind each step explained.

Use recipes as a starting point for your own flows. Every recipe can be adapted: add or remove condition branches, change delay durations, swap templates, or extend the sequence with additional steps.

## Available recipes

<CardGroup cols={2}>
  <Card title="Abandoned Checkout Recovery" icon="cart-shopping" href="./abandoned-checkout">
    Recover customers who started checkout but did not complete — with value-based branching for VIP and standard recovery paths.
  </Card>

  <Card title="Post-Purchase Cross-Sell" icon="bag-shopping" href="./post-purchase-cross-sell">
    Trigger product-specific recommendations after an order based on what the customer purchased.
  </Card>

  <Card title="VIP Win-Back" icon="star" href="./vip-win-back">
    Re-engage high-value lapsed customers when they enter a defined lapsed-buyer segment.
  </Card>

  <Card title="Back-in-Stock Notification" icon="bell" href="./back-in-stock-notification">
    Notify customers automatically when a product variant they subscribed to is restocked.
  </Card>

  <Card title="New Customer Welcome" icon="hand-wave" href="./new-customer-welcome">
    Send a welcome message with a first-order discount shortly after a new customer registers.
  </Card>
</CardGroup>

## Before using a recipe

Every recipe sends WhatsApp templates. Before activating any recipe-based automation:

* Create and submit the required templates for Meta approval — see [Templates](/whatsapp/templates/index)
* Configure the appropriate frequency cap for the automation's use case — see [Frequency Caps](../frequency-caps)
* Add any relevant exclusion rules — see [Exclusion Rules](../exclusion-rules)

Templates must reach `APPROVED` status before the automation can be activated.