6.0 Office Hours - Oct 9 - 6 PM ET

Friday, October 9, 2026. Sharad Mehta hosted an office hours Q&A at 1 PM Pacific / 4 PM Eastern. Approximately 102 minutes.

00:02:43 — Driving for dollars app shows "subscriber drive not found" because the driver role is not toggled on

00:12:49 — Duplicate leads created when sellers resubmit through third-party forms with different address formatting

00:28:52 — List stacking inbox shows STOP and wrong number replies alongside leads, and mobile app texting sends from the wrong number

00:33:26 — New user onboarding walkthrough: importing leads, creating campaigns, setting up automations with round robin

00:46:06 — Bulk tagging undelivered SMS recipients to exclude them from future blasts without deleting email-valid contacts

01:35:36 — Day-based scheduling has a 15-minute minimum interval, automations respect an 8 PM to 8 AM quiet window, and day-based and delay-based cannot be combined

01:42:37 — Announcement: Next week Monday, Wednesday, and Friday are office hours; Tuesday and Thursday are training webinars

A user tapped Start Drive in the mobile app and received a "subscriber drive not found" error. Sharad identified that the driver role was not enabled for the user's account. Driving for dollars is included for one user per account. The fix is toggling on the driver role under Settings, Manage Users and Roles, selecting the user's name, clicking Edit, and enabling the driver toggle. After enabling it, the user was able to access the driving feature. A separate error ("no property request credits remaining") appeared when clicking on a specific property; Sharad asked for a screenshot to investigate (00:12:18).
​

Path: Settings > Manage Users and Roles > [your name] > Edit > Driver toggle
​

Q: Why does the driving for dollars app say "subscriber drive not found"?
A: The driver role is not toggled on for your account. Go to Settings > Manage Users and Roles, click Edit on your name, and enable the driver toggle. Driving for dollars is included for one user per account.

​Q: Is driving for dollars included with REsimpli or does it cost extra?
A: It is included for one user per account. If you want to assign it to a team member instead of yourself, toggle it on for their profile and off for yours.

A user showed two leads with the same phone number and seller name but slightly different property addresses. The seller originally submitted through a Facebook ad connected via Hango, and then resubmitted days later. Because the address formatting differed between the two submissions, the system created a new lead instead of matching the existing one. REsimpli uses Google address verification for its own web forms, but third-party forms (Facebook, Hango) do not always pass addresses through the same standardization. Sharad confirmed he would check whether adding phone-number-based deduplication as a fallback alongside address matching is feasible (00:21:43).
​

Q: Why did REsimpli create a duplicate lead when the seller resubmitted with the same phone number?
A: REsimpli deduplicates by property address. If the address formatting differs between two submissions (even slightly), the system treats them as separate leads. Third-party forms like Facebook and Hango do not always standardize addresses the same way as REsimpli's own web forms.

​Q: Will REsimpli add phone-number-based deduplication?
A: Sharad is exploring adding phone number as a fallback dedup method alongside address matching. No timeline was provided.

A user explained that after sending a bulk SMS campaign from list stacking, every reply (including STOP, wrong number, and not interested) appears in the list stacking inbox alongside genuine leads. He requested that STOP replies be automatically filtered into a separate view so he can focus on actionable leads while working from his phone. Sharad agreed that STOP replies require no further action and said he would check with the team about auto-filtering them (00:31:56).
​

The same user reported that texting a list stacking contact from the mobile app sends from a different number than the one used in the desktop campaign. This confuses the seller, who receives messages from two different numbers. Sharad said he would check whether the system can default to the last number used for that contact when texting from the app (00:33:16).
​

Q: Can I filter STOP replies out of the list stacking inbox in REsimpli?
A: Not automatically yet. This was raised as a feature request. Currently all replies (STOP, wrong number, not interested, and interested leads) appear in the same inbox.

