6.0 Office Hours - Oct 7 - 6 PM ET

Wednesday, October 7, 2026. Sharad Mehta hosted an office hours Q&A at 1 PM Pacific / 4 PM Eastern. Approximately 78 minutes.

00:02:49 — Adding a related property to an existing seller via Portfolio > Add Manual Record copies seller info and campaign name

00:07:28 — Global search keyboard shortcut is not yet available, Enter key closes folder creation modal instead of saving, and sidebar lacks an expand-with-labels toggle

00:10:06 — Setting default activity log response type to Note prevents teams from accidentally sending internal notes as SMS

00:12:13 — Automation defer start time, choose-which-step, and SMS to all contact numbers are shipping in one to two weeks

00:13:30 — Zapier AI-extracted addresses break property lookups when city format does not match, and direct PPL provider integrations are in development

00:16:08 — Agent and vendor dual records split communication history on novation deals, but adding the contact as a listing agent on the lead merges the thread

00:30:10 — Speed-to-lead AI dialer requires a dedicated campaign phone number per web form until a fallback number update ships

00:35:00 — AI auto-disposition re-categorized an interested lead as spam after a follow-up message arrived

00:38:04 — Manual automations recommended for reusability across triggers, with stop-other-automations as the first step on every status change to prevent overlapping drip campaigns

00:47:17 — Left sidebar reorder request, list stacking new-list creation requires pressing Enter, SMS batching at 250 to 300 per day, and DNC filter uses phone status not the DNC parameter

01:09:34 — Dispo listing media pulls from the lead Files section, and inbox messages only appear when the team member was assigned at the time of receipt

01:17:46 — Announcement: Thursday, October 8 Dispo webinar at 1 PM Pacific, and weekly schedule confirmation

Daniel McCloskey asked for a shortcut to attach a second property to an existing owner without manually creating a new lead from scratch. Sharad navigated to an existing lead, opened the Portfolio tab, and clicked Add Manual Record. This created a new property record with the same seller contact information, campaign name, and optionally the same tags and buyer data. If the new property shares the same mailing address as the original, it appears automatically in the Portfolio tab because REsimpli links records by mailing address. If the mailing address differs, the user enters the new property address and clicks through to create the record (00:06:58).

Daniel noted that his team had accumulated underwrites on secondary properties that were not linked to the original lead record, making the manual lead-creation process heavier than it needed to be. The Portfolio workflow solves this for going forward, though it does not retroactively link existing orphaned records.
​

Path: Lead > Portfolio tab > Add Manual Record > enter property address > select copy options (seller info, tags, buyer info)

​Q: How do I add a second property to an existing seller without creating a brand-new lead from scratch? A: Open the existing lead, go to the Portfolio tab, and click Add Manual Record. Enter the new property address and choose which information to copy (seller info, tags, buyer data). REsimpli copies the seller contact and campaign name to the new record.

​Q: Does REsimpli automatically link multiple properties owned by the same person? A: REsimpli links properties by mailing address. If two properties share the same mailing address, they appear together in the Portfolio tab automatically. If the mailing addresses differ, you must use Add Manual Record to link them manually.

Daniel raised three UI items. First, there is no keyboard shortcut (such as Command-K) to trigger the global search bar. Sharad confirmed this is planned for the future but not available yet (00:07:34). Second, pressing Enter or Return after typing a folder name in the folder creation modal closes the dialog without saving. The user must click the save button manually. Sharad acknowledged this as a bug and said he would get it fixed, as the Enter key is incorrectly bound to the close action instead of the save action (00:08:08). Third, Daniel requested the ability to double-click the left sidebar navigation to expand it into a persistent state with text labels visible alongside the icons, similar to most other SaaS tools. Sharad explained that the team had tested an expanded sidebar in an earlier version but encountered issues with the sidebar overlapping content panels during quick navigation. He agreed to revisit the idea with the team (00:09:05).

