Added the ability to filter Decisions based on Bolt App Reader analysis values (Highly Qualified, Qualified, Natural, Not Qualified, Highly Not Qualified).

Resolved an issue where auto-filled fields were not recognized as completed, preventing them from contributing to application progress.

Resolved an issue where applicants were redirected to the registration page instead of the dashboard after account creation.

Resolved an issue where the Gender field displayed as “No” in the application PDF instead of the selected value.

Resolved an issue where changing an Application Site navigation menu item to an external link did not save and reverted immediately.

Resolved an issue where date formatting did not apply correctly to custom date picker tokens used in Application dashboard messages.

Resolved an issue where school logos in Decisions package letters displayed left-aligned despite being set to center alignment.

Resolved an issue where user tokens were not functioning correctly in Decision Letters.

Resolved an issue where the “Release” stage option was incorrectly available for IA rules with the “Change Status” action, even though released decisions cannot be updated.

Expanded the App Reader Agent to include reading Info Request Form Data (Info Request Preview) in addition to files uploaded to request forms (Info Request Overview).

Added full keyboard navigation and screen reader support to the Appointments feature to meet accessibility standards, ensuring all interactive elements are accessible and clearly indicated.

Updated appointment calendar invites and related communications to display students’ preferred names instead of their legal first names.

Resolved an issue where students received duplicate emails when scheduling or updating appointments by adding HTML markup to calendar events posted to connected Outlook calendars. This markup allows Outlook’s internal mechanism to handle email notifications to students, while Element now checks for connected Outlook calendars and skips sending its own email to prevent duplicates. As a result, both the student and internal user each receive a single, correctly triggered email, with this behavior applying only to admins who have integrated their Outlook calendars.

Resolved an issue where the appointment Type filter was not being properly respected at the user level, causing other appointment types to appear.

Resolved an issue where the appointment availability start and end date filters did not apply correctly.

Resolved an issue where students incorrectly received an “upcoming appointment” email after a past appointment was marked as Not Attended.

Added the ability to make inline edits to Bolt Agent Job messages (email subject lines, bodies, and formatting, as well as SMS message bodies), before approving.

Added a bulk Bolt Agent Job approval function allowing you to review, approve, reject, or provide feedback on multiple items at once.

Added dedicated Bolt Agent pages with scoped views for “My Approvals” and “Jobs,” including Bulk View support.

Enhanced the Bolt Agent job enrollment activity/history UI and added timestamps for “Added to Job” and “Marked as Goal Completed” in the activity timeline.

Added a new Paid Form trigger that automatically enrolls students into a Bolt Agent Job when a specified form payment is completed.

Added new triggers for Survey Response - Positive Sentiment and Survey Response - Negative Sentiment to add contacts to a Bolt Agent Job based on Survey AI Sentiment Analysis results.

Resolved several issues where enrollments were incorrectly ending up in an errored state, and added functionality to allow users to bulk retry enrollments.

Resolved an issue where a Bolt Agent’s name could not be edited after creation.

Resolved an issue where “Agent Details” displayed when the agent name was null instead of showing the Agent Type.

Resolved an issue where unsubscribes were sometimes not honored when using short codes.

Resolved an issue where adding a link to Campaign text did not automatically apply link formatting, requiring manual formatting adjustments.

Resolved an issue where the sharable preview link option was missing for SMS campaigns and only appeared when the Email channel was enabled.

Updated the Conversations inbox to display Knowledge Hub citations for in a separate light blue bubble (for Email and SMS), clearly distinguishing them from student-facing messages.

Added a new “No Staff Reply” filter in the Conversations inbox to surface conversations without a staff response, excluding replies from Bolt Agent or automated system messages.

Resolved an issue where in some cases Knowledge Hub sources were not properly hyperlinked in Messenger conversations.

Resolved an issue where Knowledge Hub source citation hyperlinks appeared above the agent’s response instead of below in Messenger conversations.

Added support to display both LMS and SIS source identifier chips in the Courses table when SIS-synced data is enriched by an LMS integration.

Added the Section Code to the header of the Section Enrollment side sheet for improved visibility.

Resolved an issue where the search feature was not functioning on the Courses page.

Updated the warning modal shown when deleting custom fields in Field Management to include clearer messaging about the permanent impact and potential breakage in related forms, applications, segments, and imports/exports.

Resolved an issue in the Documents Bin where the previously viewed Document Type persisted and displayed for files that did not have a Document Type assigned.

Resolved an issue where a 500 error occurred when attaching a CSV file during import.

Resolved an issue where the County field was not importing correctly when using the Organization import template.

Resolved an issue where export email notifications were not being sent following the AWS outage.

Resolved an issue where the event attendee export completed but the file never downloaded, leaving the loading bar stuck indefinitely.

Added a new Paid Form trigger that automatically enrolls students into a Journey when a specified form payment is completed.

Added new triggers for Survey Response - Positive Sentiment and Survey Response - Negative Sentiment to trigger journey enrollment based on Survey AI Sentiment Analysis results.

Resolved an issue where the Markdown field in the Microsites forms behaved like a text box.

Resolved an issue where the GTM tag was not firing on Microsites.

Added email validation to areas where it was previously missing, such as the contact profile.

Added the ability to use the address subfield “province” as a filter in segments.

Added checklist item visibility changes as a trigger for segment evaluations.

Resolved an issue where the “Copy” button for email in the contact’s demographic section was not functioning properly.

Resolved an issue where the city field value disappeared during address lookup when the city included “Township,” caused by the Google Lookup API treating minor subdivisions differently.

Resolved an issue where documents could not be previewed within the PDF viewer on the profile card side sheet.

Resolved an issue where date conditions in segments displayed as “infinity to infinity” instead of the selected date range.

Resolved an issue where segment filter groupings could not be updated from “All” to “Any.”

Resolved an issue where new internal users could be added without completing all required fields.

Added AI Sentiment Analysis to survey responses, providing sentiment scores (positive, negative, neutral), summaries, and reasoning, along with new triggers for workflows, journeys, and bolt agent jobs based on positive or negative sentiment.

Added a new Paid Form trigger that automatically enrolls students into a Workflow when a specified form payment is completed.

Added new triggers for Survey Response - Positive Sentiment and Survey Response - Negative Sentiment to automate workflow actions based on Survey AI Sentiment Analysis results.

Resolved an issue where workflow triggers weren't working correctly when multiple letters of recommendation were submitted for the same application.

Resolved an issue where the “Edit Own Workflows” permission was not applying to Rules.