Overview
This automation runs when a property moves to a particular stage inside one of your transaction pipelines — for example, when a wholesale deal reaches Marketing to Buyers.
It is the automation type for deals in progress, rather than leads or prospects.
Before You Start
A property only appears in the Transaction Management Pipeline once it has been put Under Contract. Until then there is no transaction stage for an automation to react to.
Steps
Part 1: Set Up Your Pipelines
Step 1: Review your transaction pipelines
Under Transaction Management you can see the pipelines you already have.
Click Edit to rename a pipeline or change its colour.
Or add a completely new pipeline, for example one for fix and flips or another exit type.
Part 2: Build the Automation
Step 2: Open your transaction automations
Go to Automations, then the transactions area, and select Status Change.
Step 3: Name it and set the condition
Add an automation name.
Set the condition — which pipeline the property must be in, and which status it must move to.
The video triggers on properties in the Wholesale pipeline moving to Marketing to Buyers.
Click Save.
Step 4: Set your timing
Choose day-based or delay-based timing.
Step 5: Build your sequence
Add the steps you want to run. The options include:
Step | What it does |
Send SMS | Message the seller, buyer, agent, or vendor. |
Send email | Email a contact tied to the property. |
Create a task | For your team. You can select from your task templates. |
Add a note | Record something on the property. |
Manage tags | Add or change tags. |
If / else conditions | Branch the sequence based on a condition. |
Add a webhook | Send the event to an outside system. |
Move to a different call flow | Change how calls to this property are routed. |
Step 6: Set up your SMS step
Write the message, or select one of your templates.
Select the recipient — seller, buyer, agent, or vendor.
Choose which number to send from, or set a fallback communication number.
Step 7: Save
Click Save. Your automation will appear in the list.
Part 3: Test It
Step 8: Put a property under contract
Open the property and move it to Under Contract. You will be asked for:
Offer from details
Offer date
Offer price
Offer details — written or verbal
Offer type
Under contract date
Scheduled closing date
Expected profit
Exit type
Which transaction pipeline the property should appear in
A contingency, if you want to add one
Click Move to Under Contract.
Step 9: Move it to your trigger status
Move the property to the status your automation watches — Marketing to Buyers in this example.
The property will appear in that pipeline at that stage, and your automation will fire.
Step 10: Confirm it ran
Open the property and check its automations.
You will see the automation active, the scheduled actions — such as sending an SMS, adding a task, and adding notes — and when each is due to run.
Part 4: Track It
Step 11: See everything enrolled
Go to Automations, the transactions area, then Status Change, and open your automation.
You will see every property with the automation enabled now, and those that had it previously and have since completed.
Click any property for its actions, step statuses, and both executed and scheduled times.
Important Notes
Under Contract comes first. A property cannot reach a transaction stage, or trigger this automation, until it has been put under contract.
The pipeline is chosen when you put the property under contract, alongside the offer and closing details. Choose the right one, or your automation will not match.
The condition is a pipeline plus a status, so the same status in a different pipeline will not trigger it.
This automation type offers if/else conditions, webhooks, and moving to a different call flow — steps not available in the simpler automation types.
A webhook lets the event reach a system outside REsimpli.
Task steps can pull from your existing task templates rather than being written from scratch.
Troubleshooting
Your property is not in the transaction pipeline
It has not been put Under Contract yet. That is what places it there.
Your automation did not trigger
Check both parts of the condition — the property must be in the right pipeline and move to the right status. The pipeline is selected when the property goes under contract.
You need a pipeline that does not exist
Add one under Transaction Management, or edit an existing one to rename or recolour it.
Your SMS did not send
Check the recipient and the sending number on the SMS step, or set a fallback communication number.
You want the event to reach another system
Add a webhook step.
Summary
You automated a transaction pipeline status change. You reviewed your pipelines under Transaction Management, then built an automation triggered by a property in the Wholesale pipeline moving to Marketing to Buyers. You added SMS, email, task, note, tag, if/else, webhook, and call flow steps, and saved. You tested it by putting a property under contract with its offer and closing details, choosing the transaction pipeline, and moving it to the trigger status — then confirmed the scheduled actions on the property and through the automation's enrollment list.