6.0 Office Hours - Oct 2 - 6 PM ET

On Friday, October 2, 2026, Sharad Mehta and Tyler Scott hosted an office hours Q&A call. The session covered web form pipeline defaults, task behavior on status changes, automation re-enrollment prevention, speed-to-lead versus inbound AI conflicts, triple-line dialer cycling and the mid-October redesign, list stacking SMS number setup, and conversational AI versus automations.

The call closed with Sharad confirming the schedule for the following week.

A user showed that leads from his cold caller's web form were landing in the default active pipeline instead of the dedicated campaign pipeline his automation specified. Sharad navigated to Settings, Web Forms, and showed that the web form itself had the default pipeline selected. Updating the pipeline and status inside the web form configuration fixed the routing. Sharad clarified that web form settings and manual lead creation both default to the first pipeline unless explicitly changed, regardless of what the new-lead-created automation specifies (00:03:24).

Path: Settings > Web Forms > [select form] > Pipeline and Status

​Q: Why are my web form leads going to the wrong pipeline even though my automation is set up correctly?
A: The web form has its own pipeline and status setting under Settings > Web Forms. That setting overrides the automation. Update the pipeline inside the web form configuration itself.

​Q: Does the new-lead-created automation control which pipeline web form leads land in?
A: No. The automation fires after the lead is created, but the web form's own pipeline setting determines where the lead is initially placed. Update both to match.

A user asked whether moving a lead to a new status deletes the tasks created by automations in the previous stage. Sharad confirmed that pending tasks are not automatically deleted. When the status changes, a popup asks what to do with pending tasks: keep them or delete them. The user requested an option to auto-complete tasks by role when a status changes, so that lead manager tasks are cleared when a lead goes under contract but dispo and TC tasks remain. Tyler added that distinguishing automation-created tasks from manually created tasks would prevent important manual tasks from being accidentally cleared during the same status change (00:17:49).
​

Q: Are automation tasks automatically deleted when I change a lead's status in REsimpli 6.0?
A: No. A popup appears asking whether to keep or delete pending tasks. Future tasks from the previous stage remain unless you explicitly delete them.

​Q: Can I auto-complete only certain team members' tasks when a lead moves to a new status?
A: Not yet. This was raised as a feature request. The team is exploring role-based task completion so that, for example, all lead manager tasks are marked complete when a lead goes under contract while dispo tasks are kept.

A user described a transaction pipeline where leads sometimes bounce between stages (under contract to renegotiation and back). Each time the lead re-enters a status, the automation re-fires and creates duplicate tasks. He requested a setting that prevents re-enrollment if the lead has already been on that automation. Sharad said he would explore a global or per-automation toggle and noted that some users may want re-enrollment while others do not (00:20:05).

Q: How do I stop a lead from being re-enrolled in the same automation when it re-enters a pipeline status?
A: There is no setting for this yet. It was raised as a feature request. The workaround is to tag leads when they complete an automation and filter by that tag, or to manually manage task assignments.

​Q: Can a lead be on the same automation twice in REsimpli 6.0?
A: Yes. There is currently no deduplication. If a lead re-enters a status that triggers an automation, it will re-enroll and create a new set of tasks. A prevention setting is under consideration.

A user requested an if-else condition that checks whether a task has been completed before proceeding to the next automation step. Sharad confirmed that several if-else condition types are being developed, including campaign-level branching after activity triggers (for example, route differently based on which campaign the incoming SMS came from). All new conditions will ship as one combined update (00:20:45).
​

Q: Will REsimpli add if-else conditions based on task completion in automations?
A: Yes. If-else conditions for task completion and campaign-level branching are being developed and will ship as one combined update. No timeline was provided.

​Q: Can I branch an automation based on which marketing campaign a lead belongs to? A: Not yet, but campaign-level if-else branching is being built alongside other condition types.

A user reported that an inbound call triggered his speed-to-lead AI script ("thanks for filling out a form") instead of his inbound sales manager script. Tyler identified that the user's new-lead-created automation had speed-to-lead enabled on the same campaigns used for inbound calls.
​
When a call comes in from one of those campaigns, the system fires the speed-to-lead action because it sees a new lead created from that campaign. The fix is separating the campaigns: web form leads go to one set of campaigns with speed-to-lead, and inbound call campaigns go to a separate set with the inbound sales manager (00:24:06).
​

Q: Why is my inbound AI answering with the speed-to-lead script instead of the inbound sales manager script?
A: Both are likely enabled on the same campaign. Speed-to-lead fires on new lead creation from that campaign, which includes inbound calls. Separate your web form campaigns from your inbound call campaigns so each triggers the correct AI.

​Q: Can I have speed-to-lead and inbound sales manager on the same campaign?
A: No. They conflict because both trigger on the same event (new lead created from that campaign). Use separate campaigns for each.

A user asked whether the triple-line dialer cycles back to unanswered records or stops at the end of the list. Sharad confirmed it cycles through up to 3 rounds. Cooldown periods apply: 30 minutes after no answer, 60 minutes after a voicemail drop, and 30 minutes if a line was canceled because another contact answered.
Each contact can be called up to 3 times per day from the triple-line dialer.
​
The single-line dialer has no cooldown. For lists of 30 to 40 records, Sharad recommended the single-line dialer. The calling window for the dialer is 8:00 AM to 8:00 PM based on the area code of the person being called; click-to-call from the lead detail is not restricted (00:44:58).

