Skip to main content

How to Set Up Activity Trigger Automations for Vendors in REsimpli

Written by Anthony Estrada

Overview

This automation runs when something happens on a vendor contact — they call or message you, or one of your calls gets a particular outcome.

A useful case is retiring a vendor: when a call comes back No Longer Active, the automation can tag them, move them out of your active list, and stop anything still messaging them.

Steps

Part 1: Build the Automation

Step 1: Open your vendor activity triggers

  1. Go to Automations.

  2. Click Vendors.

  3. Select Activity Trigger.

  4. Add an automation and give it a name.


Step 2: Choose the activity

Select what should trigger the automation:

  • An incoming message from a vendor

  • An incoming call

  • A call outcome being recorded

  • An outgoing SMS

Incoming messages and calls only trigger for vendors already in your system.

The video uses a call outcome of No Longer Active.


Step 3: Build the matching branch

Steps here run when the outcome matches. For a vendor who is no longer active, you might:

  • Add a tag to the vendor contact

  • Move them to a different status automatically — Not a Fit, for example

  • Stop other automations — everything running on that vendor, or specific ones

  • Notify team members

  • Add a task

  • Send an SMS


Step 4: Handle old pending tasks

When the automation changes a vendor's status, choose what happens to the pending tasks from their old status — complete them, or leave them open.


Step 5: Build the Anything Else branch

The Anything Else branch runs for any other outcome. Add steps here too, such as notifying your team, so other results are not ignored.


Step 6: Save

Click Save.


Part 2: Test It

Step 7: Check the vendor first

Open a vendor and check their automations. There should be none active.


Step 8: Call and record the outcome

  1. Call the vendor.

  2. Select the No Longer Active call disposition.

  3. Add the phone status. If no phone status is available, just select the call outcome.

  4. Click Exit.


Step 9: Confirm it ran

Check the vendor's automations again. Yours will be listed.

Click it to see the steps the system is scheduled to complete, along with their execution date and time.


Important Notes

  • Incoming messages and calls only work for existing vendors. This will not catch contacts who are not yet on your account.

  • Recording the call outcome is what fires it. A call ended without a disposition triggers nothing.

  • No Longer Active is a practical trigger for retiring a vendor — tag them, move them to Not a Fit, and stop anything still contacting them.

  • A status change lets you decide about old pending tasks, so nothing is left hanging against a vendor you have retired.

  • The Anything Else branch handles every other outcome. Leaving it empty means those calls do nothing.


Troubleshooting

Your automation did not trigger on an incoming message

  • Incoming messages and calls only fire for vendors already in your system.

Your automation never runs after calls

  • Your team may not be recording call outcomes. The automation fires on the disposition.

There is no phone status to select

  • You can select just the call outcome and continue.

Nothing happens on other outcomes

  • The Anything Else branch is probably empty. Add steps there.

A retired vendor is still receiving messages

  • Add a stop other automations step to the matching branch.


Summary

You built an activity trigger automation for vendors. You opened Automations, Vendors, and Activity Trigger, and chose a call outcome such as No Longer Active. In the matching branch you added a tag, a status change to Not a Fit with a decision on old pending tasks, a stop step, and team notifications, then set up the Anything Else branch. You tested it by calling a vendor, recording the outcome, and checking the scheduled actions on their record.

Did this answer your question?