Skip to main content

How to Automate Actions When a Buyer's Status Changes in REsimpli

Written by Anthony Estrada

Overview

This automation runs when a buyer is moved into a particular status — for example, tidying up and notifying the team as soon as a buyer is marked Not a Fit.

You can also customize the statuses in your buyers pipeline to match how you actually qualify buyers.

Steps

Part 1: Set Up Your Buyer Statuses

Step 1: Adjust your statuses

In your Buyers Pipeline you can have as many statuses as you need.

Click the three dots on a status to:

  • Change its title

  • Change its colour

  • Move it

  • Collapse it

  • Delete it

  • Add a new status


Part 2: Build the Automation

Step 2: Open your buyer automations

  1. Go to Automations.

  2. Click Buyers.

  3. Select Buyer Status Change.

  4. Add an automation.


Step 3: Name it and choose the status

  1. Enter an automation name.

  2. Select the status that triggers it — the video uses Not a Fit.


Step 4: Set your timing

Choose your delay preference and default time zone, then click Save.


Step 5: Add a task step

To create work for your team:

  1. Add a task step.

  2. Add the task type if you need one that does not exist.

  3. Add the details.

  4. Select the assignee.


Step 6: Add any other steps

You can also:

  • Change the buyer's status

  • Unassign a team member

  • Add a note

  • Add a tag, which is useful for documentation


Step 7: Handle other automations last

Two steps have to come at the end of your sequence:

  • Move or enable a different automation

  • Stop other automations — either specific ones you select, or all automations currently active on that buyer

Add every other step before you add these. Once the automation hands over or stops, nothing further will run.


Step 8: Save

Click Save.


Part 3: Test It

Step 9: Check the buyer first

Open a buyer and click the automations button. You should see no automations currently running.


Step 10: Change the status

Move the buyer into your trigger status — Not a Fit in this example.


Step 11: Confirm it ran

Click the automations button again. Your automation will now be listed as running.

Click it to see the scheduled actions — the steps, their rollout, and a preview.


Important Notes

  • Buyer statuses are fully customizable. Use the three dots on any status to rename, recolour, reorder, add, or delete.

  • Steps that hand over or stop automations must be last. Anything you add after them will not run.

  • Stopping other automations can be targeted — all of them, or only the ones you name.

  • Marking a buyer as Not a Fit is a good trigger for clearing them out of active sequences and recording why.

  • Checking the automations button before and after a status change is the simplest way to confirm an automation works.


Troubleshooting

Your automation did not trigger

  • Check the status on the automation matches the status you moved the buyer into.

Steps after your stop or move action never ran

  • Those steps end the sequence. Move them to the end and place everything else before them.

A buyer is still in other automations after being marked Not a Fit

  • Add a stop other automations step, and choose whether to stop all of them or specific ones.

You need a status that does not exist

  • Add one from the three dots menu on your buyers pipeline.

You want to see what will happen before it runs

  • Open the automation from the buyer record. The scheduled actions show each step, its rollout, and a preview.


Summary

You built an automation for buyer status changes. You customized your buyer statuses from the three dots menu, then opened Automations, Buyers, and Buyer Status Change to create an automation triggered by a status such as Not a Fit. You added a task with its own type and assignee, plus notes, tags, unassignments, and status changes, keeping the stop and move steps until last. You tested it by checking the buyer before and after the status change and reviewing the scheduled actions.

Did this answer your question?