Here is the latest and most complete version of the help article on using the Conditional Step in Cavaco AI’s Flow Builder, with all pieces integrated for publishing:

🧩 How to Use Conditional Steps in Cavaco AI Flows

The Conditional Step is a powerful logic block inside Cavaco AI’s Flow Builder that lets you split your automation flow based on who a customer is, what they've done (or not done), and what they're eligible for—such as receiving SMS or email messages.

This allows for highly targeted automation, helping you send the right message, to the right person, at the right time.

🔧 What is a Conditional Step?

A Conditional Step evaluates user attributes, behaviors, segment/list membership, product interactions, or engagement metrics and directs customers down different paths in your flow—typically a Yes or No branch.

For example:

• ✅ If a customer is opted into SMS, send them a text message.
• ❌ If not, send them an email instead.

You can layer in more logic using AND/OR operators to create advanced targeting.

🛠️ How to Add and Configure a Conditional Step

1. Drag in a Conditional Step block from the Flow Builder panel.
2. Name your condition (e.g. "If Customer Can Receive SMS").
3. Select a Condition Type.
4. Define the logic using dropdown menus and value selectors.
5. Add + And or + Or clauses as needed.
6. Connect the Yes and No branches to different next steps.

🔍 Available Condition Types

Here’s a breakdown of each condition type you can use:

1. ✅ If Someone Can or Cannot Receive Marketing

Use this to check if the customer has consented to receive email or SMS.

Example Setup:

• Condition: Customer has SMS Marketing
• Value: Enabled

Use Case: Only send SMS if the customer has opted in.

2. 🔁 Has Been in This Flow

Checks whether a customer has entered or completed the current flow previously.

Example Setup:

• Condition: has been in this flow
• At least: 1
• Timeframe: over all time

Use Case: Avoid sending the same promotion again to returning customers.

3. 📬 What Someone Has Done (or Not Done)

Triggers logic based on specific events or lack of action.

Available Metrics:

• Email: Opened, Clicked, Rejected, Complained, Bounced
• SMS: Sent, Failed, User Optout
• Orders: Placed, Shipped, Cancelled, Refunded
• Product: Viewed, Added to Cart

Example Setup:

• Condition: what someone has done (or not done)
• Event: Email Opened
• Count: 0
• Timeframe: in the last 7 days

Use Case: Resend an offer to users who didn’t open the first message.

4. 📦 Properties About a Product

Target users based on product interactions or attributes.

Example Fields:

• Cavaco Stats: Revenue, Orders, Views, Carts (over multiple time windows)
• Shopify Data: Price, Tags, Inventory, Product Name, On Sale

Use Case: Trigger logic based on cart size, product type, or popularity.

5. 🙋 Properties About Someone

Target based on the customer profile or Cavaco-generated engagement signals.

Example Fields:

• Address: City, Zip, Country
• Cavaco Engagement: Total Spent, Last Seen, Preferred Hour
• RFM Segments: Recency, Frequency, Score
• Personal Info: Email, Phone, DOB, Tags

Use Case: Prioritize VIP customers or send location-based messages.

6. 📊 If User Belongs to a Segment

Check if the user is in a saved dynamic segment.

Example Segments:

• Engaged (30/60/90 Days)
• Abandoned Checkout
• At-Risk Customers
• Loyal Customers

Use Case: Show different offers to loyal vs. disengaged users.

7. 📋 If User Belongs to a List

Check if the customer is in a static list you’ve imported or manually created.

Example Lists:

• SMS Subscribers List
• Email Subscribers List
• Holiday Promotions List
• New Product Releases List

Use Case: Send targeted content to a curated list.

🔀 Combine Conditions with AND / OR

Cavaco lets you chain multiple rules to create advanced filters:

• Customer has SMS Marketing = Enabled
  AND
• Total Spent > $200
  OR
• Is in Segment = Engaged (30 Days)

Result: You can dynamically tailor your automation for hyper-relevant messaging.

✅ Example: “If Customer Can Receive SMS”

You want to only send SMS to users who:

• Have SMS marketing enabled
• Have a phone number
• Haven’t opted out

Configuration:

1. Condition Type: if someone can or cannot receive marketing
2. Field: Customer has SMS Marketing
3. Value: Enabled

Flow Logic:

• Yes Branch: Send SMS
• No Branch: Send fallback email or exit flow

🧪 Pro Tips

• Use “Has Been in Flow” to avoid re-entering loops.
• Combine behavioral + demographic conditions for precise targeting.
• Use segments and lists to simplify logic that would require many rules.

🧱 Next Step: Add Messaging Actions

Once you’ve configured your condition:

• Connect the Yes path to a Send SMS, Send Email, or other action.
• Connect the No path to a fallback or exit step.
• Add Wait Steps if you want to pause before sending the next message.

💬 Need Help?

If you're unsure which condition to use for a campaign goal, reach out to the Cavaco team or explore the Help Center for templates and playbooks.

Would you like this exported into a Google Doc or formatted for your in-app knowledge base (help.cavaco.ai)?

‍