Every 2 weeks, we push out (or "release") new features, improvements, and bug fixes to our production environment (my.sisu.co). In this article, you can see a history of all those changes for 2023. The most recent release is always at the top, followed by past releases. Use the table of contents to the right to easily jump to past releases.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

If you need to use Sisu on the go, download our mobile app so you can access your Dashboard, your transactions, your reports, and your data at any time. The mobile app is available in both the Apple Store (iOS) and the Play Store (Android).

The app is specifically for accessing Sisu NEXT, the newest and fastest version of Sisu. If you don't have access to Sisu NEXT, email Kaela at [email protected] to learn more about how to get access.

--Where can I find quick links to the apps?--

1. On your phone, go to sisu.co/onboarding.

2. The 2 quick links are at the top of the Onboarding page. Click whichever applies to you and the store you need to access.

Some users sign on recruits but then have a mandatory training that must be completed before they're officially on the team. Now, these new recruits can have a status of pending while they complete any final recruiting requirements.

In order for users to track pending recruits, we're adding the following:

When using the Sierra integration, Canadian provinces are now pulled into Sisu when you use the integration to create a new Sisu transaction.

We've reordered the property details fields in Client Portal that appear in each transaction. The fields are now in a more chronological order.

--Where do property details appear in Client Portal?--

In Client Portal, click in-line with a transaction to open it. The Transaction tab opens by default, which is where you can find all property details.

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

In our FUB integration, you can now specify exactly which buyer/seller transaction stages you want the integration to track. Team admins can now make these customizations in the setup window they used to configure the integration.

--Location of the Setup Window--

Admins can reconfigure their integration preferences by doing the following:

1. In Sisu, go to Admin > Integration Hub.

2. Click the "Follow Up Boss" tile.

3. In the top-right corner, click the "Reconfigure" button. This opens the integration setup window.

We've decided to rename the Transaction Form to Transaction Overview to give it some added clarity. The Transaction Overview functions similarly to the forms you create in Sisu (which is why it was called a form for so long), but at the same time, it's different than user-created forms. You can't delete it, change its name, or restrict it from view. It also might not correspond to one of your team's actual forms. It's just a place to house basic transaction information, hence the name change to "overview."

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

In Sisu NEXT, you can now send DMs to other users and other groups of users. DMs are only visible to the recipient(s) of the message. In Sisu Classic, you can still see any DMs as chats in the Messages tab of your Message Center panel, and you can reply to them.

--How do I access the Message Center in Classic?--

Click the notification bubble in the top-right corner.

--How to Access Reports--

To find reports, click the "Reports" tab at the top of Sisu.

At the bottom of the Lead Sources by Agent report is a Totals section. You can now sort this information by clicking any of the column headers. For example, to sort by lead count, you simply click the "Lead Count" column header.

--Feature Location--

1. Click the Reports tab at the top of Sisu.

2. In the list of reports on the left, click Lead Sources by Agent.

3. Scroll to the bottom of the report to find the Totals section.

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

Now whenever you send a document from within a transaction, the following information will appear in the Transaction History:

--How do I send a document from within a transaction?--

1. Go to Transactions > Transactions. This opens the Transactions screen.

2. Click in-line with a transaction to open it.

3. In the menu on the left, click "Documents."

4. Scroll down to the list of uploaded documents.

5. In-line with a document, click the "Send" button on the right.

--Where can I see the Transaction History?--

1. Open a transaction.

2. In the menu on the left, click "History."

Click the "CSV" button at the top of the report to download it.

--How to Access Reports--

To find reports, click the "Reports" tab at the top of Sisu.

When admins/TCs enable the new setting called "Show summary dashboard to agent," agents will be able to view the Summary Dashboard report.

--Location of the New Setting--

1. Go to Admin > Team Settings.

2. In the menu on the left, click "Preferences."

3. Scroll down to see the new setting: "Show summary dashboard to agent."

We've added another graph option to the Snapshot screen called "Foreclosed Closed Units: This Year."

--How do I adjust a graph on the Snapshot screen?--

1. Go to Dashboard > Snapshot.

