The Best Salesperson in Your Building Doesn't Know They're a Salesperson
July 29, 2026

The Best Salesperson in Your Building Doesn't Know They're a Salesperson

A tech just spent forty minutes on a call with a client whose server had been throwing errors all morning.

The client was stressed. Her team couldn't access the files they needed for a client presentation at noon. She had already tried restarting things twice herself. By the time she called, she wasn't just frustrated with the technology. She was frustrated, embarrassed in front of her own team, and running out of time.

Your tech found the issue, fixed it, and had her back up with fifteen minutes to spare before her meeting.

She thanked him. Genuinely. The kind of thank you that has real relief behind it, not the polite kind people say out of habit.

He said "no problem, let me know if you need anything else" and moved to the next ticket in the queue.

That was the single highest-trust moment this client will experience with your business all year, and it just evaporated into nothing.

Nobody did anything wrong. The tech did his job well. He fixed the problem fast and treated her with respect the whole time. He just had no idea that the thirty seconds after he solved her problem were worth more than anything your sales team could have said to her in a month of outreach, and so he let it pass like every other ticket.

Here is what nobody has told him. He is your best salesperson. He doesn't know it yet.

WHY THAT MOMENT IS WORTH MORE THAN A SALES CALL

Think about what your sales team has to do to earn a prospect's trust. They start from zero, usually with a stranger, usually with that stranger fully aware they are being pitched to. Every word gets filtered through the prospect's guard. It takes calls, meetings, proposals, and time to get anywhere close to the trust your tech just built in forty minutes by actually solving a real problem.

Your help desk tech starts every conversation already ahead. The client called because something was genuinely wrong. The tech fixed it. There was no sales filter running in her head during that call, because the conversation was never framed as a sales conversation. By the time the ticket closed, she wasn't thinking about being sold to. She was thinking about relief, gratitude, and the fact that someone competent just saved her morning.

That emotional state is the best possible condition for a referral, an upsell mention, or a genuine testimonial to exist in. Nothing manufactured. Nothing rehearsed. A trained salesperson has to build urgency and rapport from a cold start. Your tech had real urgency handed to him by her actual crisis, and rapport that was earned by actually fixing it.

A sincere thank you delivered by the person who just proved their competence converts better than almost anything your sales team produces. It isn't a pitch. It's the truth, spoken by the person who just lived it with her.

THE THREE MOMENTS YOU ARE LETTING PASS EVERY DAY

There are three specific moments buried inside every resolved ticket where your techs are sitting on value nobody has ever told them how to use.

The resolution moment. The issue is fixed. Relief is at its peak. This is the single highest-trust moment in the entire client relationship, and most techs let it pass with "let me know if you need anything else." They did nothing wrong. Nobody ever told them there was something more valuable available in that window.

The pattern recognition moment. A tech who works enough tickets for the same client starts to notice things nobody else in your business ever sees. The same issue keeps coming up. The client is clearly outgrowing a piece of their stack. The client mentioned something in passing about opening a second location or hiring a new team. Techs hear this constantly. Almost none of it ever gets routed anywhere, because nobody ever told them it mattered or gave them a simple way to pass it along.

The referral moment. A client who just had a great experience is, for a short window, the most likely person in your entire client base to think of someone else who needs the same help. That window closes fast. If nobody asks while the gratitude is fresh, the impulse fades and the referral never happens, even though she genuinely would have given it if asked in the moment.

Every one of these moments happens dozens of times a week across your help desk team right now. Almost none of them get captured because nobody built the system to capture them.

HOW TO FIND THE TECHS WHO ARE ALREADY WIRED FOR THIS

Not every tech should become a salesperson. Some of your best technical minds are introverted, task-focused, and would resent being pushed into anything that feels like sales. That's fine. This isn't about forcing every person on your help desk into a role they will hate and be bad at.

Start the identification before you even hire. Look at resumes for customer service experience outside of IT entirely. Retail. Food service. Hospitality. Call centers. Any job where someone had to manage a frustrated person face to face or voice to voice and turn the interaction around before clocking out. That experience teaches something technical certifications never touch. How to read emotional tone. How to de-escalate someone who is upset. How to leave a stranger feeling better than they felt when the interaction started. A candidate with two years waiting tables alongside their technical training often has sharper instincts here than a candidate whose only experience is help desk tickets.

Once someone is hired, watch for the signals that are already showing up in how they work. Which techs get unsolicited thank-you notes from clients. Which techs have clients who call back and ask for them by name. Which techs naturally chat with a client while they work instead of sitting in silence. Which techs already say things like "you might want to think about upgrading that" without anyone ever telling them to.

Those are your naturally wired people. They are already doing an informal, unrecognized version of exactly what this post is about to give a name to.

WHAT TO ACTUALLY GIVE THEM

This isn't about handing your techs a sales script and a quota. It is about giving your naturally wired people three specific tools they don't currently have.

Language for the resolution moment. A simple, natural line that opens the door without sounding like a pitch. Something like, "Glad we got that sorted for you. If you know anyone else dealing with something like this, feel free to send them our way, we're always happy to help." Thirty seconds. Zero pressure. A massive difference from silence.

A simple way to flag patterns. A field in the ticket system. A dedicated Slack channel. A five-second note at ticket close. "Mentioned they're opening a second location next quarter." "This is the third time this month with the same printer issue." Someone on the sales or account management side needs to see that within days, not never.

