Frequently asked questions.

JEFF is the autonomous operations agent inside essensys Platform, and the interface operators use to run their digital estate. It monitors every site continuously, detects connectivity and infrastructure problems, resolves eligible issues within the controls set in Command, and verifies the fix held — escalating to a person only when one is needed.

JEFF was essensys's original product, launched in 2010 and built on three principles: provision, manage, monitor. It has run flex workspace buildings for more than fifteen years. It is now an agent, doing the same job autonomously.

Operators decide. In Command, every action JEFF can take is set to one of three paths — fully autonomous, approval-first, or human-required — configurable per action and per site. Every action, autonomous or approved, is logged with full context.

Monitoring software detects problems and raises alerts for a person to action. JEFF detects the problem, works out who is affected, applies an authorised fix — or packages the diagnosis and context for approval or human action — and confirms the outcome. The difference is between being told about an issue and having it taken through to resolution.

JEFF monitors session quality, application performance, device behaviour, authentication events, roaming performance, bandwidth delivery, and failure frequency — at user, tenant, site, and portfolio level. In multi-tenant buildings, most experience problems come from device behaviour, authentication failures, congestion, and contention rather than core infrastructure, which is why conventional network monitoring misses them.

Yes. JEFF operates across an operator's entire estate rather than site by site, which allows patterns identified at one building to inform work across the others.

Signal turns what essensys Platform sees into practical decisions about tenant experience, space utilisation, hardware lifecycle, and carrier performance. It surfaces what matters and can attach the next action for JEFF to take within the controls set in Command.

Signal brings together four core readings: space utilisation, digital experience, hardware lifecycle, and WAN performance. Because the readings come from the same telemetry, teams can see where experience, occupancy, infrastructure, and carrier performance intersect.

Signal can surface changes in experience and utilisation that may indicate a tenant is thriving or beginning to drift. These patterns give teams earlier evidence to investigate; they do not replace a commercial conversation or guarantee that a tenant will renew or leave.

DX Score can support operational teams, prospects, landlords, boards, and investors. The relevant view can be provided at tenant, site, or portfolio level, depending on the audience and permissions involved.

Signal can derive utilisation insight from essensys Platform telemetry without requiring separate occupancy sensors for that analysis. The appropriate method and level of detail depend on the estate, network coverage, and reporting requirement.

Yes. Signal can compare digital experience and utilisation across tenants and sites, track hardware lifecycle states, and show WAN and carrier performance so teams can identify variation, breaches, and areas that need action.

Command is where an operator defines how its digital estate runs: buildings, floors and spaces; tenants and users; network policy; service tiers; what each team member can access; and what JEFF may do autonomously.

Command configures tenants, users, sites, network policy, service tiers, branding, firmware, reporting, and the limits within which JEFF can act. Settings can be applied at the appropriate tenant, building, or portfolio level.

Command defines the required standard, Signal detects deviations, and JEFF can correct eligible firmware, configuration, and policy drift within the operator's controls. This turns a one-time configuration into a standard that is continuously monitored and maintained.

Authority is role-based and site-scoped. Operator, Site Manager, IT Lead, and Owner roles can each be configured to see and control only what is appropriate for their responsibilities.

Command defines JEFF's operating envelope. Each action can be configured as fully autonomous, approval-first, or human-required, with controls applied by action type and site.

Yes. Command maintains an audit trail for human and agent actions, including who or what acted, when it happened, which policy permitted it, why it was taken, and the outcome.

essensys holds ISO 9001 and ISO 27001 certifications and has a SOC 2 Type II report covering its information-security control environment.

Through the multi-tenant data model and the network layer together. Tenants can be isolated per user on a shared network, or given a dedicated VLAN with their own firewall and router provisioned to the port. Both are standard configurations.

Yes. Subject to the appropriate permissions, tenant IT teams can receive relevant DX and performance data for their space, together with governance and incident records.

Only what the operator has authorised in Command, per action type and per site. Every action is logged against the policy that permitted it.

Access is role-based and site-scoped. Operator, Site Manager, IT Lead, and Owner roles each see and control only what is appropriate, as configured in Command.

Yes. essensys Platform works with Cisco, Juniper, Ruckus, Ubiquiti, and mixed estates. Some software-controlled network-management capabilities require an eNMA device on-site, but functional switches and access points can remain in place.