Overview
On Thursday, October 2, 2026, Tyler Scott led the Automations Masterclass webinar with Sharad Mehta co-hosting. The session ran approximately two hours and covered the full automation system in 6.0: what changed from 5.0, the three-part anatomy of every automation (trigger, steps, stopping point), Tyler's real wholesaling setup, common pitfalls, cold list automations in list stacking, troubleshooting, and upcoming features.
In 5.0, drips could send texts, emails, ringless voicemails, and direct mail. In 6.0, automations can do texts, emails, AI calls, and direct mail, plus 16 additional internal action steps (add task, notify team member, add/remove tags, change pipeline status, stop other automations, move to another automation, add notes, and more). Ringless voicemail is no longer available in automations.
5.0 drips required manual one-by-one application or were triggered only by new lead creation. 6.0 has five trigger types: new lead created, status change, activity trigger (call, text, direct mail scan), other triggers (appointment booked, lead marked unqualified), and manual assignment (including bulk application).
All 5.0 drip campaigns migrated to Automations under manual assignment with their message copy intact, but all were stopped and leads did not keep their place. Leads are tagged with their legacy drip name and can be filtered, found, and bulk-reapplied at up to 100 per day (increasing to 250). Manual status-change applications have no cap. Tyler shared that reapplying old drips has already generated new appointments and a user locked up a $20,000 deal from a reapplied lead.
Every automation has three parts: a start (trigger), steps (each with an action and a time delay), and a stopping point (inbound reply, manual stop, or handoff to another automation so no leads fall through the cracks).
Of the 20 available action steps, only four send an external message (text, email, direct mail, AI call). The other 16 handle internal workflow: tasks, notifications, tags, pipeline changes, stopping or chaining automations, and notes.
Speed to lead now lives inside automations. When a new lead is created, the automation can assign team members (round robin, weighted round robin, first to claim, or manual), set tasks, send an immediate text or AI call, and notify the team, all within the same flow.
Lead reply handling is improved: 6.0 can route based on whether the reply is interested or not interested. The per-automation toggle to stop or continue on reply is being brought back.
List stacking can now run automations on cold records, which was not possible in 5.0.
The automation enrollment tab and automation activity tab provide visibility into what is happening, which was difficult to see in 5.0.
Some API endpoints for automations will be available, and a future Thursday call will feature a REsimpli user with a 15-person team demonstrating how he uses OpenAPI, Claude, and Slack together.
Common pitfalls include not setting up the new-lead-created automation, forgetting to reapply legacy drips, and not verifying that team members are assigned before going live.
The call closed with Tyler confirming Friday, October 3, has two calls at noon and 6:00 PM Eastern (the regular schedule), and starting the following week, calls move to one per day at 1:00 PM Pacific / 4:00 PM Eastern, with Monday, Wednesday, and Friday as open office hours and Thursday as a user showcase webinar.