​Q: Does the REsimpli triple-line dialer cycle back to leads that did not answer?
A: Yes. It cycles through up to 3 rounds. Cooldown periods apply: 30 minutes after no answer, 60 minutes after voicemail, 30 minutes if a line was canceled. Each contact can be called up to 3 times per day.

​Q: What are the triple-line dialer cooldown periods in REsimpli?
A: 30 minutes after no answer, 60 minutes after voicemail drop, 30 minutes if a line was canceled because another contact answered.

​Q: What is the dialer calling window in REsimpli?
A: 8:00 AM to 8:00 PM based on the area code of the person being called. Click-to-call from the lead detail is not restricted by this window.
​

Q: Should I use the triple-line or single-line dialer for a small list of 30 to 40 leads? A: The single-line dialer. The triple-line dialer is designed for larger lists of 150+ records. With 30 to 40 records, the cooldown periods in the triple-line dialer will leave you waiting between rounds.

Sharad shared Figma mockups of the mid-October dialer redesign. The new interface will show which round the session is on (1, 2, or 3), how many records have been dialed, how many connected, and session time. The disposition screen will include inline options for status change, add to automation, open Zillow, open Google, create task, and create appointment.
​
A toggle will let users choose 1, 2, or 3 lines from the same dialer interface. A "call next number" button will dial the next phone number on the same contact, and a "call next contact" button will move to a different person on the same property, for example from husband to wife (00:46:03).

Expected: mid-October 2026. First previewed: Oct 2 12PM.

​Q: When is the new REsimpli dialer redesign coming? A: Mid-October 2026. It will show visible round counters, session stats, a new disposition screen with inline actions, and a toggle to choose 1, 2, or 3 lines.

​Q: Will the triple-line dialer be able to call multiple phone numbers per lead? A: Yes. The redesigned dialer will have a "call next number" button to dial the next phone number on the same contact and a "call next contact" button to move to a different person on the same property.

​Q: Can I use the triple-line dialer as a single-line dialer? A: Yes. The redesigned dialer will include a toggle to choose 1, 2, or 3 lines from the same interface.

A user attempted to send bulk SMS from list stacking but had no number available in the dropdown. Tyler walked him through purchasing a dedicated list stacking dialer number. Both Sharad and Tyler emphasized treating this as a burner line that can be swapped out if it gets flagged, and not using a vanity number or a number tied to active pipeline leads. Tyler noted he sends 200 to 300 texts per day from REsimpli without delivery issues. Sharad mentioned a power user who sent approximately 25,000 messages in two to three weeks without being locked, though he advised dialing back at volumes above 5,000 per day (01:02:00).

Path: Settings > Communication > Manage Numbers > List Stacking Dialer > Add Number

​Q: How do I send bulk SMS from list stacking in REsimpli 6.0? A: Go to Settings > Communication > Manage Numbers and add a number under List Stacking Dialer. This number will appear in the dropdown when you select records in list stacking and choose Actions > Send SMS.

​Q: Should I use my main campaign number for list stacking cold texts? A: No. Use a dedicated list stacking number and treat it as a burner line. Cold texting can get numbers flagged, and you do not want that to affect your active pipeline communications.
​

Q: How many cold texts can I send per day from REsimpli without getting flagged? A: Tyler sends 200 to 300 per day without issues. One power user sent 25,000+ in two to three weeks. Sharad recommended staying below 5,000 per day to avoid carrier attention.

A user showed that some leads had future tasks visible while others on the same automation did not. Tyler identified that the upfront task creation update shipped Tuesday or Wednesday of that week (September 29 or 30). Leads enrolled before that date were not retroactively updated. Sharad confirmed the team is migrating those records over the weekend. A separate user reported duplicate task sets created by removing and re-adding automations in an attempt to force future tasks to appear. Sharad created a ticket to investigate (01:31:13).

​Q: Why are some of my automation tasks not showing up as future tasks in REsimpli 6.0?
A: If the lead was enrolled in the automation before the upfront task creation update (shipped around September 30), future tasks were not created retroactively. The team is migrating those records. Any lead enrolled after the update should show future tasks immediately.

​Q: I removed and re-added an automation and now I have duplicate tasks. What happened?
A: Re-adding an automation creates a new set of tasks without removing the previous ones. The team is investigating a fix. Avoid removing and re-adding automations as a workaround for missing future tasks.

A user asked about the difference between automations and conversational AI. Tyler explained that automations are trigger-based outbound sequences that send texts, make AI calls, create tasks, and change pipeline statuses on a schedule.
​
Conversational AI activates when a lead replies to one of those texts. It analyzes the reply, determines interest, continues the conversation immediately, and books an appointment on the user's calendar while the lead is still engaged. The user noted that this solves his biggest bottleneck: leads replying while he is busy, causing hours-long delays that kill momentum (01:34:38).

​Q: What is the difference between automations and conversational AI in REsimpli 6.0?
A: Automations are scheduled outbound sequences (texts, AI calls, tasks, status changes). Conversational AI handles inbound replies in real time: it reads the response, determines whether the lead is interested, continues the conversation, and books an appointment automatically.

​Q: Does conversational AI book appointments directly on my calendar?
A: Yes. When the AI determines a lead is interested, it books an appointment on your calendar, adds it to the lead record, and sends you a notification.

​Q: Should I use automations or conversational AI for follow-up?
A: Both. Automations send the initial outbound texts and calls on a schedule. Conversational AI picks up when the lead replies, so the response is instant even if you are unavailable.