6.0 Masterclass on Automations 101 - 5 Essential Automations Every Investor Should Set Up

Tuesday, October 13, 2026. Sharad Mehta and Tyler Scott hosted the Automations 101 Masterclass webinar at 1 PM Pacific / 4 PM Eastern. Approximately 81 minutes.

00:01:58 — The new-lead-created automation is the most critical setup: it controls pipeline, team assignment, call flows, inbox, and all downstream automations

00:03:00 — Five team assignment methods explained: round robin, first to claim, manual, all selected, and weighted round robin

00:30:00 — Status-change automations stop previous drips and move the lead to a new automation when the pipeline stage changes

01:13:52 — Tyler's live can't-reach automation: 503 leads on a 30-day drip that auto-moves to long-term nurture

00:45:00 — Activity trigger automations fire on call outcomes to change status, add tags, or start a new drip

01:16:04 — A2P for list stacking: under 500 messages use your main A2P; multiple A2Ps per account coming later this year

01:17:28 — Cold texting TCPA risk: start small, do not send thousands per day, move to the next marketing channel if no response

01:20:08 — Triple-line dialer keeps re-calling the same lead after disposition; team investigating

01:20:42 — LinkBlue iMessage integration ending; iMessage numbers being ported to regular Twilio numbers; new partner being sought

01:21:07 — Announcement: Tomorrow is office hours; Thursday is a pipeline setup webinar

Sharad opened by explaining that the new-lead-created automation is the foundation everything else depends on. Without it, leads default to "active leads, new leads" with no team member assigned. This breaks call flow routing for repeat callers (the system cannot find anyone in the assigned role), prevents tasks from firing in downstream automations (tasks assigned to an acquisition manager fail if no one holds that role on the lead), and causes leads to not appear in the correct team member's inbox. Every campaign in the account must be assigned to a new-lead-created automation. When adding a new campaign, a prompt offers to assign it to an existing new-lead-created automation automatically (00:06:03).
​

Path: Automations > Leads > New Lead Created > [select campaigns] > Assign Pipeline, Status, Team Members Path: Settings > Marketing Campaigns > Create Campaign > Assign to New Lead Created Automation
​

Q: What is the most important automation to set up in REsimpli 6.0?
A: The new-lead-created automation. It assigns the pipeline, status, and team members to every incoming lead. Without it, call flows, inbox routing, team assignment, and all downstream automations break.
​

Q: What happens if I don't assign a campaign to a new-lead-created automation? A: Leads from that campaign will default to "active leads, new leads" with no team member assigned. Call flows for repeat callers will fail, tasks will not fire, and leads will not appear in the correct inbox.

Sharad and Tyler walked through each assignment method. Round robin distributes leads evenly across selected team members. First to claim sends a notification to all team members in a role; the first person to open and claim the lead becomes the assigned member. Manual assignment requires the owner or manager to go in and assign leads by hand, useful when assignment depends on geography or property value. All selected team members assigns every person to every lead, common for small teams that collaborate on all leads until a later stage. Weighted round robin lets you assign a ratio (for example, 5 leads to a senior member for every 1 to a junior member). Solopreneurs are auto-assigned as owner to all leads and do not need to configure team assignment unless they add team members (00:07:42).
​

Q: What team assignment methods are available in REsimpli 6.0 automations?
A: Round robin (equal distribution), first to claim (notification to all, first person claims it), manual (hand-assigned), all selected (everyone assigned), and weighted round robin (ratio-based, for example 5:1 senior-to-junior).
​

Q: Do solopreneurs need to set up team assignment?
A: No. As the account owner, you are automatically assigned to all leads. Team assignment becomes critical once you add team members.

Sharad built a status-change automation live. When a lead moves from "new lead" to "attempted contact," the automation stops any previous automation running on that lead and starts a new drip specific to the attempted contact stage. He emphasized that without the "stop other automations" step, the old drip keeps running alongside the new one, causing conflicting messages. Tyler noted that his team operates from a one-page document listing what each status does: move to "can't reach" starts a 30-day re-engagement drip, move to "long-term nurture" starts a quarterly follow-up, and so on. The team members only need to move leads to the correct status; the automations handle everything else (00:44:47).
​

Q: Do I need to manually stop the old automation when I move a lead to a new status?
A: No, if you add a "stop other automations" step at the beginning of each status-change automation. Without it, the old drip keeps running alongside the new one.
​

Q: How does Tyler's team know what happens when they move a lead to a new status?
A: Tyler maintains a one-page document listing each pipeline status and what automation it triggers (for example, "can't reach" = 30-day re-engagement drip, "long-term nurture" = quarterly follow-up). Team members just move leads to the correct status.

