Release Notes: September 15th, 2025

Overview

This release introduces enhancements across the platform, including improvements to the subscription display logic, address search in checkout, expanded support for custom fields, and key updates in billing, workforce, and API functionalities.

Product update

User interface

• Subscriptions now reflect the most relevant subscriptions based on the account state. For example, suspended accounts will now show Suspended subscriptions instead of always defaulting to Active.

Checkout

• Improved address search: Address lookups are now triggered only after the user finishes typing, reducing unnecessary API calls.
• Faster appointment availability: Appointment slots are now preloaded in the background when a customer reaches the Start checkout step.
• Custom fields support extended: You can now display custom fields at all checkout steps. This includes optional questions like "How did you hear about us?"
  Self-serve configuration is not available yet. Contact us at support@gaiia.com if you’d like to enable it or for any changes.
• Irish phone numbers are now supported.
• Automatic payments are now enforced for BACS payment method.

Billing

• Call Detail Records (CDR): Additional enhancements include:
  • Support for international calling
  • Call type tracking (e.g., payphone, direct dial)
  • Taxation now based on call scope (e.g., interstate only)
  • Support for DIDs through the Inventory module
• [Authorize] It's now possible to specify the customer ID when issuing a refund.

Workforce

• Work orders can now be manually assigned outside of shift hours from the Schedule page, with a warning prompt and an audit trail entry in the Work Order Activity Log. Role-based permissions apply. Learn more in the article.
• [Field service app] If a user only has access to one tenant, the app now skips the tenant selection screen.
• [Fixed]: Work orders created by the checkout now correctly include the unit number in the address.

API

• Clients using the GraphQL API can now set the deactivationDate on an account via the updateAccount mutation. See documentation.