Features
What Envoy does today.
Envoy’s features are organized around four jobs: confirming the monitoring is working, coordinating the response, showing the whole portfolio in one place, and keeping the record. Everything below ships today.
Architecture
How it is organized.
Four jobs, and everything sits under one of them. New features get added inside those four rather than as standalone modules.
What Envoy verifies
Infrastructure trust.
These features confirm that the monitoring is actually working. Where a property is partly covered, Envoy fills in the gaps. Where nothing is watching for a particular problem, Envoy supplies the monitoring itself: water leak detection, temperature, humidity, mold condition detection, power, internet connectivity with router reboot, occupancy and motion, as well as geolocation and geofencing for movable assets on the property. Either way, these features work for all of it.
If the monitoring is already there, Envoy absorbs it, verifies it, and expands it. If it is not, Envoy provides it.
Envoy monitors and coordinates. It is not an alarm system.
Heartbeat verification.
Every connected device sends a regular signal that it is still there and reporting. Envoy checks for that signal continuously and tells your assigned contact when a device stops sending it.
Connectivity tracking.
Envoy tracks cellular, network, and gateway connectivity across the monitoring it verifies. When a connection drops, Envoy raises an alert, so a piece of the property doesn’t go unwatched.
Integration health.
Envoy checks that every system it is connected to is still sending what it should. When an integration stops producing data, Envoy flags it and routes it to your assigned contact to resolve.
Device inventory and status.
Envoy keeps a live list of every device it is verifying, with its current status, when each one last reported, and what it has done since. That record answers whether a property was actually covered last month.
Coverage gaps.
Envoy identifies properties or zones where nothing is monitoring for a problem and notifies you so you can close the gap.
Internet monitoring and remote router reboot.
Envoy monitors the property’s internet connection independently of the devices that rely on it, and can automatically reboot the router or queue a manual reboot. When the connection drops, the property’s other connected systems can go down with it. Envoy’s own monitoring doesn’t depend on the property’s internet connection, so it keeps reporting and tells your assigned contact what happened.
What Envoy coordinates
Operational coordination.
These features handle what happens after an alert fires. Alerts arrive from different systems in different formats, and the response usually spans more than one team. Envoy delivers each alert to the right person, tracks it through to closure, and escalates it when no one picks it up.
Alert ingestion across systems.
Alerts arrive from sensors, building management systems, point monitoring, and resident automation, each in its own format. Envoy takes them in as they come and puts them into one form, so your team handles every alert the same way no matter where it came from.
Ownership routing.
You set ownership rules by property, system, alert type, and time of day. Envoy applies them the moment an alert fires and tracks who owns it until the alert is resolved.
Response lifecycle tracking.
Envoy follows each alert through every stage: received, acknowledged, in progress, resolved, and closed. The timeline is captured as the work happens, so no one has to reconstruct it later.
Escalation workflows.
If an alert isn’t acknowledged or resolved within the expected window, Envoy escalates it past your assigned contact. You configure the timeframes and where each escalation goes.
Cross-system coordination.
Envoy coordinates across the systems where alerts originate and the systems where the response actually happens. One alert can drive work in the PMS, in the field operations system, and with the team that handles it.
What Envoy shows
Portfolio visibility.
These features show you what is happening across the portfolio without anyone having to assemble a report. It is already there, at whatever level you need to look at it.
Portfolio dashboard.
One view of every property you cover, showing which monitoring is verified, what alerts are open, and which responses are underway. You see the whole portfolio without asking anyone to pull it together.
Property-level detail.
Click into any property from that view. Each one has its own operational record, a list of the systems in place, and a log of recent activity.
Role-based views.
Operations leadership, regional managers, and on-site teams each see the portfolio at their own level. The person running one property isn’t looking at the same screen as the person running two hundred.
Filtering and search.
Search the portfolio by what is actually happening: properties with open alerts, properties with coverage gaps, properties where a response is overdue, properties running normally. You get answers instead of impressions.
Mobile access.
The portfolio view and property detail both work on phones, so leadership and field teams can see the same information from anywhere.
What Envoy documents
Operational accountability.
These features build the record of what happened. They fill in as the work runs, so when a carrier, lender, or owner asks what a property has been doing, the answer is already there.
The record builds itself.
What monitoring was verified, which alerts fired, who handled them, how long it took, and how each one ended, all captured as the work happens. Nobody has to stop and write it up afterward.
Exports.
Pull the record in a structured format for a carrier, lender, ownership group, or anyone else who asks. Run an export on demand or schedule it to run automatically.
Property history.
Every property has a complete history, no matter how far back you need to look. That is what a refinancing review, an insurance renewal, or a change of ownership typically requires, and you don’t have to reconstruct it to answer.
Documentation for compliance work.
The record is organized around the operational evidence carriers and lenders increasingly request. Envoy does not certify compliance. It gives you the documented history to work from when you need it.
Who did what, and when.
Every event in the record carries its own trail: who saw it, who owned it, what they did, and when it was resolved.
Across all four jobs
Deployment and administration.
These features sit underneath the four jobs above: getting Envoy running, connecting it to what a property already has, and administering it once it is live. ObjectSpectrum builds and operates Envoy on Prism, its platform, which has run in live client deployments for years.
Integration coverage.
Envoy connects to compatible property management systems, building management systems, resident automation, inspection software, and point monitoring. Where a system is compatible, Envoy reads from it and confirms that it is still reporting.
Partner administration.
A partner managing several customers sees all of them in one place: each customer’s portfolio, the open alerts across the book, and where each one stands.
Owner/operator administration.
An owner or operator managing its own portfolio controls who has access, what each person can do, and what each role sees.
What Comes Next
The list keeps growing.
New features ship as Prism matures underneath Envoy and as deployments turn up things worth building. This page gets updated when the feature set changes, and partners hear about what is coming before it ships.