​Q: Is there a keyboard shortcut to open the REsimpli global search? A: Not yet. A keyboard shortcut for global search is planned but has not shipped as of October 7, 2026.

​Q: Why does pressing Enter in the folder creation modal close it instead of saving the folder? A: This is a known bug. The Enter key is bound to the close action instead of the save action. A fix is planned. For now, click the save button manually.

​Q: Can I expand the left sidebar to show labels next to the icons? A: Not currently. The sidebar only supports the collapsed icon-only view. A persistent expanded state with labels is under consideration.

Daniel's team expressed concern about accidentally sending an internal note as an outgoing SMS, especially when composing candid notes about a seller. Sharad showed a per-user setting that changes the default response type from SMS to Note. When set to Note, the activity log input defaults to adding an internal note every time a user opens a lead. To send an SMS, the user must explicitly click "Send SMS" to switch input modes. This setting also syncs to the mobile app (00:11:46).

Path: Settings (gear icon inside the lead) > Activity Log > Default Response Type > select "Add Note"

​Q: How do I make sure my team does not accidentally send an internal note as an SMS to a seller? A: Each team member should go to the gear icon inside any lead's activity log, open the Activity Log settings, and change the Default Response Type to "Add Note." This makes Note the default input mode. The user must explicitly click Send SMS to switch to messaging mode.

​Q: Does the default response type setting apply to the mobile app as well? A: Yes. Changing the default response type in the web app also updates the mobile app for that user.

Daniel asked whether the automation defer start time option from REsimpli 5.0 had been restored. Sharad confirmed three automation improvements shipping together in one to two weeks (by approximately October 21, 2026). First, defer start will allow users to delay an automation's start time after the trigger fires. Second, users will be able to choose which step an automation begins on, rather than always starting at step one. Third, automations will support sending SMS to all phone numbers attached to a contact, not just the primary number (00:13:03).

Path: Automations > [select automation] > (defer start and step selection options coming)

​Q: Can I delay an automation from starting immediately after the trigger fires? A: Not yet, but a defer-start option is shipping in approximately one to two weeks (by around October 21, 2026). This will let you set a delay before the automation begins.

​Q: Can I choose which step an automation starts on instead of always starting at step one? A: This feature is coming in the same update as defer start, approximately one to two weeks out.

​Q: Can automations send SMS to all phone numbers on a contact, not just the primary? A: This is also part of the upcoming automation update shipping in one to two weeks.

Christopher Swade reported that leads pushed into REsimpli via Zapier from one specific lead source had addresses that did not sync correctly. When opening the lead, Zillow and other property lookup tools showed no data, and he had to manually delete and re-enter the city and state to get the address to resolve. The issue occurred because Zapier AI was extracting address data from Gmail notifications and formatting the city field in a way that did not match REsimpli's expected format. Sharad said this is a known class of issue caused by address formatting mismatches and that Anthony would follow up on Thursday, October 8, to review the Zap configuration (00:14:39).

Separately, Michael Roos, a brand-new user who signed up Tuesday, October 6, asked about alternatives to Zapier. Sharad confirmed that REsimpli has an open API for more technical setups but noted that most PPL providers only support Zapier on their end. Direct integrations with Property Leads, Lead Solo, Motivated Seller, and Motivated Leads are in development, with Anthony already in communication with those providers (00:25:07). Sharad also pointed Michael to the solopreneur training recording from Tuesday, October 6, and the automation setup recording for onboarding preparation.

​Q: Why are my Zapier leads showing broken property data or empty Zillow lookups? A: The address format pushed by Zapier may not match REsimpli's expected format. Open both apps side by side and compare how the address fields (especially city and state) are formatted. Contact support or have Anthony review your Zap configuration. This is typically a formatting mismatch on the Zapier side, not a REsimpli bug.

​Q: Are direct integrations with PPL providers like Property Leads coming? A: Yes. Direct integrations with Property Leads, Lead Solo, Motivated Seller, and Motivated Leads are in development. Anthony is in communication with those providers. No specific ship date has been announced.

