Product Improvements: March and April 2026

CRM completed work:

The CRM updates focused on cleaner contact data, more reliable workflows, better email and Gmail syncing, improved inbox permissions, stronger listing alert delivery, more accurate MLS/listing data, better Zapier/Twilio reliability, and improved login/account stability.

CMS / IDX Website completed work:

The website updates focused on better property search, cleaner filters, more accurate maps and location handling, improved saved searches, faster listing detail pages, better mobile/tablet layouts, stronger form/auth behavior, cleaner listing cards, and improved SEO/schema structure.

Biggest themes completed across both systems:

More reliable listing alerts and saved searches
Better CRM email, inbox, and Gmail behavior
Cleaner contact and lead data
More accurate MLS/listing synchronization
Better IDX website search and map behavior
Faster listing detail pages
Stronger SEO/schema foundation
Better mobile and UI polish
More stable workflows, integrations, and automation
Better login, session, and deep-link behavior across CRM and CMS

CRM Updates Completed

1. Contact Data, Lead Records, and CRM Data Accuracy

A major amount of CRM work was completed around making contact records, imported leads, custom fields, source data, and listing/contact relationships more reliable.

Completed CRM improvements include:

Fixed contacts created through Registration Forms so First Name, Last Name, and Phone details are properly captured.
Added created_at and updated_at support for Areas, Area Groups, and Jobs modules for better tracking and reporting.
Fixed custom field values so they reliably appear in the Contacts table.
Corrected Address filter behavior so address-based filtering uses the proper field type.
Improved lead import mapping so birthdays and tags are not mismapped during imports.
Added/expanded CRM contact fields and improved field consistency across accounts.
Cleaned up contact fields and saved views to reduce duplication and confusion.
Improved contact and listing source/location data to create clearer origin details.
Stabilized contact record navigation so users are not unexpectedly bounced out of contact records.

Plain-English impact: contact records should be cleaner, filters should behave more predictably, imports should be more accurate, and agents should have more confidence in the data they are seeing.

2. CRM Workflows and Automation

Several releases focused on making workflows more dependable, especially around branching, email sending, appointment triggers, tags, task assignment, and lead assignment.

Completed CRM workflow improvements include:

Improved workflow stability for saved/favorited property triggers so the right automations fire without duplication.
Improved multiple appointment triggers so appointment-based automations behave more reliably.
Improved message collection support so inbound messages can be used within workflows.
Fixed branch logic errors in workflows.
Fixed workflow branch logic and tag selection mismatch issues.
Added more flexible tag-based workflow triggers for starting/stopping workflows when tags are added or removed.
Stabilized workflow branching and workflow deletion.
Fixed MongoDB ID errors impacting workflows.
Fixed workflow emails not being saved or failing to send.
Corrected workflow email delivery status in contact logs so logs no longer show emails as successful when they were not actually delivered.
Enabled workflow tasks to be reliably assigned to the Contact Owner.
Removed the “Nurture” status from new lead-source prefixed workflows to standardize workflow stages.
Fixed cloned workflows defaulting lead assignment to the GGMS Demo Agency instead of the correct account owner.

Plain-English impact: workflows should be more reliable, easier to trust, and less likely to misfire, duplicate actions, assign leads incorrectly, or show inaccurate email delivery information.

3. Email, Inbox, Gmail, and Communication Improvements

A large CRM focus was improving email visibility, Gmail sync, inbox reliability, email threading, attachments, permissions, and email-to-contact matching.

Completed CRM communication improvements include:

Fixed Gmail-integrated emails so they open reliably in the CRM.
Added agency-level email integration visibility with permission controls.
Fixed inbound emails so they attach to the correct contact records.
Improved email threading, CC handling, and contact association.
Improved separation between sent and received messages inside the inbox.
Improved Gmail receive/reply sync back into the CRM.
Improved email polling and sync logic for a more complete email history.
Improved email content formatting in the CRM inbox.
Ensured incoming email attachments are captured and accessible from the CRM.
Expanded email polling to include prior lead engagements where appropriate.
Implemented email filtering based on CRM contacts and agent access.
Corrected Inbox navigation so opening or composing email no longer redirects users back to Contacts unexpectedly.
Fixed synced email ordering so CRM timelines use the original sent/received date instead of import time.

Plain-English impact: email history should be easier to follow, better connected to contacts, more accurately synced from Gmail, and better protected by permissions.

4. Listing Alerts, Saved Searches, and Alert Email Reliability

This was one of the biggest themes across the releases. The CRM work focused heavily on listing alert reliability, saved search behavior, alert templates, email delivery, deep links, and listing card consistency.

Completed CRM listing alert improvements include:

Fixed issues preventing some clients from setting up listing alerts or saved searches.
Improved listing alert delivery reliability.
Fixed automated email alerts that were sending unresolved template placeholders instead of property data.
Fixed email formatting issues in templates.
Tuned slow listing alert queries to reduce latency and improve alert generation.
Moved Listing Alerts to a system-wide email template for consistent design and behavior across agencies.
Implemented updated Listing Alerts card design with dynamic branding based on the assigned contact owner.
Ensured emails sent from Contacts → Collections → Listings use the latest system-wide design.
Updated the “Adjust your filters” CTA so it routes to the saved-search management view.
Improved outbound email reliability when SendGrid showed sent/delivered but recipients did not receive messages.
Added missing Property Type to listing cards for manual alerts.
Added auto-login URLs and embedded contact/lead auth tokens in alert cards for deep-link behavior.

