6.0 Office Hours - Sep 16 - 6 PM ET

On Tuesday evening, September 16, 2026, Tyler Scott hosted the 6:00 PM office hours call, with Sharad Mehta joining briefly and Anthony handling Zapier and API questions throughout. The call ran approximately two hours and 18 minutes, covering Zapier mapping gaps, custom field editing limitations, triple-line dialer workflow issues, eSign downtime, call flow routing problems, and dispo tab automation requests.

The call closed with Tyler confirming the Wednesday, September 17, sessions at noon and 6:00 PM Eastern.

A user reported that when adding buyers or agents through Zapier, the company name field does not appear as a mappable option. The field exists in the REsimpli UI when adding a buyer or agent manually, but Zapier's integration does not expose it. Anthony confirmed the gap and created a ticket.

The same user also reported that custom fields cannot be edited after creation. Both his account and his partner's admin account see the field type and checklist responses grayed out once saved. Tyler confirmed he has the same limitation on his end. The only workaround is deleting the field and creating a new one, which the user noted is impractical when variables are changing frequently. Tyler submitted a ticket to allow editing custom fields after the fact (00:09:48).

A user asked about the missing "push to leads" call outcome that existed in the 5.0 dialer. In the old version, a qualified list stacking record could be pushed directly to the acquisition pipeline through a disposition option. Tyler confirmed the feature is not available yet and walked through a workaround: create a custom call outcome called "Push to Leads," then after the session, sort by that outcome and manually push the matching records to the active pipeline (00:11:14).

The same user reported that the dialer does not distinguish between records that have already been called and those that have not, causing the team to re-dial the same numbers. Tyler demonstrated a filter workaround using "number of attempts by contact equals zero" to isolate uncalled records. He also noted that cold calling campaigns are being discussed internally and may return, which would provide a cleaner session-based workflow (00:13:47). A separate complaint addressed the triple-line dialer not displaying the seller's phone number during an active call. Tyler confirmed an update is in progress that will show the address, phone number, and name on the calling screen (00:14:59).

A user explained that in 5.0, his Zapier integration created multiple leads with the same property address and seller name but different phone numbers, allowing him to contact every number on file. In 6.0, the system rejects any lead with a duplicate property address. Anthony confirmed that the platform now enforces one lead entry per property address and noted a related bug where leads with no property address mapped are also flagged as duplicates because the system reads them all as "N/A." He added the user's case to an existing backend ticket (00:19:51).

Anthony briefly shared his screen to demonstrate an update shipped that day: the single-line dialer now displays the property address during a calling session, and the address is a clickable link that opens the full lead detail in a new tab. This was one of the most requested changes from the noon call. The update applies to the list stacking single-line dialer specifically (00:21:03).

A user demonstrated that eSign throws an error when loading, and another user confirmed the same issue in the chat. Tyler escalated it as urgent. Anthony noted he already had a ticket open from a separate user experiencing the identical error. Tyler confirmed eSign is being treated as a top priority alongside the advanced caller ID rollout (00:25:04).

A user described the standard calling workflow: make a call, send a follow-up text, complete the associated task, and review seller context, all from the dialer screen. In 6.0, the dialer does not offer a way to complete tasks inline or view the activity log without leaving the session and opening each lead individually. Tyler agreed this is a significant regression and confirmed tickets are open to bring back both inline task completion and the activity log panel from the old dialer. No timeline was provided, but the development team is on overtime prioritizing fixes (00:24:46).

A user showed that since the September 12 launch, all inbound calls are routing to his account regardless of which team member owns the lead. His call stats show hundreds of calls aggregated under his name while his reps show near-zero activity. Tyler confirmed this is a known issue tied to call flow handling since the migration.

The same user flagged that speed-to-lead texts are sending from the first phone number in the system (a personal line) instead of from the campaign number attached to the lead source. Neither Tyler nor Anthony had heard this specific complaint before, and Tyler created a ticket. The user categorized eSign as a P0 and these routing issues as P2 or P3 (00:30:34).

A user asked whether automations can be triggered by status changes on the dispo tab (the deal-specific buyer pipeline). Tyler confirmed this is not available yet but said he had pushed for it before launch and it is on the roadmap. The current priority is resolving existing bugs before adding new automation triggers (02:14:46).

The same user asked whether his web developer can access custom CSS and plugins on the REsimpli website builder. Anthony explained that 6.0 website templates use Elementor and noted that plugin access was limited even in 5.0. He said he would confirm with the backend team whether CSS and plugin access is available in the current version and follow up via email (02:16:00).

Tyler confirmed the team would be back Wednesday, September 17, at noon and 6:00 PM Eastern, with all issues raised in the session added to the developer queue overnight.