Configuring Rainmaker Condition Flow Actions for Inbound Text and Email Messages

Please Note:

Before configuring workflows, test Rainmaker prompts until they consistently evaluate messages as expected.

For more details, refer to this article: Optimizing Rainmaker Prompts: Best Practices for AI Message Handling.

About This Guide

This guide outlines the step-by-step process for configuring Rainmaker Condition Flow Actions for inbound text messages. These actions enable automated responses by evaluating specific conditions and initiating appropriate follow-ups.

For agencies configuring workflows for inbound email automation: Use the onAfterEmailInbound trigger instead of onAfterTextInbound. The setup follows the same structure but should be adjusted for email-specific conditions.

Please Note:

The configurations provided in this guide serve as examples of available tools for setting up Rainmaker Condition Flow Actions. Agencies should tailor their workflows to align with their specific business needs.

Step 1: Create an Action Path

1. Navigate to Setup → Workflow → Action Paths.

2. Click New to create a new Action Path.

Step 2: Define the Action Path

1. Right-click on the newly created Action Path Container.

2. Select Edit.

3. Enter the following details:

   1. Label: Rainmaker Filters for onAfterTextInbound

   2. Description: Inbound text evaluations via Rainmaker

   3. Class Name: (Auto-fills by default)

   4. Bundle Action: False

   5. Text Manager Action: True (*Optional setting if you want to be able to select and run the same action path manually)

4. Click Save.

*Text Manager Action Field

When the Text Manager Action is enabled, users can manually initiate an action path from the Text Message Manager. This allows users to select a Rainmaker Condition from the Action Path dropdown and run it manually. For details, refer to How to Manually Trigger a Rainmaker Condition.

Step 3: Add Rainmaker Condition Flow Actions

Example 1: Wrong Number

1. Right-click on Rainmaker Filters for onAfterTextInbound and select New.

2. Enter the following details:

   1. Class Name: Rainmaker Condition

   2. Prompt:

      1. Positive Trigger: Detects phrases indicating a wrong number (e.g., "wrong number," "that's not me").

      2. Negative Prompt: Ignores generic responses (e.g., "Who is this?" "What company is this?").

   3. Label: Rainmaker Condition - Wrong Number

3. Click Save.

True Flow Actions for Wrong Number:

1. If True: Add the following actions:

   1. Account Flag Add: Rainmaker Evaluation Phone Number

   2. Send Text Message: Wrong Number

   3. Set Account Field: Next Step - Skip Trace for Cell Number

   4. Set Important Note: Rainmaker Auto Reply

2. If False: Proceed to the next condition (Dispute).

Example 2: Dispute

1. Right-click on Rainmaker Filters for onAfterTextInbound and select New.

2. Enter the following details:

3. Class Name: Rainmaker Condition

   1. Prompt:

      1. Positive Trigger: Identifies dispute-related responses (e.g., "I dispute this debt," "This is already paid.").

      2. Negative Prompt: Ignores general inquiries (e.g., "Can you explain this charge?" "What is this balance from?").

   2. Label: Rainmaker Condition - Dispute

4. Click Save.

True Actions for Dispute:

1. If True: Add the following actions:

   1. Set Status Code: Dispute

   2. Set Account Field: Next Step - Verify Dispute

   3. Send Text Message: Dispute Submittal Response

   4. Account Flag Add: Rainmaker Eval Dispute

   5. Set Important Note: Rainmaker Auto Reply

2. If False: Proceed to the next condition (Can't Pay).

Example 3: Cannot Pay

1. Right-click on Rainmaker Filters for onAfterTextInbound and select New.

2. Enter the following details:

3. Class Name: Rainmaker Condition

   1. Prompt:

      1. Positive Trigger: Identifies inability to pay (e.g., "I don't have the money right now," "I can't pay.").

      2. Negative Prompt: Ignores payment scheduling inquiries (e.g., "Can I have more time?" "When is my payment due?").

   2. Label: Rainmaker Condition = Can't Pay

4. Click Save.

True Actions for Cannot Pay:

1. If True: Add the following actions:

   1. Send Text Message: Can't Pay

   2. Set Account Next Work Date: Today

   3. Account Flag Add: Rainmaker Eval Can't Pay

   4. Set Important Note: Rainmaker Auto Reply

2. If False: Leave the condition empty (no further action).

Step 4: Connect the Action Path to the Trigger

1. Navigate to Setup → Workflow → Triggers.

2. Select onAfterTextInbound trigger, click to open

3. Enter the following details:

   1. Event Type: onAfterTextInbound

   2. Description: Initiates after an inbound text has been received if we can associate it with an account, or after a text has been linked to an account.

   3. Active: (Check the box to activate)

   4. Flow Action ID: Rainmaker Filters - onAfterTextInbound

4. Click Save.

Step 5: Final Review & Testing

• Ensure all conditions are saved correctly.

• Monitor flagged accounts in Email Manager or Text Message Manager.

Manually Initiating Rainmaker Condition Flow Actions

While Rainmaker Condition Flow Actions are designed to run automatically based on configured workflow, there may be cases where users need to manually apply a Rainmaker Condition to a specific message.

If Email Manager Action or Text Manager Action is set to True, users can select a Rainmaker Condition from Email Manager or Text Message Manager when automation is not sufficient or a condition requires review.

How to Manually Trigger a Rainmaker Condition:

1. Open Email Manager or Text Message Manager.

2. Select an account and navigate to the Action Path dropdown.

3. Choose the appropriate Rainmaker Condition (e.g., Rainmaker Condition = Cannot Pay).

4. Click Run to execute the selected action.