6.0 Office Hours - Oct 21

Moving years of leads into a new CRM takes more than uploading a spreadsheet. You need to preserve your pipeline stages, marketing sources, follow-up sequences, and buyer relationships without losing track of the people you're already working with.

That was one of the main discussions during the October 21 REsimpli Office Hours, hosted by Tyler Scott.
​

Tyler explained how to organize imported leads, build reusable automations, and handle dispo offers coming through your buyer website. He also demonstrated how Claude can help with tasks such as formatting spreadsheets, building automations, and customizing websites.
​

The session highlighted several improvements still in development, including automation pause controls, more useful offer notifications, and an autonomous AI lead manager.
​

Migrating thousands of records can get complicated, particularly when those leads belong to different pipelines, statuses, and marketing campaigns.
​

Tyler recommended separating the data based on how the leads are currently being used.

Active Leads is where you should import sellers you're already working with, including verified contacts and prospects enrolled in long-term follow-up.
​

List Stacking is better suited for raw property data, cold prospecting lists, and records you haven't contacted or verified.
​

REsimpli 6.0 supports bulk importing directly into Active Leads, but the session exposed a limitation: the import process required users to select particular pipeline, status, and campaign values rather than automatically matching every row to its corresponding value.

For a database spanning several years, that could mean splitting records into many separate spreadsheets.
​

Tyler agreed this needed improvement and recommended contacting the onboarding team for assistance rather than spending days manually organizing the files.

Practical tip: Start by separating active leads from raw prospecting data. For complicated migrations, work with REsimpli support to preserve your existing lead information, statuses, and marketing history.
​

What if you've just moved into REsimpli 6.0 and your Automations section is empty?
​

Tyler shared an automation library containing examples from his own account and Sharad's, including the triggers, actions, delays, and message content.

The library can be used as a reference when building your workflows.
​

At the time of this session, REsimpli 6.0 didn't have a pause or draft toggle for active automations. That made it difficult to copy an entire library of trigger-based automations into another account without risking unintended actions.
​

Tyler explained that pause/publish controls were being developed, with broader automation sharing and a possible marketplace planned for the future.
​

In the meantime, he recommended starting with a handful of essential workflows rather than trying to automate every possible situation.
​

A useful approach is to separate your follow-up sequences from the events that trigger them.
​

For example, create a Can't Reach sequence under Manual Assignment Automations, complete with the messages, delays, and other actions you want.
​

Then create a status-change automation that moves leads into that sequence when their status changes to Can't Reach.
​

You can use the same structure for long-term nurture, appointment follow-ups, and other recurring workflows.
​

This gives you one sequence to maintain rather than several copies of the same messages.
​

Tyler also demonstrated how to find leads without an active automation or follow-up task and enroll them back into an appropriate sequence.
​

It's worth checking those records regularly. A reply or incoming call can interrupt an existing automation, leaving a lead without its next scheduled action.
​

The discussion turned to a common question: How should you handle a verified seller contact who hasn't explicitly opted in to automated text messages?

Tyler explained how REsimpli adds opt-out language to initial outbound texts and uses A2P 10DLC registration for business messaging.
​

However, A2P registration and opt-out instructions don't automatically establish legal permission to send marketing texts. Consent requirements depend on the type of outreach, applicable laws, and carrier rules.
​

Before enrolling cold prospects in SMS automations, make sure your outreach meets the relevant consent and messaging requirements. An accurate phone number alone isn't evidence that the owner agreed to receive marketing messages.
​

Imagine hosting an investor open house and asking buyers to submit their highest and best offers through your dispo website.
​

Offers start coming in, but there's no clear notification showing which buyer submitted an offer, for which property, or for how much.
​

An attendee reported running into exactly that problem.
​

Tyler reviewed the Dispo Tab and found that the available notification settings included multiple-offer alerts but lacked a straightforward alert for every individual offer.

New buyer inquiries and offers could also appear together, requiring users to search through the records and manually move buyers into the appropriate offer stage.
​

Tyler agreed that submitting an offer should trigger a more useful notification and place the buyer in the correct stage automatically.
​

He committed to discussing these changes with Sharad and the development team.

Current limitation: These improvements were requested during the session, not demonstrated as released functionality.

Once you've accepted a buyer's offer, you need the transaction coordinator to know who's buying the property and what they've agreed to pay.

Tyler demonstrated how to move a buyer into the Accepted Offers stage inside the property's Dispo Tab.
​

The existing offer information can populate the acceptance details, and the accepted buyer remains linked to the property.
​

You can then open the buyer record, review the associated deal, and send an assignment agreement through REsimpli's eSign functionality.
​

Tyler also showed how buyer records could be filtered by previous offer activity.
​

The session highlighted an opportunity to make this information easier to find directly from the transaction pipeline, without navigating through several screens.
​

REsimpli supports automations based on buyer pipeline changes, but Tyler confirmed that the stages inside an individual property's Dispo Tab didn't yet offer the same automation triggers.
​

For example, moving a buyer into Offers Received couldn't directly trigger a Dispo Tab automation that automatically marked them as a VIP or started a follow-up sequence.
​

Tyler discussed adding those capabilities in a future update.
​

For now, users can build automations around the broader Buyers pipeline, including moving buyers between stages and triggering the corresponding follow-ups.
​

One of the more practical discussions involved using Claude to handle repetitive account setup.
​

An attendee demonstrated a redesigned dispo website built using Claude and a WordPress child theme, while keeping the REsimpli-connected listing functionality intact.
​

Tyler then demonstrated how Claude could navigate his REsimpli account and begin setting up an automation through browser interaction.
​

The same approach can help with:

Tyler recommended testing AI-assisted imports on a small sample, such as ten leads, before applying the changes to an entire database.
​

The same caution applies to automations and website changes: review what the assistant creates before enabling workflows or publishing changes.
​

Tyler closed with an update on REsimpli's autonomous AI lead manager.
​

Unlike an assistant that simply responds to individual questions, the planned system is intended to carry out more of a lead manager's workflow, including following up with prospects and moving them between pipeline stages.
​

Because those actions directly affect live leads, Tyler explained that the feature was still being tested.
​

A limited beta was being planned for selected users, but the autonomous lead manager hadn't launched at the time of the session.
​