6.0 Office Hours - Oct 23

Automations can save you hours of repetitive work, but they still need to behave the way you expect. An SMS that goes out a day late, an AI agent that repeats itself, or a dialer that keeps calling the same prospects can quickly become a headache.
​

These were some of the issues Tyler Scott addressed during the October 23 REsimpli Office Hours.

Tyler demonstrated how to build follow-up sequences, use AI calling and direct mail in automations, and manage incoming seller responses. He also investigated problems with the Triple-Line Dialer, discussed improvements to Conversational AI, and reviewed requests for better lead data, saved views, and dead lead management.

The session was a mix of practical walkthroughs and product feedback, with several fixes and improvements still being worked on.

REsimpli 6.0 changed how standard calling and texting are included in its plans.

Previously, legacy plans came with a fixed number of calling minutes and SMS credits. Once those were used, investors had to purchase additional credits to continue.
​

Tyler explained that current 6.0 plans include unlimited standard calling and texting, removing the need to keep purchasing additional communication credits in the same way.
​

This makes it easier to budget for regular seller follow-up, although applicable usage policies and messaging requirements still matter.
​

Say you've mailed 5,000 absentee owners, and one calls back.
​

You recognize the phone number, but the new lead doesn't have a property address attached. Now you're asking the homeowner to repeat information you already have in List Stacking.
​

REsimpli 5.0 had a useful shortcut for this situation. When an incoming phone number matched a skip-traced record, users could hover over the number and copy the matching property information into the new lead.
​

Tyler tested the feature in both versions during the session.
​

It worked in 5.0 but wasn't available in the 6.0 workflow he tested.

He agreed to send the demonstration to the development team to investigate restoring it.

​Why it matters: Matching incoming calls against existing property records can save time and help your acquisitions team identify which property the seller is calling about.

This was a reported missing feature, not a confirmed fix.

Conversational AI is supposed to keep seller conversations moving naturally, but some investors had noticed that its responses weren't as consistent as before.

Examples included repeating appointment details, suggesting a slightly different time after the seller had already agreed, and failing to create an expected calendar appointment.

Tyler acknowledged these issues and explained that the team was auditing Conversational AI.

A revised version had undergone extensive testing, with adjustments intended to improve response quality and appointment handling.

He expected the update to be released around the following week, although that remained an estimate.

For now, it's worth reviewing conversations where the AI has been involved, especially when an appointment is supposed to be booked. Check that the agreed time is correct and the appointment appears on your calendar.

Imagine someone submits a lead form late at night. Your automation should acknowledge the inquiry, but the SMS falls outside the permitted sending window.

When will the message actually go out?

An attendee reported that a message had been delayed longer than expected.

Tyler explained that REsimpli had recently changed how automated messages are
handled outside the configured sending window.

Previously, some scheduled actions could be skipped. The updated behavior was intended to hold the message until the next eligible sending time instead.

The team was also reviewing whether certain consented inbound inquiries could receive immediate automated responses outside the usual window, subject to legal requirements.

​What to check: Review the scheduled actions on new leads that arrive after hours. If a message doesn't send at the next expected opportunity, capture the lead and automation details for support.

Tyler hadn't personally verified the reported issue after the update, so the session didn't establish that every timing problem was resolved.

A question came up about scheduling a one-time SMS blast for a future date and time.

Tyler explained that this capability had previously existed for buyer communications and was planned to return for both buyers and sellers.

Until that scheduling feature is available, use an appropriate automation when you need a timed sequence rather than sending a blast immediately.

The discussion also covered outbound AI cold calling.

Tyler clarified that AI calling directly through raw List Stacking cold-call campaigns wasn't available at the time. However, AI calling could be incorporated into workflows for existing leads through the relevant AI agents and automations.

When using these tools, follow the applicable calling, consent, and Do Not Call requirements.

What's the difference between Conversational AI and the upcoming autonomous AI lead manager?

​Conversational AI responds to incoming SMS conversations and works toward outcomes such as booking an appointment.

However, Tyler clarified that it doesn't independently manage every part of your lead pipeline. For example, if a seller asks to be contacted in three months, your team may still need to update the lead's status and arrange the appropriate follow-up.

The planned Autonomous Lead Manager is intended to handle more of that work, coordinating AI agents, updating pipeline stages, and managing future follow-ups.

Tyler described a system that could eventually take a seller's request, move the lead into long-term nurture, and schedule further contact without manual intervention.
That broader functionality was still being developed.

With several AI agents and automation options available, it isn't always obvious which tool to use.

Tyler shared two resources to simplify setup.

​The AI Handbook explains the individual agents, their use cases, and how to configure them. It includes tools such as Contact Intelligence, which prepares pre-call briefs and seller or buyer insights from previous interactions.

