Skip to main content

Put your workforce on autopilot

AdvancedLabAI WorkforceAutomationsCRMWire your AI Workforce to act · Step 5 of 10
Estimated time · about 30 minutes|Required · Partner Center access, A CRM with at least one contact source already flowing in, such as a form or an AI Employee

Outcomes

Build a smart list that triggers on a real filter
Pair a smart list with an automation using a starter recipe
Read an activity log entry without mistaking a safety net for a failure
Describe what the multi-location review-automation pattern looks like when a business is ready for it

Build a smart list that triggers automatically

You are here: Partner Center → Automations. The automation you just built waits for a conversation to end. This one waits for nothing: a list decides who is in it, and the automation runs on whoever lands there.

Labbuild a smart list

Go to CRMLists.

Matching contacts populate immediately, and keep populating as new ones match: the list itself is the trigger, no manual upkeep required.

Pair it with an automation

Labconnect the list to an action

Go to AutomationsMy automations, then Create automation.

Every contact who lands on the smart list now sets off the automation, with no one needing to notice they arrived.

Three starter recipes cover most of what a workforce needs autopilot for. Building the first one end to end is worth doing now; the other two follow the exact same shape once the pattern clicks.

Labship the nurture recipe

Go back to AutomationsMy automations.

A form submission now starts a nurture campaign on its own, the moment the contact lands on the list.

The other two follow the same shape, one trigger and one or two steps: a new-lead list paired with a CRM sales task for the contact plus an SMS acknowledgment, so a person and the lead both hear something right away; and, once a completed-job integration is in place, a jobs-done list paired with a review-request campaign for the company.

Read the log before assuming something broke

An automation's activity log is where you go to confirm a run actually happened, not just to check for problems. It lists runs that started and the outcome of each step, so the thing to learn to read is what isn't there. If you have a re-entry setting like "One at a time per account" and you trigger the automation again while a run is still going, the second trigger is quietly dropped: no error, no warning, no new entry. That silence is the safety net working. To confirm it, compare the number of times the trigger should have fired against the number of runs you can actually see.

Go deeper

The Lists guide covers every filter type and list option, Creating and configuring automations covers every trigger and step, and Managing your automations walks through what each activity-log status means.

Branch review requests by location

One smart list and one automation cover a single business well. A multi-location business eventually asks for more: branching a review request by zip code to the right satellite location, with a webhook per location and a safety-net fallback to the hub when nothing matches. Worth knowing the shape exists; this step is not where it gets built.

Keep a person in the loop

Anything that reaches a client's customers on its own, especially content a client did not expect to see posted automatically, deserves a human approval step before it goes out. Build the review in as a step in the automation.

Knowledge Check

Three quick questions on smart lists, starter recipes, and reading the activity log.