​Q: Do bulk-imported leads automatically enter an automation? A: No. Bulk imports do not auto-trigger automations by design. Set up your automations first, then manually add imported leads to the appropriate automation after import.

Harris Carr showed that when a listing agent on a novation deal is stored in REsimpli as both an agent record and a vendor record, the communication history splits between the two records. Messages sent via the vendor profile do not appear in the agent profile and vice versa. Sharad walked through a workaround: open the lead, click the plus button next to the seller name at the top of the lead record, search for the agent's name, and add them with the relationship type "listing agent." Once linked as a listing agent on the lead, communication stays within that lead's activity log (00:18:22).

The caveat is incoming calls. If the same agent is the listing agent on multiple properties, outgoing calls made from a specific lead stay attached to that lead. But incoming calls from that agent will appear on all properties the agent is linked to, because REsimpli cannot determine which property the incoming call relates to (00:20:03).

Harris also reported that his inbox filters for agent and vendor messages were not populating correctly. He had been receiving text messages from agents that should appear in the inbox but did not show up, even though the number and filter settings appeared correct. Sharad asked Harris to send a Loom video with specific examples so the team could investigate (00:23:09).

Path: Lead > click "+" next to seller name > search agent name > set relationship to "Listing Agent"

​Q: Why is communication split between agent and vendor records for the same person on a novation deal? A: Agent and vendor are separate record types in REsimpli with separate communication logs. To unify communication on a specific deal, add the person as a listing agent directly on the lead using the plus button next to the seller name. This keeps all communication within that lead's activity log.

​Q: If the same agent is linked to multiple properties, will incoming calls show on all of them? A: Yes. Outgoing calls stay attached to the property you called from, but incoming calls from an agent linked to multiple properties will appear on all of those properties because REsimpli cannot determine which property the call is about.

​Q: My inbox filters for agent and vendor messages are not showing messages. What should I do? A: If your inbox filters are set correctly but messages are still not appearing, send a Loom video to support showing the specific contact, the messages received, and your filter settings so the team can diagnose the issue.

Jose Mota reported that the speed-to-lead AI (Kathy) was not dialing leads who filled out web forms. On the previous week's office hours (approximately Wednesday, October 1), Jose had reported a related PPC speed-to-lead issue. This time, the root cause was that the web form campaigns did not have a dedicated campaign phone number assigned. Sharad confirmed that speed-to-lead currently requires a campaign number attached to each campaign to place outbound calls (00:31:39).

As a temporary workaround, each web form campaign needs its own phone number. Jose asked whether one number could cover all three of his campaigns; Sharad said no, each campaign needs a separate number for the next one to two weeks. An update shipping by approximately October 21, 2026, will add a fallback number option, similar to how SMS campaigns work, allowing multiple campaigns to share a single outgoing number (00:32:45).

Path: Automations > Speed to Lead > ensure a campaign phone number is assigned to each web form campaign

​Q: Why is speed-to-lead not dialing my web form leads? A: Each web form campaign must have a dedicated campaign phone number assigned. Without a campaign number, speed-to-lead cannot place outbound calls. Assign a phone number to each campaign under the automation settings.

​Q: Can I use one phone number for speed-to-lead across multiple web form campaigns? A: Not yet. Each campaign currently requires its own dedicated number. A fallback-number update is shipping in approximately one to two weeks (by around October 21, 2026) that will allow multiple campaigns to share a single number.

Jovan Rivera Ramirez reported that the AI auto-disposition correctly categorized a lead as "interested" and moved it to the appropriate status, but when the seller sent a follow-up message, the AI re-evaluated the conversation and re-categorized the lead as "spam, do not call," moving it out of his pipeline. In a second scenario, each incoming message triggered a new "interested" notification even while the conversation was already active, creating duplicate alerts. Sharad asked Jovan to share his email and the property address or phone number so the AI team could review the conversation history and diagnose the hallucination (00:36:38).

