USE CASE
Verified Helpdesk
Verified Helpdesk
One of the areas Verifiable Credentials really shine is in helpdesk or service desk environments. In the age of deepfake voices, constant leaks of PII, and relentless phishing attacks, it is harder than ever to truly Know Your Customer.
The VO platform dramatically reduces fraud risk by enabling helpdesk agents to verify customers easily and securely.
Sounds too good to be true? You can see it in action for yourself!
We’ve created a series of video walkthroughs on some of the most impactful helpdesk applications of verifiable credentials.
A VO Verified Helpdesk means:
- Your customers will be protected.
- Your helpdesk agents will be more efficient.
- Your customer satisfaction will increase.
- You’ll save money.
And, perhaps most importantly, you’ll keep yourself and your company off the front page for a massive security breach that could have been avoided.
Verify an Email Request
When a customer submits a ticket to your helpdesk via email, the helpdesk agent is able to verify the customer using a verifiable credential.
Verify a High-Risk Request
When a customer has already used a verifiable credential to log into your helpdesk system, your helpdesk agent can request an additional verification for a high-risk event, like updating bank account details.
Verify a Request from a New Source
When the helpdesk receives a request from a source that isn't immediately known to the platform (new email, new phone number or where the agent creates the ticket on-behalf of a user), the agent can request verification of the unconfirmed source.
Customer Rejecting an Unauthorised Request
When your helpdesk agent requests verification from your customer before completing a high-risk event, the customer is able to verify themselves and then reject the action approval request.
Approved Risky Request
When a customer has called your helpdesk with a risky request, your helpdesk agent is able to verify the customer using a verifiable credential.
