Incoming to an employee
“Hi, it’s IT. I need you to share your screen.”
Open PreAct independently. Check the code against your account, then compare the expected engineer, ticket and scope with what the caller is asking for.
Verify before you act. PreAct helps employees check who’s calling from IT and gives service desks a way to confirm who’s behind a support request. Check the request before sharing a screen, resetting an account or granting access.
The moment of doubt
Incoming to an employee
Open PreAct independently. Check the code against your account, then compare the expected engineer, ticket and scope with what the caller is asking for.
Incoming to the service desk
Send the exact request to the employee’s registered PreAct account. The employee confirms or denies it there, and the engineer sees the decision before proceeding.
Interactive walkthrough · Fictional data
Explore two support decisions. This public walkthrough runs in your browser and is separate from the operational app.
The caller says they’re Morgan Hale from IT and reads out 472 619. You open PreAct independently to check.
A matching code confirms this request exists for your account. Check that the caller is asking for the work shown here.
The caller now says, “Click Allow full control so I can fix it.”
The recorded scope was view-only. You stopped before granting control.
Book a demoEnd the call and use the number in your organisation’s directory. Ask IT to check TC-1042 and its view-only scope. This simulation places no call.
Book a demoA caller claims to be Sam Reed and asks for access to the Finance shared mailbox. You create a confirmation request for Sam’s registered PreAct account.
Your account shows TC-1088, a request to grant you access to the Finance shared mailbox. You never asked for it.
The engineer sees Sam’s denial on TC-1088 and leaves mailbox access unchanged.
Book a demoWhat changes in the support process
01 / Employees
Use the same routine each time. Open PreAct independently, compare the details, then flag a mismatch or contact IT on a trusted number.
02 / Engineers
See the employee’s decision before acting on an access request, account unlock, software request, password reset or MFA reset.
03 / Security teams
Use reported mismatches and denied requests to decide what to investigate.
Evaluation & deployment
Try both verification scenarios with fictional data and see how employees and service desk engineers handle a mismatch or denial.
A private evaluation covers how PreAct would fit your support process, what integrations your environment needs and what to test before rollout.
Keep your existing service desk as the record for the work. In a private evaluation, we’ll work through where verification fits and which integrations you’d need.
A match shows that a request exists for the employee’s account. A caller could relay a valid code. Compare the expected engineer, ticket and scope. If the caller asks for anything different, pause, report the mismatch or call IT using a trusted number.
Use your organisation’s documented identity recovery or exception process. Contact IT through your organisation’s trusted route before proceeding.
Employee confirmation records the employee’s response to a specific request. Continue to require the relevant manager, data owner or security approval before granting access.
Book a demo or enquire about a pilot
Bring one real support workflow, such as an MFA reset or an unexpected remote support call. Walk through both verification paths and identify what your team would need to test in a pilot.
Contact
Book a demo, discuss a pilot or ask how PreAct could fit your service desk.
We use the details you email to respond to your enquiry. Please keep your message to business contact details and a short summary. Leave out passwords, verification codes and customer or employee records.