Skip across the chapter
Quota Playbook

Remote access rules: 3 checks before a rep gets IT help

Quota Playbook Editorial Team · Published · 12 min read

Before approving remote IT help for a rep, check whether the rep is present, which devices are accessible, and when access ends.

Key takeaways

  • Know whether the rep is present for the session.
  • Count the sessions and devices that one login can reach.
  • Put a time limit on every session, and end it when the job is done.

When a rep's CRM stops syncing or the quoting tool throws an error an hour before a demo, remote help is one possible way to address the problem. A remote session puts another person's hands on a machine that holds customer lists, pricing sheets, contracts, and email. If the session is set up badly, the same access that fixes the quoting tool can expose everything else on the laptop.

You do not need to become a security engineer to make this call well. As the manager, you need a short set of rules that the team knows, and a quick check you run before you say yes.

These rules are general practice, not a security certification. Where I give specific details, they come from two vendor pages: Splashtop's page for its remote support product and Okta's guidance on session lifetime. Those pages describe their own products, not yours. Your IT team or outside provider may use different tools and settings, so treat the details below as questions to put to them, not settings to copy.

Rule 1: Know whether the rep is present

The first question is the simplest: is the rep sitting at the computer while someone connects to it?

Splashtop draws this line clearly on its remote support page. It describes attended support as access to a remote computer "while the user is present, after they run the access app and give you a 9-digit access code" ( Splashtop, Remote Support). In plain terms, the rep starts the session, reads a code to the technician, and watches what happens. That is a very different situation from a technician connecting to a machine while nobody is sitting in front of it.

Attended support is the default you want for a sales rep. Confirm that the rep knows a session is happening, can see what the technician is doing, and knows how to end it using controls the tool permits. It also gives you a natural record: the rep was there, and the ticket can say so.

Unattended access is a different decision. Some IT teams need it for maintenance on machines that no one uses during the day, or for shared equipment. If your team uses it at all, write down who may approve it, which machines it covers, and what the rep should expect to happen. Do not let it become the default just because it is faster to set up. A faster session is not a better one if nobody knows it happened.

Two more checks belong under this rule. First, confirm which product is in use. Splashtop separates its tools by who uses them. Its remote access product is for end users to reach their own computers. The same page says that product uses named-user licensing and supports up to 10 endpoints with each license ( Splashtop, Remote Support). Its remote support product is for IT pros supporting devices, and the page says that one uses concurrent-user licensing and supports up to 300 endpoints with each license ( Splashtop, Remote Support). A rep reaching their own laptop and a technician fixing a device are different uses. If your IT team is using one tool for both, ask why, and ask which license covers each.

Second, teach the rep to treat unexpected requests with suspicion. If someone calls, emails, or messages a rep asking them to start a remote session or read out a code, the rep should stop and confirm with IT through a known number or channel before doing anything. Set the rule in advance, so the rep does not have to decide under pressure in the middle of a call with a customer waiting.

Rule 2: Count the sessions and devices one login can reach

The second rule is about scale. A single login that can reach one laptop is a small risk. A single login that can reach many machines at once is a bigger one, and it is easy to miss because nobody thinks about it when they approve a ticket. The risk grows with the number of accounts, too. Every extra login is another way in, and another name you have to remember when you review who did what.

The Splashtop page makes this concrete. It says that for each technician or user license, up to 10 users can be on the account, and any one of those users may use the product on one device at a time to run remote access sessions ( Splashtop, Remote Support). It also says that from your own computer, you can simultaneously access up to 10 computers and devices at a time ( Splashtop, Remote Support). Those are vendor limits, and your plan may differ. The point for you as a manager is the question behind them: how many people can connect, to how many machines, at the same time?

Put that question into practice with three checks:

  • Who has an account? Get a list of everyone who can start a remote session, including former employees, contractors, and shared logins. Shared logins make it hard to tell who did what, so ask IT to replace them with named accounts wherever the tool allows it.
  • How many machines can one person reach at once? If one technician can open ten sessions from a single console, that is a lot of reach from one set of credentials. Ask whether the setting can be narrowed to the machines the team actually supports, and whether a single person needs that much reach at all.
  • Does the license count match the team? In Splashtop's model, licenses use named-user or concurrent-user counts, so a team can look covered on paper and still be short when two people need to connect at once. A shortage is not a security failure by itself. But guard against sharing logins as a shortcut around a shortage, and solve the licensing question before it turns into a shortcut.

For sales reps specifically, a good default is one rep, one work computer, one session at a time. If a rep's laptop is the only device that matters for their job, there is no reason for a technician to have a stack of other sessions open on the same login. Keep the reach as small as the job requires, and widen it only for a stated reason.

Rule 3: Put a time limit on every session, and end it when the job is done

The third rule is about time. A session that stays open is a session that can be used when no one is watching, and the people who approved it may have forgotten it existed.

Okta's guidance on session lifetime makes the general point well. It says to "enforce a limited session lifetime in your org policies to reduce the risk of malicious access to a user's applications" ( Okta, Enforce a limited session lifetime). Okta is writing about its own organization policies for user applications, not about remote desktop tools. But the principle carries over: an access grant should expire on its own, so that a forgotten session does not stay open indefinitely.

