Skip to content
Vareon

Sessions and incidents, learned as episodes.

Duplex learns each session, run or incident as an episode your team can ask about later.

Persistent intelligence. It runs After a job step or when a job closes.

On Monday, Duplex can tell the team how Saturday’s checkout outage unfolded, step by step.

The checkout starts failing, and the on-call engineer is paged.

Step 1 of 5: The alert

One episode covers the whole incident.

The alert, the steps taken, who took them and how it ended stay together, so anyone can follow what happened.

Step 1 of 4: What happened

What happened: checkout failed for 39 minutes.

Each closed incident informs the next one.

When a session, a run or an incident closes, Duplex turns it into an episode. The next time something similar happens, the team can ask what happened then.

Step 1 of 4: An incident

The checkout fails on a Saturday afternoon.

Every episode follows your rules.

Episodes stay in their work area, follow your retention rules and can be removed. Your access settings decide who can ask about them.

Step 1 of 5: Work area

It stays in the work area where it happened.

See it on your own work.

From your own assistant to every agent your company runs, a pilot puts Duplex on your own work, with the measures agreed before it begins.