​Q: Why did the AI auto-disposition re-categorize my interested lead as spam after a follow-up message? A: The AI re-evaluates the conversation when new messages arrive and can sometimes hallucinate a different category based on the full thread context. This is a known issue being investigated by the AI team. Share your email and the property address with support so they can review the specific conversation.

​Q: Why am I getting duplicate "interested" notifications on every incoming message for a lead already marked interested? A: The AI may re-trigger the interested classification on each new message instead of recognizing the lead is already categorized. Report the specific lead to support for investigation.

Jovan asked why REsimpli recommends building automation steps inside manual automations rather than directly inside status-change or activity triggers. Sharad explained that a manual automation is reusable: once built, it can be attached to any trigger (status change, incoming SMS, incoming call, tag added, new lead). If you build steps directly inside a status-change trigger, those steps can only fire from that one trigger and cannot be reused (00:39:01). The recommended pattern is to create a master manual automation with your full follow-up sequence, then reference it from multiple triggers using "move to other automation."
​

Sharad also demonstrated that each status can only have one automation trigger. You cannot create two separate automations for the same status change. If you need multiple actions on a status change, add all steps within that single trigger or have it hand off to a manual automation (00:45:39). Status-change triggers can include steps before the handoff: send an SMS, create a task, add a tag, then move to the manual automation.

Rise Gen Homes then showed a live example of overlapping drip campaigns. A seller who had been moved from "offer made" to "under contract" three to four days earlier received a drip message intended for the offer-made stage. Sharad logged into the account and found two automations actively running on that lead. The offer-made automation had not been stopped when the status changed. Sharad stopped both automations on the lead and set up a new status-change automation on "under contract" with "stop other automations" as the first step (01:01:17). This ensures that any time a lead moves to under contract, all previous automations are terminated before new steps begin.

Path: Automations > Lead Status Change > [select status] > Step 1: Stop Other Automations > Step 2+: your follow-up steps or move to manual automation

​Q: Why should I build my follow-up sequences in manual automations instead of directly in status-change triggers? A: Manual automations are reusable. You build the sequence once and attach it to any trigger: status change, incoming SMS, incoming call, tag added, or new lead. Steps built directly inside a trigger can only fire from that one trigger.

​Q: Can I create two separate automations for the same status change? A: No. Each status can have only one automation trigger. Add all steps within that trigger or have it hand off to a manual automation.

​Q: How do I prevent drip campaign messages from going out after a lead moves to a new status? A: Add "Stop Other Automations" as the first step in every status-change automation. This terminates any previously running automations on that lead before new steps begin. Without this step, the previous drip campaign will continue sending messages even after the status change.

​Q: How can I tell if a lead has active automations running? A: Open the lead record and look for a blue indicator showing active automations. If you see entries in blue, those automations are still running and will continue to send messages or create tasks on schedule.

Ruben asked whether the left sidebar navigation icons (Home, Active Leads, Websites, etc.) could be reordered, as he frequently clicked Websites instead of Active Leads. Sharad said reordering is not available but he would discuss it with the team (00:49:03). Ruben also reported an intermittent UI issue where hovering over the sidebar caused a gray overlay to get stuck on screen until he clicked elsewhere. Sharad suggested making sure the app is on the latest version by clicking the update prompt at the bottom of the screen and asked for a Loom video if the issue persists (00:50:09).

On list stacking, Ruben could not figure out how to create a new list name when pushing records from the list builder. The input field shows a dropdown of existing lists as you type, making it appear that only existing lists can be selected. Sharad demonstrated that pressing Enter after typing a new name creates the list. Sharad acknowledged the UX gap and said he would add a hint like "Press Enter to create a new list" (00:52:55).

