The reason this is important is that the integration will retroactively populate Sisu's Lead Source counts for your leads. It's not a deal breaker if your leads weren't imported into Lofty correctly, but this functionality will be diminished if it isn't being driven off the original Reg Date and Source for each lead in Lofty.

The integration relies on matching each Lofty user to a Sisu user via their Email Address (not their Alternate Email Address). Without this matching, the integration won't work for that user - and that includes the integration's "ISA" functionality (discussed in the videos).

The reason this is important is to prevent any unwanted tasks or emails from occurring via a Task List getting triggered during the integration go-live process. The initial integration synchronization can sometimes add appointment information to your existing Sisu transactions (assuming that information is missing on a Sisu transaction and the integration finds an appropriate Lofty appointment on the Lofty lead to utilize).

As soon as the integration is turned on, you can add the "Appt Set (status)" and "Appt Met (status)" triggers back to any necessary task lists again if desired.

The reason this is important is that on your integration go-live night, we will try to uniquely match your existing Sisu transactions to Lofty leads (and possibly match or create Lofty transactions as well). Our matching process is driven by multiple data points (such as first name, last name, phone number, etc.) but to ensure the best chances of each Sisu transaction uniquely matching a Lofty lead, please make sure each Sisu transaction has a "Contact Email" filled out that exactly matches to only one Lofty lead's email address respectively.

Any Lofty transactions that created or matched against (and therefore become linked and managed via the integration) will have "[Linked to Sisu]" appended to their name. For example, "123 Main St, Aspen, CO 12345 [Linked to Sisu]". These are transactions that you don't want to delete in Lofty since the integration will be managing them.

During the go-live, if necessary, we will give you a Sisu transaction matching report that will show your matched Sisu transactions along with your unmatched Sisu transactions and why they couldn't be matched.

If a current Sisu transaction doesn't match a Lofty lead, it simply means it won't show up when you look at that Lofty lead's bridge page and it won't get updated via the integration. Depending on the nature of the transaction, this can be a relatively minor thing and generally, teams don't worry too much about the few Sisu transactions that might not have been matched. However, if desired, you can make adjustments so that we can uniquely make a match to a Lofty lead and we can rerun the matching process if requested.