Hosted by Sharad Mehta. This evening session was a solo Q&A covering a wide range of post-launch topics from notifications to call flow configuration. Attendees included Cade, Ray, Sahil, San, Courtney, Mike, Roman, Don, Jessica, and Ahmed.

The session closed with Sharad confirming calls would continue the next day, Wednesday, September 23, at the usual 12:00 PM and 6:00 PM ET slots, and reminded attendees about the automation masterclass scheduled for Thursday, September 24.

​0:02:00 Notification redesign and role-based routing

Cade raised concerns about notification clutter, particularly duplicate data showing up in the notification center. Sharad confirmed that version 6.0.5, expected within a few days, will clean up redundant notification content and add the ability to call back, text back, and reply to internal comments directly from the notification panel without navigating to the lead record. Unread-only filtering is also coming.

On the question of role-based notifications filtered by pipeline and stage, Sharad acknowledged the request but explained that custom pipelines make this a more complex engineering effort. As a current workaround, users can configure notification preferences per phone number. Sharad also confirmed that automations will not loop: if a status-change automation adds a tag, it will not re-trigger a separate tag-based automation.

​0:12:00 Speed-to-lead, call answering, and automation folders

Cade asked whether speed-to-lead confirms a live human connection before counting the lead as reached. Sharad explained this is a Twilio-level limitation and confirmed it does not verify a live answer. The team is working on in-app call answering so users can pick up directly inside REsimpli rather than through forwarded calls.

The incoming call answer screen currently lacks context about who is calling. Sharad said property address and lead status will be added to the answer screen by Friday, September 25, along with a draggable call widget. Cade also requested automation folders for organization, which Sharad confirmed will be added.

​0:20:00 Stopping drip campaigns with activity triggers

Ray needed help configuring an automation to stop all active drip campaigns when a lead responds by call or text. Sharad walked through the setup live: create an activity-based automation triggered by incoming call, add a "stop all other automations" action, then duplicate it for incoming SMS. Sharad cautioned that the incoming SMS trigger fires regardless of pipeline stage, so users should be mindful of unintended matches.

Sahil reported that tasks from reapplied automations were not appearing immediately. Sharad explained that the current system creates tasks only when they come due, not at enrollment time. An update to create all future tasks at the moment the automation is triggered was in testing and expected to ship by Thursday, September 24. Sahil also flagged an automation email stuck in pending status, which Sharad committed to investigating.

​0:32:00 Caller ID update, task view, and upcoming releases

Sharad shared a brief preview of several updates shipping together. The caller ID selection feature went live that morning. The classic task view is returning, and clicking a task in the notification panel will open it for inline editing. The automation on/off toggle (draft vs. active status) is designed and in development. Once the toggle ships, pre-built automation templates will be pushed to all accounts in draft mode so users can review and activate them selectively.

​0:35:00 Inbox navigation, AI automation builder, and dashboard customization

San raised a UX concern about inbox clicks opening new browser tabs. Sharad acknowledged the tradeoff, noting the behavior was added by user request, and said the team will explore a user-level preference for same-tab navigation. San also asked about the list stacking inbox tab, and Sharad confirmed that since September 17, contacts already in the leads pipeline no longer appear in the list stacking inbox.

San asked whether automation creation could be driven by natural language, similar to Zapier's AI copilot. Sharad confirmed this is on the roadmap: users will eventually be able to describe a multi-step automation in plain language and have the system generate it as a starting point. San also requested a customizable dashboard with movable widgets for KPIs, inbox, and recent activity. Sharad said dashboard customization will come after the current release stabilizes, balancing widget options against page load performance.

​0:49:00 Pricing plans, e-signing, and platform onboarding

Courtney asked about a potential November price increase for existing users. Sharad confirmed there is no price increase planned for legacy accounts. Upgrading to the new plan structure is optional and makes sense primarily for high-volume users whose calling and texting costs exceed the unlimited plan threshold.

Mike asked about the timeline for integrating the e-signing company REsimpli acquired, which would auto-populate property data like legal descriptions and parcel IDs into contracts. Sharad said active integration work would begin in a few weeks, with a more concrete ETA available in about a month, around late October. Roman asked about voicemail drop, which is currently available only in the triple-line dialer.
​
Sharad said the single-line dialer will be updated to let users choose one, two, or three lines from a unified interface, bringing voicemail drop to all modes. Roman also confirmed that the campaigns section is being restored for cold calling workflows.

Don reported that the A2P/10DLC registration form would not submit despite trying multiple browsers. Sharad escalated this to the team member who handles A2P registration and also arranged a trial extension since the registration delay had consumed most of Don's trial period. Sharad reminded users that A2P registration requires a company email address, not a Gmail.

​1:05:00 Call flow configuration, list stacking access, and pipeline management

Jessica asked how call flow works with first-to-claim lead assignment when no one is assigned yet. Sharad demonstrated that if no individual is assigned to the lead manager role, the system rings everyone in that role. Once someone claims the lead, future calls route only to the assigned person. He also highlighted the repeat-call settings, which can route return calls based on pipeline stage rather than following the new-lead call flow.

Jessica noted that Google Calendar events synced to REsimpli now display actual event titles instead of the previous "personal appointment" label. Sharad explained this was changed based on user feedback and recommended using a dedicated business calendar if privacy is a concern.

Ahmed's cold callers could not see list stacking records. Sharad logged into the account live and found the team members had list stacking access but lacked triple-line dialer permissions. He granted access on the spot and walked through the recommended workflow: keep prospects in list stacking, dial from there, and move contacts to the leads pipeline only after a meaningful conversation.

Mike reported that SMS responses from leads pushed from list stacking to leads were routing to the list stacking inbox instead of the lead record. Sharad said this should not be happening after the September 17 update and committed to investigating. Mike also asked about keyboard shortcuts for quick follow-up actions. Sharad demonstrated a tag-based automation workaround: create a tag like "FU," build an automation triggered by that tag to create a task and add a note, then simply apply the tag to any lead for instant follow-up scheduling.

A final caller asked about moving leads between pipelines and reported that status-change automations were still showing as pending rather than executing. Sharad showed how to bulk-move leads across pipelines using the select-all and change-status actions, and asked for specific examples of the pending automation issue to be emailed for investigation.
​
​Key TakeawaysKey Takeaways