Start with the failed handoff
A new inquiry lands in your CRM. It has a name and phone number, but the wrong agent owns it and there is no clear next task. Before adding another tool, identify which part of the workflow needs to change: intake, assignment, follow-up, or the connection between systems.
Follow Up Boss already has tools for much of this work. The first check is which automation version your account uses. A tutorial that matches an older account can send you looking for controls that have changed.
Why your account may look different from a tutorial
Follow Up Boss documents a migration to Automations 2.0 that converts existing Action Plans into Automations. After migration, legacy Action Plans have limited controls; you cannot create, edit, or start them as before. The vendor says the account owner must enable the migration and that the account change cannot be reversed. Confirm your account's state before planning around the older interface. Automations 2.0 migration.
Treat migration and the workflow improvement as separate decisions. First write down the result you need, the active setup, and who is responsible for it. Changing versions is not itself proof that the team will follow up better.
Match the problem to the right part of the system
| What is going wrong? | Where to start | What to verify |
|---|---|---|
| A brand-new web lead gets the wrong initial assignment | Lead Flow for that source | The incoming data, matching rule, default route, and intended owner |
| An existing contact needs a next step after a change | The applicable Automation | The trigger, conditions, actions, and behavior when it runs again |
| An older tutorial tells you to create an Action Plan | Your account's migration state | Whether the instructions apply to your version |
| A form or outside system creates an incomplete record | The integration feeding the CRM | What event and fields arrive, and what happens on an error or repeat |
In Automations 2.0, Lead Flow still configures distribution and the automation associated with future new web leads from a source. That is distinct from deciding what should happen later to a contact already in the database. Lead Flow overview.
The current automation editor supports triggers, conditions, delays, and actions such as creating a task, adding a note, or reassigning an agent. Its Manual trigger is also required for automations applied through Lead Flow or from a lead profile. The label alone does not mean someone must click it for every new lead. Automations 2.0 overview.
Example 1: a new inquiry goes to the wrong agent
Use a fictional contact through an approved test source. Write the expected agent down before the test. Then compare the submitted information, CRM record, selected route, and resulting assignment.
Follow Up Boss processes advanced Lead Flow rules from top to bottom and uses the default rule when none match. Check both the specific rule you intended and the fallback. A routing condition cannot help if the required information never reaches the CRM. Advanced Lead Flow rules.
Repeat the check with a missing field and with an existing contact. Do not assume those paths should produce identical results. Agree on whether an existing relationship should retain its owner before designing reassignment.
The useful outcome is an appropriate owner with a visible next action. A notification by itself does not establish either.
Example 2: the form creates a contact, but follow-up never starts
For a custom connection, ask the person maintaining it how it sends the inquiry. Follow Up Boss directs lead sources to its events endpoint, /v1/events. Its documentation warns that creating a person through /v1/people does not run the lead automations described in its intake flow. Sending in leads.
The event type matters too. The API documents different eligible event types for workflow triggers and says historical events do not trigger workflows on creation. An HTTP response is only one part of the evidence: check the contact history and intended workflow as well. Events reference.
This is a reason to inspect an integration before buying a replacement. The missing step may be the way an inquiry is represented, rather than a missing automation feature.
Example 3: the first text is fast, but the handoff is unclear
The current Instant Response feature uses Lead Flow's Initial Text setting. Follow Up Boss says these automated first texts can affect response-time reporting. A quick recorded response therefore needs context: was it an automated first message, an agent's attempt, or a two-way conversation? Instant Response.
Choose the result you want to measure before changing the workflow. For example, track eligible inquiries with an assigned owner and next task, then separately track agent attempts, conversations, and appointments. Define coverage hours and exceptions so you compare the same kind of work before and after.
When an outside integration earns its place
Start with the native setup when it can produce the agreed result. Consider a connector or custom implementation when needed information is held elsewhere, when the workflow crosses systems, or when an unsupported step creates recurring manual work.
Before choosing one, define who maintains it, how failures become visible, what a retry does, and how someone can correct the record. Include ongoing costs and review effort. A working connection still needs a useful team process around it.
Bring one process to the review
Use the guided workflow worksheet to record your source, owner, expected result, exceptions, and first test. If the problem is specifically lead follow-up, the Lead Leak Map can help you describe the handoff.
I can review the setup and help fix the step that is failing. Bring your CRM version, lead sources, one example with customer details removed, and the result you want your team to see. See how I help real estate teams.
Product documentation checked September 8, 2026. The scenarios above are illustrative, not reported client results.