Introduction to Sisu and BoomTown

In partnership with BoomTown, we are excited to announce our direct Sisu integration.

Here is a quick high level overview of the benefits and features of Sisu and having your BoomTown CRM "talking" to Sisu.

Overview, highlights, and key features

Here is an introduction video on the integration and configuration overview. In addition to watching this video, please make sure to read all the information below, in detail, and watch the additional videos below.


  • The integration is designed to run only from the time that you have turned on the integration and NOT pull historical data from BoomTown.
  • Turn off other integrations. If you are currently using a third-party provider in conjunction with Sisu and BoomTown (i.e. Real Synch, API Nation, or Zapier), please disable any integration(s) that may affect your live data. The video below walks you through how to deactivate the likely integrations that you may have in place between Sisu and BoomTown.


  • The integration runs automatically every five minutes, however, a Sisu Admin or TC can run the sync on-demand with the "Run Now" button.
  • If a BoomTown client record was used to create a Sisu transaction through this sync, your Sisu users can open the BoomTown client record directly from Sisu.
  • The integration is designed (unless specified below) to do a one-time Sisu transaction creation from BoomTown client record data. There will not be any BoomTown lead record syncing with the Sisu transaction record (i.e. updating the phone number on the BoomTown lead record will not update the Sisu transaction record).
  • If you specify that you want BoomTown transaction records to be created when Sisu transactions go "Under Contract", the Sisu transaction will be the primary record source for the BoomTown transaction. Your users will make all of their updates to the Sisu transaction which will automatically keep the BoomTown transaction record in sync (i.e. date changes, transaction amount changes will be made in Sisu and pushed to BoomTown).
  • The integration setup has to be performed by a Sisu and BoomTown Administrator.
  • After setup, and to ensure your Activities are accurate, your Sisu configuration will have the following Activities LOCKED. These Activities can only be modified through BoomTown usage.
  • To ensure that your Conversations and Dial metrics are valuable on your team and personal dashboards, leaderboards and in your Sisu Production & Activity, Agent Accountability, Performance & Conversion reporting, BoomTown Dials will automatically add to Sisu's NUMBER OF DIALS core system activity and BoomTown Conversations will automatically add to Sisu's NUMBER OF DIALS and CONVERSATIONS core activities.
  • We have greatly simplified the authentication between Sisu and BoomTown. Your User - Agents table in BoomTown will automatically remain in sync with your Sisu users. The best practice is to add your user to BoomTown first which will automatically add users directly into Sisu. For your existing Agent lead roster in BoomTown, they will initially come over to Sisu as "Active" users and you can manually make any of the users "Inactive". This process could take up to 5 minutes to sync. For Sisu licensing purposes you will need to ensure that you have a Sisu license for each active BoomTown user.
  • Stay in the loop with the BoomTown Logs table. See in real-time what is going on with your BoomTown and Sisu sync.

What the BoomTown and Sisu integration currently DOESN'T do

In an effort to rapidly release this first version of the integration to address the majority of concerns and requirements our BoomTown and Sisu customers had with prior integrations, we weren't able to fit everything into this initial release. After the initial release of this integration, we will be quickly working on the following:

  1. Automated lead source reporting: Automating the total Agent Lead Count and Total Lead Count from your BoomTown agent assignment and reassignment, per lead source is vital and a top priority for the next release. This will ensure that your Lead Source ROI and Lead Sources by Agent reports are automated and accurate.
  2. Support for ISA functions and roles: Although BoomTown doesn't distinguish an ISA role or function, Sisu does provide powerful functionality for your ISA team members. Being that we know who the logged-in user in BoomTown is (i.e. the ISA team member who is setting the To-Do type of "Meeting"), and we know the ISA role this user is assigned to in Sisu (and since we maintain an active sync between the BoomTown user table and Sisu users), it will be easy to segment this process and associate the ISA who sets the To-Do "Meeting" in BoomTown to our ISA metrics in Sisu.

Getting started

Let us know that you want us to turn on the BoomTown integration in your Sisu Automation Hub by shooting us a chat.

Connecting Sisu and BoomTown

Setting up Sisu and BoomTown the first time is a snap. Here are the highlights of the setup:

Configuring your Sisu and BoomTown integration and running your initial sync with BoomTown

Configuring you Sisu and BoomTown integration is easy. Make sure you regularly check the embedded Sisu video for configuration and setup updates (click on the exclamation point for the most recent configuration video).

Strategies on your initial synchronization

