Inrō’s logic actions empower you to create dynamic, flexible automation workflows. They enable you to mimic natural interactions, branch conversations based on user input, trigger modular sub-scenarios, conduct A/B tests, and filter out unwanted content.
This guide covers the six key logic actions in Inrō and explains how each can optimize your automation.
Logic Actions
1. Time Delay
Inserts a customizable pause between automation steps.
How to Use: Select the “Time Delay” action in your scenario setup, then specify the pause duration (e.g., 30 seconds, 1 minute) to mimic a natural response interval.
Why It’s Useful: It helps your workflow feel less robotic by introducing realistic pauses.
Additional Note: Adjust the delay duration based on the context of your conversation for optimal pacing.
2. Trigger a Scenario
Initiates another scenario within your current workflow.
How to Use: Choose the “Trigger a Scenario” action, then select the scenario you want to run as a sub-workflow from the available list.
Why It’s Useful: It allows you to modularize complex workflows into smaller, reusable components.
Additional Note: This is also helpful if your audience journey has repetitive flows. For example, you can create a modular scenario for the registration message and survey and then reuse it for multiple promotional content.
3. Wait for Reply
Pauses the automation until a user responds.
How to Use: Add the “Wait for Reply” action, then set up the expected reply keywords (e.g., “yes,” “yup,” “sure”) and configure branching options based on different responses.
Why It’s Useful: It creates interactive, responsive conversations by adapting the workflow based on real-time user input.
Additional Note: Define a fallback branch for cases when no expected reply is received. You can also set a follow-up branch if the user does not respond within a specified time.
4. Scenario Condition
Evaluates specific conditions based on contact attributes or behaviors.
How to Use: Insert the “Scenario Condition” action and set the criteria (such as whether a contact follows you or a contact property matches a specified value)
Why It’s Useful: It tailors your automation by ensuring subsequent actions are only executed for contacts that meet the defined conditions.
Additional Note: Use conditions to segment your audience and deliver more personalized interactions if they meet certain criteria. For example, you send them a freebie only when they follow you.
5. A/B
Randomly splits your audience into two groups for testing different approaches.
How to Use: Choose your "A/B Testing" action, then configure the two branches with different messaging sequences or actions.
Why It’s Useful: It enables you to experiment with alternative workflows and optimize your messaging by comparing performance.
Additional Note: You can also combine it with the "trigger a scenario" action in these branches, allowing you to test entire workflows or journeys instead of just messaging.
6. Hate & Spam Filter
Detects hate speech or spam, halting the current sequence and preventing further automated engagement.
How to Use: Add the “Hate & Spam Filter” action to your workflow; configure the folder in which you want to put them.
Why It’s Useful: It protects your brand’s reputation by automatically managing abusive or spam messages.
Additional Note: This is really useful for handling trolls and spammers. Also, the folder you configured earlier allows you to review them and decide on the next steps. You can even use this in conjunction with another scenario handling, specifically contacts in this folder.
Inrō Insider Tips
Optimize Reply Branching: When configuring the "Wait for Reply" action, pre-define a comprehensive set of reply keywords and create distinct branches for each. This granular setup minimizes ambiguity and ensures smoother user interactions.
Modularize Complex Workflows: Use the "Trigger a Scenario" action to break down large, complicated workflows into smaller, focused scenarios. This not only simplifies management but also improves troubleshooting and optimization.
Continuous A/B Refinement: Regularly analyze A/B test results and adjust branch conditions based on real engagement data. Small tweaks in timing, messaging, or condition parameters can significantly improve conversion rates.
Feedback
We’d love your insights on setting up and optimizing logic actions in Inrō. If you have any questions, suggestions, or success stories, please contact our support team or leave feedback on this article. Your input is invaluable in helping us enhance the Inrō experience for everyone.