Overview
On Wednesday, September 23, 2026, Tyler Scott hosted the noon office hours call solo, with developer Anthony handling Zapier and API questions in a breakout room. Sharad Mehta was off the call but responding to escalations in the background.
A user on the 15-user Legacy plan was blocked from uploading list stacking records despite having unlimited list stacking; Tyler escalated the issue to Sharad, who began investigating during the call.
A feature request was discussed for auto-pulling list stacking custom fields, such as offer amounts from check mailers, into lead records when a seller calls in, along with restoring the list stacking link indicator that existed in 5.0.
The acquisition manager dashboard's calls-made count only reflects outgoing calls, creating a discrepancy with the communication logs total that includes both directions; a combined total calls metric is coming soon.
Tyler recommended all users review the per-number inbox visibility setting under their phone numbers to control which team members see incoming communications for each line.
Buyer web form inquiries are creating new buyer entries in the dispo tab, but the actual question text submitted by the buyer is not transferring into the record.
The A2P compliance prompt forcing users to re-enter company information on every manual text in list stacking was confirmed as a known issue affecting Tyler's own account as well, with a ticket actively being worked.
The call closed with Tyler noting the evening session would resume at 6:00 PM Pacific.
00:03:31 A Legacy plan user is incorrectly blocked from uploading list stacking records
A user on the 15-user Legacy plan, who routinely uploads 16,000 to 18,000 records per week into a list stacking database of over 500,000 records, received an error telling him to upgrade. A support rep confirmed the limit was being enforced, contradicting the user's understanding that the Legacy plan includes unlimited list stacking. Tyler messaged Sharad and the team directly during the call, and Sharad began checking the account in real time (00:10:42).
The user also mentioned that in previous uploads, he stored offer amounts in the notes field as a workaround, since there was no dedicated custom field for that data. With 6.0 now supporting custom fields in list stacking, he wanted to explore using them but had concerns about whether the data would follow the lead downstream.
00:05:42 List stacking custom fields do not carry over to leads created by incoming calls
The same user explained that his team mails check letters with unique offer amounts per property. When a seller calls in, the incoming call creates a new lead record, but the offer amount and other list stacking custom fields do not transfer. The person answering the phone has to pause, search list stacking manually, and look up the offer before confirming it with the seller.
Tyler ticketed the request to display list stacking custom fields on the lead detail screen when a matching address exists (00:09:04). For offer history across multiple mailings, Tyler suggested creating separate custom fields like "Offer 1," "Offer 2," each with a date, since re-uploading the same field overwrites the previous value. The user also noted that the 5.0 indicator showing whether a lead existed in list stacking is missing from 6.0, and Tyler agreed it should come back (00:10:00).
00:11:09 The acquisition manager dashboard undercounts calls because it only tracks outgoing
A user shared his screen showing the acquisition manager dashboard filtered for a single team member on a specific day. The calls-made count and total talk time were significantly lower than what appeared in the communication logs. Tyler explained that the dashboard currently counts only outgoing calls, while the communication logs include both inbound and outbound, which explains the gap. A total calls metric that combines both directions is planned for the dashboard soon (00:12:33).
Tyler also mentioned discovering the same discrepancy with his own lead manager the previous day and using the communication logs as the more complete data source in the interim.
00:25:45 Per-number inbox visibility settings control which team members see incoming messages
Tyler walked through the phone number settings and recommended all users audit which team members are selected to view incoming communications for each number. He shared his own example of toggling off his acquisition manager and lead manager from list stacking SMS numbers so only the VA who handles those responses sees the notifications. This reduces inbox clutter for team members who do not need to see cold outreach replies (00:26:40).
A related issue surfaced where buyer web form inquiries were creating new buyer records in the dispo tab, but the question text submitted through the form was not populating on the record. Tyler had not seen the issue before and ticketed it for investigation (00:27:00).
00:29:01 A2P compliance re-prompts on every manual text in list stacking
A user demonstrated on screen that after sending an initial bulk SMS with the required A2P company identification, attempting to reply manually to a seller's response forces him to re-enter the company name and compliance information. Tyler confirmed the issue exists on his own account as well and that a ticket is already in progress. The bug is specific to manual texting in list stacking; automated SMS sent through drip campaigns does not re-prompt (00:30:07). The workaround for now is re-entering the compliance text each time.