Overview
On Monday, September 28, 2026, Sharad Mehta hosted the office hours call with Tyler Scott handling tickets in the background, covering automation design boundaries, file upload limitations, list stacking import failures, and inbox visibility issues.
Lead and transaction automations are intentionally kept separate; a tag added from a transaction will not trigger a lead automation, by design.
File uploads for .MOV videos and certain JPEG images are not rendering in the system; a ticket was created to expand supported file types.
The Open API rate limit was increased from 100 to 500 requests, and webhook limits can be raised from 1 to 10 on request.
A user's list stacking bulk uploads of 14,000 records were failing silently, showing 100% new records when roughly 30% should have been duplicates, with tags not applying.
Inbox visibility mismatches between the account owner and an acquisition manager were traced back to lead assignment gaps.
Appointment calendar suggestions included color-coding entries by pipeline stage and allowing status changes directly from the appointment pop-up.
A2P opt-out language is required only on one-to-one messages, not on bulk SMS campaigns from list stacking.
The call closed with a reminder about the Tuesday basic setup webinar and the Thursday Open API guest webinar, both on separate webinar links.
00:02:40 Lead and transaction automations are separated by design, and file upload types need expanding
A user asked about triggering a lead automation from a transaction tag, specifically to route deals in renegotiation or fallout back to the correct lead pipeline stage. Sharad confirmed that the two automation engines are deliberately isolated so that tags in transactions do not accidentally fire lead-side workflows. He suggested sending a Loom video detailing the desired flow so the team can evaluate whether a cross-trigger option makes sense.
The same user raised a recurring problem with file uploads: .MOV videos and JPEG images uploaded by contractors are not rendering or downloadable within REsimpli (00:04:07). Sharad created a ticket to add .MOV and JPEG support and asked the team to audit commonly used phone-native file types including HEIC.
00:07:01 The Open API rate limit doubled to 500, and webhook limits can be raised to 10
A user reported being stuck at a single webhook, which Sharad said he would increase to 10 by the next day. The Open API rate limit was also raised from 100 to 500 requests, either that day or the next. These increases are available on request and are not automatic for all accounts.
00:08:18 List stacking bulk uploads are failing silently for at least one user
A user who uploads 12,000 to 15,000 records weekly described three consecutive upload failures. The import log showed the files as successfully processed with 100% new records, but searches for the applied tags returned zero results, and existing records that should have been updated with new offer amounts were not.
Sharad checked the import log, confirmed the issue looked like a back-end processing failure, and escalated it. He also noted a known issue from the previous week where custom fields were not mapping during uploads, which had since been fixed separately.
00:29:00 Inbox visibility differences between owner and acquisition manager stem from lead assignment
An account owner and his acquisition manager were both filtering the inbox by "Sellers Only," but the AM was not seeing any of the same messages. Sharad logged into the account and found the AM was not assigned to the leads in question. He walked the owner through adding the AM to the correct phone number's visibility settings and confirmed that lead assignment controls inbox access.
The call also covered calendar appointment improvements. One user suggested color-coding appointments by the pipeline stage the lead is in, and another asked for the ability to change a lead's status directly from the appointment pop-up without opening the full lead detail screen (00:28:37). Sharad added both to the roadmap.
02:03:38 Bulk SMS campaigns from list stacking do not require A2P opt-out language
A new user who had just received A2P approval was unsure whether to include opt-out language in list stacking SMS blasts. Sharad clarified that the "Reply STOP to opt out" language is only enforced on one-to-one messages sent through automations or manual texting, not on bulk campaigns. He recommended starting with a small sample of 10 to 50 leads to learn the system and build a process around the replies before scaling up.