<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1876746335844462&amp;ev=PageView&amp;noscript=1">
Skip to content
  • There are no suggestions because the search field is empty.

Release Notes - 03/12/26

In CRM v1.0.22 and CMS v1.0.7, we closed 15 tickets focused on improving data reliability, search and filtering accuracy, and listing and contact management stability across the CRM and website.

Across these two coordinated releases (CRM v1.0.22 and CMS v1.0.7), we closed:

  • Total tickets: 15

  • Bug fixes: 11

  • Improvements / enhancements / new capabilities: 4

Roughly 73% of this bundle focused on bug fixes and stability, with 27% delivering new capabilities and UX polish.

Release v1.0.22 – CRM

Scope: This release improves contact data visibility, lead import accuracy, listing storage, and address handling in CRM.

Highlights

  • Custom field values now reliably appear in the Contacts table (CRM‑185)

    • Resolved an issue where certain custom field values were not visible in the Contacts table, even though they existed for the contact. You should now see your custom fields consistently across contacts, improving confidence in your day‑to‑day workflows and reporting.

  • Address filter behavior corrected to use the proper field type (CRM‑184)

    • Fixed the Address filter so that it uses the correct field type and returns the expected records. This ensures that filtering by address (e.g., city, state, or other location-based data) behaves more predictably when you’re targeting specific segments.

  • Stabilized phone functionality for critical communication workflows (CRM‑173, CRM‑181)

    • Addressed several underlying issues impacting phone-related functionality within CRM. These fixes improve reliability for outbound and inbound calls so that agents can more consistently connect with leads and contacts from within the system.

  • Improved lead import mapping to keep birthdays and tags accurate (CRM‑170, CRM‑166)

    • Corrected an issue where the “Birthday” column could be mistakenly mapped to Tags during lead import. Improved validation and mapping behavior to reduce the risk of mislabeled or misplaced data when importing large lead lists.

  • Listings from multiple MLS sources now store correctly and remain unique (CRM‑156)

    • Fixed an issue that prevented some unique listings from multiple MLS sources from being stored correctly. You should now see more complete and accurate inventory across MLS feeds, with fewer missing or duplicated records.

  • Collections behavior stabilized after recent platform changes (CRM‑107)

    • Resolved issues affecting Collections after recent backend changes. Collections should now behave as expected, allowing you to group and work with sets of contacts or listings more reliably.

  • Additional contact and listing attribute improvements (CRM‑163, CRM‑157)

    • Added a new country key to the Listings API attributes, laying groundwork for better geographic reporting and filtering. Continued refinements to contact source/location data to ensure contact records have clearer and more consistent origin details.

Release v1.0.7 – Website (CMS)

Scope: This release focuses on website search behavior, form/notification consistency, and overall listing display experience.

Highlights

  • More reliable filter results when data is available (GGMI‑3450)

    • Fixed an issue where filters with available matching listings could still return no results. Visitors should now see accurate results when they filter on criteria such as price, beds, baths, or other listing attributes.

  • Improved heading customization for “What’s Special” sections (GGMI‑3448)

    • Added typography and color controls for “What’s Special” headings. This gives you more flexibility to align key highlight sections with your brand’s look and feel.

  • Cleaner tag display on listing overview sections (GGMI‑3442)

    • Corrected a layout issue where tags on the overview sometimes wrapped into multiple rows, even when there was enough horizontal space. Tags now display more cleanly, improving readability and presentation across devices.

  • More consistent feedback on sign‑in and contact forms (GGMI‑3417)

    • Standardized toast notifications for Sign In and Contact Agent forms to match how other forms behave. Users now receive clear confirmation or error messages, reducing confusion and making it easier to know when a form has been submitted successfully.

  • Smoother loading experience with fewer “No Result Found” flickers (GGMI‑3400)

    • Addressed a timing issue where a “No Result Found” message could briefly appear before listings loaded, and where a loading skeleton sometimes failed to display. Visitors should now see a more polished loading state and fewer confusing messages while results are being fetched.