6.0 Office Hours - Oct 16

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

00:01:06 — SMS to all contact numbers timeline and the primary-versus-all-numbers automation option

00:03:36 — STOP reply behavior at the number level versus the property level in automations

00:17:27 — Sellers with multiple properties and automation conflicts: the no-automation pipeline workaround

00:23:13 — Schedule and next week preview

John asked for a status update on sending automation texts to all phone numbers on a property, not just the primary. This feature has been discussed since October 5. Sharad confirmed it is being bundled into the larger automation update that includes defer start and choose-which-step. The timeline is now 2 to 3 weeks. When live, each automation will have two sending options: primary number only (current behavior) or all contacts/all numbers. John expressed frustration that the timeline has shifted multiple times. Sharad explained the team decided to ship it as part of one combined update rather than piecemeal (00:02:22).

​Q: When will REsimpli automations support sending SMS to all phone numbers on a lead, not just the primary?
A: Expected in 2 to 3 weeks from October 16 (approximately early November 2026). It will ship as part of the automation update that also includes defer start and choose-which-step.

​Q: How will the all-numbers automation option work?
A: Each automation will offer two sending modes: primary number only (current behavior) or all contacts/all numbers. Selecting all numbers sends the same text step to every phone number on the lead.

John asked what happens when one phone number on a multi-number property replies STOP while an automation is running. Sharad clarified the behavior in detail. When a contact replies STOP, Twilio blocks all future texts to that specific phone number. The automation itself continues at the property level: emails, direct mail, tasks, and texts to other phone numbers on the same property keep going. The automation does not stop unless you have a "stop automation on any reply" trigger configured, in which case the entire automation stops for all numbers on that property (00:06:02).

John flagged this as a pain point: if one number out of four replies STOP or is a wrong number, the automation for the remaining three good numbers stops too when "stop on reply" is active. Sharad acknowledged the limitation and noted that the "start at step X" feature (coming in the same update) partially addresses it: if the automation stops, you can restart it at the next step rather than from the beginning. Per-number automation paths (independent drip schedules per phone number on the same lead) are not feasible because most automation actions (status changes, tags, tasks) operate at the property level, not the number level (00:06:32).

​Q: If one phone number on a lead replies STOP, does the automation stop for all numbers on that property?
A: Not by default. Twilio blocks texts to the specific number that replied STOP. Texts to other numbers on the property continue. The automation only stops for all numbers if you have a "stop automation on any reply" trigger configured.

​Q: Can I have independent automation schedules per phone number on the same lead?
A: No. Automations operate at the property level, not the number level. Most actions (status changes, tags, tasks) apply to the lead as a whole. Per-number drip paths are not planned.

​Q: What happens to emails and tasks when one number replies STOP?
A: They continue. STOP only blocks SMS to that specific number. Emails, direct mail, tasks, and calls are unaffected.

Cade described a scenario where the same seller owns multiple properties. When both properties enter the active pipeline and trigger status-change automations, the seller receives duplicate messages from both automations simultaneously. Sharad recommended creating a separate pipeline called "seller with multiple properties" with no status-change automations attached. Move the secondary property to that pipeline and work it manually. The primary property stays in the active pipeline with automations running normally (00:21:08).

Sharad also showed that the if-else condition "number of properties owned" already exists in the automation builder and pulls data from the Portfolio tab. A future if-else based on tags will provide additional flexibility. Until then, the separate pipeline workaround is the cleanest solution. Cade noted that 3 to 4 out of 5 multi-property situations come in as a package, but occasionally a second property surfaces mid-conversation during a sales call (00:22:04).

​Q: How do I prevent duplicate automation messages when the same seller owns multiple properties?
A: Create a separate pipeline with no status-change automations. Move the secondary property to that pipeline and work it manually. The primary property stays in the active pipeline with automations running.

​Q: Is there an if-else condition for sellers who own multiple properties?
A: Yes. The "number of properties owned" condition exists in the automation builder and pulls from the Portfolio tab. You can route leads differently based on how many properties the seller owns. If-else based on tags is also coming.

Points to Remember: