Overview
This automation runs when something happens on a buyer contact — they call or text you, or one of your outgoing calls gets a particular outcome.
Like the other activity triggers, it branches: one sequence for the outcome you are targeting, another for everything else.
Steps
Part 1: Build the Automation
Step 1: Open your buyer activity triggers
Go to Automations.
Click Buyers.
Select Activity Trigger.
Add an automation and give it a name.
Step 2: Choose the activity
Pick what should trigger the automation:
Incoming SMS
Incoming call
Outgoing call outcome
Outgoing call
Incoming SMS and incoming calls only trigger for buyers already in your system. A message or call from someone who is not yet a buyer will not fire the automation.
The video uses outgoing call outcome, with the outcome set to Busy.
Step 3: Name the branch and set timing
Add a branch name.
Click Save.
Choose your delay preference.
Step 4: Build the matching branch
Steps here run when the outcome matches — a call marked Busy, in this example.
To text the buyer:
Add a message step.
Select one of your templates, or type the message.
Choose which number to send from.
Step 5: Add any other steps
You can also:
Add a tag
Set up a task for your team
Send an email
Change the buyer's status — for example moving them to qualified or active
Notify team members
Step 6: Build the "anything else" branch
The second branch runs if no previous condition matched — any outcome other than the one you selected.
Add steps here too, such as a task with an assignee, so those calls are not left without a follow-up.
Step 7: Save
Click Save.
Part 2: Test It
Step 8: Call a buyer
Open a buyer and start a call.
When the call ends, add the call outcome.
Select Busy, then click Exit.
Step 9: Confirm it ran
Click the automations button on the buyer. Your automation will be listed as triggered.
Click it to see the scheduled actions — the steps the system will take, the scheduled date and time, and the message that will go out.
Important Notes
Incoming SMS and calls only work for existing buyers. If you want to catch unknown contacts, this is not the automation for it.
This automation branches. One path for your chosen outcome, one for everything else. The second branch runs when no previous condition matched.
Recording the call outcome is what fires it. A call ended without a disposition will not trigger anything.
A busy outcome is a useful trigger for an automatic follow-up text or a task, so a missed connection is not forgotten.
The automation can move a buyer's status, so a call outcome can advance them through your pipeline.
Troubleshooting
Your automation did not trigger on an incoming message
Incoming SMS and calls only trigger for buyers already in your system. Check the contact exists as a buyer.
Your automation never runs on outgoing calls
Your team may not be selecting a call outcome. The automation fires on the disposition, not on the call itself.
Nothing happens on outcomes other than the one you chose
The "anything else" branch is probably empty. Add steps there for every other result.
Your SMS did not send
Check the message and the sending number on that step.
You want to see what is scheduled
Open the automation from the buyer record. It lists every step with its scheduled date and time.
Summary
You built an activity trigger automation for buyers. You opened Automations, Buyers, and Activity Trigger, chose an activity such as an outgoing call outcome of Busy, and named the branch. You built one sequence for that outcome — a templated SMS, tags, tasks, an email, a status change, and team notifications — and a second for every other outcome. You then tested it by calling a buyer, recording the outcome, and checking the scheduled actions on their record.
