Open a request
Log the customer’s issue in the queue with a priority.
Your customer opens a link, types a code and shares a screen or window from their browser. You guide them in the chat, and the session stays tied to their request.
Three steps from a request to a solved problem, with the person in charge of their own screen.
Log the customer’s issue in the queue with a priority.
Send the join link by email or chat; the code rides along after the # sign.
Watch the shared window, answer in the chat and leave pointer notes, then resolve the request.
A starting point, not a rule: every setting can change per workspace.
| Setting | Suggested | Why |
|---|---|---|
| Approval | Ask the person you help | The customer decides, on the join page |
| Queue | One request per customer issue | Each session links back to its request |
| Reports | Resolution time and SLA met | Shows how fast customers get unstuck |
Yes. They use their desktop browser’s own screen sharing: open the link, type the code, click Share my screen.
Open the join link from the support team in Chrome, Edge, Firefox or Safari on a computer, type the code and click Share my screen. The browser does the sharing.
Not the screen. On a phone they can still join with the code and use the chat.
No. Notes your team adds stay in the console. The customer sees the chat and your pointer notes.
Tell us about your team and how you help people today. We read every request and reply by email.
Office hours: Monday to Saturday, 10:00–18:00 IST+91 74158 85838