Prerequisites
- Tenant includes QDesk (End User Accounts) or QVerify Plan
- Quickpass Dashboard integrated with ConnectWise
https://support.getquickpass.com/hc/en-us/articles/1500005922122-Connectwise-Manage-Integration-Setup-Guide - Quickpass POD setup for ConnectWise Service Desk
https://support.getquickpass.com/hc/en-us/articles/1500005980202-Add-Quickpass-POD-to-ConnectWise-Manage-Service-Ticket
NOTE: Although the End User Account does not have to match to a Quickpass Account, the Integration with ConnectWise and the POD setup must be completed to use this new feature.
Verify End-User Identities in ConnectWise Manage Service Tickets
- In ConnectWise Manage open a service ticket that was emailed in by an end-user or created manually.
Note: One or more of the Email address or Mobile Phone number for the ConnectWise contact must be populated
- In the Quickpass Pod section, the PSA only Data will be shown. You can use this to provide identity verification
If you think this account SHOULD be matched to a Quickpass End User account, review this Article
https://support.getquickpass.com/hc/en-us/articles/1500005978882-Match-ConnectWise-Contacts-with-Quickpass-Accounts - Select the Identity Verification link
- Select which method to send the Verification to the End User and click the SEND button in the Quickpass Pod. The possible values shown here are based upon the Contact Details.
Note: After clicking the SEND button the end-user will receive an SMS or an Email (based upon selection) with the verification code.
- Ask the end-user what the verification code is that they just received.
- Scroll down within the POD to see the box you must populate with the code the End User received.
- Populate the number into the box and click Verify
- If the code matches what was sent and you clicked Verify this screen will be presented
- If the code does not match was was sent and you clicked Verify this screen will be presented
- If you clicked Deny you will see this screen
All of the actions that were performed will be logged in the Internal Notes for the ticket
Comments
0 comments
Please sign in to leave a comment.