REACH integrated into your mobile app and customer support platform. It's that simple. Here is how your customer enables support and save you staff time and money,
Your customer requests a support session using their mobile phone with your mobile app to connect with a customer support representative to initiate the Reach℠ support session.
Reach℠ can support any device that can accept incoming communications of some kind. Common communication protocols include Bluetooth, Bluetooth Low Energy, local WiFi, USB, ect. A mobile app or desktop with Reach℠ may be customized for any kind of communication.
Today, Reach℠ SDKs are provided in TypeScript/JavaScript, Kotlin, and Swift and can be integrated into your already-existing device interaction code. If you need an SDK for a different language, contact us.
Before a customer support agent is allowed to connect, a unique PIN number is shared to ensure the highest level of security and privacy.
Reach maintains the highest level of security by encrypting traffic during transport. No data is stored on Reach servers
The customer is required to stay in proximity of the device with their mobile or desktop application to ensure that they have physical access to the device at all times.
Once the technician is allowed access, a two-way communication channel is created between the technician and the customer.
The technician leverages the Reach℠ communication functionality to get and set information on the device, without the need for customer interaction.
The customer can sit back and relax while the technician works, without the typical back-and-forth that is often required to identify the technical details that are affecting the customer’s device.
Instead, the technician has access to all of the technical details of the device via the web-to-mobile and mobile-to-device communication channels.
Things like:
• Logs
• Firmware updates
• Device controls and configuration
• Event logs
Reach℠ is designed to interact seamlessly with a mobile or web app’s UI. UI elements can react to changes in both the device’s connection status and the device’s state via callbacks, which keeps the customer in the loop about what’s happening on their device. Reach℠ supports chat messages that include text, photos, and videos to help the customer and technician diagnose the issue.
Technicians can perform customer support for customers despite language barriers. Once the technician has access to the device, the customer likely does not need to be involved in the process of updating the device. In order to gain access, the customer only needs to enter a pin number into their mobile app; this is often possible despite language barriers, giving the technician access to the information they need.
If the internet connection between the customer support technician and the customer drops, Reach℠ will automatically reconnect the session when an internet connection is restored and the support session will pick up where it left off. All data transfer is paused on disconnect and resumed on reconnect, ensuring that frequent drops due to poor internet connections don’t prevent customers from getting their devices fixed.
The most common customer support requests are for connectivity issues. Reach℠ can sidestep the issue where technicians are unable to connect to the device remotely due to the customer’s device connectivity issues because, rather than connecting to the device, the technician can connect to the customer’s mobile device, which can, in turn, connect to the device over LAN or BLE technology. This provides better remote access to devices for technicians.