Support-Key Entry for Guided Troubleshooting
GoToAssist Support - Customer is built around an attended support workflow rather than a standalone dashboard. A customer opens the app after a trusted support representative provides a support key, enters that key in the main field, and uses Join session to begin the handoff. This keeps the first step clear when help is already in progress.
The start screen stays focused on the action that matters: connecting the right device to the right support case. The key-based entry also gives agents a simple way to direct a customer into a specific session without asking the customer to search through menus or create a separate workspace.
Live Screen Sharing and Chat During a Session
Once a session is authorized, the app lets the customer share the Android screen with the support agent in real time. That view gives the agent context for a setting, error, or confusing step while the customer remains in the loop about what is happening on the device.
Chat adds a direct channel for short instructions, confirmations, and explanations alongside the remote view. This combination is useful for help desks that need to point out a control, verify a change, or guide someone through a repair without relying on a long phone call or a separate messaging app on the same device.
Remote Control with Customer Permission
GoToAssist can use Android accessibility access during an active support session to provide broader remote assistance. Depending on the device and session, the agent may be able to guide or control supported actions rather than describing them, which can shorten troubleshooting for customers who are not comfortable navigating technical settings.
The customer remains the gatekeeper for the connection: the session begins with a support key, and sensitive device access should go to an agent the customer trusts. This makes the app most useful for attended support, device setup, and guided fixes where both sides need to stay coordinated. It suits short, hands-on assistance when instructions alone would be slower.
Notification and Session Awareness
The Android app can use notifications to keep a customer aware of support activity and permission changes while a session is being prepared or running. Notification controls are available through Android settings, so users can decide how prominently the app appears on the lock screen, in the notification shade, or as a pop-up throughout the live support process.
This is practical when a support session needs the customer to approve a prompt, return to the app, or notice that an agent has connected. For privacy, the customer should review the support request and the person providing the key before enabling broader device access.