For remote help, that means you should know three things before you approve a session:

  • How long can it last? Ask IT what the maximum session length is for the tool, and whether that length can be set by policy. If the honest answer is "until someone closes it," push for a setting that closes it automatically.
  • Who ends it? The rep should know how to stop the session, and the technician should end it as soon as the fix is confirmed. A session left open after the ticket closes is a problem to prevent.
  • What happens if the fix runs long? Sometimes a problem takes more than one session. The clean answer is to end the session, write down what was done, and start a new one when the rep is ready. A fresh approval is better than a long session that quietly continues while the rep is in a client meeting.

Then close the loop. When the ticket is resolved, ask the rep to confirm the issue is fixed and the session has ended. If a session needs to run past its normal length, the technician should say why in the ticket, and the rep or the manager should approve the extension. Nobody should be surprised to find a remote session still running at the end of the day.

Illustrative example: An attended repair

A rep's quoting tool stops syncing with the CRM before a demo. The rep opens a ticket with IT. You check that the request came from the rep, the rep is at the desk, and the ticket names the laptop that needs the fix.

IT offers a remote session. The rep starts an attended session from the access app, reads the access code to the technician, and stays in the chair. The technician finds a stale sync setting, changes it, and asks the rep to test a quote. The rep confirms that the quote now works. The session ends when the rep says so, and the technician closes the connection. The ticket records what was fixed, when the session started and ended, and who was involved.

A quick check before you say yes

When a rep asks for remote help, run through these questions. Together they cover all three rules.

  1. Will the rep be present, sitting at the machine and watching the session?
  2. Is this an attended session, and is the rep the one who starts it?
  3. Is the request genuine? Did the rep ask for help through a known channel, or did someone contact them first?
  4. Which machine is it, and is that the only one this session needs?
  5. Who is the technician, and do they have a named account rather than a shared login?
  6. How long will the session last, and who will end it when the fix is confirmed?
  7. Will the ticket record what was done, and when the session ended?

If the answer to any of these is unclear, do not guess. Ask IT to clarify before the session starts. A short delay is almost always better than an open-ended session on a machine that holds customer data.

When the deadline pushes back

Reps under deadline pressure will push for a faster path. Sometimes the request is reasonable, and the fix really cannot wait. In those cases, the answer is usually to use the approved path more quickly, not to skip it. Agree in advance on who can approve a same-day session, how the rep can reach that person, and what the rep should do while they wait. A backup laptop, a saved copy of the quote, or a short call with the customer to reschedule a single step can keep the work moving without opening a session.

It also helps to explain the reason behind the rules. People accept a limit more readily when they understand that it protects them and the customer. A rep's laptop often holds more customer information than anyone realizes, and a remote session is the same as handing another person that laptop for a while. Framing the rules that way makes them easier to follow when the pressure is on.

For the next customer call, use the demo screen-share rehearsal checks to review the separate sharing setup.

Today, ask your IT provider to review the checklist above and write down any unanswered questions.

Related guides: Sales rep exit form: 8 fields for file requests and access · Check 9 chat rules for private sales coaching calls · Log call feedback for every rep: 4 vendor rules to check.

Questions to take to your IT provider

Before the next ticket comes in, sit down with whoever runs IT for the team, even if that is one person or an outside provider. You do not need to understand the technical setup. You need answers to a short list of questions, and you need those answers written down.

Which remote access product does the team use?

Ask IT to identify the product and its license model. Is it the product for end users reaching their own computers, the product for IT staff supporting devices, or both? Who pays for the licenses, and how many does the team have? If the answer to the license question is a number you cannot verify, ask for the admin report that shows active accounts, and read it yourself.

Who can start a session, and who can approve one?

Ask IT for the account list and approval rules. Are any accounts shared? Can the tool show a list of past sessions with start and end times? If it cannot, documenting the session in the ticket becomes especially important, and a ticket is only as good as the person who wrote it.

What is the maximum session length?

Ask IT for the current limit and whether it can be set by policy. Does the tool end a session on its own when nobody is active in it, or does it stay open until someone closes it? Who is responsible for ending a session when the ticket is closed?

What changes when someone leaves or joins the team?

Ask IT to document account removal and new-account approval. When someone leaves the company, how quickly are their remote access accounts removed? When the team adds a rep, who approves the new account? Ask IT to tell you before a new tool or a new setting goes live, so the rules in this post can be checked against what is actually in use. For an exit review, also use the seller login removal checks.

Write the answers down in one place. A shared document is enough. If an answer changes later, update it and tell the team. A rule that matches the tool your team really uses is far more useful than a rule written from memory.

Write the rules down

These three rules work best when they are written, short, and shared with the whole team. A one-page note is enough. It should say who may request a remote session, who may approve it, which tool the team uses, what the session limits are, and where to report a session that did not end when it should. Review the note with IT every few months, and again whenever the team changes tools or adds reps.

Your job as the manager is not to understand every setting in the remote tool. It is to make sure the questions get asked and the answers get written down. Presence, reach, and time provide a practical framework for reviewing a remote help session.

Sources

  1. Update team roles in 3 checks after the setup change
  2. Lost seller phone recovery: 4 steps for 2FA lockouts
  3. HubSpot quote checks: 5 limits to run before email
  4. Scoring model limits
  5. HubSpot workflow retention

More plays