Mon to Fri 8:00 to 18:00 CT Austin, Texas
SPLE / REMOTE BENCH +1 (899) 555-5520
SPLE 30.27 N
97.74 W
  1. Home
  2. How a session runs
Process / P1

A remote tech support session starts with a code you read out, and ends with nothing of ours left on your machine.

This is the clock of a booked remote computer support session, from the confirmation email to the moment we disconnect. You watch the screen the whole time. Nothing connects until you click Allow, and the block price is agreed in writing before that click.

From $45 per 30-minute block Hardware verdict inside 10 min, no fee Windows 11 / macOS
Phone on speaker while the customer accepts the connection prompt 00:01 / The Allow prompt
Timeline / T1

Thirty minutes of a remote support session, by the clock.

This is a typical 30-minute block for a single problem. A 60-minute booking runs the same way with a longer middle. Times are measured from the moment you click Allow, not from when the phone rings.

  1. −1 day

    Booking confirmed in writing

    You send the form or call +1 (899) 555-5520. We reply with a time, the block length and the price basis, which starts at $45 for 30 minutes. If the problem description smells like hardware, we say so here and save you the booking. Same-day slots happen; we never promise one.

  2. −5 min

    We call you

    On the number you gave. Not a chat window, not a robot. A technician asks you to describe the fault in one sentence and to have the machine on, plugged in and logged in. If it is a laptop, put it on the charger. A battery that drops to 4% mid-update is how a 30-minute job becomes two.

  3. 00:00

    You open the tool and read us the code

    On Windows we use Quick Assist, which ships with Windows 10 and 11. On a Mac, or where Quick Assist is blocked, we send a link to a one-time RustDesk client that runs without installing. You read us the code on your screen: six characters in Quick Assist, a nine-digit ID plus a one-time password in RustDesk. It expires when the session closes, so a code read out yesterday opens nothing today.

  4. 00:01

    Consent prompt: you click Allow

    Your operating system shows a prompt naming the session and the permission requested: view only, or full control. We ask for full control only when the fix needs it, and we tell you which before you click. Until you click, we see nothing. If you click Deny, the session never existed.

  5. 00:02

    Triage, out loud

    We look at what you see: Event Viewer or Console, Device Manager, the disk health report, the update history. We narrate as we go. "Opening Settings, Windows Update, Update history" is the level of detail you should expect. If you want silence, say so; most people stop listening by minute four.

  6. 10:00

    Hardware checkpoint

    By the tenth minute we know whether this is a screen-side job. If SMART shows reallocated sectors climbing, if the battery report shows swelling-level wear, if the machine shuts off under load, we stop. You get a written note of what we found and which kind of bench to take it to, and that session is not charged. That is how we work, not a promise about how your fault will turn out.

  7. 10:00
    to 27:00

    The fix

    The actual work. A driver replaced with the maker's own package, an Outlook profile rebuilt, a print spooler cleared, a startup list cut from 41 entries to 9. Anything we install, we name before we install it. Anything we delete, we name before we delete it. You can say stop at any point and the clock stops with you.

  8. 27:00

    Over-run question

    If the fix will not finish inside the block, we say so at minute 27 and ask before the next 30 minutes start. You can say no. We leave the machine in a working state, write down where we got to, and you can book the remainder later. We never roll into a second block on silence.

  9. 30:00

    Test, then disconnect

    You run the thing that was broken while we watch: print the page, send the mail, open the shared drive. Then we close the session from our side, and you see the tool close on yours. Quick Assist leaves nothing behind. The RustDesk one-time client is deleted in front of you before we hang up.

Logging / L1

Every session leaves a paper trail you can read.

The technician keeps notes while the session runs. Not a recording of your screen. We do not record video of sessions, and we would rather lose the occasional "what did you click at minute 14" argument than hold footage of somebody's inbox.

What gets written down is plain: start and end time, the tool used, the permission level you granted, each change made and why, anything installed or removed, and the result of the test at the end. You get a short summary by email after the call. If something we changed causes trouble later, that summary is how the next technician picks it up in two minutes instead of twenty.

Session note / what is recorded
FieldExample entryWho sees it
Window14:02 to 14:29 CTYou and us
Tool and accessQuick Assist, full controlYou and us
ChangesGeneric PCL6 driver removed, maker's driver 4.1 installedYou and us
Left installedNothingYou and us
OutcomeTest page printed from Word and EdgeYou and us
Customer closing the laptop once the session has ended 30:00 / Disconnected
Close / E1

How the session ends, and what stays behind.

  1. You test it, not us

    The fault is fixed when you can do the thing yourself. We watch you print, sign in or connect, then we stop.

  2. We close from our side

    The session window closes on both screens. The code you read out is dead from that moment.

  3. Leftovers removed in front of you

    Any one-time client is deleted, and we show you the Apps list or the Applications folder without it.

  4. Summary and invoice by email

    Usually within the hour. The invoice matches the price confirmed before you clicked Allow.

  5. Seven days of cover

    If the same symptom comes back within 7 days, the follow-up session costs nothing. The full wording is in the terms, under Session guarantee.

Questions / Q1

The four questions people ask before the first call.

If yours is not here, ask it on the phone. We would rather spend two minutes on it before the session than ten during.

Can you see my files while you are connected?

Technically, with full control, yes, the same as someone sitting at your desk. That is why you watch. We open only the windows the fault needs, and we say what we are opening before we open it. If a folder is private, close it before we start; we will work around it.

What if my internet drops mid-session?

The session dies with it and nothing is left half-connected. We call you back, you read a fresh code, and the clock resumes where it stopped. If the fault is the internet itself, we work from your phone's hotspot or move to the router and Wi-Fi job.

Who is this not for?

Anyone whose machine will not power on, will not reach the desktop, or has had a drink spilled into it. Remote help needs a working screen and a network. Those go to a local bench, and our about page explains where we stop and why.

I look after other people's machines. Can I sit in?

Yes. Repair shops and freelance IT book us for their own clients, often with three people on the call. Sessions can run under your shop's name; see the technician's second pair of hands.

Book / B1

Book a 30-minute block. We ask before the next one.

From $45 per block, confirmed in writing before we connect. Booking hours Mon to Fri 8:00 to 18:00 CT.