2. Scroll down to a graph and click the drop-down arrow at the top of the graph.

All transactions with a Forecasted Closed Date will appear on the following reports, regardless if the date occurred in the past:

--How to Access Reports--

To find reports, click the "Reports" tab at the top of Sisu.

Previously, the Transactions screen showed 2 different numbers in the Count tile: the total number of transactions on the screen and the total after excluding credit splits, rentals, and outbound referrals. We're now adding another number to the Count tile: the total number of transactions on the screen minus any credit splits.

--How do I get to the Transaction screen?--

To get to the Transactions screen, go to Transactions > Transactions.

--Where will admins see this change?--

1. Go to Admin > Vendors.

2. Edit a vendor or add a new vendor. The "Partner" checkbox is near the top of the vendor details screen.

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

To include Lost transaction data in the Agent Accountability report, do the following:

1. In Sisu, click the "Reports" tab at the top of the screen.

2. Select "Agent Accountability" from the list of reports on the left.

3. Click the "Include Lost Transactions" checkbox.

When logging into Client Portal, users need to enter a verification code, which is normally sent to a mobile phone. Now we're adding the option to send the code to an email address.

In Sisu Recruiting, we've added the ability to filter recruits by recruiting coordinator. This is helpful if you want to see all the recruits assigned to a single recruiting coordinator. The Recruits Filter now has a Recruiting Coordinator section where you can select a recruiting coordinator.

If a user enters a date in a transaction that should trigger a task list, the list will still trigger if the date entered is up to 5 days in the past. If the entered trigger date is older than 5 days in the past, the list will not trigger.

New users will be required to make stronger passwords. This will not affect current users unless they reset their password or click "Forgot Password."

The new requirements are as follows:

--How do I change my password?--

Go to Account > Change Password.

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

We've been working hard on a new, revolutionary version of our platform that we're calling Sisu NEXT. This new version offers a new and improved UI experience, mobile integration, and speed optimization. It also sets the groundwork we need to build new exciting features in the future, like custom dashboards. All Essentials and Premier users can now access Sisu NEXT through our classic version of the platform (Sisu Classic). Follow the steps below to give it a try!

--How do I access Sisu NEXT?--

We've split the ISA report into 2 different reports: ISA report by ISA and ISA report by Agent.

--Reports Location--

To find reports, click the "Reports" tab at the top of Sisu.

If you don't want clients seeing a certain vendor in Client Portal, you can hide the vendor from client view.

--How does an admin hide a vendor from clients in Client Portal?--

1. Go to Admin > Vendors.

2. In-line with a vendor, click the "Edit" button. This opens the vendor information screen. (You could also add a new vendor to get to this screen.)

3. On the vendor information screen, scroll down to the "Viewable In Client Portal" checkbox. The box is checked (enabled) by default. Click the box to uncheck it if you want to hide the vendor from client view in Client Portal.

Note: Team members will still see the vendor in Client Portal regardless of this setting.

Previously, merging transactions would omit transaction comments from whatever deal was not chosen to keep. Now when you merge 2 transactions, all the comments from both deals will be merged into the transaction you decide to keep.

--More About Merging Transactions--

If you want to learn how to merge transactions in Sisu, check out this article in our Knowledge Base.

We've added the client's address to the Client Portal notification emails. This will help our agents, especially those with multiple deals under contract, quickly identify which transaction each email is referencing.

We added a "Paid Date" column to the Commissions CDA Payments report. When the Sisu date field "Paid Date" is added to a transaction form and a paid date is entered, the date will be displayed on the Commission CDA Payments report in the "Paid Date" column.

--Reports Location--

To find reports, click the "Reports" tab at the top of Sisu.

When determining a user's time zone, Sisu looks first at the user's personal time zone preferences. If the user hasn't specified a time zone in their profile, Sisu then looks at their team's time zone preferences. If the team hasn't specified a time zone in the team settings, Sisu uses Mountain Standard Time.

--Where do I change my personal time zone?--

1. Go to Account > Profile.

2. Scroll down to the "Timezone" field.

--Where does an admin change the team's time zone?--

