Q2 Co-Pilot is a thin and lightweight app that provides primarily read-only access to limited end-user data so that FIs can administer level-1 support for Q2 products.
While end-user data is mainly visible through Q2 Console and Q2central (an administrative application that has extensive capabilities and access to a large amount of end-user data obtained from the FI’s core banking system), there may be circumstances where it's not practical for an FI to install or allow staff access to Q2central.
Here are some examples on why Q2 Co-Pilot might be a better solution than Q2central:
-
The staff providing support is entry level, and training for Q2central isn't planned or hasn't happened yet.
-
The staff providing support is mobile within the job site, such as working on tablets linked to multiple allowed IP addresses.
-
The level-1 support function is outsourced to a third-party organization.
With Q2 Co-Pilot, FIs can provide support in these circumstances without exposing sensitive end-user data to editing.
You can perform many level-1 support actions in Q2 Co-Pilot, including:
-
Reset passwords.
-
Unlock Logins.
-
Enable or disable Users and Logins.
-
View User and Login statuses.
-
View, add, and delete Secure Access Code (SAC) contacts.
-
Launch CSR Assist.
-
View details about an end user, such as the User, Customer, and Group they belong to.
Although Q2 Co-Pilot is a valuable tool, there are some things that you can't do, including:
-
View end-user account balances (except through CSR Assist).
-
Add or remove accounts.
-
Create new Logins or changing existing Logins.
-
Update contact information.
If a customer needs help that you can't provide through Q2 Co-Pilot, contact FI staff with access to Q2 Console for assistance.