Garbage In... Garbage Out... The data in Sisu will only be as good as your data and configuration in BoomTown. If you have been lax in the management of your BoomTown platform - then you run the risk of corrupting your existing Sisu production data (if you are an existing Sisu customer) or new Sisu production data (if you are a new Sisu customer). Here are some great strategies to follow on your initial synchronization with BoomTown.

Setting and reviewing your BoomTown categories prior to your initial sync: The creation of Sisu PIPELINE transactions trigger off of the current BoomTown Categories settings you determine in Sisu and the current category of the BoomTown lead. For example, if you have a lot of inaccurate BoomTown "Hot" category leads even going back many years, running an initial sync would automatically add Sisu transactions for any leads in those categories if you have the CREATE SISU TRANSACTION ON: "BoomTown Category is 'hot'.

Check out this helpful video on running your initial sync and ensuring your BoomTown data is updated.

Monitoring your Sisu and BoomTown integration

At least initially, we recommend creating a couple of saved transaction filters to monitor your BoomTown and Sisu integration. The video below walks you through how to setup these specific transaction filters from your Sisu transaction filter drawer.

How do I select multiple options in my configuration screen

If you have never used a multi-select selection screen in other systems, it is really easy to select multiple items by using Command + Mouse Click (in Mac OS), Control + Mouse Click (in Windows), or Control + Mouse Click (in Chrome OS).

Understanding the BoomTown logs

The BoomTown Logs screen provides real-time sync information for your BoomTown and Sisu Admins and TC's. This will assist you during ongoing usage when BoomTown users have questions about records and activities syncing. Our Sisu Customer Success team will leverage this for troubleshooting as well.


Manually running the sync and clearing your BoomTown logs

The integration runs automatically every five minutes, however, a Sisu Admin or TC can run the sync on-demand with the "Run Now" button.

Additionally, the "Clear Logs" button allows you to always ensure that you are seeing the most up-to-date information regarding your BoomTown sync.

What Sisu custom activities are created on integration setup?

To ensure lead measure metric accuracy upon setup of the integration, we will automatically create the following Sisu Custom Activities:

This ensures that the only way these activities can be updated by your agents is through their BoomTown usage. By default, these activities are set to display (checked) and are LOCKED.

Where are my custom activities in the record screen?

Being that these Custom Activities cannot be manually updated, and can only be updated through BoomTown usage, they will not display in the Record screen for your agents.

These Custom Activities will be available in the following:

Leaderboards

Team and personal dashboards

Agent and team activity logs
Check out this video below.





Team and personal snapshot displays

Goal setup

Goal display


How can I disable my BoomTown sync?

At any time, you can disable the integration between Sisu and BoomTown with the "Disable" button. You also have a visual prompt indicating the integration's status: Enabled or Disabled.

Logging dials, emails, and texts in BoomTown

Do you want dials, manual and drip emails, and manual and drip texts to only count for prospecting efforts (vs. counting them on any contact in BoomTown)? If so, you can limit the updating of Sisu Activities to only BoomTown Active Lead Categories ("New", "Qualify", "Watch", "Nurture", "Hot") rather than Non-Active Lead Categories ("Pending", "Closed", "Archive", "Trash"). We provide the ability to customize this based on your business processes:

BoomTown category definitions

Sisu Automation Hub configuration for Sisu custom activities

The integration will update corresponding Sisu Custom and Sisu Core Activities when the following BoomTown activities are created:

BoomTown activity

Updates these Sisu custom activities

Also updates these Sisu core activities

Talked to Prospect

BOOMTOWN CONVERSATIONS and BOOMTOWN DIALS

CONVERSATIONS and NUMBER OF DIALS

Left Message

BOOMTOWN DIALS

NUMBER OF DIALS

Call Attempt

BOOMTOWN DIALS

NUMBER OF DIALS

Opted Out

BOOMTOWN DIALS

NUMBER OF DIALS

Wrong Number

BOOMTOWN DIALS

NUMBER OF DIALS

Sending a BoomTown email

BOOMTOWN EMAILS

N/A

BoomTown drip email

BOOMTOWN EMAILS

N/A

Sending a BoomTown text

BOOMTOWN TEXTS

N/A

BoomTown drip test

BOOMTOWN TEXTS

N/A

Why do we add to CONVERSATIONS and NUMBER OF DIALS?

