6.0 Office Hours - Sep 14 - 12 PM ET

On September 14, 2026, Sharad Mehta and Tyler Scott hosted the first of a series of daily open Q&A calls following the REsimpli 6.0 launch on September 12.

The session ran over two hours with more than 100 attendees and closed with a discussion of how the "new leads" dashboard counter should be redefined now that leads can land in any pipeline stage.
​

Sharad announced that the 6.0 Zapier app was being pushed live during the call, with the CTO running final testing. An early version only created actions for leads rather than buyers, agents, or vendors, and that was being patched. All previous Zaps are incompatible because field mappings and available actions changed, so users need to create new Zaps from scratch. Webhooks are now under Settings > API and Webhooks, with limits raised on request (01:57:02), and an open API is available as an alternative to Zapier (01:58:52). One user reported a 503 error authenticating with the API key, which Sharad escalated (02:23:14). Additional API endpoints can be requested by email and will be prioritized after the initial wave of urgent fixes.
​

A change in 6.0 made it so selecting a phone number for a call saved it as the default across the entire system. Sharad confirmed a smarter routing hierarchy was in development: the system will first try the campaign number, then the number the seller last responded on, then the last number the user called from, and finally a user-defined fallback (00:11:33). The hover tooltip showing from/to numbers on call and SMS icons was missing from the active leads view and would be restored by September 15. Sharad clarified that the fallback number in drip campaigns is only used when no campaign number is assigned (02:05:01).
​

Closing the call window with the X button disconnects the UI but leaves the call active, a known issue already ticketed for a minimize-button fix. The single-line dialer was not displaying lead addresses or property details during calls (00:50:17), and the call disposition screen lacked options to set a task or appointment before moving to the next call (02:00:37). Call flow routing by property status was grayed out for at least one user (00:34:29), and incoming calls were ringing for all team members regardless of lead ownership.
​

Existing drip campaigns migrated but were paused, and Sharad shared Loom videos showing how to find affected leads and reactivate automations. The merge fields in SMS and email templates changed from the old @ syntax to new variable names, so every step in every drip needs manual updating. One user described having 20 drips with 40 steps each and called the workload overwhelming (01:08:08). Sharad acknowledged the communication gap and said preserving the old field format was impossible because variable fields were extended system-wide.
​

The inbox no longer shows tagged comments from team members; those now appear under the bell icon, and a combined inbox with internal chat is planned. The due-today task count was pulling in overdue items across all record types without displaying lead names (00:27:28), and the appointment counter was inaccurate and will be scoped to today only. On mobile, tapping open communications or tasks does not navigate to a lead list, which is critical for field teams running multiple appointments daily (01:37:50). An iOS and Android update restoring those features was expected within a day or two.
​

With up to 20 pipelines and 20 stages each, a single grid view for all leads is no longer feasible, so All Leads defaults to list view while individual pipelines retain grid view. Saved filter folders carried over in name but not in function: they appear across all pipelines even when they apply to only one, and clicking a filter from a different pipeline returns empty results (02:01:51). Filter names from the old system also block creation of identically named new filters, which users were told to work around by appending a suffix.
​

Existing customers stay on their current plans; the new Solo, Team, and Business pricing with unlimited calling and texting applies only to accounts created from September 12 onward (00:42:01). AI features remain optional. Multiple users voiced strong frustration, with one team operating out of a Google spreadsheet and another reporting a fourfold increase in lead response time (01:40:36). Sharad explained that running the old and new databases in parallel was not technically possible, but acknowledged that pre-launch communication fell short. A user requested a consolidated change-management email, and Sharad summarized the four priorities: reconnect drip campaigns, set up lead assignment automations, recreate Zapier integrations, and rebuild saved filters (01:34:51).
​