6.0 Office Hours - Sep 21 - 12 PM ET

On Monday, September 21, 2026, Sharad Mehta and Tyler Scott hosted the noon office hours call, opening with a walkthrough of the 6.0.3 mobile app update and previewing a wave of features scheduled for Tuesday, September 22, and the rest of the week.

The call closed with a reminder that the evening session would continue at 3:00 PM Pacific.

Sharad announced that the 6.0.3 update is live on both iOS and Android and asked all users to upgrade. The update fixes an issue where users on the latest iOS version were being automatically logged out, which was also causing in-app call answering to fail. The notification bell icon on the app home screen now mirrors the default notification settings configured in the web version. Users can also copy a lead address from the app and place calls directly from the dispo tab.

Sharad previewed three features in his test account, all scheduled to go live Tuesday, September 22. The My Communication Number setting will let users choose whether outbound calls go from a per-record override, the campaign number, or a personal fallback number, with the option to save the override permanently for a specific contact or use it for a single call only (00:04:03). The notification center will add an unread-only filter, display contact names on notifications, and eventually allow replying to calls, texts, and notes directly inline. The calendar will switch to a list view with all appointments at the top and tasks below, with inline editing and a bulk-complete option.

Several additional features are expected by the end of the week. A claim-lead button will appear in both grid view and list view. The list stacking dialer will offer the choice of one, two, or three lines instead of only the triple-line option. The single-line dialer is being redesigned to display full lead information and the calling script on the right side of the screen. Sharad also confirmed that the campaign-based dialer is returning, allowing users to push a subset of list stacking records into a campaign and give cold callers access to dial only that campaign without exposing the entire list stacking database (00:06:52).

A user showed that after a team member is assigned through automation, there is a one-to-two-minute delay before the next step fires. Sharad agreed the system should execute immediately and said the team would address it. The same user requested an on/off toggle for automations so they can be saved in draft without activating, similar to Zapier's toggle. Sharad confirmed there is currently no way to deactivate a saved automation and said the feature would be added (00:12:04).

Separately, the user flagged that the incoming SMS activity trigger does not include an option to select which phone number the text came from, so the automated reply cannot dynamically match the seller's inbound number. Sharad confirmed the reply should default to the campaign number and said the option would be added.

Mark confirmed that the variable field issue for name and property address in list stacking drip texts was fixed over the weekend. However, custom fields are no longer importing correctly on new uploads, a regression from a fix that worked the previous week. Tyler confirmed the ticket is open and the team is actively looking into it. Notes entered in list stacking also do not transfer when pushing a record to leads, nor do call recordings from the list stacking dialer (00:32:03).

A separate user reported that only the primary phone number transfers when pushing a list stacking record to leads, leaving all other contacts behind. Sharad explained that the design was intended to push clean data only, but agreed the system should allow selecting multiple numbers during the push, and the team will add that option (00:30:01).

A user demonstrated that roughly 75% of leads created through Zapier are no longer auto-populating property data (beds, baths, estimated value, owner info), a significant increase from the 5% failure rate in the previous version. Sharad tested the same address manually and confirmed it pulled correctly, suggesting the issue is specific to leads created via Zapier. The data provider has not changed, so the team is investigating whether stricter address validation on the Zapier path is causing the failures (00:50:19).

The same user also flagged that custom text and URL fields pushed through Zapier are not rendering as clickable links. Sharad requested the specific lead URL to have the team investigate.

A user scrolling through 34 uploaded photos on a lead found that the image carousel stops advancing after six images. Clicking directly on the seventh or eighth image also failed to load further. Tyler confirmed he has seen the same bug. Separately, the user raised an issue with uploading photos from an iPad, where HEIC-format images taken as screenshots may not render properly inside the files section.

Sharad showed that the inbox notification settings allow disabling list stacking notifications entirely, so team members who do not handle cold outreach responses can keep their inbox clean. A user requested the ability for account owners and admins to view the system as any team member to verify settings, permissions, and notification visibility. Sharad confirmed this was available in the previous version and will return, but the rebuild requires an audit trail so that any changes made while viewing another team member's account are attributed to the person who actually made them, not the team member being viewed (01:08:58).

Sharad mentioned that REsimpli is in the process of acquiring the code base of an eSign platform to replace the current third-party integration with Foxit. The acquisition will allow custom lead fields to be mapped directly into contract templates, and signed documents will automatically save into the lead's file folder. The current system requires manually downloading and re-uploading signed contracts.

A user reported that deal profit entered through journal entries is not appearing on the business KPI dashboard, even though the same workflow worked in the previous version. Sharad confirmed the journal entry method is still the correct way to record final profit and said the team would investigate why it is not pushing to the dashboard. He clarified the alternative: marking a property as sold under inventory uses the property-level profit field, which feeds manual entry KPIs. Both paths are valid, but the journal entry path is more precise for users who track exact profit after expenses outside REsimpli (01:17:08).

Sharad confirmed the team had collected a significant number of tickets from the call and would push fixes alongside the Tuesday, September 22, feature batch. Tyler noted that the volume of incoming issues was shifting from bugs toward feature requests, which he took as a sign the platform was stabilizing. Sharad previewed the week ahead: an automation masterclass on Thursday, September 25, and a potential guest session the following week featuring a REsimpli user who built dashboards and Slack integrations using the Open API and Claude. The evening office hours session was set for 3:00 PM Pacific on the same Zoom link.
​
​