For Follow Up Boss lead automation, check four things before adding more follow-up steps: the account's automation version, the source's Lead Flow configuration, the automation's trigger, and whether it is enabled. Then test a new inquiry and verify who owns the next action. A saved workflow is not proof that an agent received or acted on the lead.
This guide interprets Follow Up Boss's Automations 2.0 documentation for a U.S. real-estate team. It is not a tested account walkthrough or a Callion integration guide. The original contribution is a troubleshooting worksheet that separates configuration evidence from human follow-through.
Check the version before following an old tutorial
Follow Up Boss describes migration to Automations 2.0 as an account-owner action that cannot be reversed. Existing Action Plans are converted into automations; after migration, the old plans cannot be edited or newly started. Check the migration documentation against the account before changing anything.
Do not migrate an account merely to follow this article. First identify its current version, list the workflows your team relies on, and ask the account owner to review the consequences. Take configuration notes without copying private contact details. This article does not establish that every account has migrated.
Connect the source and the workflow deliberately
Lead Flow is where the documented setup connects a lead source with distribution and an automation for future new leads from that source. A source may first appear when its next lead arrives after integration setup. Review the vendor's Lead Flow overview; do not assume changing a source setting retroactively processes existing contacts.
For workflows applied through Lead Flow, Follow Up Boss requires a Manual trigger. That same trigger supports applying an automation directly on a lead profile; only active automations with that trigger are available there. See the Manual Trigger instructions.
Those are separate checks: the correct trigger does not prove the source is configured, and finding the automation on a profile does not prove that a new source inquiry will use it.
Keep the first test small
Automations 2.0 provides Conditions and Time Delay controls, with actions including Create Task and Add Note. Its setup instructions end with enabling the automation. Use the official overview to match the controls visible in your account.
For an initial check, propose a harmless internal task and note rather than outbound messages to a real prospect. Use a designated test contact with permission from the account owner. Confirm any other workflows that could fire on the same event before running the test.
Write down an expected result first: which source, which owner, which task, and when the team expects someone to acknowledge it. Treat that timing as your own acceptance criterion—not a vendor speed guarantee.
Troubleshoot the missing step, not the entire system
Use this proposed worksheet after the controlled test. “Proof” means evidence to collect in your own account; these are not reported test results.
| What you observe | Check next | Evidence to keep |
|---|---|---|
| Automation is missing when you try applying it on a profile | Manual trigger and active state | Configuration and visible selection result |
| A new source inquiry is assigned unexpectedly | The source's distribution settings | Test inquiry identifier and intended versus actual owner |
| The workflow was saved but nothing happens | Enabled state, entry condition and any configured delay | Configuration plus the test's actual timeline |
| A task exists but nobody follows through | Human responsibility, not just task creation | Named owner, acknowledgement and next action |
| The dashboard reports engagement | What caused that result | The underlying response or pause event, not just a total |
Do not “fix” every failed test by repeatedly importing the same contact or starting more outreach. First identify the earliest point where observed behavior differs from your written expectation. Change one relevant setting, then repeat a controlled test.
Separate workflow activity from a sales outcome
The vendor's July 22, 2026 overview defines Engaged to include either an automation-email response or a manual pause. Therefore, that count alone is not a count of prospect conversations, appointments or closings. See the dashboard definitions.
Keep your own operating record small: inquiry received, owner assigned, next action created, human acknowledgement, and actual outcome. Record what each timestamp represents rather than mixing an automated event with a person's response.
Use the lead-response plan to assign responsibility when a test fails or a task remains unattended. For broader architecture, use the lead-response automation guide. More source-specific guides live in the lead sources and integrations hub.
Configuration does not establish permission to call, text or email a prospect. This checklist evaluates workflow behavior, not legal compliance. Start with one source and a harmless test; expand only after the team can explain both the automated steps and the human handoff.