Plain-English impact: listing alerts should be more reliable, more visually consistent, better branded, less likely to fail, and easier for leads to click through from email.

5. Listings, MLS Data, and CRM/Website Data Sync

Several CRM releases addressed listing sync, MLS accuracy, status mismatches, API improvements, and property data consistency between the CRM and website.

Completed CRM listing/MLS improvements include:

Fixed listing visibility and MLS data sync issues where listings were not appearing correctly in the CRM and/or website.
Fixed unique listings from multiple MLS sources so they store correctly and remain unique.
Added a country key to Listings API attributes.
Expanded the Listings API response to include School and District fields.
Overhauled listings sync cron jobs for more consistent and timely data sync.
Fixed listing status mismatches between MLS, CRM, and website display.
Improved listings sync jobs to better handle volume and more reliable updates.
Corrected agent office listing filtration in the CRM.

Plain-English impact: MLS/listing data should be more consistent, listing statuses should be more accurate, and listing-related CRM views should better align with what appears on the website.

6. CRM Integrations, Twilio, Zapier, Login, and Platform Stability

Several fixes focused on infrastructure-level reliability, account access, Twilio, Zapier, OAuth, permissions, and general CRM stability.

Completed CRM platform improvements include:

Improved Twilio integration SID number handling.
Completed number-port request work and restored Twilio webhook handling for ported numbers.
Fixed Zapier integration so CRM field values are available for automation.
Added Zapier support for source fields and source values.
Fixed Zapier flows so Stage, Type, and Status can be updated reliably.
Fixed login/account access issues with extended load times and verification loops.
Addressed Google OAuth and site-speed-related issues observed during support.
Improved inbox permission enforcement so delete/visibility actions respect user permissions.
Fixed unauthorized inbox delete actions that appeared successful but did not actually complete.
Tightened auto-login token security so expired tokens are no longer accepted.
Fixed a CRM lock-up/unresponsive scenario triggered by a contact/search flow.

Plain-English impact: integrations, permissions, login, Twilio, and Zapier should be more stable and more predictable.

CMS / IDX Website Updates Completed

1. Website Search, Filters, and OmniSearch

The CMS/IDX Website work heavily focused on improving property search, OmniSearch, filters, location handling, school/neighborhood searches, and saved search behavior.

Completed website search improvements include:

Improved Advanced Search layout on iPad Pro.
Fixed city search so it respects the state in the URL.
Fixed infinite loading when selecting certain filters like Time on Site or Closed Market.
Improved property type filter spacing and UI.
Fixed mobile Advanced Search property type behavior.
Reduced flicker in Advanced Search on area pages.
Fixed filters that had matching listings but still returned no results.
Fixed market type toggle visibility and accuracy.
Fixed price filter behavior on area pages.
Ensured selected price range displays correctly in Advanced Search.
Added Senior Community as an Advanced Search filter.
Fixed MLS major/minor category filtering and display.
Addressed multiple OmniSearch accuracy/reliability issues.
Updated OmniSearch suggestions to bold typed or matched text.
Fixed OmniSearch UI issues like icon sizing, placeholder overlap, weak borders, and long-error toast overflow.
Improved neighborhood search behavior in global search.
Filtered irrelevant “buildings” from OmniSearch results.

Plain-English impact: visitors should get cleaner, more accurate search results, and the search experience should feel more polished across cities, neighborhoods, schools, MLS filters, and property types.

2. Maps, Location Boundaries, and Saved Search Location Behavior

Several website releases focused on map accuracy, pins, boundaries, copied URLs, saved searches, and location-based search behavior.

Completed map/location improvements include:

Fixed map pins showing when Listings API returned no properties.
Corrected map pin data point configuration on Search Results pages.
Fixed inaccurate map highlighting when duplicate place names exist in multiple regions.
Improved map zoom when loading saved searches with MLS major/minor filters.
Fixed Kern County incorrectly converting to East Bakersfield.
Improved school search map zoom so pins display properly.
Fixed listing cards opening behind map pins in Safari.
Preserved applied filter counts when opening copied URLs in new tabs.
Fixed URL behavior where reselecting an already-selected location reset the URL and appended duplicate query parameters.
Fixed shared URL handling so location boundaries are preserved when opening links with multiple selected locations.
Fixed stale UI state issues after removing collection/ACF fields, including map boundary, selected value, and title.

Plain-English impact: location-based search, maps, shared search URLs, saved search maps, and school/neighborhood searches should be more accurate and easier for website visitors to use.

3. Listing Cards, Listing Details, Featured Properties, and Property Display

A lot of CMS work focused on making listings look better, load faster, display correct data, and behave consistently across layouts.

Completed listing display improvements include:

