Support
Attended Remote Assist
Remote access is privileged. YBT confirms the issue, your permission and the safest next step before any connection is agreed.
What this can help with
Start with the situation, not the technical label.
Sending an enquiry does not launch a remote session. We first understand the issue, confirm that remote help is suitable and agree what the session is for.
- Software and settings problems
- Email and account configuration
- Reasonable troubleshooting
- Guided setup where remote work is safe
Permission → connect → resolve → disconnect
What you will get
A useful result you can understand and keep.
- A focused attended session
- A service note and next actions
- Clean session termination
Ownership: You retain control of the device and can observe or end the attended session; access is removed when the session finishes.
Attended support lifecycle
Permission first. Access ends when the session ends.
- 01Confirm authority and scope
- 02Connect with the customer present
- 03Resolve or record the safe next step
- 04Disconnect and remove temporary access
How the work usually happens
Clear steps, with room for the real problem.
You will know what is included before work begins. If the sensible answer is a smaller change—or no build at all—we will say so.
Understand
Review the issue without connecting
Choose
Confirm identity permission and consent
Deliver
Agree and conduct the attended session
Validate
End access and record the outcome
Good to know
A few things to understand before starting.
- No emergency or same-day guarantee
- No passwords recovery codes or payment details should be sent
- Active cyber incidents data recovery and specialist hardware faults are escalated
Things that may affect the route
- Scheduled and best-efforts rather than emergency or 24/7
- No uncontrolled permanent agent for ad-hoc customers
Next step
Talk through attended remote assist.
Tell us what you are trying to change. We will help work out the sensible next step.