Tyler opened his production account and showed his can't-reach automation with 503 leads currently enrolled. The drip alternates between texts and AI calls over 30 days, attempting to re-engage cold leads. At the end of 30 days, if the lead has not responded, the automation automatically moves it to the long-term nurture automation, which sends a text every 60 days. This ensures no lead ever falls through the cracks: every lead is always on some automation (01:15:19).
​

Q: How does Tyler handle leads he can't reach?
A: He moves them to a "can't reach" status, which triggers a 30-day drip with texts and AI calls. After 30 days with no response, the automation moves the lead to long-term nurture for quarterly follow-up.
​

Q: How do I make sure no leads fall through the cracks?
A: Chain your automations so the last step of each drip moves the lead to the next automation. Tyler's setup ensures every lead is always on an active automation, from initial outreach through long-term nurture.

Sharad built an activity trigger automation live. He selected "call outcome" as the trigger and tied it to the "DNC" disposition. When a caller selects DNC during a dialing session, the automation automatically changes the list stacking status to DNC and removes the record from future dialing lists. He noted that activity triggers are not limited to status changes: they can add tags, send a text, start a new drip, skip trace the property, or perform any other automation action. The same pattern works for other outcomes: "not interested" can trigger a 3-month text drip, "busy signal" can trigger a follow-up task, and "callback requested" can create a task with a due date (00:59:47).
​

Path: Automations > Activity Trigger > Call Outcome > [select disposition] > [add actions]
​

Q: How do I automatically handle DNC contacts after a dialing session?
A: Create an activity trigger automation on the DNC call outcome. Add a "change list stacking status to DNC" action. Records will be moved automatically when the caller selects DNC during the session.
​

Q: What can activity trigger automations do besides change status?
A: They can add tags, send a text, start a new drip, skip trace the property, create a task, send a notification, or perform any other automation action. They fire on call outcomes, incoming texts, incoming calls, and direct mail scans.

A user asked whether to use A2P or a DBA for list stacking SMS. Sharad recommended using the main A2P if sending fewer than 500 messages. He advised watching the opt-out rate as the key metric: if opt-outs spike, reduce volume. For accounts sending 5,000 to 15,000 messages, a separate A2P for marketing versus operations is warranted. Multiple A2P registrations under one account are coming later this year. To track which records have and have not received SMS, use the "last outgoing SMS" filter in list stacking (01:17:00).
​

Q: Should I use a separate A2P for list stacking cold texting?
A: If sending under 500 messages per day, your main A2P is fine. Watch your opt-out rate. For volumes above 5,000, plan for a separate A2P. Multiple A2Ps per account are coming later this year.
​

Q: How do I track which list stacking records have already received my SMS?
A: Use the "last outgoing SMS" filter in list stacking to see which records have been texted and which have not.

A user asked about cold texting TCPA compliance. Sharad said it is a do-at-your-own-risk situation and recommended starting with a smaller number of messages even if you have a large list. Tyler added that he does not recommend putting cold list stacking records on an aggressive multi-step automation. One simple text is enough; if they do not respond or reply STOP, take them off and move to the next marketing channel (direct mail, cold calling). Sending thousands of messages per day increases the risk of carrier flagging and TCPA complaints (01:18:01).
​

Q: Is cold texting from REsimpli legal?
A: It is a do-at-your-own-risk situation. Sharad recommends starting with small volumes and not sending thousands per day. Tyler recommends one text per cold record; if no response, move to a different marketing channel.

A user reported that the triple-line dialer continues calling the same lead repeatedly on the same day even after a disposition has been selected. Sharad confirmed this has been reported by multiple users and the team is actively investigating. An update is expected within the next day or two (01:20:23).
​

Q: Why does the triple-line dialer keep calling the same lead after I dispositioned it? A: This is a known bug being investigated. The dialer is not correctly removing dispositioned leads from the session queue. An update is expected soon.

Sharad confirmed that LinkBlue, REsimpli's iMessage integration partner, is ending support for all third-party integrations, not just REsimpli. Users with iMessage numbers are being ported to regular Twilio numbers. REsimpli is looking for a new iMessage integration partner. No SendBlue HQ integration is available (01:21:06).
​

Q: Is the iMessage integration still available in REsimpli?
A: No. The LinkBlue iMessage integration is ending. Existing iMessage numbers are being ported to regular Twilio numbers. REsimpli is looking for a new iMessage partner.

Points to Remember: