Skip to main content

6.0 Office Hours - Sep 14 - 6 PM ET

Written by Tazoar Ahsan

Overview

On Monday evening, September 14, 2026, Sharad Mehta and Tyler Scott hosted the second office hours call of the day, following a four-and-a-half-hour noon session. The call ran approximately two hours and 30 minutes. Sharad opened with a live walkthrough of drip campaign reactivation and lead assignment setup, then took Q&A on a list stacking deletion bug, legacy pricing and plan transitions, OpenAPI integrations, custom fields and pipelines, outbound phone routing, dashboard and task gaps, and buyer-to-agent bulk transfers.

  • Sharad acknowledged that the biggest mistake was assuming the pre-launch webinars (2,500+ unique attendees) were sufficient communication. He should have sent dedicated emails about drip campaign reactivation and lead assignment changes.

  • All drip campaigns from 5.0 now live under Automations in the "lead manual assignment" section. Leads that were on a specific drip can be found by filtering All Leads by drip name, then bulk-reassigned to the corresponding automation.

  • New lead assignment is now handled entirely through automations. Users must create a "new lead created" automation selecting their campaigns, target pipeline and status, and team member assignments. Leads created during or before the transition that were not assigned can be found by filtering for "does not contain" a specific role and bulk-assigned.

  • A user reported that filtering and deleting approximately 2,500 list stacking records by tag and "no phone number" wiped far more records than expected, leaving only leads-status properties visible. Sharad confirmed the team has a data snapshot and would restore the records.

  • Legacy plan users (signed up before September 12) keep their existing pricing and billing. No automatic migration to the new plans occurs. New plans (Solo, Team, Business) include unlimited calling, SMS, email, eSign, list stacking, and cash buyer searches. The only difference between tiers is team size: Solo supports up to 4 users, Team supports 5 to 12, and Business supports 12 and above. There is no functionality difference between tiers.

  • A user on an annual legacy plan reported SMS credits not resetting since June. Sharad created a ticket to investigate.

  • OpenAPI is available on all plans including legacy. Update-existing-lead is not available yet but is coming. An MCP server integration for Claude and ChatGPT is planned for later.

  • Custom fields are live and filterable, including date fields. Custom pipelines and custom statuses are live, with up to 20 pipelines and 20 statuses per pipeline.

  • The outbound phone routing update (later named smart routing) is being built with a priority cascade: record-level number, then last communication number, then last number called from, then campaign number, then personal fallback. Shipping within days.

  • The "new leads" counter on the dashboard does not exist because statuses are now customizable. The team is planning an "untouched leads" metric showing leads with no action taken regardless of pipeline or status.

  • Grid view is only available per individual pipeline. All-leads view must use list view because there can be up to 400 statuses across 20 pipelines.

  • Bulk transfer from buyer to agent is not available as an action. The workaround is tagging the records and sending a Loom video to Sharad so the team can move them manually.

  • Vendors without a campaign cannot be accessed because campaign is required. The workaround is creating a placeholder campaign and having the team bulk-assign.

  • Automations sitting in "pending" without firing through drip steps were reported by multiple users. Sharad said the team would investigate and update on the next day's call.

The call closed with Sharad confirming daily office hours would continue at noon and 6:00 PM Eastern throughout the week, with overnight fixes reviewed at the start of each call.


00:01:32 Sharad walks through drip campaign reactivation and new lead assignment setup, and acknowledges the communication gap

Sharad opened with a live screen share demonstrating two critical post-migration tasks. First, he showed how to find leads that were on a specific 5.0 drip campaign: go to All Leads, add a filter, search "drip," select the specific drip name, then bulk-select and add to the corresponding 6.0 automation. Second, he walked through setting up a "new lead created" automation with campaign selection, pipeline and status targeting, and team member assignment. Any leads from before or during the transition that were not assigned can be found by filtering for a role that "does not contain" the expected team member, then bulk-assigning (00:08:04).


Sharad said he takes full responsibility for the communication gap. The team assumed the pre-launch webinars (attended by over 2,500 unique users) were sufficient, but should have sent dedicated emails about drip reactivation and lead assignment. He noted that completing both tasks resolved 80 to 90 percent of reported issues (00:13:04).


00:10:50 List stacking bulk deletion wiped more records than expected; data will be restored from a snapshot

A user reported that filtering list stacking by a specific tag and "no phone number" and deleting the results removed far more than the expected 2,500 records. After logging out and back in, only properties with an "in leads" status remained visible. Sharad confirmed the team has a full data snapshot and would restore the missing records through a support ticket already in progress (00:12:13).


00:13:45 Legacy pricing stays unchanged; new Solo, Team, and Business plans include unlimited calling, SMS, email, and eSign

A user on an annual legacy plan reported that his SMS credits had not reset since June and asked whether everyone now has unlimited SMS. Sharad clarified that existing users who signed up before September 12 stay on their legacy plan with no automatic migration. Only users who choose to switch or new sign-ups get the new pricing. All three new tiers (Solo for up to 4 users, Team for 5 to 12, Business for 12 and above) include unlimited calling, SMS, email, eSign, list stacking records, cash buyer searches, OpenAPI access, and the triple-line dialer. The only difference between tiers is team size; there is no functionality difference. Legacy plans still include OpenAPI access. Sharad created a ticket to investigate the credit reset issue (00:16:03).


00:16:56 OpenAPI works with Claude and ChatGPT, update-existing-lead is coming, and custom fields including dates are live and filterable

A user asked whether the OpenAPI can integrate with Claude and ChatGPT. Sharad confirmed it can with some technical setup, and noted that an MCP server allowing direct app-like integration within Claude and ChatGPT is planned for later. The API currently supports creating new leads only; updating existing leads is coming soon. Sharad shared the OpenAPI docs link in the chat. He then demonstrated custom fields and custom pipelines, showing that date fields are filterable, which a user noted would be useful for tracking foreclosure auction dates in his pipeline (00:19:46).


00:08:04 Outbound phone routing cascade is being built with record-level, communication, campaign, and fallback tiers

Sharad described the upcoming routing feature (later formalized as smart routing). When making a call, the system will check for a number assigned specifically to that contact (record number), then fall back to the last number used in communication with the seller, then to the last number the user called from, then to the campaign number, and finally to the personal fallback number. This was previewed at the noon call and is expected within days (00:11:58).


02:26:50 Bulk buyer-to-agent transfer requires tagging and a Loom video, vendors need a placeholder campaign, and pending automations are being investigated

A user asked whether buyer records from 5.0 (where buyers and agents were combined) can be bulk-moved to the new agent section. Sharad confirmed there is no bulk action for this yet. The workaround is tagging the records with a unique tag like "Move to Agent," recording a Loom video, and sending it to Sharad so the team can process the move. A second user asked about vendors stuck without a required campaign. Sharad said to create a placeholder campaign and send him the details for bulk assignment. Multiple users also reported automations sitting in "pending" status without progressing through drip steps. Sharad said the team would investigate and provide an update on the next day's call (02:29:56).


02:30:03 The Tuesday, September 15, sessions resume at noon and 6:00 PM Eastern with overnight fix updates

Sharad confirmed the team would be back Tuesday, September 15, at noon and 6:00 PM Eastern, with a rundown of any fixes pushed overnight before opening to Q&A. If needed, the daily calls would extend into the following week.
​

  • Complete both critical post-migration tasks: reactivate drip campaigns from the automation section, and set up the "new lead created" automation for lead assignment.

  • Filter for roles that "does not contain" the expected team member to find and bulk-assign any leads missed during the transition.

  • Legacy plan pricing and billing remain unchanged unless you choose to switch.

  • OpenAPI is available on all plans; update-existing-lead support is coming.

  • Bulk buyer-to-agent moves require tagging and a Loom video to Sharad.

  • Pending automations that are not firing through drip steps are being investigated.

Did this answer your question?