Skip to main content

6.0 Office Hours - Sep 18 - 12 PM ET

Written by Tazoar Ahsan

Overview

Office Hours session hosted by Sharad Mehta and Anthony. This midday session opened with a recap of 12+ updates pushed that morning and a preview of items shipping the following week. The call then moved into extended Q&A covering automation, calling, SMS, list stacking, and several active bugs. Attendees included Randy, John, Mark, Michael, Fred, David, Michaela, Luke, Saad, Lyndon, Gabe, Joe, Brian, and Richie.

  • Caller ID and smart routing updates are scheduled for Monday, September 21, along with the automation draft/active toggle and automation limit increase from 25 to 50

  • Tasks will be created at automation enrollment time rather than only when due, shipping Saturday, September 19

  • The campaign_number merge field was removed in 6.0; users should switch to the marketing tracking number for source attribution

  • A bulk tag bug was confirmed where applying a tag to selected leads incorrectly combined all tags across those leads

  • Variable migration from 5.0 to 6.0 caused the first_name merge field to output full names in some SMS templates, with a fix in progress

The session closed with Sharad confirming the next call at 6:00 PM ET that same day, Friday, September 18, and noting that office hours would continue the following week with a Monday, September 21 afternoon deep dive into automations.


0:00:00 Platform updates and upcoming release preview


Sharad opened the call with a rundown of updates pushed that morning, including fixes to the lead detail page, driving directions, call recording access, internal notes, calendar sync, pipeline stage colors, and the list stacking inbox separation shipped September 17. He then previewed upcoming items: caller ID selection and smart call routing arriving Monday, September 21; tasks created at enrollment time shipping Saturday, September 19; the iOS app fix for calls; the automation draft/active toggle; automation limit increasing from 25 to 50; appointment variable fixes; and the return of the classic task view. Anthony confirmed they were tracking all feedback from the week's calls and converting it into development tickets.


​0:18:00 Campaign columns, Zapier lead creation, and bulk SMS variables


Randy reported that the marketing campaign column was missing from the leads grid view. Sharad confirmed the column had not yet been re-added after the 6.0 migration and committed to restoring it. John had an issue where a Zapier automation meant to create three separate leads from a Google Sheet was only creating one. Sharad identified the likely cause as Zapier batching rows and walked through restructuring the zap to process each row individually. Mark flagged that the property address variable was not populating in bulk SMS sent from list stacking. Sharad confirmed the variable system had changed in 6.0 and committed to fixing it.


​0:32:00 Call routing, lead assignment, and campaign-level automations


Michael reported that inbound calls were not ringing his phone. Sharad logged into the account and found the root cause: no lead assignment automation was in place, so leads entered the pipeline without an assigned user and calls had no one to route to. He built the assignment automation on the spot. Fred asked whether each marketing campaign needed its own automation to track lead sources. Sharad explained that a single automation using the marketing tracking number is sufficient, since the system attributes the source based on which tracking number the lead called.


​0:45:00 Call pop-up improvements and qualifying questions panel


David confirmed that the call pop-up now includes a link to the lead record, a fix that shipped September 17. He raised a new issue: during an active call, the qualifying questions side panel overlaps the call controls, making it impossible to end or mute the call. Sharad acknowledged the layout conflict and said the team would address it. David also requested the ability to trigger the qualifying questions panel directly from the call pop-up.


​0:52:00 Automation filters, appointment variables, and search sorting


Michaela asked about the "contains" and "does not contain" filter logic in automations, and Sharad confirmed both are available for text-based conditions. She reported that the appointment date/time variable was pulling incorrect values. Sharad said the fix was scheduled for Saturday, September 19. Michaela also asked for search results to sort by most recent activity rather than alphabetical order, which Sharad agreed would be more useful and committed to changing.


​1:02:00 SMS notifications, campaign number removal, and pipeline structure


Luke reported that SMS notifications had stopped working for his entire team. Sharad investigated live and could not identify the cause from the account settings, so he escalated the issue. Luke also discovered that the campaign_number merge field had been removed in 6.0. Sharad explained that campaign-level number assignment was replaced by the marketing tracking number system, and walked through how to update existing templates. Luke asked about structuring warm leads versus active leads, and Sharad recommended using pipeline stages within a single pipeline rather than creating separate pipelines to avoid complicating automations.


​1:22:00 Bulk tag bug, automation save failures, and iOS call conflicts


Saad reported a bulk tag bug: selecting multiple leads and applying a tag resulted in all tags from all selected leads being combined and applied to every selected lead. Sharad confirmed the bug and escalated it. Saad also reported that automation changes were not saving, with edits reverting after he navigated away. Sharad could not reproduce the issue immediately and asked for screen recordings. Saad further reported that the call pop-up had never worked on his account and that iOS was conflicting with REsimpli calls, causing them to drop when the phone's native dialer activated. Sharad acknowledged the iOS conflict as a known issue with a fix in progress.


​1:38:00 Variable migration, duplicate detection, and Zapier field issues


Lyndon reported that the first_name variable in his SMS templates had started outputting the lead's full name after the 6.0 migration. Sharad confirmed this was a variable migration issue and committed to fixing it. Gabe found that duplicate lead detection was failing when the same address was entered in different formats, such as "Road" versus "RD." Sharad said the system currently requires an exact match and agreed to look into fuzzy matching. Gabe also reported that duplicate lead notifications were not firing through Zapier. Joe had an unresolved two-step Zapier issue from a previous call, and separately discovered a race condition where a one-minute delay in an automation allowed a "stop all automations" trigger to fire before the delayed steps completed.


​1:52:00 Buyer templates, deal counts, scheduled blasts, and list stacking transfers


Brian reported that SMS templates assigned to the buyer pipeline were not visible in the inbox compose view when texting a buyer lead. Sharad confirmed this was a bug. Brian also noted that the buyer deals count on the dashboard was showing the number of linked properties rather than closed deals, which Sharad committed to correcting. Brian requested scheduled email and SMS blasts with batch sending to spread delivery over time, which Sharad confirmed is on the roadmap. Richie encountered a "contact already exists" error when moving leads from list stacking to the active pipeline. Sharad found and fixed a backend issue on the spot that resolved it. Richie confirmed his AI calling automation was now working after the fix. A final caller asked about inline editing on the transaction management page and zooming the pipeline grid view on smaller screens, both noted as future considerations.

Did this answer your question?