Overview
This automation runs when a sold property meets a condition you set — a sale above a certain price, a profit above or below what you expected, or a particular tag being present.
It is the automation type for reacting to the numbers on a closed deal, rather than simply to a property being sold.
Steps
Part 1: Build the Automation
Step 1: Open your sold automations
Go to Automations, then Sold.
Step 2: Choose your trigger condition
Pick what the automation should watch for:
Condition | How it works |
Tag | Fires when a specific tag is on the property. You select which tags. |
Actual profit | Fires when actual profit is more than, less than, or is an amount you set. |
Sold price | Fires when the sold price is more than, less than, or is an amount you set. |
Expected profit vs actual profit | Fires when expected profit is more than or less than actual profit. |
The video uses a sold price of more than $100,000.
Step 3: Set your timing
Choose day-based or delay-based timing for when the steps run.
Step 4: Add your steps
Build what should happen when the condition is met. You can:
Add a note
Send an SMS
Notify a team member
Step 5: Set up an SMS step
Write the message, or select one of your templates.
Choose the recipient — the seller, buyer, agent, or vendor.
Select which of their contacts receives it.
Choose the number the message sends from.
Step 6: Set up a team notification
Choose who is notified — by role, by naming members, or everyone assigned to that property.
Choose the notification channel:
Channel | Where it arrives |
SMS | As a text message. |
To their email address. | |
Web | In REsimpli in the browser. |
In-app | On the mobile app, if they have it installed. |
Write the notification text.
Step 7: Save
Click Save.
Part 2: Test It
Step 8: Move a property to sold
The property must already be under contract.
Move it to Under Contract.
Then move it to Sold.
Select the team member and fill in the details, including the sold price.
If the details meet your condition — a sold price over $100,000, for example — the automation fires.
Step 9: Confirm it ran
Open the property and check its automations.
You may see two automations listed. That is expected: one for the property being added to the sold pipeline, and one for your condition being met. A property can run several automations at once.
Click your automation to see its steps and when each is scheduled.
Step 10: Check enrollment
Open the automation and go to Automation Enrollment.
You will see which leads have it enabled, along with each step's status — executed or pending, when it ran, and when the rest are scheduled.
Important Notes
This triggers on the numbers, not on the sale itself. Use the new sold properties automation if you want something to run on every sale regardless of value.
Conditions use comparisons. More than, less than, or exactly — so you can act only on deals above a threshold, or flag deals that came in under expectation.
Expected versus actual profit is its own condition, which makes it useful for catching deals that underperformed.
In-app notifications go to the mobile app, so that channel only reaches people who have it installed.
Several automations can run on one property at once. Seeing more than one listed is normal, not a fault.
The property has to pass through Under Contract before it can be sold, so the numbers are only available at that point.
Troubleshooting
Your automation did not fire on a sale
Check the condition against the actual figures. A sold price condition of "more than $100,000" will not fire on a $100,000 sale.
You can see two automations on one property
That is expected if one automation runs on every sold property and another runs on your condition. Both can run together.
Your team was not notified
Check the channel. In-app notifications only reach people with the mobile app installed — use SMS or email as well if you need certainty.
Your SMS did not send
Check the recipient, the contact selected, and the sending number on the SMS step.
You want to know whether a step has run
Open Automation Enrollment and check the step status, execution time, and schedule.
Summary
You built an automation that reacts to the numbers on a sold deal. You opened Automations and Sold, chose a condition such as sold price over $100,000, and set your timing. You added a note, an SMS to a contact on the deal, and a team notification with your chosen channel. You then tested it by moving a property through Under Contract to Sold, and confirmed from the property and from Automation Enrollment that it ran.