1. Go to Admin > Team Settings. The Team Profile opens by default.

2. In the Team Profile, navigate to the "Timezone" field. It's near the top.

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

Improvements to existing functionality:

For a list of bug fixes, click here.

Client Portal notifications weren't being sent as quickly as we wanted. We've now optimized these notification emails so that when a Client Portal step is completed, an email is sent out to both the agent and the client within 10 minutes.

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

Previously, if users wanted to invite vendors to Client Portal, our Customer Success team would have to enable these invites first. This is no longer the case. Now admins can enable vendor invites to Client Portal on their own.

--How do admins enable vendor invites to Client Portal?--

--What can I expect once I enable vendor invites?--

When a user adds a vendor to a transaction, they’ll receive a Welcome email that will help them set up a username and password. If the vendor doesn’t get the email, you can click “Send Platform Invite” to manually resend the email.

In the Sent Email Log, we were previously only keeping track of the first email recipient on each sent email. Now we're showing all the email recipients that each email was sent to.

--Where is the Sent Email Log?--

This log is only available for admins and TCs. To find the Sent Email Log, do the following:

1. Go to Admin > Tasks.

2. In the menu on the left, click "Sent Emails."

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

In a previous release, we added the ability for admin users to create and edit multiple versions of the CDA instructions. As of this release, admins can now also set any of these versions as their default.

--How do you set a version of CDA instructions as the default?--

1. Go to Admin > Commissions.

2. In the menu on the left, click "CDA."

3. In the Commission Instruction box, click the "Set as default" button in-line with a version of CDA instructions.

Previously, when you clicked a “Print CDA" button in the Commission Form (see screenshot below), the previous CDA version was overridden, leaving only 1 CDA at a time in the Documents section of the transaction.

Now when you click a "Print CDA" button, every new version is saved. The naming convention for new CDA versions will look as follows:

--Examples of CDA Version Names--

When using Sisu Recruiting, you can now filter recruits by lost reason. When you choose to filter by Lost status, a drop-down appears allowing you to specify a lost reason.

We're adding an Expense tile to the top of the Income - Org by Team report. This tile shows the sum of all the expenses from the teams listed in this report. The tile pulls expense information from Admin > Expenses.

--Reports Location--

To find reports, click the "Reports" tab at the top of Sisu.

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

Improvements to existing functionality:

For a list of bug fixes, click here.

Clients who no longer want to receive roadmap emails can click an "Unsubscribe" link found in the email itself.

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

We've added a new preference setting called "Show leaderboards on the team dashboard." This setting allows you to choose whether or not your leaderboards will load on the team Dashboard. We've disabled the setting by default in order to decrease load times, but if you want to see your leaderboards on the team Dashboard, you can go ahead and enable this setting.

--Setting Location--

1. In Sisu, go to Admin > Team Settings.

2. In the menu on the left, click "Preferences." This opens a page full of different preference settings.

3. The first settings on the page are the Miscellaneous settings. At the bottom of that list of settings, you can find the setting called "Show leaderboards on the team dashboard."

We now allow for multiple versions of CDA instructions for those who need different sets of instructions to accommodate for different scenarios.

--How can an admin create an additional version of CDA instructions?--

--How can agents choose between instruction versions in a transaction?--

You can use the Commission CDA Payments report to see and export all the information you would see in the CDA:

--Reports Location--

To find reports, click the "Reports" tab at the top of Sisu.

The names of transaction stages now appear in the Transaction History, instead of the stage's ID number.

--Transaction History Location--

The SkySlope form on a transaction now accepts Canadian postal codes.

In Client Portal, each roadmap step must be connected to a task in a transaction's task list. Currently, if you add steps to a roadmap that don't have a corresponding task in any of the transaction's task lists, a single task list is automatically added to the transaction called Roadmap Supported Tasks.

The only tasks added to that task list are those needed to make all steps appear in the roadmap. This ensures that all the steps added to your roadmaps appear for the client.

--Location of Task Lists in a Transaction--

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

Improvements to existing functionality:

For a list of bug fixes, click here.

