Overview
On Friday evening, September 25, 2026, Sharad Mehta hosted a short office hours call solo, noting that support ticket volume had returned to normal levels since the 6.0 launch.
The communication log duration filter was returning calls under the threshold due to rounding logic, and a fix was ticketed alongside a request to add incoming/outgoing direction filters.
Task filters were returning leads with no active tasks because completed tasks were included by default; adding a "Pending" status filter resolves this.
A buyer SMS campaign reply bug prevented users from texting back buyers who had responded to an SMS blast, showing a "landline or invalid number" error; Sharad promised a fix by the next morning.
Call flow configuration was adjusted live from sequential cell-phone forwarding to in-app simultaneous ring, which Sharad said had been stabilized in recent updates.
Smart Routing was enabled for another user's account to prevent number overrides across the team.
The call closed with a repeat of the next week's schedule: one call per day at 1:00 PM Pacific, with Monday, Wednesday, and Friday as office hours and Tuesday and Thursday as webinar deep dives.
00:02:00 Communication log filters return incorrect results for call duration and task assignee
A user demonstrated that filtering communication logs for calls of two minutes or longer was returning 38-second and 53-second calls. Sharad explained that the system rounds any call over one minute up to two, which accounts for some results, but acknowledged a bug for calls well under a minute and ticketed it. The same user noted that filtering leads by task assignee returned leads with no tasks at all; the issue was that the filter included completed tasks by default, and adding a "Pending" task status filter resolved it (00:05:55).
Sharad also confirmed that incoming versus outgoing call and SMS direction filters, which existed in 5.0, are not yet available in 6.0 communication logs. A workaround is filtering by "Call Answered By" and selecting team members, but this misses unanswered inbound calls. Both the direction filter and the duration fix were added to the team's queue.
00:09:06 A buyer SMS campaign reply bug blocks outbound texting to responsive buyers
A user set up an SMS blast to buyers for a specific deal and had messages delivered successfully. When a buyer replied expressing interest, every attempt to text them back returned a "landline or invalid number" error, despite the initial message having been delivered and the buyer having responded. The workaround involved removing the buyer from the SMS campaign before replying, but that required desktop access and could not be done from the mobile app by the dispo team in the field (00:15:02).
Sharad logged into the account, confirmed the issue, and said the fix would ship overnight. He also switched the account to Smart Routing and checked the A2P 10DLC registration status. The user noted this was blocking their ability to market deals entirely, since their dispo team works from mobile and cannot perform the desktop workaround.
00:16:06 Call flow adjusted from sequential cell forwarding to in-app simultaneous ring
A user reported that incoming calls were ringing only once on the mobile app, showing as missed calls even when someone was actively on the line, causing duplicate callbacks from other team members. Sharad found the call flow was set to sequential forwarding to cell phone numbers and walked the user through switching to in-app ringing with a single forward step and both team members selected for simultaneous ring. He removed a conflicting second step in the call flow and added a voicemail fallback at the bottom. Sharad noted that the in-app calling experience had stabilized in recent updates and recommended users switch back to it.