​Q: Why does texting from the REsimpli mobile app send from a different number than my desktop campaign?
A: List stacking is not fully available on the mobile app, and the app may default to a different list stacking number. Sharad is checking whether the system can default to the last number used for each contact.

Sharad walked a new user through a full account setup. He demonstrated importing a CSV of leads from BatchLeads into list stacking, creating a marketing campaign for each lead source, and setting up the new-lead-created automation. The automation triggers when a new lead enters a specific campaign, assigns it to a pipeline and status, and distributes leads to team members via round robin. Sharad emphasized watching the Tuesday solopreneur masterclass recording for a more detailed walkthrough of pipelines, statuses, and automations (00:43:37).
​

Path: List Stacking > Upload CSV Path: Settings > Marketing Campaigns > Create Campaign Path: Automations > New Lead Created > [select campaigns] > Assign Pipeline, Status, Team Members

​Q: How do I import leads from BatchLeads into REsimpli?
A: Export your leads from BatchLeads as a CSV. Go to List Stacking > Upload CSV and map the columns to REsimpli fields.

​Q: How do I set up round robin lead assignment in REsimpli 6.0?
A: Create a new-lead-created automation, select the campaigns it applies to, choose the target pipeline and status, and set the assignment method to round robin. Leads will be distributed evenly among the selected team members.

A user with 716 undelivered messages in one SMS campaign asked how to clean his list without losing the email addresses. Sharad walked through the workflow: click the "not delivered" count in the SMS campaign view, which pulls up the full list of undelivered contacts. Select all, then use the bulk action to add a tag (for example, "do not text"). Before the next SMS blast, add a filter excluding contacts with that tag. This preserves the contact for email campaigns while removing them from text blasts (00:51:02).
​

Sharad also flagged that the user had sent 18,000 messages on October 7, but each message was three segments long, so Twilio processed approximately 50,000 messages. He recommended shortening SMS messages and blasting VIP buyers first before sending to the full list (00:49:06).
​

Path: SMS Campaigns > [select campaign] > Not Delivered count > Select All > Action > Add Tag
​

Q: How do I stop sending texts to contacts whose messages were not delivered without deleting them?
A: Click the "not delivered" count in your SMS campaign, select all, and add a tag like "do not text." Before your next blast, filter out contacts with that tag. This keeps their email address active while removing them from text campaigns.
​

Q: Why did my 18,000 SMS blast use 50,000 messages?
A: Each SMS segment is 160 characters. If your message is 480 characters, Twilio counts it as 3 messages per recipient. Shorten your messages to reduce costs and improve deliverability.

A user wanted to send two texts one minute apart (a compliance message followed by a question) using day-based scheduling, but the minimum interval is 15 minutes. When he set both to the same time slot, the second message arrived before the first. Sharad recommended using delay-based scheduling with a 1-minute delay between steps. He confirmed that delay-based automations respect the 8:00 PM to 8:00 AM quiet window: if a step would fire at 2:00 AM, it pushes to 8:00 AM the next day. No messages are sent during quiet hours from any automation (01:39:25).
​

Sharad also clarified that day-based and delay-based scheduling cannot be combined within a single automation. You can switch from one mode to the other once, but you cannot alternate back and forth. He will check with the team about reducing the day-based minimum interval from 15 minutes to 1 or 5 minutes (01:41:58).
​

Q: What is the minimum time interval between steps in day-based automation scheduling?
A: 15 minutes. Sharad is checking with the team about reducing it to 1 or 5 minutes.

​Q: Will automations send text messages in the middle of the night?
A: No. Automations respect an 8:00 PM to 8:00 AM quiet window. If a step would fire during quiet hours, it pushes to 8:00 AM the next day. This applies to both day-based and delay-based scheduling.
​

Q: Can I combine day-based and delay-based scheduling in one automation?
A: You can switch from one mode to the other once within an automation, but you cannot alternate back and forth. For most use cases, Sharad recommends sticking with delay-based.

Points to Remember: