Configuring Rules

Feature Snapshot

Summary:
Rules are conditional logic statements built into LeadConduit that evaluate specific lead data fields using defined conditions, enabling automated decisions such as routing, dynamic pricing, or rejection.

Key Benefits:

• Automates decision-making by processing leads based on custom criteria
• Enhances data quality by filtering or adjusting leads that do not meet defined requirements
• Enables dynamic pricing and routing by combining simple and complex logical conditions

Typical Use Cases:

• Validating lead submissions by checking if required fields are present or formatted correctly
• Routing leads to specific recipients based on demographic or geographic criteria
• Setting dynamic pricing for leads based on attributes such as state, age, or income
• Combining multiple conditions using “ALL” (AND) or “ANY” (OR) logic to decide whether to process or block a lead

How Configuring Rules Works

In LeadConduit, rules form the backbone of the decision-making engine. A rule comprises three components: the left-hand value (the field or data point to test), the operator (the method for comparison such as “is equal to” or “is not blank”), and the right-hand value (the benchmark to compare against). Once configured, rules are applied at critical points in a flow (such as during acceptance criteria, pricing, or routing) to determine whether a lead should continue processing or be stopped.

Step‑by‑Step Instructions

1. Access Your Flow Editor:
   Log in to your LeadConduit account and open the specific flow you want to configure.

2. Navigate to the Rules Section:
   Locate the section or tab labeled “Rules” within your flow’s configuration interface.

3. Add a New Rule:
   Click the “Add Rule” button to begin creating a new condition.
   Expected Result: A new rule entry appears in your rules list.

4. Select the Left-Hand Value:
   Choose the field you wish to evaluate (e.g., “State,” “Age,” “Email”) from the dropdown menu.
   Note: Ensure that this field is correctly set up and mapped within your flow.

5. Choose the Appropriate Operator:
   Select an operator that matches your criterion (for example, “is equal to,” “is not blank,” “is greater than”), which will dynamically adjust based on the selected field type.

6. Enter the Right-Hand Value:
   Type the value to compare against (e.g., “CA” for California leads) in the provided field.
   Callout: If the data uses non-standard values or requires multiple acceptable inputs, verify with your team which benchmarks should be used.

7. Combine Additional Rules (if needed):
   To incorporate multiple conditions (e.g., requiring that “State is equal to CA” AND “Age is greater than 18”), add further rules either within the same group or as nested sub-rules using ALL (every condition must be true) or ANY (at least one condition must be true) logic.

8. Save Your Rule:
   Once all conditions are configured, click the “Save” button to lock in the rule set.
   Expected Result: The new rule appears in your flow’s active rules list, and incoming leads are automatically evaluated against it.

Validation & Monitoring (optional)

• Test the Setup: Submit test leads that both satisfy and do not satisfy the configured rule conditions. For instance, if you set a rule “State is equal to CA,” verify that leads with state “CA” continue in the flow, while others are blocked.
• Where to Monitor?: Check the Events tab and flow dashboard to view rule evaluation details and outcomes for each processed lead.

Best Practices

• Start Simple and Iterate: Begin with basic rules and gradually incorporate additional conditions as you gather performance data from processed leads.
• Order Specific Rules Before General Rules: Place highly specific conditions ahead of broader ones so that non-qualifying leads are rejected early in the process.
• Use Consistent Field Mapping: Ensure that every field referenced in your rules is correctly mapped in your inbound configuration to prevent unexpected mismatches.
• Test and Monitor Regularly: Continually run tests and review the Events tab to evaluate which rules are passing or failing in order to fine-tune thresholds and logic.
• Document Your Rule Configuration: Keep notes within your flow that explain the rationale behind each rule, which is helpful for troubleshooting and future revisions.

Troubleshooting

Frequently Asked Questions (FAQ)

What exactly are rules in LeadConduit?

Rules are logical conditions that evaluate specific lead data to decide whether a lead should continue processing, receive dynamic pricing, or be routed differently. They are built from a left-hand value, an operator, and a right-hand value.

Why should I configure rules?

Configuring rules automates lead processing, ensuring that only leads that meet your defined criteria proceed through the flow. This improves data quality, optimizes routing and pricing, and reduces processing costs by blocking unqualified leads early.

How do I choose the correct operator for my rule?

Select an operator based on the data type of your chosen field. For text fields, use operators like “is equal to” or “is not blank,” and for numeric fields, use “is greater than” or “is less than.” The available operators will adjust based on the field type.

Can I combine rules for more complex logic?

Yes. You can group multiple rules using AND (ALL) or OR (ANY) logic to create more complex conditions that must be met for a lead to pass through the flow.

What if the source data uses non-standard values?

Ensure your field mappings are up-to-date and standardized. If there is any uncertainty, add a callout in your configuration notes and confirm the acceptable values with your technical team.

Glossary