​The Automation Library contains examples of Tyler's and Sharad's workflows, including the actions, delays, and messages used in each sequence.

Tyler recommended choosing one set of automations as a starting point rather than copying everything and ending up with duplicate follow-up campaigns.

You can adapt the examples to your own acquisition process and follow-up schedule.

What happens after you've built a manual follow-up sequence?

Tyler demonstrated two ways to start it.

​Option 1: Add it manually. Open a lead, click the automation icon, select Add Automation, and choose the sequence you want to run.

​Option 2: Trigger it through a status change. Create a status-change automation that moves the lead into the appropriate Manual Assignment Automation.

For example, moving a seller into Can't Reach can trigger a sequence of follow-up calls, texts, and emails.

Once activated, the automation icon shows that the lead has an active sequence.

To monitor seller responses, use the Inbox, where incoming calls and messages
appear together. You can respond directly or open the associated lead record.

Not every seller responds to text messages. Some prefer a call, while others may respond to a piece of mail months later.

Tyler demonstrated how to include both AI calls and direct mail in REsimpli automations.

For AI calls, activate the appropriate outbound calling agent and add it as a step in
your follow-up sequence.

You can configure what happens when the seller answers or doesn't answer, including voicemail, follow-up actions, or appointment handling.

Tyler also confirmed that REsimpli no longer offered ringless voicemail in the
workflow being discussed. Instead, an unanswered AI call could leave a voicemail.

​Direct mail works as another automation step. For example, a long-term nurture sequence might send a text after 30 days, make an AI call later, and follow up with a physical mail piece.

It's a way to maintain contact over time without relying on one communication channel.

REsimpli offers different AI agents for different parts of the lead management process.

Tyler explained some of the most relevant options:

The broader AI Lead Manager package combines multiple capabilities, while individual agents can be activated based on the workflow you need.

For example, a business generating most of its leads through PPC or pay-per-lead campaigns may benefit from using an inbound AI agent as backup when team members can't answer calls.

Tyler also demonstrated how Deal Intelligence can populate useful information from conversations, allowing investors to filter leads by details such as seller timeline, property condition, and asking price.

Different teams need different information from the same lead database.

An acquisition manager may want to see seller motivation, property details, and appointment status. A transaction coordinator may care more about contract dates, title issues, and closing information.

REsimpli allows users to customize which columns appear in List View and change their order.

But an attendee wanted to save several column layouts and switch between them without manually selecting the fields every time.

Tyler confirmed that saved column configurations weren't available at the time and agreed to follow up on the feature request.

He also mentioned using REsimpli's API and Claude to build separate reporting dashboards as a possible alternative, although that isn't the same as saving native CRM column views.

Dead lead reasons become especially important when you're using them to trigger automations.

Suppose your team has predefined reasons such as Sold, Not Interested, or Outside Buying Area. Each reason may connect to a different workflow.

If team members create new reasons freely or leave the field blank, those workflows can break down.

An attendee requested three improvements:

Tyler agreed that these would help teams maintain cleaner records.

At the time, he wasn't aware of a direct way to edit a previously selected reason. The workaround he described was to move the lead back to an active status and then return it to Dead Leads with the correct reason.

These changes were feature requests, not existing settings.

What if you select 3,000 records for a calling campaign, but only a fraction appears in the Triple-Line Dialer?

An attendee reported this problem, along with the dialer repeatedly calling prospects who had already been contacted.

Tyler demonstrated how to use phone status and last call outcome filters to exclude records that shouldn't be called again.

For example, you can filter out DNC records, wrong numbers, and relevant dispositions before starting another campaign.

However, those filters didn't explain the reported reduction in eligible contacts.

Tyler tested the behavior and observed a 250-record limit in the dialer. He agreed to
raise the issue with the development team.

As a temporary workaround, he suggested dividing a large list into smaller batches, tagging each batch, and working through them separately.

For example, call the first 250 records, record their outcomes, then move to the next tagged batch.

This wasn't presented as an ideal solution, just a way to keep prospecting while the issue was investigated.

A property record may contain multiple owners or phone numbers, but the primary contact isn't always the person you need to reach.

Sometimes the primary number is a landline or has no useful contact information, while a secondary contact has a mobile number.
​

An attendee reported that List Stacking SMS workflows were only using the primary contact, leaving other numbers unused.
​

Tyler explained that the team had been discussing improvements to allow more flexible outreach across the phone numbers associated with a property.

The proposed behavior would include eligible mobile numbers rather than automatically relying on the primary contact alone.

That functionality was still being requested during the session. Any broader outreach should continue to respect consent, opt-outs, and applicable messaging restrictions.

Keep your dialing lists clean. Filter previous call outcomes and DNC records, and verify which contacts are eligible before starting another Triple-Line Dialer session.