Quick-logon for computing device

1. A method comprising:

receiving, from a computing device associated with a user, a secure token to fulfill a first authentication request, wherein the secure token is generated by a token generator associated with the device;

verifying that the secure token matches the secure token generated by the token generator associated with the device;

authenticating the user to engage in a first activity on a first channel without further interaction from the user in response to verification that the secure token matches the secure token generated by the token generator associated with the device;

providing, to the user, access to the secure token in a human-readable format to fulfill a second authentication request to engage in a second activity that requires a different level of authentication than the first activity;

in response to the user requesting engagement in the second activity, requesting, from the user, the secure token, wherein the secure token requested to fulfill the second authentication request to engage in the second activity is the same secure token that was used to fulfill the first authentication request; and

authenticating the user to engage in the second activity on the first channel in response to verification that the secure token provided by the user matches the secure token generated by the token generator associated with the device.

2. The method of claim 1 , wherein the second activity requires a higher level of authentication than the first activity.

3. The method of claim 1 , wherein providing, to the user, access to the secure token comprises at least one of: displaying the secure token on a lock screen of the computing device or storing the secure token in an application installed on the computing device.

4. The method of claim 1 , wherein the secure token is dynamic, wherein the first channel is one of: a mobile application, a web portal, a chat room, a voice and data call, or a voice call.

5. The method of claim 4 , wherein providing, to the user, access to the secure token comprises providing a list of secure tokens with time indications, wherein the method further comprises requesting the secure token present at a particular time to fulfill the second authentication request.

6. The method of claim 1 , wherein the secure token is a quick response code, wherein the quick response code is physically presented to a second device.

7. The method of claim 1 , wherein authenticating the user comprises verifying an identity of the user, wherein verifying the identity of the user comprises:

monitoring interactions of the user including browsing behavior with the computing device;

determining whether the interactions of the user with the computing device matches, within a predetermined degree of tolerance, expected behavior within a user profile of the user; and

in response to the interactions of the user matching the expected behavior within the user profile, verifying the identity of the user.

8. A non-transitory computer-readable medium comprising instructions stored thereon, that when executed on a processor, perform operations comprising:

receiving, from a computing device associated with a user, a secure token to fulfill a first authentication request, wherein the secure token is generated by a token generator associated with the device;

verifying that the secure token matches the secure token generated by the token generator associated with the device;

authenticating the user to engage in a first activity on a first channel without further interaction from the user in response to verification that the secure token matches the secure token generated by the token generator associated with the device;

providing, to the user, access to the secure token in a human-readable format to fulfill a second authentication request to engage in a second activity that requires a different level of authentication than the first activity;

in response to the user requesting engagement in the second activity, requesting, from the user, the secure token, wherein the secure token requested to fulfill the second authentication request to engage in the second activity is the same secure token that was used to fulfill the first authentication request; and

authenticating the user to engage in the second activity on the first channel in response to verification that the secure token provided by the user matches the secure token generated by the token generator associated with the device.

9. The non-transitory computer-readable medium of claim 8 , wherein the second activity requires a higher level of authentication than the first activity.

10. The non-transitory computer-readable medium of claim 8 , wherein providing, to the user, access to the secure token comprises at least one of: displaying the secure token on a lock screen of the computing device or storing the secure token in an application installed on the computing device.

11. The non-transitory computer-readable medium of claim 8 , wherein the secure token is dynamic, wherein the first channel is one of: a mobile application, a web portal, a chat room, a voice and data call, or a voice call.

12. The non-transitory computer-readable medium of claim 11 , wherein providing, to the user, access to the secure token comprises providing a list of secure tokens with time indications, wherein the operations further comprise requesting the secure token present at a particular time to fulfill the second authentication request.

13. The non-transitory computer-readable medium of claim 8 , wherein the secure token is a quick response code, wherein the quick response code is physically presented to a second device.

14. The non-transitory computer-readable medium of claim 8 , wherein authenticating the user comprises verifying an identity of the user, wherein verifying the identity of the user comprises:

monitoring interactions of the user including browsing behavior with the computing device;

determining whether the interactions of the user with the computing device matches, within a predetermined degree of tolerance, expected behavior within a user profile of the user;

in response to the interactions of the user matching the expected behavior within the user profile, verifying the identity of the user.

15. A call routing system comprising:

one or more processors; and

a computer readable storage medium having instructions stored thereon, which when executed by the one or more processors, cause the call routing system to:

receive, from a computing device associated with a user, a secure token to fulfill a first authentication request, wherein the secure token is generated by a token generator associated with the device;

verify that the secure token matches the secure token generated by the token generator associated with the device;

authenticate the user to engage in a first activity on a first channel without further interaction from the user in response to verification that the secure token matches the secure token generated by the token generator associated with the device;

provide, to the user, access to the secure token in a human-readable format to fulfill a second authentication request to engage in a second activity that requires a different level of authentication than the first activity;

in response to the user requesting engagement in the second activity, request, from the user, the secure token, wherein the secure token requested to fulfill the second authentication request to engage in the second activity is the same secure token that was used to fulfill the first authentication request; and

authenticate the user to engage in the second activity on the first channel in response to verification that the secure token provided by the user matches the secure token generated by the token generator associated with the device.

16. The call routing system of claim 15 , wherein the second activity requires a higher level of authentication than the first activity.

17. The call routing system of claim 15 , wherein providing, to the user, access to the secure token comprises at least one of: displaying the secure token on a lock screen of the computing device or storing the secure token in an application installed on the computing device.

18. The call routing system of claim 15 , wherein the secure token is dynamic, wherein the first channel is one of: a mobile application, a web portal, a chat room, a voice and data call, or a voice call.

19. The call routing system of claim 18 , wherein providing, to the user, access to the secure token comprises providing a list of secure tokens with time indications, wherein the instructions, which when executed by the one or more processors, further cause the call routing system to request the secure token present at a particular time to fulfill the second authentication request.

20. The call routing system of claim 15 , wherein authenticating the user comprises verifying an identity of the user, wherein verifying the identity of the user comprises:

monitoring interactions of the user including browsing behavior with the computing device;

determining whether the interactions of the user with the computing device matches, within a predetermined degree of tolerance, expected behavior within a user profile of the user;

in response to the interactions of the user matching the expected behavior within the user profile, verifying the identity of the user; and

verifying that the computing device is pre-registered.