Previously, teams could use both "00:00" and "24:00" to enter a time for midnight in the Notification Delivery Window fields. However, this was only causing problems for those setting their notification window from "00:00" to "24:00." Due to the way that time is recognized in the system, this led to notifications not being sent at all. So now, "24:00" is no longer an option. If you want your team's notification window to span the entire day, you need to set the window start to "00:00" and the window end to "23:00."

--Where do I specify my team's notification window?--

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

When you click on the "Tags" field in the Transaction Form, a list of tags opens. The order of this list now matches the order of the tags in the tag setup screen.

See the screenshots below to see how tag order in the admin settings is reflected in the Transaction Form's "Tags" field.

Tag admin settings

Tags drop-down menu in the Transaction Form

--Where can admins set up tags?--

--Where can I find a transaction's Transaction Form?--

When you open a transaction, the Transaction Form opens by default.

Starting today, we're enabling roadmap notifications for everyone. Team admins can then choose to disable the notifications for their entire team, and individuals can decide to disable the notifications just for themselves.

--Where can admins disable roadmap notifications?--

--Where can individual users disable roadmap notifications?--

--What are roadmap notifications?--

In Client Portal, you can set up roadmap steps so that an email notification is sent when the agent completes the step.

We made improvements to the Income report to prevent long load times and timeouts.

--Location of Reports--

To find reports, click the "Reports" tab at the top of Sisu.

Previously, when admins created or edited groups, an autosave feature was supposed to save any changes made to the group members or the group name. However, sometimes the autosave would not save all the changes. We've switched out the autosave feature for an actual save button to guarantee that changes will always be saved. Moving forward, when admins create or edit groups, they'll need to click the "Save Group" button when they are done making changes.

--Where can an admin set up (and save changes to) groups?--

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

Now at the bottom of the Commission Form, you'll find a button that says "Print Primary Agent CDA and Save to Documents Folder." This generates a CDA that only includes splits and commissions for the primary agent.

--Setting Location--

This new button is found in the Commission Form, which you can find by doing the following:

Previously, we had a Y/N field called "Referral" that you could add to your forms. When "Y" was selected, this would label the transaction as a referral and thus prevent it from counting toward Dashboard credit. We've renamed this "Referral" field to "Outbound Referral" for added clarity. It still functions the same as before.

--How do admins add a field to a form?--

For help adding fields to a form, check out this article in our Knowledge Base.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

We're adding a new feature to our CINC integration. Now, when users apply the label "Sisu New" to a lead in CINC, this action will cause the CINC Activity in Sisu called "CINC - NEW LEADS" to increase by 1.

--Activities in Sisu--

You can see Activity information on your Dashboard (by scrolling down to the Activity tiles) or via one of the Activity reports (Activity by Agent; Activity Log).

We've made improvements to how the Lead Source ROI by Agent report runs and loads to prevent long loading times and timeout errors.

--Location of This Report--

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

Rentals and referrals are NOT counted on the Dashboard, which means that the pacer circles on the Dashboard also won't count them. However, the Appointment Met and Appointment Set pacer circles were the exception. Rentals and referrals WERE still being counted toward those 2 pacer circles.

This is still the case, but for those who do NOT want rentals and referrals to count toward the Appointment Met and Appointment Set pacer circles, we're adding 2 new settings:

Now admins can decide whether or not rentals and referrals will count toward the Appointment Met and Appointment Set pacer circles.

--Location of New Settings--

1. Go to Admin > Team Settings.

2. In the menu on the left, click "Preferences." The Miscellaneous section appears at the top of the screen.

3. Scroll to the bottom of the list of Miscellaneous settings and you'll find the 2 new settings. Click the tooltips for added details.

--How do you tell Sisu that a transaction is a rental or a referral?--

You need to set the "Referral" field or "Rental" field to "Yes."

Recently, we added the ability for admins to set the Default Transaction Page Form for their entire team. (If you need a refresher on this functionality, please click here to see the release note.) The Transaction Form is the Default Transaction Page Form by default; however, admins can choose any of their other forms to be the Default Transaction Page Form.

