Overview
On Wednesday evening, September 23, 2026, Sharad Mehta and Tyler Scott hosted the 6:00 PM office hours call, fielding questions on per-lead call flow overrides, three-way calling setup, bulk SMS to multiple contacts, and Google Calendar sync issues.
The Change Call Flow feature at the lead level applies to all contacts and properties tied to that phone number in the system, not just the single lead being viewed.
Three-way calling with overseas team members works by purchasing a dedicated number in the system, assigning it to the team member, and forwarding calls to them in-app.
Bulk SMS to all skip-traced numbers on a single lead (husband, wife, and associated contacts) is not currently available but is expected in the Monday, September 28, web update.
Google Calendar is not syncing edited appointments; new appointments push correctly, but changes to date or time do not update in Google Calendar. The issue is ticketed.
Smart routing was again recommended as the default for most users, and Sharad re-walked several users through the Settings > Communication & Marketing > My Communication Number screen.
A2P compliance language is re-prompting on every text in list stacking even after the first message includes opt-out language. Sharad acknowledged the issue and said a fix is in progress.
The call closed with a reminder about the Thursday, September 24, noon office hours and the automation masterclass scheduled for Thursday evening.
00:02:00 Per-lead call flow changes apply to all contacts sharing that phone number across the system
A user asked whether the Change Call Flow button on a lead would affect other records. Sharad clarified that the override is tied to the phone number, not just the individual lead. If a seller has the same number across multiple properties, the call flow change applies to all of them because the system cannot determine which property an inbound caller is referencing. The warning text in the interface was reworded during the call to say "all contacts" rather than "all related properties" to reduce confusion (00:03:39).
Sharad also explained that this replaces the old Change Call Forwarding feature, which accepted a raw phone number. The new version routes to a call flow instead, which means users can forward calls in-app to overseas team members without needing a US phone number for each person.
00:04:41 Three-way calling works through a dedicated number assigned to the team member
A user asked how to add a third party, such as a seller's family member, to a live call. Sharad confirmed three-way calling is functional and walked through the setup for adding overseas team members: purchase a phone number in the system, assign it to the team member as an all-purpose number, and set the call flow to ring them in-app. When a call is transferred or conferenced, the number rings directly inside the REsimpli app on the receiving end.
00:04:51 Bulk SMS to multiple contacts per lead is expected in the Monday, September 28, update
A user whose business focuses on foreclosures described a workflow where each property may have multiple skip-traced numbers for both husband and wife. In the previous version, a single Zapier push would send bulk SMS to all associated numbers. In 6.0, the system only sends to the first contact. Sharad confirmed the update to support multi-contact SMS is scheduled for the web release on Monday, September 28. In the interim, users sending to multiple numbers per address have to text each contact individually (00:05:00).
00:05:52 Google Calendar does not sync when appointments are edited after initial creation
A user reported that new appointments created in REsimpli push to Google Calendar correctly, but when the appointment date or time is changed in REsimpli afterward, Google Calendar does not update. Sharad confirmed this is a known issue with a ticket open. The workaround is to delete the original appointment and create a new one, which will push to Google Calendar as a fresh entry.
00:02:24 A2P opt-out language is re-prompting on every text in list stacking
A user flagged that even after including the "Reply STOP to opt out" message on the first text to a list stacking contact, the system requires re-inserting the opt-out language on every subsequent message in the same conversation. Sharad acknowledged this as a bug specific to list stacking and said the fix is in progress alongside the broader A2P compliance refinements.