JEFF is how your organisation runs its digital estate. Site teams, regional managers, operations directors and leadership all work through it — asking, acting, getting answers about every building you operate. It isn't a general-purpose assistant with a workspace skin on it. It does one job: delivering and proving digital experience, and doing the work itself rather than telling you about it.
is watching 214 sites…When a tenant reports a connectivity problem, that isn't a support ticket arriving. It's proof that we didn't catch it in time. Fast resolution is a consolation prize — the job is stopping the problem reaching them at all.
Fix it before they feel it. That's not a slogan. It's the standard JEFF is measured against.
.From the centre admin to the CEO, anyone can ask JEFF whatever they need — whether it's “give me proof points for tomorrow's site tour”, “which sites are at renewal risk?” or “how did we perform last quarter?” — get a straight answer, and then tell JEFF to take action.
What JEFF does
JEFF isn't a chatbot bolted onto a dashboard. It does the work — continuously, across every site you run.
Every session, every application, every device, every login, every handover between access points — continuously, across the estate. JEFF spots the thing going wrong while it's still an anomaly rather than a failure.
What that meansYou hear about problems from JEFF, not from a tenant.
“The WiFi's slow” has a dozen possible causes. JEFF works through session, application, device, authentication and roaming data to isolate the real one.
What that meansNo guesswork, no swapping kit that was never the problem, no asking a tenant to try turning it off and on again.
“Add tim@abc.com to ABC Corp at Liverpool Site 1.” JEFF provisions it instantly, and it appears in Command straight away.
What that meansMoves, adds and changes happen while you're still in the conversation. No work order, no ticket queue, no half-configured tenant on their first morning.
A prospect asks a technical question on a site visit — bandwidth, security, tenant isolation, resilience. Whoever's showing them round asks JEFF and answers it there and then, with evidence from that actual building.
What that meansYou stop losing momentum while someone waits for IT to come back to them. The hardest questions get answered when they're asked.
A daily read on the estate, pitched to whoever's reading it — portfolio health for leadership, site performance for regional managers, what needs attention today for the site team.
What that meansEveryone starts the day knowing where they stand, and nobody builds a report to tell them.
Ahead of a renewal, JEFF produces the diagnostic on how that tenant's experience actually performed across the term. It generates tenant-facing QBRs automatically, on the schedule you set in Command.
What that meansYou walk into every renewal with the evidence already in hand. The renewal stops being a negotiation and becomes a demonstration.
When a WAN circuit degrades against its SLA, JEFF detects it, raises the incident with the carrier, manages it through to resolution, and keeps you posted throughout. You see the outcome. You don't carry the case.
What that meansThe job nobody in your business wants — sitting on hold to a telco with a reference number — stops being anyone's job.
Who's affected
The moment JEFF spots a problem it works out what sits downstream of it — which switches, which floors, which tenants — and how big the impact really is, before deciding what to do.
Not just how many tenants could be affected — how many are on-site right now. A router fault at 7am is a different decision to the same fault at midday. JEFF knows the difference. It knows who's on site because every login flows through essensys. No sensors, no guesswork.
doesn't hand it back.JEFF owns a problem through to resolution. Work out the cause, check what it's permitted to do, apply the fix, verify it held — and if it didn't, move to the next approach. It only involves your team when it reaches a limit you set. Tenants keep working throughout.
Human in the loop
Every action JEFF can take follows one of three paths — and you decide which, per action and per site, in Command.
JEFF detects, fixes and verifies entirely on its own — the loop runs end to end without interrupting anyone.
e.g. clearing a degraded access-point config overnightJEFF proposes the fix with impact, rollback plan and confidence attached — and waits for one tap before executing.
e.g. power-cycling internet access in the middle of a work daySome actions are never autonomous — or physically need a person. JEFF does the diagnosis, packages the context and hands it over.
e.g. ordering replacement hardware for a failed switchAutonomous actions are logged and explained the same way — just ask JEFF what changed, and why. JEFF runs throughout the product, wherever you're working.
Today JEFF acts within the policy you set. It will earn more autonomy over time, by demonstrating it deserves it. We move at the pace your trust develops, not faster.
Get started
Assured digital experience across every site in your portfolio.
FAQ
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.
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 is how patterns learned at one building get applied at the others.
Proven at every site