Previously, if an admin set another form to be the Default Transaction Page Form but wanted to once again make the Transaction Form the default, they just needed to click the "Remove Default Transaction Page Form" link. However, the name of the link was causing confusion, leading some to wonder if clicking the link would delete their Transaction Form. For this reason, we've renamed this link to say "Unassign Default Transaction Page Form."

--Feature Location--

We're now tracking all changes made to custom fields via the API. These changes are now visible in the Transaction History of each transaction.

--How do I get to the Transaction History?--

1. Go to Transactions > Transactions, and click on a transaction to open it.

2. In the menu on the left, click "History."

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

When admins create a new user, they now can control whether or not the Welcome email is sent automatically.

--Feature Location--

We're adding a new setting that gives admins the option to allow TCs to view the Income report. When the setting (Allow TC’s to view Income Report) is enabled, TCs will be able to see the Income report. The setting will be disabled by default.

--Setting Location--

We've added some text to the "Closed Units" tile at the top of the Dashboard: "Calculated after credit splits, rentals, and referrals." This is to make it clear that the number that appears on the "Closed Units" Dashboard tile will exclude certain transactions (like those marked as rentals or referrals), while the "YTD Closed" tile on the Snapshot screen will include ALL transactions. If you click on either tile, you're taken to the Transactions screen. The "Count" tile on this screen shows both numbers: the total number of closed transactions and the number that subtracts out any splits, rentals, or referrals.

Previously, we had an admin setting called "Agent/ISA View of Income Report, Commission Report, and Commission Form" that allowed admins to hide these 3 things from agents and ISAs. But it was all or nothing. Now we've separated the Commission Form out into its own setting so that admins can hide either the reports or the Commission Form if they choose.

--Setting Location--

Previously, if you filtered the Commission Payment report by a secondary agent, it would not show the commission they made as the secondary agent. You had to filter the report by the primary agent in order to see the commission made by secondary agents. We've now improved this report so that you can filter by either a primary or secondary agent. Now, when you filter the report by a secondary agent, you will be able to see all the commission they've made as a secondary agent.

--Location of the Commission Payment Report--

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

It's now easier for admins who are part of multiple organizations to select a model team, shared forms, and model agents for each org they're in. This can all be done from a single location in Sisu: Admin > Organization Settings.

Below is a screenshot of what it looks like to set a model team as a user who is part of 2 organizations. As you can see, there's a box for each organization.

The Team Forms screen now has a drop-down to allow users to easily switch between organizations.

--Feature Location--

Previously, the only columns that admins could add to the Summary Dashboard report were for Dashboard metrics (like Appointment Set, Signed, and Closed to name a few). We're now allowing admins to add columns for Activities as well, including custom Activities.

--Where can admins choose which columns appear on the Summary Dashboard report?--

--Report Location--

Previously, you could see the results of past challenges by filtering the Challenges screen by month or year. We're now adding the ability to filter past Challenges by week as well. This allows users to see who was the point leader for any given week.

--Feature Location--

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

For a list of bug fixes, click here.

Currently, the columns displayed on the Transactions page match the fields from the form that is set as the Default Transactions Page Form. Each user can set their preferred Default Transactions Page Form in their User Profile.

We've now added the ability for team admins to set the Default Transactions Page Form for their entire team. However, each user's individual default preferences will still override team preferences.

--Where can an admin set the Default Transactions Page Form for their team?--

--Where can an agent set their personal preferences for the Default Transactions Page Form?--

--What is the Default Transactions Page Form when none is set by a user?--

If no default is set at the admin level or the individual level, the Default Transactions Page Form is the Transaction Form.

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features:

Improvements to existing functionality:

For a list of bug fixes, click here.

Recently, we released a new feature that allows admins to set up Sisu notifications so that they're sent directly to a Slack channel of their choice. Previously, admins needed to reach out to support in order for them to enable the feature, but this is no longer the case. Now, any team can set this up without reaching out to our chat team. If you're an admin who would like Sisu notifications sent to Slack, check out this article in our Knowledge Base for detailed step-by-step instructions on how to get it all set up.

