6.0 Office Hours - Sep 22 - 12 PM ET

This office hours session took place on Tuesday, September 22, 2026. Sharad Mehta hosted with Tyler Scott, REsimpli's Head of AI, and the call opened with a walkthrough of the overnight product updates before moving into an extended open Q&A.

The call ended with a reminder about the automation master class on Thursday, September 24 at 6:00 PM ET, the next office hours that evening at 3:00 PM Pacific (6:00 PM Eastern), and an OpenAPI session with investor and developer John planned for the week of September 28.

​00:02:03 My Communication Number caller ID settings, Smart Routing, and record number overrides

Sharad walked through the new My Communication Number setting and recommended Smart Routing as the default. With Smart Routing on, an outbound call or text from inside a lead uses the user's record number for that contact if one exists, then the campaign number attached to the lead, then the fallback number the user sets. That fallback can be the same across the whole team or different for each person. A user can override the number for a single call or text, or save it as their record number for that contact. Either way, the change applies only to that user, never to the whole team. Later in the call, Gail learned that the Make a Call action outside a lead follows this same setting, which explained why she couldn't change the number from that screen.

For now the update works only on the web, for calls and texts made from inside a lead. Smart Routing for the single line dialer, triple line dialer, and bulk SMS is coming by Friday, September 25, and the app version is waiting on store approval. Automations and AI agents keep using the numbers set in each step. They send from the lead's marketing tracking number, or from the fallback when a lead has no campaign number. The team is also weighing an option to switch caller ID automatically to the last number a seller replied to, including whether that switch should apply to the whole team or only to one person. Separately, Sharad agreed to add a reply-from-the-receiving-number option to incoming SMS triggers after Katrina asked for it.

Sharad and Derek also discussed a multi-number texting strategy. The first message, sent with A2P 10DLC opt-out language, goes from the main number, and follow-up texts or AI calls go from a second number. This lets teams A/B test different messages and keeps the opt-out language out of later threads.

​00:05:53 List stacking updates, dialer filters, and migration gaps

The list stacking improvements drew follow-up questions throughout the call. Katrina reported that a test lead's phone number had attached itself to many existing list stacking records, and Sharad opened a ticket for it. Tyler confirmed that conversational AI and AI dialing are not in list stacking yet. Both were pulled before the 6.0 launch while the team works out how AI memory should handle cold leads. They should arrive this year, after a beta with volunteer accounts, but not within the next few weeks.

Mera, a lead manager, said the triple line dialer starts over at the first record after she logs back in, and that redial skips back about ten leads. Tyler showed her how to build saved filters by list name and last outgoing call date, for example 7 to 28 days, so each session starts on the right records. Sharad will test the redial behavior himself. Mera also lost her saved filters in the migration, which could not be carried over, along with some tasks, which should have transferred and now have a ticket. Mark asked for clickable property analytics on the list stacking dashboard, and Sharad committed to getting him an ETA.

​00:06:47 Automation limits, day zero actions, and chaining workflows

Within a day or two, automations will create all their tasks as soon as they trigger, even tasks due months later. The limit of 100 automations per day applies only to manual bulk assignments. Incoming leads and activity triggers such as incoming SMS have no limit, and Sharad hopes to raise the manual limit the week of September 28. Until checklists can be added directly to automation tasks, users can get them by creating those tasks from a task template.

Derek walked through his 90-day new lead automation for PPL leads. Day-based automations allow only one day zero action, because the system can't know when a lead will arrive. The workaround is to put the immediate steps in a minute-based automation and add a Move to Other Automation step that hands off to a second automation built under Manual. The day-value error Derek saw on September 18 has since been fixed, so day-based automations can again run past 30 days. Copying an automation isn't available yet, but the team will copy one on request by email. To tag leads from each PPL vendor, Derek was advised to create a separate marketing campaign and automation for each vendor. Caleb's "active AI conversation" block on older leads goes to the team. In the meantime, the suggested fix is to stop the AI conversation and restart it.

​00:07:13 Notification center redesign and calendar list view

The redesigned notification center will let users filter to unread items and reply to mentions, calls, and texts without leaving the panel. Also due the week of September 21, the calendar list view goes back to its earlier layout, with upcoming appointments at the top and a task list below that supports bulk actions and inline edits. Calling from filtered call tasks is planned for later.

​00:10:58 Leaderboard AI agent tracking and lead manager dashboard metrics

Starting the week of September 28, the leaderboard will list the AI agent as its own team member, showing how many calls the AI makes and how many texts and emails automations send. Today those calls are credited to the account owner. Tyler pointed out that one lead manager's dashboard showed 179 calls while the communication logs showed 473. Sharad explained that the dashboard counts unique properties so repeated dials can't inflate the numbers, and agreed to add total dials next to it. Dashboard data appears only when the user is in the lead manager role and assigned as lead manager on the lead.

Caleb asked how to read appointment metrics. Sharad explained that the qualified versus not qualified mark measures the lead manager's appointment quality. Kept versus not kept reflects the acquisition side, whether the cancellation came from the seller or the team. Reading both alongside conversion to contract shows where a team's process breaks down.

​00:18:23 Mobile app bugs, SMS sync prompt, and iOS incoming calls fix

Caleb sent videos of bugs he found on the latest app version, and those went to the dev team. He also reported a sync prompt that appears every time he texts the same contact. Sharad traced it to contacts linked to multiple properties and said the system will default to the single property when only one exists. Emma's missed incoming calls came from an Apple privacy change. Deleting the app and reinstalling version 6.0.3, released over the weekend of September 19 and 20, fixes the problem on both the app and the web. Noah's team was locked out after canceling, even though they had data access until October 9, and that issue went to support.

​00:50:52 Lead intake errors, TCPA quiet hours, agents as vendors, and OpenAPI

James reported a Facebook-to-Zapier lead rejected as a duplicate even though it had no address. The bug was fixed on Saturday, September 19 but showed up once more on September 22, and Anthony will run tests with him. Two-step forms now merge into one lead when the second step arrives without an address within 30 minutes. James also asked that leads with invalid emails come in with the email left blank instead of being rejected, and Sharad will raise this with the team. Automated texts and AI calls run only from 8:00 AM to 8:00 PM, based on the area code of the contact's phone number, to stay within TCPA rules. An attorney is reviewing whether users with proper opt-in can lift this restriction for inbound leads.

For nationwide novations, Tyler recommended adding listing agents as vendors until agents can be linked to sellers. He suggested the Agents app for agent outreach and a custom referrals pipeline for realtor referrals. Through OpenAPI, enriched data can be pushed in only when a lead is created, and an update-lead endpoint is coming soon. John will lead a session on his OpenAPI builds the week of September 28.

The call wrapped on an upbeat note. Support tickets are improving, and the team is now hearing more feature requests than bug reports.