Recognition when it works. When a flagged pattern turns into a real opportunity, or a referral a tech mentioned turns into a new client, celebrate it the same way you would celebrate a closed sales deal. Publicly. By name. That recognition teaches the whole team this is a real, valued part of the job, not busywork stapled onto their actual job.

WHY THIS BEATS HIRING ANOTHER SALESPERSON

You are already paying for these conversations. The tech is already on the call. The client is already engaged, already trusting, already grateful for what just happened. There is no additional headcount required to capture any of this. No new hire. No new base salary. No new commission plan competing against the one you already run.

The only investment is training your naturally wired techs on the language, building the lightweight system to capture what they notice, and recognizing them publicly when it produces something real. That costs a fraction of a single new sales hire, and it converts on trust that already exists instead of trust that has to be built from a cold start.

Most owners keep adding to their sales team to solve a growth problem that is sitting unused on their own help desk.

WHERE THIS LIVES IN YOUR FIELD GUIDE

This belongs in your field guide's sales and client experience systems, documented as a defined extension of the help desk role rather than an informal hope that occasionally happens with your one naturally gifted tech.

Document the resume signals to screen for in hiring. Document the resolution-moment language so techs aren't improvising in the moment. Document the pattern-flagging system and exactly where it routes once a tech notes something. Document the recognition cadence that reinforces the behavior publicly. And document the clear boundary for techs who aren't naturally wired for this, so nobody feels pressured into a role that doesn't fit who they are.

When it is documented, this becomes a system that produces referrals and upsell signals consistently across your entire help desk team. Not an accident that only happens with the one or two people who were naturally good at it without anyone ever asking them to be.

You have salespeople on your help desk right now.

They are closing trust deals every single ticket, in moments your actual sales team could never manufacture, and you have never once told them that is what they are doing.

Look at your resolved ticket volume this week. Multiply it by the number of clients who felt real relief when the issue got fixed. That is the number of high-trust moments your business produced and let evaporate because nobody gave the person in that moment the language, the system, or the recognition to use it.

Find the techs who are already doing this instinctively. Give them the three tools. Document the system in your field guide so it runs consistently instead of by accident.

Your best salesperson has been answering tickets the whole time. Go tell them. Start at builttorunmsp.com.

FREQUENTLY ASKED QUESTIONS

Why are help desk technicians effective at generating referrals and upsells?

Help desk technicians build trust in a way a traditional salesperson can't replicate. A salesperson has to earn trust from a cold start, usually with someone who knows they are being pitched to. A help desk tech earns trust by actually solving a real problem the client was frustrated by, which means the trust is proven rather than promised. The moment right after a ticket is resolved is the highest-trust point in the entire client relationship, because the client is experiencing genuine relief and gratitude rather than sales resistance. A referral request or upsell mention made in that moment converts at a much higher rate than the same message delivered through a traditional sales channel.

How do you identify which help desk technicians will be good at generating referrals?

Look for customer service experience outside of IT on their resume before you even hire them. Retail, food service, hospitality, and call center experience all teach a skill that technical certifications don't: how to read emotional tone, de-escalate frustration, and leave someone feeling better than they did at the start of the interaction. After hiring, watch for signals in how a tech already works. Technicians who get unsolicited thank-you notes, who have clients asking for them by name, who naturally chat with clients during a fix, or who already mention upgrade opportunities without being told to are showing you they are naturally wired for this role extension.

What should a help desk technician say to a client after resolving a ticket?

A short, natural line that opens the door without sounding like a sales pitch works best. Something like, "Glad we got that sorted for you. If you know anyone else dealing with something like this, feel free to send them our way, we're always happy to help." The key is keeping it brief, low-pressure, and genuine rather than scripted. The goal isn't to close a deal in that moment. The goal is to plant a natural invitation while the client's gratitude and trust are at their peak, which is a completely different conversation than a formal sales pitch.

How do you capture sales opportunities that help desk technicians notice during tickets?

Build a lightweight flagging system rather than relying on techs to remember and manually follow up. A dedicated field in the ticket system, a specific Slack channel, or a five-second note at ticket close works well. The tech notes something specific, like a client mentioning an upcoming expansion or a recurring issue that signals they have outgrown part of their stack. Someone on the sales or account management side needs to see that flag within days so it can be acted on while it is still relevant. Without a defined system, this information gets mentioned once in passing and then disappears because nobody owns following up on it.

Does every help desk technician need to become a salesperson?

No, and trying to force it will backfire. Some of the best technical minds on a help desk team are introverted, task-focused, and would resent being pushed into anything that feels like sales. The goal is identifying the technicians who are already naturally wired for this, based on resume signals and observed behavior, and giving them specific tools rather than pressuring the entire team into an unnatural role. Technicians who aren't naturally suited for this should continue focusing on excellent technical resolution, which remains the foundation the entire trust-based approach depends on in the first place.

About the author
Adam Kuester

Adam Kuester

Adam Kuester has a PhD in genetics and a career built inside managed services, an unusual combination that shapes how he works. He spent time designing operations at an MSP before joining Bruce McCully to build Galactic Advisors, where he's served as VP of Special Projects. His focus has been operational: finding gaps, building systems, and turning expertise into tools MSP owners can use across a partner base of nearly 1,000 companies. Built to Run MSP is that same work in a different form, practical frameworks for MSP owners who are good at winning business and want to get equally good at running it.