With the full release of our Slack Notifications feature, we're now fully deprecating the functionality under Admin > Notifications. Any active notifications under Admin > Notifications have been automatically disabled. You'll still be able to navigate to Admin > Notifications to see the list of old notifications, but you won't be able to enable them or send them out.

Recently we added a new feature to the Summary Dashboard report that allowed for a way to measure the average days between certain status changes. (Click here for a recap of that feature.) We've now decided to include data from Lost transactions in these averages so that this data can be more accurate. We also found that the report was pulling some of these numbers incorrectly. We've fixed this as well.

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

New features in this release:

Improvements in this release:

For a list of bug fixes, click here.

We're adding a checkbox to the top of the Agent / Team Production report that will allow users to include all agents in the report, even those with zero production.

--Feature Location--

As soon as you enable the BoomTown integration, a new field called "BoomTown Contact URL" will become available and admins will be able to add it to any form. When agents open a Sisu transaction that originated from BoomTown, they'll be able to use this field to open the corresponding BoomTown Lead Profile in another tab.

--How do admins add a field to a form?--

For help adding fields to a form, check out this article in our Knowledge Base.

--How do I use the field once it's been added to a form?--

--Will the field still work if I don't use it right away?--

Yes! We store each BoomTown URL even though the field isn't being used.

Let's say you turn on the BoomTown integration, but you don't add this field to a form for a month. In that time, 10 transactions came from BoomTown to Sisu. When you add the field to a form, you'll still be able to use it to link to each transaction's BoomTown Lead Profile.

--Will this field work for transactions created before this release?--

Unfortunately, not. This link will only work for transactions created in Sisu after January 18th.

We had several users report that the Caps report was missing data. After doing some digging, we found out that these users were selecting the incorrect cap year from the drop-down at the top. To make this report more intuitive, we're changing the wording of the "Cap Year" drop-down to "Cap End Year."

--Example Scenario--

If you select 2023 from the drop-down, the report will show you cap date ranges ending in 2023.

--Location of the "Cap End Year" Drop-down--

If a task list has a trigger date that's more than 5 days in the past, the task list will NOT be assigned to the transaction. You'll still be able to assign the task list manually. We made this change because many users were having problems with task lists being applied when they shouldn't.

--Example Scenario--

Let's say a task list is set to trigger on transactions when the Under Contract date is entered. Then on January 5th, an agent sets a transaction's Under Contract date to December 15th. Since December 15th is MORE than 5 days in the past, the task list won't be applied to that transaction.

--Where does an admin set up task lists?--

--Where do task lists appear in a transaction?--

If a notification task has a trigger date that's more than 5 days in the past, the notification email will NOT be sent. It will appear in the task list with the following verbiage in the Due column: "Backdated, not sent. X days overdue." You'll be able to send the notification manually by clicking the "Send" button to the right of the verbiage. (See screenshot below.) Until the notification is sent, the task will have a status of To Do. We made this change because many users were having problems with notification emails being sent when they shouldn't.

--Example Scenario 1--

Let's say a notification task is set to trigger when the Under Contract date is entered. This notification task is part of a task list that has been added to Sally Hugh's transaction. Then on January 5th, an agent sets Sally's Under Contract date to January 2nd. Since January 2nd is LESS than 5 days in the past, this triggers the notification email to be sent that same day.

--Example Scenario 2--

Using the same scenario outlined above, let's say that on January 5th, an agent sets Sally's Under Contract date to December 15th. Since December 15th is MORE than 5 days in the past, the notification email won't be sent. The agent will have to click the "Send" button to send it.

--Where do tasks appear in a transaction?--

--Where can admins add tasks and edit task triggers?--

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.

For a list of improvements, click here.

For a list of bug fixes, click here.

We've added a setting ("Include ROI expenses on the Income report") that allows admin/TC users to choose whether or not ROI expenses are included in the Income report.

Setting Location

Location of the Income Report

You can access all reports, including the Income report, by clicking the "Reports" tab at the top of Sisu.

We're now allowing users to assign admins as the TC of a transaction. This will be helpful for teams where the admin performs TC tasks when there is no designated TC.

Feature Location

Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.