REQARO Front Office
Inquiry handling, draft review and office handoff across your configured service business.
Open Core ↗REQARO · OPERATIONS PLATFORM
Maintenance intelligence and energy review, alongside your existing front office.
Rules-based pilot. No predictive model, generative AI, live sensor feed or device control is active. Manufacturer documentation and a qualified technician remain essential. Examples are synthetic; changes reset on reload.
Inquiry handling, draft review and office handoff across your configured service business.
Open Core ↗Equipment history and evidence-based service review.
Customer-entered consumption comparisons and clearly labeled scenarios.
Module switches control this pilot, not a paid subscription. Disabling a module preserves records. Core pricing is unchanged; premium and enterprise scope require a separate agreement.
Add equipment before recording service history or consumption.
Demo equipment · no live device · Rooftop heat pump
Synthetic Phoenix office · ZIP 85004
Installed 2018
Last maintenance: 1/15/2025
Configured interval: 180 days
Example code reported; manufacturer interpretation not available
Source: Synthetic technician noteRecorded against RTU-01 · Main office. Numeric readings retain their units but are not diagnosed. “Completed maintenance” advances the last service date.
Prioritized by reported safety concern, service review, then missing data. No fault probability or remaining useful life is calculated.
RTU-01 · Main office
621 days since 2025-01-15; your configured interval is 180 days.
Have your team verify the history and plan maintenance under the applicable manufacturer instructions. This is a calendar rule, not a failure prediction.
Prepare a reviewed service request ↗RTU-01 · Main office
2026-08-20 · Synthetic technician note: Example code reported; manufacturer interpretation not available
Verify the exact model and code against manufacturer service documentation. A code does not establish the failed component; no cause is inferred.
Prepare a reviewed service request ↗Furnace-02 · Service bay
No last completed maintenance date is recorded.
Check service records and the manufacturer’s maintenance schedule. Missing data is not evidence of a fault.
Prepare a reviewed service request ↗Compare the latest two completed periods per equipment, meter, unit and scope. End dates are exclusive: July 1 to August 1 is 31 days.
This is your assumption, not an AI estimate. Cost scales proportionally with entered period cost; fixed charges, demand charges, capital costs and tariff changes are not modeled. No annual extrapolation.
RTU-01 · Main office
54 kWh/day8/1/2026 — 9/1/2026 (exclusive)
1,674 kWh · $251.10 · Source: Synthetic meter total
+35% vs. previous daily average · REVIEW PATTERN
Baseline: 7/1/2026 — 8/1/2026 · 1,240 kWh · Source: Synthetic meter total
Period-length adjusted only. Not weather-, occupancy- or load-normalized. A 20% increase flags review, not proven inefficiency. Whole-building consumption cannot be attributed to HVAC.
Next: verify meter coverage, weather, occupied hours and schedule changes before considering setpoint or operating-time adjustments. No automated setpoint change is made.
Add normalized JSON records to this workspace. Stable IDs prevent duplicates; conflicting IDs and overlapping periods are rejected. No files are sent to an AI service.
Download synthetic import exampleMaximum 50 records per import and 24 KB per API request. Pilot limits: 50 units, 150 observations, 150 periods. Import is all-or-nothing.
Manual synthetic workflow. No scheduler, live webhook, credentials or external calls. This pilot session is not an unattended integration credential.
No saved pilot activity.