Tag Based Integration

What is our tag based integration and how to use it!

Mihir Lodhavia avatar
Written by Mihir Lodhavia
Updated over a week ago

Our tag-based integration works the same as previous tag-based integrations but with one major difference. Since it’s tied to the embedded app we’re not searching for Sisu transactions by the contact’s email address. We’re updating the Sisu transaction that is tied to the embedded app opportunity tile, so no more duplicates or uncertainty.

The embedded app also provides a secondary option for syncing transactions so no more one buyer and one seller transaction per contact limitation. The tag-based integration comes with the Single-Click Embedded App by default but can also be used with the Simple Form Embedded App. Watch a demo here.

Important Considerations

  • This integration will ONLY work if the user's name in FUB matches the user's name in Sisu. For example, if the user's name were "Zac Muir" in FUB and "Zachary Muir" in Sisu, nothing will come over.

  • The integration will only work for 1 deal at a time for a contact. The tag symbol in our embedded app would indicate which deal would get updated if a relevant tag is applied.

ISA Sync

This type does NOT track appointments being set by ISAs and push that information to Sisu by itself. Creating the appointment using our normal type embedded app and webforms can track ISAs and update the Appt Set By field in Sisu.

The workflow is simple. Add a tag in FUB and it shows up as a transaction in Sisu.

Create the following tags in FUB exactly as they appear below:

  • #SellerPipeline

  • #SellerApptSet

  • #SellerApptMet

  • #SellerSigned

  • #SellerLivelistings

  • #SellerPending

  • #SellerClosed

  • #SellerLost

  • #BuyerPipeline

  • #BuyerApptSet

  • #BuyerApptMet

  • #BuyerSigned

  • #BuyerPending

  • #BuyerClosed

  • #BuyerLost

Drop our team a mail at [email protected] if you need any help!

Following data is sent from FUB to Sisu when an opportunity is created using InterFace Tag Integration, for any transaction stage:

a. Transaction Status
b. Assigned Agent (Directly from FUB)
c. First Name and Last Name (Directly from FUB)
d. Contact Email (Directly from FUB)
e. Mobile Phone Number (Directly from FUB)
f. FUB Contact Link (Directly from FUB)
g. Lead Date (Directly from FUB)

1. Pipeline Stage

a. Client Type (Buyer/Seller)

2. Appointment Set Stage

This stage can be directly used instead of Pipeline with same flow of information from FUB to Sisu, in addition to the following fields:

a. 1st Appointment Date (Today by default)

3. Appointment Met Stage

a. Status > Appointment Met
b. 1st Time Appointment Met (Today by default)

4. Agreement Signed Stage

a. Status>Signed
b. Signed Date (Today by default)

5. Pending Stage

a. Status>Pending
b. Under Contract Date (Today by default)

6. Closed Stage

a. Status>Closed
b. Settlement Date (Today by default)

7. Terminate Deal

To archive the deal in FUB and update status as Lost in Sisu, use Termination functionality. Following is updated in Sisu:

a. Status>Lost

Feel free to contact our support team at [email protected] if you have any questions!

Did this answer your question?