2023 Feature Releases:
March 15
New features:
Improvements to existing functionality:
For a list of bug fixes, click here.
New Features
Admins Have the Option to Withhold the Welcome Email When Creating a New User
When admins create a new user, they now can control whether or not the Welcome email is sent automatically.
--Feature Location--
Go to Admin > Users.
Click "Add New User."
See the "Send Welcome Email" checkbox at the bottom of the form. The box is checked by default. You can leave it as is or uncheck the box.
Click "Add" when finished. This adds the user to Sisu. If the "Send Welcome Email" checkbox was left checked, the Welcome email is automatically sent to the user. Otherwise, the email isn't sent.
Admins Can Allow TCs to View the Income Report
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--
Go to Admin > Team Settings.
In the menu on the left, click "Preferences."
At the bottom of the Miscellaneous section, see the setting called "Allow TC’s to view Income Report."
Improvements
We've Added Clarifying Text to the "Closed Units" Tile
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.
Admins Can Now Show or Hide Just the Commission Form
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--
Go to Admin > Team Settings.
In the menu on the left, click "View Restrictions."
In the section at the top, see the setting called "Agent/ISA View Of Commission Form." When set to "Displaying," agents and ISAs can view the Commission Form, even when the Income Report and Commission Report setting are set to "Restricted."
We've Improved the Commission Payment Report For Secondary Agents
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--
Click the "Reports" tab at the top of Sisu.
In the list of reports on the left, click "Commission Payments."
Click the "Scope" drop-down at the top of the report and select a secondary agent. The report will show you the commission they have earned as a primary agent AND as a secondary agent.
Bug Fixes
Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.
Previously, the API was only recognizing state abbreviations that were in all caps (e.g., CA or WA). If a state abbreviation came over with lowercases (e.g., Ca or Wa), the "State" field in the Sisu forms would remain blank. We've fixed this moving forward so that the API will recognize state abbreviations regardless of capitalization. We will also be fixing past transactions that have been affected by this. (7539)
The API was not looking for a default TC nor setting it when new transactions were coming in from other systems. We've fixed the API so that it will honor the default TC that has been set up and add that TC to new transactions that come through the API. (7424)
Users were reporting that Dashboard links, created under Admin > Team Settings > Preferences, were resulting in errors. We fixed this.
Note: The links are designed to be for people who don't have Sisu. If a Sisu user tries to use the link, it will log them out of Sisu. (7392)
There was a bug that was denying coaches access to the Income report. We fixed this so that coaches are again allowed access to the report. (7095)
March 1
New features:
Improvements to existing functionality:
For a list of bug fixes, click here.
New Features
Multi-Org Admins Can Select the Model Team for Each Org From One Location
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--
Go to Admin > Organization Settings.
Improvements
Admins Can Now Add Columns for Activities to the Summary Dashboard Report
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?--
Go to Admin > Team Settings.
In the menu on the left, click "Preferences."
Scroll down to the last section called "Show the Following Items in Summary Report."
Note: I recommend just doing a Control+F search (or Command+F for Macs) for the phrase "summary report."
In this section, admins can click the checkboxes to choose which columns appear on the report. Activities now appear in this section.
--Report Location--
Click the "Reports" tab at the top of Sisu.
In the list of reports on the left, click "Summary Dashboard."
We're Adding the Ability to See the Weekly Results of Past Challenges
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--
Go to Challenges > Challenges.
Click the date drop-down to select past dates, including specific weeks.
Bug Fixes
Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.
We fixed a bug that was causing inaccurate numbers to appear in the At Bat column of the Lead Source ROI reports. Now the At Bat column is once again pulling numbers from the counts entered under Admin > Lead Sources > Counts and Expenses, as designed. (7429)
Previously, the Net Agent Paid Income tile on the Dashboard was not correctly reflecting the net agent paid income. We've now fixed this. This tile will now also include secondary agent income. (7303)
We had several reports of duplicate notification emails. We've implemented a fix to keep this from happening. (7280)
We fixed a bug that was hiding the settings found under Admin > Team Settings > Transaction Stages Board. These settings are now visible again. (7400)
We fixed an error that was appearing when admins tried to go to Admin > Tasks > Transaction Tags in Beta. (7450)
February 15
New features:
For a list of bug fixes, click here.
New Features
Admins Can Set a "Default Transactions Page Form" for the Team
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?--
Go to Admin > Team Settings.
In the menu on the left, click "Forms and Fields."
On the right side of the screen, click the "Default Transaction Page form" button in-line with the form that you want to set as the default for your team.
Note: If you just want the Transaction Form to be your Default Transaction Page Form, click "Remove Default Transaction Page Form" in the top-right corner.
--Where can an agent set their personal preferences for the Default Transactions Page Form?--
Go to Account, Profile.
Scroll down to the "Default Transactions Page Form" drop-down. The form you select here will be your 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.
Bug Fixes
Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.
The 2023 Total GCI tile on the Team Dashboard was showing one number, but then after you clicked it, it would show another. We've fixed this so that the number stays the same after clicking the tile. (7300)
Previously, if an organization (1) had a shared organization form with multiple choice options and (2) those options were changed, those changes weren't being copied to the shared forms throughout the organization. We've fixed this so that any changes to an organization form are also made to the shared forms throughout the organization. (7298)
When organizations were viewing the leaderboards on the Dashboard, not all teams were present and the rankings were incorrect. We've fixed this behavior. (7151)
Tasks assigned to TCs were being assigned to admins. We've fixed this so that TC tasks are assigned to TCs. (6828)
When the setting "Show agents with zeros in leaderboards and challenges" was created, inactive users began appearing on leaderboards even though inactive agents aren't supposed to be included on leaderboards. We've now fixed this. Inactive users shouldn't be included on challenges or leaderboards. (6408)
February 1
New features:
Improvements to existing functionality:
For a list of bug fixes, click here.
New Features
Sisu Notifications Can Now Be Sent to a Slack Channel of Your Choice
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.
Improvements
Notifications Under Admin > Notifications Are Fully Disabled
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.
Updates and Fixes for New Summary Dashboard Report Metrics
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.
Bug Fixes
Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.
Users reported that certain automated notification emails were being sent more than once. We've fixed this. (6943)
Users reported that the Net Agent Paid Income tile on the personal Dashboard was not including income that was earned as a secondary agent. We've fixed this. The Net Agent Paid Income tile should include income earned as a primary agent AND a secondary agent. (5542)
Some users are receiving messages in the Message Center that have an address for a property that does not belong to them. We've fixed this so that the addresses that appear on messages are accurate. (5741)
January 18
New features in this release:
Improvements in this release:
For a list of bug fixes, click here.
New Features
Agents with Zero Production Can Appear on the Agent / Team Production Report
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--
Click the "Reports" tab at the top of Sisu.
In the menu on the left, click "Agent / Team Production."
The new checkbox, labeled "Show agents with zero production," appears at the top of the report.
New Sisu Field that Will Link Transactions from BoomTown Back to the BoomTown Lead Profile
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?--
Open a transaction in Sisu that originated from BoomTown.
In the menu on the left, select a form that contains the "BoomTown Contact URL" field.
Scroll down to the field. You'll see a URL in the field. Click the button to the right of the field, and the contact's BoomTown Lead Profile will open in another tab.
--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.
Improvements
We're renaming the "Cap Year" drop-down in the Caps report
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--
Click the "Reports" tab at the top of Sisu.
In the menu on the left, select the Caps report. The "Cap End Year" drop-down is at the top.
A Change to Backdated Task List Triggers
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?--
Go to Admin > Tasks. The Task Lists screen opens by default.
--Where do task lists appear in a transaction?--
Go to Transactions > Transactions and click on a transaction to open it.
In the menu on the left, click "Tasks."
A Change to Backdated Notification Task Triggers
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?--
Go to Transactions > Transactions and click on a transaction to open it.
In the menu on the left, click "Tasks."
Scroll down.
--Where can admins add tasks and edit task triggers?--
Go to Admin > Tasks.
In the menu on the left, click "Tasks."
Bug Fixes
Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.
We fixed an error that was appearing when admin and TC users were trying to generate a Dashboard link (Admin > Team Settings > Preferences). (7069)
Some users reported that when they entered addresses in the search bar of the Transactions screen, transactions with applicable addresses weren't appearing in the search results. We've fixed this. (7017)
Users reported that expenses were no longer being included in the Income report. This was due to a bug that was introduced when we recently added the setting called "Include ROI Expenses on the Income report." We've fixed this bug, so expenses will appear on the report once again. (7015, 7157)
When organizations were sharing forms from their Model Team with other teams in the organization, the multiple choice options weren't being added to the shared forms. We've fixed this. (6993)
Some users were reporting that they weren't receiving emails when @mentioned in task comments. This has been fixed. (5978)
Task notifications that have been sent were appearing in the Task Board and Task Calendar under the To Do column. We've fixed this. Task notifications that were sent should not appear as a to-do on the Task Board. They should appear as complete on the Task Calendar. (6280)
January 5
New features in this release:
For a list of improvements, click here.
For a list of bug fixes, click here.
New Preference Setting
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
Go to Admin > Team Settings.
In the menu on the left, click "Preferences."
At the bottom of the Miscellaneous section, you can find the setting "Include ROI expenses on the Income report."
Note: Remember to use the tooltips to the right of each setting to learn more about them.
Location of the Income Report
You can access all reports, including the Income report, by clicking the "Reports" tab at the top of Sisu.
You Can Now Assign an Admin as the TC
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
Go to Transactions > Transactions.
Click a transaction to open it.
In the menu on the left, select a form with the "TC" drop-down.
When you click on the "TC" drop-down, users with the role of admin will now appear in the list.
Improvements
When an ISA logs into Sisu, their ISA Dashboard will now open by default.
Bug Fixes
Internal Employee Note: Each bug fix in this section includes relevant ticket numbers so you can reference an original ticket if you need to.
Previously, when you inactivated an agent, they were being unassigned from tasks. This was not intended behavior. We've changed this so that inactivated agents remain assigned to the tasks they were already assigned to. (6802)
Previously, a cap year's end date would overlap with the next cap year's start date. An example would be of a cap year spanning 7/19/2021-7/19/2022 and the following cap year spanning 7/19/2022-7/19/2023. If an amount was applied to the cap on the end date, the system didn't know which cap year it should apply the amount to: the current cap year (7/19/2021-7/19/2022) or the next cap year (7/19/2022-7/19/2023). Now, there can no longer be overlap in the cap date ranges. If a cap year starts on 7/19/2022, the end date must be 7/18/2023. (6699)
There's a bug that's causing the Net Agent Paid Income tile on the personal Dashboard to calculate totals based on the scope date selected, rather than the current full year. We've fixed this so that this tile always reflects the current year-to-date total despite the selected scope. (6542)
Previously, any commissions earned via adjustments weren't included in the Commission report. Now users can view the Commission report and see all of the commission information, including adjustments that were added to the Commission Form. (6425)