Skip to main content

Put your workforce on autopilot

IntermediateLabHire your first AI Employee · Step 6 of 7
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 your receptionist from step 2

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

What runs when nobody is watching​

By the end of this step, one real automation is live on your own account, running without you touching it again. You are here: Partner Center, the same account you have been building on since step 2. The workforce so far only acts when spoken to; this step is what runs when nobody is in the conversation at all.

Labbuild a smart list

You are going to CRM → Lists → Create.

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

You are going to Automations → 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

You are back in 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. A line reading "entity already exists" usually means the safety net worked exactly as intended, most often when an entry-setting choice like Only once per account correctly blocked a second run, not that anything failed. Read the log first; it usually already answers the question.

Where autopilot grows into​

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. Set that review in as a deliberate step in the automation itself, not as an afterthought caught by chance.

What you now have​

  • A smart list that updates itself, with no manual upkeep
  • One automation live on your own account, running the nurture recipe end to end
  • Two more starter recipes ready to build the same way
  • The habit of reading an activity log entry correctly before assuming something is wrong
  • A clear sense of where autopilot grows next, and where a human stays in the loop on the way there

Knowledge Check

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

Congratulations, you completed this step!

Hire your first AI Employee · Step 6 of 7

Keep learning