Conversations and Number of Dials are core Sisu activities that drive additional functionality throughout the Sisu platform. Additionally, by having specific activities for BoomTown, we provide valuable optics for you and your team on your BoomTown usage in isolation. Then, rolling these numbers up appropriately to the Sisu core system activities allows you to fully leverage the following Sisu reports:

Production & activity reporting

Agent accountability reporting

Performance & conversion

Here is a quick video overview:

Creating Sisu transactions from BoomTown category changes

Sisu allows you to set multiple BoomTown categories to trigger the creation of your Sisu transactions.

A few items to highlight:

  • Unless designated below, the Sisu transaction creation from BoomTown is intentionally designed to be a one-way push of BoomTown client record data to Sisu.
  • For Buyer/Seller transactions in BoomTown, the sync will create TWO Sisu transactions: One for the Buyer side and one for the Seller side.
  • Check out this video for a detailed walkthrough:

What Sisu transaction information is initially added from BoomTown category changes and/or To Do "Meeting" creation?

Unless specified below, the sync is designed to be a one-time push of the following BoomTown client information to create the Sisu transaction:

From BoomTown client→

To Sisu transaction:

When:

First

FIRST NAME

One time creation on initial submission

Last

LAST NAME

One time creation on initial submission

Buyer Agent or Listing Agent (designated by B, S, or B/S)

AGENT

One time creation on initial submission. For B/S transactions, a unique Sisu transaction will be created for the Buyer side and one for the Listing side (possibly two different agents).

Phone

MOBILE PHONE NUMBER

One time creation on initial submission

Email Address

CONTACT EMAIL

One time creation on initial submission

"Hot" Category

Sets the Sisu status to "PIPELINE" (meaning no other dates have been populated)

One time creation on initial submission

Source

LEAD SOURCE

One time creation on initial submission

To-Do of "Meeting" (Date Set)

1ST TIME APPT SET date is populated based on the creation date of the BoomTown To-Do "Meeting". This causes the Sisu status to be "APPT SET"

Can occur anytime after the transaction is created in Sisu from BoomTown. Only the first To-Do "Meeting" creation date will populate the 1ST TIME APPT SET date in the Sisu Transaction, regardless of the number of subsequent To-Do "Meetings" that are created in BoomTown for that client record.

The completion of the To-Do of "Meeting" (Date Set)

1ST TIME APPT MET date is populated based on the completed date for the To-Do "Meeting". This causes the Sisu status to be "APPT MET"

Can occur anytime after the transaction is created in Sisu from BoomTown. Only the first To-Do "Meeting" completed date will populate the 1ST TIME APPT MET date in the Sisu Transaction, regardless of the number of subsequent To-Do "Meetings" that are created in BoomTown for that client record.

Registered (date of the lead registration)

Lead Date

One time creation on initial submission

Viewing BoomTown custom activity logs from the team and personal dashboards

Ensuring that you and your team alway know when and who created your BoomTown Custom Activities is an important query for you to run from the team and personal dashboards.

Here is a quick overview:


Opening BoomTown client records directly from Sisu

We make it easy to access your BoomTown client records directly from Sisu after the transaction is created from a BoomTown category change ("Hot" or "Pending") or after a BoomTown "Meeting" To-Do item is created (and thus the Sisu transaction would be in the "APPT SET" status).

Here is a quick overview:

Creating the initial Sisu transactions and setting the Appointment Set and Appointment Met from BoomTown To-Do "Meeting" type

Adding the 1ST TIME APPT SET date and 1ST TIME APPT MET date in Sisu from BoomTown is simple. A couple of highlights to ensure you have everything set up correctly:

  • To create the Sisu transaction from a BoomTown To-Do of "Meeting", make sure you have "BoomTown todo: meeting created" as one of your Sisu transaction creation settings:
  • The Agent that is assigned on the BoomTown lead record will get credited for the Appointment Set and the Appointment Met. Support for ISA functions through this sync will be coming in the next release.

Here is a quick overview:


Setting appointments on any transaction that was created from the BoomTown and Sisu sync

For those "Hot" BoomTown Category changes that created a Sisu transaction, your agents can still set the 1ST TIME APPT SET and 1ST TIME APPT MET Sisu dates directly from BoomTown by using the "Meeting" To-Do type.

For example, if you have other procedures of when to move BoomTown clients into Sisu, but you still want to motivate your agents to set appointments within BoomTown, the video below walks you through how to accommodate for this. Regardless of the number of To-Do "Meetings" that were set on your BoomTown client record, Sisu will only populate the 1ST TIME APPT SET and 1ST TIME APPT MET dates once - i.e. the first time.