Ruben then asked how to send SMS to a 1,300-record list without burning his phone number. Sharad recommended batching at 250 to 300 records per day, spread across morning, afternoon, and evening sends of about 100 each. Using the list stacking filter "automation has none of [your automation name]" surfaces the remaining unsent records after each batch. This spreads messages across five to six days and also lets users compare response rates by time of day (00:56:46).

Wayne asked how to filter out DNC numbers in list stacking. He had used the "DNC equals no" filter parameter, but it returned results that still included DNC numbers. Sharad showed that the correct filter is "phone status has none of DNC" under the phone status filter, not the DNC parameter. The phone status filter returned zero results in Wayne's live demo, so Sharad asked Wayne to email his account details for follow-up (01:08:59).

Path: List Builder > Action > Push to List Stacking > type list name > press Enter to create Path: List Stacking > Filter > Automation > Has None Of > [select automation]
​
Path: List Stacking > Filter > Phone Status > Has None Of > DNC

​Q: How do I create a new list when pushing records from the list builder to list stacking? A: In the "Push to List Stacking" dialog, type the new list name in the input field. The dropdown will show matching existing lists, but pressing Enter creates a new list with the name you typed.

​Q: How many SMS messages should I send per day from list stacking? A: Batch at 250 to 300 records per day. Spread sends across morning, afternoon, and evening (about 100 each) to avoid burning your number and to test which time of day gets the best response rate. Use the filter "automation has none of [your automation]" to see remaining unsent records.

​Q: How do I filter out DNC numbers in list stacking? A: Use the phone status filter, not the DNC parameter. Set the filter to "Phone Status has none of DNC" (and optionally "Wrong Number"). The DNC equals no parameter may not filter correctly.

​Q: Can I reorder the left sidebar navigation icons? A: Not currently. This has been noted as a feature request.

Erby reported that the media section of a Dispo listing showed a lock icon and did not allow image uploads. Sharad clarified that listing media is not uploaded directly in the listing workflow. Instead, property images and videos must first be uploaded to the lead's Files section. Once files are in the Files section, they become available in the listing's Add Media step. There is no limit on file types in the Files section: photos, videos, buy-side documents, and sell-side documents all go there (01:11:51).

Separately, Jovan returned to report that his list stacking inbox was not showing all incoming messages. Sharad hopped into Jovan's account and found that the messages existed on the lead record but did not appear in the inbox. Jovan explained that earlier that morning, he noticed the leads were not assigned to him, so he bulk-reassigned them. Sharad identified the likely cause: when the messages arrived, Jovan was not yet assigned to the records, so the inbox did not route those messages to him. The inbox routes messages based on team member assignment at the time of receipt, not retroactively. Sharad created a ticket for the engineering team to investigate further and confirm whether this is the expected behavior or a bug (01:16:45).

Path: Lead > Files tab > upload images and videos > Listing > Add Media > select from uploaded files

​Q: Why do I see a lock icon in the Dispo listing media section and cannot upload images? A: Listing media pulls from the lead's Files section. You must upload images to the Files tab on the lead record first. Then go to the listing and click Add Media to select the uploaded files.

​Q: Why are incoming messages on my list stacking leads not showing in my inbox? A: The inbox routes messages based on team member assignment at the time the message is received. If you were not assigned to the record when the message arrived, it will not appear in your inbox. Bulk-reassigning records after the fact does not retroactively populate the inbox. Contact support if you believe you were assigned at the time of receipt.

Sharad confirmed the next session is a Dispo-focused webinar on Thursday, October 8, 2026, at 1 PM Pacific / 3 PM Central / 4 PM Eastern. The webinar link will be emailed and automatically added to calendars. The Friday, October 10 session will be an open office hours Q&A in the same format as today's call. Monday, Wednesday, and Friday calls are always on the same Zoom link and can be bookmarked. Tuesday and Thursday calls are webinar-style with a different link each time, sent via email. All recordings are posted to help.resimpli.com under the Webinars and Office Hours sections, with timestamps and basic summaries being added.

​Points to Remember: