Release 2.52.1 - November 14th, 2023
After a development release is deployed, a native module appears on the app. Users will click Apply to refresh the page with the new updates applied. This replaces the browser notification and only requires the user to click Apply once.
The issue that prevented users from selecting a team CRM number has been resolved.
After a development release is deployed, a native module appears on the app. Users will click Apply to refresh the page with the new updates applied. This replaces the browser notification and only requires the user to click Apply once.
The issue that prevented users from selecting a team CRM number has been resolved.
Release 2.51.0 - November 13th, 2023
A new merge field has been created to insert the Team Logo. The Team logo can be added in Team Settings > Profile.
An error message will display when attempting to delete a tag that is in use by an automation
When creating a new user, if the maximum number of licenses are already in use, an error message will display stating: “You have reached the maximum number of licenses. Please reach out to support@thinkaidium.com to increase your number of licenses available in the Aidium CRM.”
Date fields in the format yyyy-mm-dd-Thh:mm:ss:mssZ can now be used in CSV uploads. Previously these values were invalid.
A new merge field has been created to insert the Team Logo. The Team logo can be added in Team Settings > Profile.
An error message will display when attempting to delete a tag that is in use by an automation
When creating a new user, if the maximum number of licenses are already in use, an error message will display stating: “You have reached the maximum number of licenses. Please reach out to support@thinkaidium.com to increase your number of licenses available in the Aidium CRM.”
Date fields in the format yyyy-mm-dd-Thh:mm:ss:mssZ can now be used in CSV uploads. Previously these values were invalid.
Release 2.51.0 - November 7th, 2023
Users can now save commonly used filters for transactions, just like they can for contacts.
Users can now save commonly used filters for transactions, just like they can for contacts.
Release 2.49.0 - November 6th, 2023
When applying a filter to a numerical value, users can now enter a range.
Editing all fields in the Team Profile (including the logo) will now be done from an edit drawer, in order to be more consistent with the rest of the application.
When applying a filter to a numerical value, users can now enter a range.
Editing all fields in the Team Profile (including the logo) will now be done from an edit drawer, in order to be more consistent with the rest of the application.
Release 2.48.1 - November 2nd, 2023
Enterprise Automations Management (EAM) has been released to all enterprises! Enterprise Owners and Admins have the ability to access it.
Enterprise Automations Management (EAM) has been released to all enterprises! Enterprise Owners and Admins have the ability to access it.
Release 2.48.0 - November 2nd, 2023
A new endpoint was added to the API for getting team data for an enterprise.
The issue that prevented records from being added to a copied automation when “Enroll Existing Records” was enabled and the Automation was enabled at the time it was copied has been resolved.
A new endpoint was added to the API for getting team data for an enterprise.
The issue that prevented records from being added to a copied automation when “Enroll Existing Records” was enabled and the Automation was enabled at the time it was copied has been resolved.
Release 2.47.0 - November 1st, 2023
Users can now save commonly used filters, saving them time and effort. Visit our Knowledge Base Article for details.
The contact creation method (i.e. Encompass, Manual) can now be used as an entry or exit condition in Automations.
When inviting a user, there is now a visual indicator to let the user know where they are in the process.
Users can now save commonly used filters, saving them time and effort. Visit our Knowledge Base Article for details.
The contact creation method (i.e. Encompass, Manual) can now be used as an entry or exit condition in Automations.
When inviting a user, there is now a visual indicator to let the user know where they are in the process.
Release 2.46.0 - October 30th, 2023
The automation filter tabs are now working as expected.
To reduce dashboard load times, we now paginate the tasks module.
The automation filter tabs are now working as expected.
To reduce dashboard load times, we now paginate the tasks module.
Release 2.44.0 - October 23rd, 2023
We now map Cell and Work phones from Encompass for all Partner Contacts
The issue that prevented the proper update of an existing status’s or tag’s casing has been resolved.
The regression issue that allowed contacts without a first or last name to be added to a team has been resolved.
We now map Cell and Work phones from Encompass for all Partner Contacts
The issue that prevented the proper update of an existing status’s or tag’s casing has been resolved.
The regression issue that allowed contacts without a first or last name to be added to a team has been resolved.
Release 2.43.5 - October 19th, 2023
Users can now create a task in an Enterprise Automation.
There is no longer an error that occurs when applying the condition or enabling the automation using the “Known” and “Not Known” condition operators.
Improved handling of adding a large number of records to an automation at the same time.
Users can now create a task in an Enterprise Automation.
There is no longer an error that occurs when applying the condition or enabling the automation using the “Known” and “Not Known” condition operators.
Improved handling of adding a large number of records to an automation at the same time.
Release 2.43.4 - October 16th, 2023
We now map Cell, Home, and Work phones from Encompass for Borrowers and Co-Borrowers.
Users can now enter a decimal value in custom fields that have the “number” field type.
To increase usability, we have moved the Automations behavior card below Entry Conditions, as this provides a more intuitive flow to the automation builder.
When a team member integrates with SimpleNexus we now check that the user exists on the configured SimpleNexus account. This ensures users do not make mistakes when entering their account information in, making the integration more resilient.
The regression bug that removed the ability to upload a transaction CSV on behalf of a team member has been resolved.
The bug that caused all records to display as eligible when using relative date filters in Automation Entry Conditions has been resolved.
Transfer Contact
Speed improvements have been to the Transfer Contact feature.
We now map Cell, Home, and Work phones from Encompass for Borrowers and Co-Borrowers.
Users can now enter a decimal value in custom fields that have the “number” field type.
To increase usability, we have moved the Automations behavior card below Entry Conditions, as this provides a more intuitive flow to the automation builder.
When a team member integrates with SimpleNexus we now check that the user exists on the configured SimpleNexus account. This ensures users do not make mistakes when entering their account information in, making the integration more resilient.
The regression bug that removed the ability to upload a transaction CSV on behalf of a team member has been resolved.
The bug that caused all records to display as eligible when using relative date filters in Automation Entry Conditions has been resolved.
Transfer Contact
Speed improvements have been to the Transfer Contact feature.
Release 2.43.2 - October 13th, 2023
Some UI changes have been made to the Automations page. Most notably, each section of the Automation Builder is now collapsible and the “Trigger” section has been renamed to “Entry Conditions”.
Some UI changes have been made to the Automations page. Most notably, each section of the Automation Builder is now collapsible and the “Trigger” section has been renamed to “Entry Conditions”.
Release 2.43.0 - October 11th, 2023
Users can now edit a contact from the Context Menu on any page the menu exists. This action is now “Edit” instead of “Update”.
Users can now easily select all teams to push down an Enterprise Automation to.
The bug that prevented some users from creating a transaction has been resolved.
The bug that occasionally caused automation actions to be out of order for a copied automation has been resolved.
The bug that allowed duplicate automation actions to trigger when a relative date condition was used has been resolved. This was the bug that allowed birthday automations to send multiple communications to contacts.
Load times, particularly on the Automations page, have been improved
*Deleting a Contact
The bug that prevented some contacts from being deleted has been resolved.
*Was released in 2.43.1 on October 11th
Users can now edit a contact from the Context Menu on any page the menu exists. This action is now “Edit” instead of “Update”.
Users can now easily select all teams to push down an Enterprise Automation to.
The bug that prevented some users from creating a transaction has been resolved.
The bug that occasionally caused automation actions to be out of order for a copied automation has been resolved.
The bug that allowed duplicate automation actions to trigger when a relative date condition was used has been resolved. This was the bug that allowed birthday automations to send multiple communications to contacts.
Load times, particularly on the Automations page, have been improved
*Deleting a Contact
The bug that prevented some contacts from being deleted has been resolved.
*Was released in 2.43.1 on October 11th
Release 2.42.0 - October 9th, 2023
When a user attempts to delete a status assigned to a contact/transaction or the status is in use by an automation as a trigger or exit condition, an error toast notification describing why the status cannot be deleted.
Note: If the status is used only as an action for an automation, the status can still be deleted. This will be prevented in a future release.
Users are no longer required to enter a lower-case email for the SimpleNexus integration to work properly. Any upper case letters will be converted to lowercase upon adding the integration.
When a user attempts to delete a status assigned to a contact/transaction or the status is in use by an automation as a trigger or exit condition, an error toast notification describing why the status cannot be deleted.
Note: If the status is used only as an action for an automation, the status can still be deleted. This will be prevented in a future release.
Users are no longer required to enter a lower-case email for the SimpleNexus integration to work properly. Any upper case letters will be converted to lowercase upon adding the integration.
Release 2.41.0 - October 5th, 2023
Users can now use custom contact and transaction fields as conditions in their respective automations.
When a user attempts to delete a custom field in use by any automation (disabled or enabled) they will be prevented from doing so. A list of all automations using the custom field will display and users can open the automation in a new tab to remove the custom field. Note: users are not prevented from deleting a custom field if only the associated merge field is in use.
The timezone of the Enterprise is now used the default timezone when creating new teams.
Users can now use custom contact and transaction fields as conditions in their respective automations.
When a user attempts to delete a custom field in use by any automation (disabled or enabled) they will be prevented from doing so. A list of all automations using the custom field will display and users can open the automation in a new tab to remove the custom field. Note: users are not prevented from deleting a custom field if only the associated merge field is in use.
The timezone of the Enterprise is now used the default timezone when creating new teams.
Release 2.40.0 - October 3rd, 2023
Transaction CSVs can now be exported from the UI. A link to download the file is sent to the user’s email containing all selected records in the manner displayed in the UI at the time of the export.
An issue in which transaction field data could not be deleted from a transaction has been resolved.
An issue in which automations were firing at the wrong time for birthdays has been resolved.
Transaction CSVs can now be exported from the UI. A link to download the file is sent to the user’s email containing all selected records in the manner displayed in the UI at the time of the export.
An issue in which transaction field data could not be deleted from a transaction has been resolved.
An issue in which automations were firing at the wrong time for birthdays has been resolved.
Release 2.39.0 - October 2nd, 2023
Duplicate automation communications have been sent due to a backend function processing the actions multiple times (retrying after an initial attempt). We have disabled the retry functionality to prevent duplicate automation actions from processing, thus preventing duplicate communications from sending, while the root cause of the issue is being fixed.
Duplicate automation communications have been sent due to a backend function processing the actions multiple times (retrying after an initial attempt). We have disabled the retry functionality to prevent duplicate automation actions from processing, thus preventing duplicate communications from sending, while the root cause of the issue is being fixed.
Release 2.38.0 - September 28th, 2023
Two-Factor Authentication is now available. Enterprise owners/admins will need to reach out to their CSM or Support to enable it for their enterprise.
The Timezone card has been moved from Enterprise Profile to Enterprise Settings.
The issue that caused a timeout error when enrolling a large number of existing records in an automation when enabling an automation has been resolved.
Two-Factor Authentication is now available. Enterprise owners/admins will need to reach out to their CSM or Support to enable it for their enterprise.
The Timezone card has been moved from Enterprise Profile to Enterprise Settings.
The issue that caused a timeout error when enrolling a large number of existing records in an automation when enabling an automation has been resolved.
Release 2.36.5 - September 25th, 2023
Users can now updated status via automations! For contact-based automations, the Borrower or Co-Borrower Contact Status can be updated. For transaction-based automations, The Transaction Status or the Contact Status of the Borrower or Co-Borrower can be updated.
We have made UI and backend changes to the MAXA image selector feature, including adding a search bar. Users with dozens/hundreds of MAXA files can now quickly navigate to the desired file.
The issue causing an error page to display when editing a contact’s notes has been resolved.
Users can now updated status via automations! For contact-based automations, the Borrower or Co-Borrower Contact Status can be updated. For transaction-based automations, The Transaction Status or the Contact Status of the Borrower or Co-Borrower can be updated.
We have made UI and backend changes to the MAXA image selector feature, including adding a search bar. Users with dozens/hundreds of MAXA files can now quickly navigate to the desired file.
The issue causing an error page to display when editing a contact’s notes has been resolved.
The issue that prevented users from saving links with a long ending (such as “.mortgage”) has been resolved.
The issue that prevented users from saving links with a long ending (such as “.mortgage”) has been resolved.
Release 2.36.2 - September 19th, 2023
The issue causing text messages to send up to an hour after the allowed timeframe has been resolved.
The issue causing timeouts when automations are processing has been resolved.
Improvements have been made to the app’s loading time, specifically for the Contact Details Page
The issue causing text messages to send up to an hour after the allowed timeframe has been resolved.
The issue causing timeouts when automations are processing has been resolved.
Improvements have been made to the app’s loading time, specifically for the Contact Details Page
Release 2.36.1 - September 14th, 2023
Users can now prevent contacts from being added to an automation after a specified date. Note: A Trigger must exist in order to enable this Automation Behavior.
Users can now prevent contacts from being added to an automation after a specified date. Note: A Trigger must exist in order to enable this Automation Behavior.
Release 2.35.1 - September 12th, 2023
A new section of the Enterprise Profile has been added to set the Enterprise’s Timezone.
The bug removing an associated contact from a task upon saving (editing existing tasks) has been resolved.
The bug causing no contacts to be available in the create contact drawer for the Referred By field has been resolved.
There was an issue when copying a single Playbook Automation (vs. copying multiple at once) when there is an existing automation with the same name. A suffix, (1), (2), etc. should be added. This was not working as expected, and the copied automation could not be saved, as the name was not unique. This has been resolved.
A new section of the Enterprise Profile has been added to set the Enterprise’s Timezone.
The bug removing an associated contact from a task upon saving (editing existing tasks) has been resolved.
The bug causing no contacts to be available in the create contact drawer for the Referred By field has been resolved.
There was an issue when copying a single Playbook Automation (vs. copying multiple at once) when there is an existing automation with the same name. A suffix, (1), (2), etc. should be added. This was not working as expected, and the copied automation could not be saved, as the name was not unique. This has been resolved.
Release 2.35.0 - September 11th, 2023
The context menu (ellipsis) is now available for all contacts, including related contacts, on all pages with tables (Contacts, Transactions, and Tasks).
Merge fields for related users on a transaction are now available. Related Users include:
Enterprise Settings - Expanded Profile for A2P 10DLC Data
The Enterprise Settings Profile page has been updated. All data required for initial A2P 10DLC registration can be entered in the Business Details and Point of Contact sections.
Note: This is currently data entry only (this does not trigger A2P 10DLC registration via the APIs).
The bug causing the task drawer not to open when clicked in the Tasks widget on the Dashboard has been fixed.
The bug causing Related Playbook Automations to display incorrectly when viewing details of a Playbook Automation has been fixed.
The bug causing fields of a previously viewed/edited transaction to prepopulate when creating a new transaction has been fixed.
The context menu (ellipsis) is now available for all contacts, including related contacts, on all pages with tables (Contacts, Transactions, and Tasks).
Merge fields for related users on a transaction are now available. Related Users include:
Enterprise Settings - Expanded Profile for A2P 10DLC Data
The Enterprise Settings Profile page has been updated. All data required for initial A2P 10DLC registration can be entered in the Business Details and Point of Contact sections.
Note: This is currently data entry only (this does not trigger A2P 10DLC registration via the APIs).
The bug causing the task drawer not to open when clicked in the Tasks widget on the Dashboard has been fixed.
The bug causing Related Playbook Automations to display incorrectly when viewing details of a Playbook Automation has been fixed.
The bug causing fields of a previously viewed/edited transaction to prepopulate when creating a new transaction has been fixed.
Release 2.34.0 - September 7th, 2023
Global Search is more user friendly, and can be opened when viewing any page with a Team ID in the URL (i.e. not enterprise settings) using hotkeys: Ctrl + K (PC) or Cmd + K (Mac).
We now only display a type of Playbook Automation if at least one automation is available.
Our first iteration of the Aidium API has been released for Beta Testing. Endpoints have been created for Contacts and Transactions. Any requests for an API Key must be submitted to the Product Team for approval. For now, we are limiting this to Enterprise clients.
The ability to restrict Encompass updates to specific folders (whitelisting) has been added. This has been enabled for NEO’s Encompass Instance. Any requests for whitelisting loan folders for an Encompass integration must be submitted to the Product Team for approval.
We have resolved the issue that prevented line breaks from being reflected correctly in outbound emails.
We have resolved the issue causing “no content” to display in the automations builder action step for emails. This was occurring for automations installed from the playbook modal.
We have removed the extra/duplicate line spacer when a task had no associated contact or description
We have fixed the bug that prevented default contact statuses, "Prospect" and "Lead", from being created for New Enterprises added in Retool.
Global Search is more user friendly, and can be opened when viewing any page with a Team ID in the URL (i.e. not enterprise settings) using hotkeys: Ctrl + K (PC) or Cmd + K (Mac).
We now only display a type of Playbook Automation if at least one automation is available.
Our first iteration of the Aidium API has been released for Beta Testing. Endpoints have been created for Contacts and Transactions. Any requests for an API Key must be submitted to the Product Team for approval. For now, we are limiting this to Enterprise clients.
The ability to restrict Encompass updates to specific folders (whitelisting) has been added. This has been enabled for NEO’s Encompass Instance. Any requests for whitelisting loan folders for an Encompass integration must be submitted to the Product Team for approval.
We have resolved the issue that prevented line breaks from being reflected correctly in outbound emails.
We have resolved the issue causing “no content” to display in the automations builder action step for emails. This was occurring for automations installed from the playbook modal.
We have removed the extra/duplicate line spacer when a task had no associated contact or description
We have fixed the bug that prevented default contact statuses, "Prospect" and "Lead", from being created for New Enterprises added in Retool.
Release 2.33.0 - August 31st, 2023
Users can now export a contact CSV. The CSV includes all selected contacts and enabled columns at the time of the export. An email is sent to the user. Clicking the link in the email will download the CSV file.
Users can now export a contact CSV. The CSV includes all selected contacts and enabled columns at the time of the export. An email is sent to the user. Clicking the link in the email will download the CSV file.
2.32.0 - August 21, 2023
Tags are now being created on the team when a team member creates an automation from a playbook that uses tags.
When clicking the + button in the Kanban view, the status is automatically set to match the column from which the + button was clicked.
When inviting a user to teams, the list now displays alphabetically
The error that displayed when viewing Automations with Type “Simple Nexus” has been fixed.
The error that prevented users from reassigning a contact has been fixed.
The bug that prevented tags from being properly created, if one with the same name exists on another team on the enterprise, has been fixed
The error that prevented users from updating a contact or transaction status name has been fixed.
Tags are now being created on the team when a team member creates an automation from a playbook that uses tags.
When clicking the + button in the Kanban view, the status is automatically set to match the column from which the + button was clicked.
When inviting a user to teams, the list now displays alphabetically
The error that displayed when viewing Automations with Type “Simple Nexus” has been fixed.
The error that prevented users from reassigning a contact has been fixed.
The bug that prevented tags from being properly created, if one with the same name exists on another team on the enterprise, has been fixed
The error that prevented users from updating a contact or transaction status name has been fixed.
Release 2.31.1 - August 14th, 2023
Team Settings no longer has a cascading menu. Selecting Team Settings will open a new page with its own primary navigation for all submenus.
We have added a scroll bar to the MAXA Image Selector. Users can now see more than their 12 most recently updated MAXA files.
When sending an email in an Automation, in addition to selecting a contact, users can manually type in any email address in the To field.
We can now create out-of-the box Aidium Automations that include Exit Conditions.
Team members with Encompass and SimpleNexus integration will now display their integrated User ID (Encompass) or Email (SimpleNexus) to the right of their name on the Team Integrations page.
Due to technical issues, in-sequence call forwarding has been removed. All numbers that previously had this configuration will now forward calls to all forwarding numbers simultaneously. See this Knowledge Base article for full details on how the forwarding numbers feature works.
An issue in which emails were not properly sending from Automations has been resolved.
Team Settings no longer has a cascading menu. Selecting Team Settings will open a new page with its own primary navigation for all submenus.
We have added a scroll bar to the MAXA Image Selector. Users can now see more than their 12 most recently updated MAXA files.
When sending an email in an Automation, in addition to selecting a contact, users can manually type in any email address in the To field.
We can now create out-of-the box Aidium Automations that include Exit Conditions.
Team members with Encompass and SimpleNexus integration will now display their integrated User ID (Encompass) or Email (SimpleNexus) to the right of their name on the Team Integrations page.
Due to technical issues, in-sequence call forwarding has been removed. All numbers that previously had this configuration will now forward calls to all forwarding numbers simultaneously. See this Knowledge Base article for full details on how the forwarding numbers feature works.
An issue in which emails were not properly sending from Automations has been resolved.
Release 2.31.0 - August 7th, 2023
Partners created/updated via Encompass (related contacts who are not the Borrower or Co-Borrower on the loan) will have their Contact Type set to Partner.
Send an email/text, add a note, add a task, or be redirected to the contact details page for the associated contact in a transaction.
We now have the ability to delete enterprises in Retool. Enterprise Owner(s) will receive a confirmation email before the enterprise is deleted.
Emails are now sent to all recipients instead of separate emails being sent to the CC and BCC recipients.
The issue in which the contact details page would display an error for contacts created/updated via Zapier with multiple lines mapped in Notes has been resolved.
The issue in which a related contact could not be unlinked properly has been resolved.
Partners created/updated via Encompass (related contacts who are not the Borrower or Co-Borrower on the loan) will have their Contact Type set to Partner.
Send an email/text, add a note, add a task, or be redirected to the contact details page for the associated contact in a transaction.
We now have the ability to delete enterprises in Retool. Enterprise Owner(s) will receive a confirmation email before the enterprise is deleted.
Emails are now sent to all recipients instead of separate emails being sent to the CC and BCC recipients.
The issue in which the contact details page would display an error for contacts created/updated via Zapier with multiple lines mapped in Notes has been resolved.
The issue in which a related contact could not be unlinked properly has been resolved.
Release 2.30.0 - August 2nd, 2023
Send an email/text, add a note, add an additional task, or be redirected to the contact details page for the associated contact in a task.
When a Transaction is created via Zapier’s Transaction Action, we automatically set the Loan Officer and the Transaction Assignee to be the integrated user.
The current production version of Zapier is now 3.3.1
Engage Co-Borrowers in Contact-based Automations
Co-borrowers can now be the recipients of email and/or SMS actions in contact-based automations, just like Borrowers, Referrers, etc.
Preview Playbook Automations
When browsing the available automations in our Playbook, customers can preview the actions of the automation before copying it to their team.
Transaction Assignee Automation Default
All email actions in transaction-based automations are now by default set to be from the transaction assignee instead of the contact owner. This only applies to newly created automations.
SendGrid Email Replies Routed to User’s Email
When a contact replies to an email sent through SendGrid, we now route that to the user’s email address.
Prepopulate Primary Borrower When Creating Transaction
When creating a transaction from the contact details page, that contact is automatically added as the Primary Borrower.
When we receive loan data from Encompass for an integrated user, if there is an existing transaction with a matching loan number, we will update it, regardless of the creation method for the transaction (i.e. CSV).
Fixes the issue that was preventing some existing users from being added to a new team successfully.
Fixes the issue that was causing an Unknown Error to display when accessing the Users page in Enterprise Settings.
Send an email/text, add a note, add an additional task, or be redirected to the contact details page for the associated contact in a task.
When a Transaction is created via Zapier’s Transaction Action, we automatically set the Loan Officer and the Transaction Assignee to be the integrated user.
The current production version of Zapier is now 3.3.1
Engage Co-Borrowers in Contact-based Automations
Co-borrowers can now be the recipients of email and/or SMS actions in contact-based automations, just like Borrowers, Referrers, etc.
Preview Playbook Automations
When browsing the available automations in our Playbook, customers can preview the actions of the automation before copying it to their team.
Transaction Assignee Automation Default
All email actions in transaction-based automations are now by default set to be from the transaction assignee instead of the contact owner. This only applies to newly created automations.
SendGrid Email Replies Routed to User’s Email
When a contact replies to an email sent through SendGrid, we now route that to the user’s email address.
Prepopulate Primary Borrower When Creating Transaction
When creating a transaction from the contact details page, that contact is automatically added as the Primary Borrower.
When we receive loan data from Encompass for an integrated user, if there is an existing transaction with a matching loan number, we will update it, regardless of the creation method for the transaction (i.e. CSV).
Fixes the issue that was preventing some existing users from being added to a new team successfully.
Fixes the issue that was causing an Unknown Error to display when accessing the Users page in Enterprise Settings.
Release 2.29.0 - July 17th, 2023
We are now able to integrate with SimpleNexus. When a loan application is abandoned or submitted, the contact is created/updated in Aidium and a tag is added:
* We are still finalizing our out-of-the-box Playbook Automation for Simple Nexus, and we will not be officially rolling this out to customers until that is completed.
A full walkthrough of the integration and how it works can be found in the support article found on the knowledge base.
Users can access the MAXA design studio page from the Team Settings > Integrations page. The design studio is now an overlay instead of a full page. The previous “design-studio” URL will redirect the user to the integrations page.
Aidium emails (@aidium.email) now include the full name of the customer to improve email appearance in end-consumers’ inboxes.
When uploading transactions via CSV customers have the option to choose with which team member to associate the uploaded transactions.
Whether it is a contact or transaction CSV upload, users will now receive an email containing the CSV of the records that were unable to be uploaded due to various errors.
Whether it is a contact or transaction CSV upload, users will now receive an email containing the CSV of the records that were unable to be uploaded due to various errors.
Actions will no longer be executed for newly created records that enter automations with “Delay until Day” actions in the past, i.e. a contact record created on July 15th will no longer receive the July 4th email.
Whether it is a contact or transaction CSV upload, these uploaded statuses will now appear on the dashboard.
Selecting options on mobile (e.g., from a large list) will now load and render properly.
We are now able to integrate with SimpleNexus. When a loan application is abandoned or submitted, the contact is created/updated in Aidium and a tag is added:
* We are still finalizing our out-of-the-box Playbook Automation for Simple Nexus, and we will not be officially rolling this out to customers until that is completed.
A full walkthrough of the integration and how it works can be found in the support article found on the knowledge base.
Users can access the MAXA design studio page from the Team Settings > Integrations page. The design studio is now an overlay instead of a full page. The previous “design-studio” URL will redirect the user to the integrations page.
Aidium emails (@aidium.email) now include the full name of the customer to improve email appearance in end-consumers’ inboxes.
When uploading transactions via CSV customers have the option to choose with which team member to associate the uploaded transactions.
Whether it is a contact or transaction CSV upload, users will now receive an email containing the CSV of the records that were unable to be uploaded due to various errors.
Whether it is a contact or transaction CSV upload, users will now receive an email containing the CSV of the records that were unable to be uploaded due to various errors.
Actions will no longer be executed for newly created records that enter automations with “Delay until Day” actions in the past, i.e. a contact record created on July 15th will no longer receive the July 4th email.
Whether it is a contact or transaction CSV upload, these uploaded statuses will now appear on the dashboard.
Selecting options on mobile (e.g., from a large list) will now load and render properly.
Release 2.28.0 - July 3rd, 2023
We have added a “preferred” designation for related contacts. When merge fields are used, they will pull data from the preferred related contact.
Transactions can now be updated when using the CSV upload feature.
We have added a “preferred” designation for related contacts. When merge fields are used, they will pull data from the preferred related contact.
Transactions can now be updated when using the CSV upload feature.
Release 2.27.0 - June 23rd, 2023
Users can now select their MAXA creations within the email builder. It will load the most recently accessed files in MAXA from the user’s account. Note: There is currently no way to resize an image that has been added. This will be available in the future.
Additional Fields have been added to the Create Contact action in Zapier:
Additional Fields have been added to the Create Transaction action in Zapier:
Application Date is now brought over from Encompass loans.
Provides the ability to create rules that instruct automations on when a contact should no longer be a part of the automation's workflow and remove them before the automations completed the remaining actions. This functionality is particularly crucial for long-term automations.
Example: a lead engagement automation that consistently engages with leads over time, but once a lead responds back, there is no longer a business necessity to continue engaging them.
Speed Improvements
The communications page should be loading much more quickly now (less than 3 seconds). Upon subsequent openings of the page, it is substantially faster.
There are a number of places in the app where we search an entire list of contacts or transactions. This fix greatly increases the speed in which these lists are loaded and now provides the ability to search on these fields, including:
The issue that caused dates mapped from 3rd party sources to populate 1 day before the actual value has been fixed.
The issue which caused a Zap to fail upon updating certain date fields (i.e. application date) is resolved.
Create Transaction Zaps will no longer fail because a related contact does not have all required fields. The transaction and other related contacts will still be created/updated, but the related contact with invalid or incomplete data will not be.
Incorrect field mapping has been fixed:
Encompass: Retry on Create/Update Failure
If we hit Encompass concurrency limits, causing a transaction not to be created or update, we now put it in a queue to retry later.
We have fixed the issue that allowed contacts to be created via Encompass without a First and Last Name (user could not access contact details pages for these contacts). Contacts will not be created if their First and Last Name is missing.
Users can now select their MAXA creations within the email builder. It will load the most recently accessed files in MAXA from the user’s account. Note: There is currently no way to resize an image that has been added. This will be available in the future.
Additional Fields have been added to the Create Contact action in Zapier:
Additional Fields have been added to the Create Transaction action in Zapier:
Application Date is now brought over from Encompass loans.
Provides the ability to create rules that instruct automations on when a contact should no longer be a part of the automation's workflow and remove them before the automations completed the remaining actions. This functionality is particularly crucial for long-term automations.
Example: a lead engagement automation that consistently engages with leads over time, but once a lead responds back, there is no longer a business necessity to continue engaging them.
Speed Improvements
The communications page should be loading much more quickly now (less than 3 seconds). Upon subsequent openings of the page, it is substantially faster.
There are a number of places in the app where we search an entire list of contacts or transactions. This fix greatly increases the speed in which these lists are loaded and now provides the ability to search on these fields, including:
The issue that caused dates mapped from 3rd party sources to populate 1 day before the actual value has been fixed.
The issue which caused a Zap to fail upon updating certain date fields (i.e. application date) is resolved.
Create Transaction Zaps will no longer fail because a related contact does not have all required fields. The transaction and other related contacts will still be created/updated, but the related contact with invalid or incomplete data will not be.
Incorrect field mapping has been fixed:
Encompass: Retry on Create/Update Failure
If we hit Encompass concurrency limits, causing a transaction not to be created or update, we now put it in a queue to retry later.
We have fixed the issue that allowed contacts to be created via Encompass without a First and Last Name (user could not access contact details pages for these contacts). Contacts will not be created if their First and Last Name is missing.
2.21.0 - May 19th, 2023
With the help of custom fields, you can now customize the CRM to capture the most important data needed to convert more loans and save them time in the process.
We support both contact-based and transaction-based custom fields. Either one of these can have text, numeric or date-based fields - the possibilities for customization are virtually endless!
We also support using custom field values as merge fields in outgoing communications, so the messages sent can feel unique based on their specific preferences and style.
Custom fields are accessed under the Team Settings drawer and can be added with a few clicks - no need for reaching out to our support team or involving a developer.
Once there, users can add custom fields to appear on Contacts or Transactions.
In the future, custom fields will also be able to:
When creating a new automation, you will now see the number of eligible contacts (or transactions, when using a transaction-based automation). This will make it clear how many records will receive communications or other actions set up in the automation when the automation is enabled and the setting to “enroll existing records” is also enabled.
We now have a search component that dramatically decreases the load times for searching through large lists of contacts - both adding a related contact and adding an associated contact to a task are done quickly and easily.
With the help of custom fields, you can now customize the CRM to capture the most important data needed to convert more loans and save them time in the process.
We support both contact-based and transaction-based custom fields. Either one of these can have text, numeric or date-based fields - the possibilities for customization are virtually endless!
We also support using custom field values as merge fields in outgoing communications, so the messages sent can feel unique based on their specific preferences and style.
Custom fields are accessed under the Team Settings drawer and can be added with a few clicks - no need for reaching out to our support team or involving a developer.
Once there, users can add custom fields to appear on Contacts or Transactions.
In the future, custom fields will also be able to:
When creating a new automation, you will now see the number of eligible contacts (or transactions, when using a transaction-based automation). This will make it clear how many records will receive communications or other actions set up in the automation when the automation is enabled and the setting to “enroll existing records” is also enabled.
We now have a search component that dramatically decreases the load times for searching through large lists of contacts - both adding a related contact and adding an associated contact to a task are done quickly and easily.