Automatically updating BoomTown categories on Sisu transaction status changes

Keeping your BoomTown categories in sync with Sisu is vital to ensure your CRM stays the primary source of record for your clients.

Update your BoomTown categories on Sisu "Under Contract", "Closed", and/or "Deletes" status changes.

Here is a quick video overview:

Creating BoomTown transactions from Sisu transactions

Creating BoomTown transactions from Sisu transactions provides a wealth of historical information for you and your team, greatly eliminates duplicate entry, and provides an automated way to ensure that you can quickly submit your BoomTown transactions to Dotloop or other contract generation and compliance solutions.

To ensure that you are creating the initial BoomTown transaction from Sisu, make sure that you have turned on the "CREATE BOOMTOWN TRANSACTION WHEN:" setting to create a BoomTown Transaction when a Sisu transaction goes "Under Contract"

A few automatic and time-saving steps we provide on the BoomTown Transaction creation:

  • Automatically changes the BoomTown Transaction status to Under Contract
  • When Sisu Transactions are Closed, we automatically change the BoomTown Transaction status to Closed
  • If you have set the "SET BOOMTOWN CATEGORY ON SISU TRANSACTION STATUS CHANGE:" to "Sisu Under Contract is BoomTown Pending" and "Sisu Closed is BoomTown Close" setting we will update the BoomTown Categories. This setting does not require that you use the "CREATE BOOMTOWN TRANSACTION WHEN:" setting and can be used independently if you do not want to create BoomTown Transactions from Sisu Transactions when they go Under Contract in Sisu.

Best practices to keep BoomTown transactions up to date

The majority of Sisu customers thoroughly use Sisu transaction management functionality as their core system of record. Largely, in part:


This being said, the current design of how Sisu interacts with the BoomTown Transaction records is a ONE-WAY, continuous update of Sisu transaction information to the corresponding BoomTown transaction record. Changes in the BoomTown transaction will be overwritten by the Sisu transaction.

A recommended process for your TC's and Agents who interact with the Sisu transaction before and after it is locked, is to make all updates to the Sisu transaction in order to automatically keep the BoomTown transaction information up-to-date for historical review from BoomTown and/or Dotloop or other document generation/compliance updates.

What BoomTown transaction information is updated initially and ongoing from the Sisu transaction?

The sync is designed to update BoomTown transactions from the creation of the Sisu transactions and ongoing updates in the Sisu transaction. Changes made in the BoomTown transactions will not be reflected in the Sisu transactions upon saving and will be overwritten from Sisu with ongoing transaction syncs. Required BoomTown and Sisu fields are indicated below with an asterisk:

From Sisu Transaction →

To BoomTown Transaction:

STATUS (Under Contract, Closed)

Status * (UNDER CONTRACT, CLOSED)

AGENT *

Agent

TRANSACTION TYPE * (Buyer, Seller)

Representing * (Buyer, Seller)

ADDRESS LINE 1

Address *

CITY

City *

STATE

State *

POSTAL CODE

Zip

TRANSACTION AMOUNT

Price *

GCI

Gross Commission Income

GROSS AGENT(S) PAID INCOME

Agent Split

UNDER CONTRACT DATE

Acceptance Date

CLOSED (SETTLEMENT) DATE

Closing Date

This video provides a detailed walkthrough of creating BoomTown transactions from Sisu transactions and updating Sisu transactions and having those changes reflected in the BoomTown transaction:

Creating dual-sided (Buy/Sell) transactions from BoomTown and how to create BoomTown transactions from these dual side Sisu transactions

We understand that your dual-sided transactions will move through your sales cycle at a very different pace. Both Sisu and BoomTown can easily accommodate this part of your business.

For those dual-sided transactions in BoomTown, the sync will create two separate transactions in Sisu when you set the BoomTown Category change - one for the buyer side and one for the seller side.

This also accommodates the possibility that different agents may handle the buyer side and listing side since there is one transaction per side in Sisu.

If you have the the "CREATE BOOMTOWN TRANSACTION WHEN: Sisu goes Under Contract" setting turned on in your configuration, we will create a distinct BoomTown transaction record for each Sisu transaction when it goes Under Contract, and we will ensure that updates to each Sisu transaction get pushed to the corresponding BoomTown transaction (i.e. pricing, GCI, agent paid income changes and setting the BoomTown transaction status to "Closed" on Sisu CLOSED status change).

This detailed video provides a great overview:

Did this answer your question?