Reference · built on requestOperator by FibricFacilities & comfort

Comfort Complaint

Matches hot and cold complaints to zone readings and proposes a setpoint change or a work order for the terminal unit.

Request accessPricing ↗

About

"Too cold" arrives as a Zendesk ticket or a Teams message, and the person who reads it has to find the zone, pull the trend, and decide whether it is a setpoint or a broken box. Comfort Complaint does the finding. It reads new tickets and channel messages, matches each to a zone by the desk, room, or floor named, and pulls that zone's space temperature, setpoint, damper or valve position, and airflow from the building management platform over BACnet/IP.

If the zone is holding its setpoint, it proposes a small setpoint change and a reply to the requester. If the zone cannot reach setpoint, it proposes a work order on the terminal unit in your CMMS. A person approves either. It never writes a setpoint itself.

This is a reference listing. It documents what Fibric would read from Comfort Complaint and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • New and updated tickets in Zendesk with subject, description, requester, status, tags, and custom fields such as floor or room
  • Channel and chat messages in Microsoft Teams through the Graph chatMessage resource, with sender, body, mentions, and createdDateTime
  • Space temperature, effective setpoint, and occupied mode for the matched zone over BACnet/IP or from Niagara, Metasys, or Desigo CC
  • Terminal unit state for that zone: VAV damper position, reheat valve position, airflow setpoint and measured airflow, where the controller exposes them
  • The supply air temperature and fan state of the air handler serving the zone, so a whole-floor complaint is read at the source
  • Open work orders on the same terminal unit in Fiix, MaintainX, UpKeep, or Limble, so a known fault is not filed again

Proposed actions

  • Target capability: propose a setpoint change of the size you allow for a zone that holds its setpoint while the requester reports discomfort
  • Target capability: propose a work order on the terminal unit when the zone cannot reach setpoint, with the damper, valve, and airflow readings attached
  • Target capability: propose a reply to the ticket or message naming the zone, what was found, and what will be done
  • Target capability: propose linking the complaint to an open work order when the same unit already has one, instead of filing a second
  • Target capability: propose a review note when one zone draws complaints from both hot and cold in the same week, for the controls contractor

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Answer a cold-call ticket with the reading

    A Zendesk ticket says the fourth-floor corner is cold. The operator finds the zone over BACnet/IP, sees it holding setpoint, and proposes a small change within your band plus a reply to the requester.

    With Zendesk, BACnet / IP

  • File the broken VAV, not another setpoint

    The zone reads well below setpoint with the reheat valve fully open in Niagara. The operator proposes a Fiix work order on that terminal unit with the readings attached and a Teams reply saying a technician is coming.

    With Tridium Niagara, Fiix, Microsoft Teams

  • Stop the hot-cold tug of war

    One zone draws hot and cold complaints in the same week from a Teams channel. The operator proposes linking them, holding setpoint changes, and a review note in MaintainX for the controls contractor.

    With Microsoft Teams, BACnet / IP, MaintainX

Requirements

  • A Zendesk connector, or a Microsoft Teams connector with read access to the channel where comfort complaints arrive
  • A building management platform connector over BACnet/IP, or Niagara, Metasys, or Desigo CC, with the zone and terminal unit points on its list
  • A CMMS connector such as Fiix, MaintainX, UpKeep, or Limble, with terminal units listed as assets
  • A map from desks, rooms, and floors to zones and terminal units, so a complaint can be placed
Authentication
Reads tickets and messages through the Zendesk API token or Microsoft Graph permissions your connectors hold, reads points through the read allow-list of your building platform connector, and files work orders and replies through those connectors after approval.

Limits

  • It places a complaint by the location it names. One naming no room uses the requester's desk, if provided, or waits for a person.
  • Setpoint proposals stay within the band you set per zone. It does not judge the ASHRAE 55 conditions of the space; it reports the readings.
  • It proposes. It never writes a setpoint, overrides a damper or valve, or changes an occupancy schedule.
  • Zones with no airflow or valve feedback get a temperature-only diagnosis, which cannot tell a stuck damper from a closed one.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Comfort Complaint ↗

Questions and answers

What does a person approve?
Every setpoint change, work order, reply, link, and review note. The proposal shows the complaint, the zone it was matched to, the readings at the time, the open work orders found, and the exact change or text. Approve it, edit the value or the text, or dismiss it.
What record is left?
A receipt per complaint: the ticket or message, the zone matched, the readings read, the proposal made, who approved it, the setpoint before and after or the work order id, and how to restore the previous setpoint.
Will it change a setpoint on its own?
No. It reads points and writes nothing until a person approves. An approved setpoint change is sent once through your building platform connector, within the band you set. Damper, valve, and schedule writes are never proposed.
Ask about Comfort Complaint

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy