Documentation

The FUB Sisu Activity Integration Syncs Calls, Texts, Emails, and Lead Sources. We sync this data in real-time as activities occur in FUB. We also run a daily sync to makes sure the data in Sisu mirrors the data in FUB for that day.

PLEASE NOTE: All ‘Custom Activities’ must be specifically requested for them to be included in the integration.

Daily Sync (~2 AM)

Every day around 2 AM, the integration extracts data from Follow Up Boss and syncs it with SISU. When data is associated with an agent, it is synced from FUB to SISU if there is an agent with a matching name.

  1. Calls

    1. NUMBER OF DIALS: Outbound calls logged in FUB

    2. INBOUND CALLS (CUSTOM ACTIVITY): Inbound calls logged in FUB

      1. INBOUND CALLS BY SOURCE (CUSTOM ACTIVITY): Inbound calls logged in FUB for a specific source. Currently, two sources can be tracked.

    3. NUMBER OF UNIQUE DIALS (CUSTOM ACTIVITY): The number of unique contacts in FUB that an outbound call was logged to. This measures how many people were called rather than the number of calls made.

    4. CONNECTIONS (CUSTOM ACTIVITY): Calls logged in FUB that last 60 seconds or longer

      1. Optional: The minimum and maximum duration can be set as desired

    5. CONVERSATIONS: Calls logged in FUB that last 2 minutes or longer

      1. Optional: The minimum duration can be set as desired

    6. MINUTES TALK TIME (CUSTOM ACTIVITY): Duration of calls logged in FUB

      1. MINUTES TALK TIME INBOUND CALLS BY SOURCE (CUSTOM ACTIVITY): Duration of Inbound calls logged in FUB for a specific source. Currently, two sources can be tracked.

  2. People

    1. TEAM TOTAL LEAD COUNT: All new FUB leads will be added, by lead source, to the team monthly Total Lead Count.

Daily Sync Coming Soon:

  1. UNIQUE EMAILS: The number of contacts that were emailed

  2. UNIQUE TEXTS: The number of contacts that were sent a text

  3. TEXT CONVERSATIONS: A back and forth text exchange with a contact

Real-Time Sync

Data that will be synced from FUB to SISU in real-time

  1. CALLS

    1. NUMBER OF DIALS: Outbound calls logged in FUB

      1. NUMBER OF DIALS BY STAGE (CUSTOM ACTIVITY): Outbound calls logged in FUB for contacts that are in a specific stage.

      2. WEIGHTED NUMBER OF DIALS BY STAGE (CUSTOM ACTIVITY): A weighted number of outbound calls logged in FUB for contacts that are in a specific stage, based on the number of contacts in that stage for that agent. For example, if an agent dials a contact in the ‘Lead’ stage, and currently has 10 leads assigned to them in the ‘Lead’ stage, they will get credit for 0.1 dials.

    2. CONNECTIONS (CUSTOM ACTIVITY): Calls logged in FUB that last 60 seconds or longer

      1. WEIGHTED CONNECTIONS BY STAGE: Weighted Calls logged in FUB that last 60 seconds or longer for contacts that are in a specific stage, based on the number of contacts in that stage for that agent. For an example of how weighted activities work, see ‘weighted number of dials by stage’ above.

      2. Optional: The minimum and maximum duration can be set as desired

    3. CONVERSATIONS: Calls logged in FUB that last 2 minutes or longer

      1. CONVERSATIONS BY STAGE (CUSTOM ACTIVITY): Calls logged in FUB that last 2 minutes or longer for contacts that are in a specific stage.

      2. WEIGHTED CONVERSATIONS BY STAGE (CUSTOM ACTIVITY): Weighted Calls logged in FUB that last 2 minutes or longer for contacts that are in a specific stage, based on the number of contacts in that stage for that agent. For an example of how weighted activities work, see ‘weighted number of dials by stage’ above.

      3. Optional: The minimum duration can be set as desired

    4. MINUTES TALK TIME (CUSTOM ACTIVITY): Duration of calls logged in FUB

      1. MINUTES TALK TIME BE STAGE (CUSTOM ACTIVITY): Duration of calls logged in FUB for a specific stage.

  2. People

    1. LEAD SOURCE COUNT BY AGENT

      1. Option 1: When a lead comes into FUB and is assigned to an agent it is counted in SISU for that agent under the relevant lead source. This doesn't account for reassigned leads in FUB.

  3. Emails

    1. EMAILS SENT: The number of emails sent in FUB

    2. WEIGHTED EMAILS BY STAGE (CUSTOM ACTIVITY): Weighted emails logged in FUB for contacts that are in a specific stage, based on the number of contacts in that stage for that agent. For an example of how weighted activities work, see ‘weighted number of dials by stage’ above.

  4. Texts

    1. TEXT MESSAGES: The number of texts sent in FUB

    2. WEIGHTED TEXTS BY STAGE (CUSTOM ACTIVITY): Weighted texts logged in FUB for contacts that are in a specific stage, based on the number of contacts in that stage for that agent. For an example of how weighted activities work, see ‘weighted number of dials by stage’ above.

  5. Appointments (Custom Activity): The Appointment Set Activity metric in Sisu has been discontinued as a default metric. We can sync FUB Appointments to a custom Appointment Set activity in Sisu. For the Appointment Set, Met, etc. pipeline, please see our FUB Sisu Webform Pipeline Integration.

    1. APPOINTMENTS (CUSTOM ACTIVITY): The number of appointments set in FUB

    2. WEIGHTED APPOINTMENTS SET BY STAGE (CUSTOM ACTIVITY): Weighted appointments logged in FUB for contacts that are in a specific stage, based on the number of contacts in that stage for that agent. For an example of how weighted activities work, see ‘weighted number of dials by stage’ above.

Real-Time Sync Coming Soon:

  1. People

    1. LEAD SOURCE COUNT BY AGENT

      1. Option 2: Count the lead in SISU when first assigned to an agent and then count it again in SISU each time it's reassigned to a different agent. The issue with this option is that the second or third agent assigned to a lead will have a much lower probability of closing it than the first, but the data will be tracked as if they have an equal opportunity.

      2. Option 3: Count the lead in SISU when first assigned to an agent differently than if/when it is reassigned to a different agent. For example, in SISU we could have the lead source 'Ylopo' for when a Ylopo lead is first assigned to an agent, and a source 'Ylopo Reassigned' for when Ylopo leads are reassigned. The issue with this option is additional complexity.

Web Form Pipeline: FUB Sisu Integration

Update FUB deals and Sisu transactions with web forms embedded in FUB custom fields.

Historic Sync

Calls and Lead Sources (Team only) can be backfilled.