Fixed listing card tag overlap.
Fixed listing cards with no images in map view.
Fixed listing card stretching on large screens in map view.
Fixed Featured Listings carousel navigation.
Fixed Featured Properties widget pagination/crash issues.
Fixed MLS logo display on Featured Properties widget.
Improved Featured Properties widget HTML/schema and listing metadata.
Added ld+json structured data to Featured Properties cards.
Cleaned up listing overview tag display.
Updated property type and standard-status icons to better match familiar real estate UX patterns.
Fixed Similar Listings / Featured Properties behavior so listing cards open in the same tab.

Plain-English impact: listings should look cleaner, behave more consistently, and better support both visitor browsing and SEO.

4. Listing Detail Page Performance and Loading Experience

Listing detail performance became a major focus in April.

Completed performance improvements include:

Added server-side Listing Details skeletons and removed unused HTML after skeleton usage.
Removed a legacy Listing Details CSS file to avoid styling conflicts.
Started layout caching and API caching for listing details.
Added server-side caching for listing-details API responses.
Reduced listing-details wait time by running layout and listing-details API requests in parallel.
Ran PageSpeed audits and implemented listing-detail recommendations.
Resolved severe production slowness where listing detail pages could take 2–4 minutes to load.
Disabled WP Rocket JS defer where it hurt first render.
Added missing skeleton loaders so sections do not render blank while data loads.

Plain-English impact: listing detail pages should load faster, feel smoother, and avoid blank/flickering states during loading.

5. Saved Searches and Saved Properties

Saved search and saved property behavior received several fixes across releases.

Completed saved search/property improvements include:

Fixed Save button loading state when editing saved searches.
Fixed saved property card layout issues on large screens.
Fixed Saved Searches frequency dropdown usability.
Fixed Saved Properties rename menu placement.
Fixed saved search frequency dropdown incorrectly opening when clicking saved searches.
Updated saved search cards to display state names in all caps.
Fixed saved-search update issues with dynamic tags.
Improved saved search deep-link behavior, including filters, modals, saved search actions, and unsubscribe flows.

Plain-English impact: users should have fewer problems saving searches, adjusting alert frequency, opening saved searches, and managing saved properties.

6. Website Forms, Authentication, Auto-Login, and Deep Links

Several CMS updates focused on authentication, sign-in behavior, contact forms, auto-login from email links, and session handling.

Completed CMS auth/form improvements include:

Fixed Sign In header button behavior so it opens the expected popup instead of redirecting incorrectly.
Fixed Ask a Question action for guest users so the correct auth popup appears.
Fixed phone placeholder behavior in the Contact Agent form.
Fixed duplicate forms on Sign Up and Login pages.
Standardized toast notifications for Sign In and Contact Agent forms.
Fixed accurate login state in the User Profile widget.
Improved sign-in redirect when a valid local auth session already exists.
Added auto-login support on CMS for CRM email deep links.
Fixed CMS auth/session mismatches where users appeared logged in but could not perform authenticated actions.
Prevented Sign In modal from appearing while auto-login is still in progress.
Added clearer feedback when a listing-alert link requires login due to expiration.
Fixed broken auth states after expired auto-login tokens.
Reduced sign-out delay and improved logout state.

Plain-English impact: clients clicking listing alert emails should have a smoother login/deep-link experience, and website forms/authentication should behave more consistently.

7. Mobile, Tablet, UI, and Editor Experience

There were many smaller but meaningful UI/UX fixes across mobile, tablet, dashboards, widgets, editor tools, buttons, forms, and loading states.

Completed UI/UX improvements include:

Fixed skeleton loaders across listing overview, smaller screens, hidden/favorite properties, and loading states.
Fixed Ask a Question and Request Tour card alignment.
Fixed tour card error toast alignment.
Fixed transparent dropdown issues in editor controls.
Added style controllers for Tour Request and Ask a Question success cards.
Added controllers for Price dropdown configuration.
Fixed testimonial widget star ratings.
Fixed collection dropdown reliability in Page Editor.
Fixed “Any” filter option alignment on mobile.
Revamped the search widget UI for better usability and consistency.
Fixed editor-mode form re-rendering during configuration.
Increased mobile page navigation dropdown width to prevent truncation.
Fixed profile initials rendering so new users no longer see a “?” placeholder.
Eliminated Advanced Search flicker on iPad/mobile refresh.

Plain-English impact: the platform should feel smoother, cleaner, and more stable across mobile, tablet, desktop, and the CMS editor.

8. SEO, Schema, Structured Data, and Accessibility

The release notes show several completed website SEO/schema improvements.

Completed SEO/schema improvements include:

Updated Featured Properties widget to use proper HTML tags and schema markup.
Added structured ld+json data to Featured Properties cards.
Implemented proper HTML structure and schema on search result pages.
Improved listing detail page markup and schema coverage.
Made listing cards use proper anchor tags for better accessibility and navigation.
Added PageSpeed accessibility-driven improvements for listing detail pages.

Plain-English impact: website pages should be cleaner for search engines, better structured for listing content, and more accessible for users.