Rainmaker Condition Flow Actions: Evaluating Inbound Text & Email Messages

What is Rainmaker?

Rainmaker is an AI-powered automation tool that operates across chat, text, and email platforms to handle customer inquiries. It provides:

• Accurate Account Information: Pulls relevant data to provide precise responses.

• 24/7 Support: Continues handling inquiries even when human agents are unavailable.

• Smart Workflows: Identifies consumer intent and can be used to trigger automated workflow.

For more details, refer to What is Rainmaker Chatbot?

How Rainmaker Condition Flow Actions Work

Rainmaker Condition Flow Actions evaluate inbound text and email messages to determine the appropriate workflow. Rainmaker Condition Flow Actions can be initiated by these two triggers:

• onEmailInbound

• onAfterTextInbound

Please Note:

Rainmaker does not evaluate images or file attachments—only text in email or text messages.

Rainmaker Condition Flow Actions evaluate inbound text and email messages using conditional logic to determine workflow for a true path and/or false path.

1. Initiated Event – A text message or email is received.

2. Prompt Evaluation – Rainmaker checks to see if the inbound message matches the prompt.

3. Conditional Logic – If the condition is True, the workflow follows one path; if False, it follows another.

4. Workflow Execution – Based on the evaluation, Rainmaker may be configured to take any number of actions including the following:

   1. Send an automated reply

   2. Update an account record

   3. Flag a message for review

   4. Move the account into a follow up worklist

Please Note:

To enable these actions, workflows must be properly configured to define how Rainmaker evaluates and responds to messages.

Best Practices for Using Rainmaker Condition Flow Actions

Test Before Deployment

Rainmaker prompts should be thoroughly tested with a variety of inbound text and email messages before being used in production. A suggested method is to first flag test accounts where Rainmaker prompts initiate workflows before broadly automating action paths with Rainmaker Condition Flow Actions.

1. Start with Low-Risk Automation

Begin by flagging accounts before implementing automated changes to ensure accuracy and minimize risk.

2. Test & Iterate Regularly

Continuously analyze real-time interactions and refine prompts to improve Rainmaker's response accuracy.

3. Use Positive & Negative Prompting

Define what Rainmaker should include as positive and negative prompts to minimize errors.

4. Leverage Flow Actions

Combine Rainmaker’s decisions with status updates, notifications, and escalation rules to enhance automation efficiency.

Use Case Example

One practical application of Rainmaker Condition Flow Actions is managing consumer replies to text campaigns. In the example above:

• A text message campaign is sent to multiple consumers.

• A recipient responds, "This isn’t me" or "You have the wrong number."

• A Rainmaker prompt evaluates: "Are they saying they are the wrong person?"

• If True, additional automated actions might include:

  • Flagging the Account

  • Sending an apology message

  • Removing the account from the call campaign

  • Updating the phone number status

  • Moving the account into a follow-up worklist

Why Iteration is Key

Rainmaker requires continuous monitoring and refinement to optimize its performance over time.

• Monitor Rainmaker Condition Flow Action Performance – Confirm results are as expected.

• Refine Prompts as Needed – Adjust to reduce incorrect evaluation.

By consistently testing and refining Rainmaker Condition Flow Actions, agencies can reduce manual workload while ensuring that consumer inquiries are handled efficiently.