Traceless Integration
A sensitive request gets checked against the employee it claims to be, on the authenticator that person already carries, before anything runs. Your clients stay protected, and your technicians are not guessing.
What you get
Checked before anything sensitive runs
The employee approves the push on their own phone before the agent touches the account. Rallied has the result within seconds and carries on from there.
One setup covers Authenticator and Duo
Each push goes to the factor that user already has, Microsoft Authenticator or Duo Mobile. A client base split across the two takes one integration instead of one per provider.
The requester is checked as well as the plan
Your approval settings decide whether the agent may run a sensitive action, and Traceless decides whether the requester is who they say. A denial, a timeout, or a failure stops the action even when a technician already approved the plan, and the requester has to resubmit.
The outcome is written on the ticket
The outcome lands on the ticket as an internal note as soon as it resolves. Whoever picks the ticket up later can see whether the person was verified.
What it handles
- Challenges the requesting employee at their work email
- Covers Microsoft Authenticator and Duo under one integration
- Gives the employee five minutes to answer
- Stops the action on a denial, a timeout, or a failure
- Writes the outcome on the ticket as soon as it resolves