Match the right system.
Connect the appropriate customer, location, and equipment identities, including sites with multiple HVAC systems.
API-based integrations for compatible CRM, field-service, property, and program workflows.
AirSenz supports API-based connections with CRM and field-service platforms, helping connect equipment insights with customer records and service workflows. Available connections and data exchanges depend on the platform and your organization’s setup.
Connect the appropriate customer, location, and equipment identities, including sites with multiple HVAC systems.
Use supported workflows to connect alerts with the service team’s next action. Account configuration determines the enabled workflow.
Define the service records and equipment information needed for the agreed use case, then validate the exchange during onboarding.
With the contractor’s approval, AirSenz can integrate with ServiceTitan for customer lookup and alert-linked tasks. Other platforms and additional data exchanges are evaluated against the available APIs and account permissions.
Explore CRM and API integrations →Identify the customer records, equipment context, alerts, or follow-up work that the connection needs to support.
Confirm account permissions and match the correct customer, location, and equipment identifiers.
Validate the agreed data exchange and service process before it is used in day-to-day work.
API documentation supports implementation. An API specification does not mean every platform has a prebuilt connector or that every operation is enabled for every account.
Yes. With the contractor’s approval, AirSenz can integrate with ServiceTitan. Supported workflows include customer lookup and follow-up tasks linked to AirSenz alerts. Permissions, record matching, and enabled workflows are confirmed during onboarding.
Setup includes authorized API access, the required account permissions, and matching the correct customer, location, and equipment records. We define the data exchanged and test the agreed workflow before using it in day-to-day service. A customer ID alone is not the whole connection setup.
Yes. Each monitored HVAC system should have its own equipment identity and location details. When connecting service records, match them to the correct system so work on one unit is not interpreted as service on another unit at the same address.
No universal dispatch behavior is assumed. Connected workflows and any automation must be configured for the account and operating process. A follow-up task, a booked job, and a dispatched visit are different steps; the responsible team remains in control of the agreed process.
No. API integration uses authorized access to supported data and operations. Permissions and record matching determine the intended scope. The website’s integration description does not offer unrestricted access to customer or equipment records.