The biggest pitfall of handling support yourself is thinking you can answer questions better than the platform itself. You've just set up your first customer for security awareness in the system. Within a week, the first questions flood in: "How do I add users?" "What does this report mean?" "Why aren't we seeing this data?"
Your first instinct is understandable. You want complete control over your customer relationship, you want to give quick answers, and you want to see your customers satisfied. Yet this is precisely the moment when many partners make a costly mistake. Even though it feels like you have to do everything yourself, that's not wise right now.
This article builds on "How to Become a Security Awareness Reseller" and an article on organizing support as a partner. Read this article as a warning before you take complete support into your own hands.
Risk 1: You make promises about things the platform cannot do
Your first customer calls with a question: "Can we organize the training modules differently per department?" It seems simple. You're not far enough along in understanding the platform to say no immediately, so you say: "I'll look into that for you."
Three weeks later, you discover it's not possible. Your customer is disappointed. Worse: your customer now thinks you're incompetent, when the platform simply doesn't have this feature. Your reputation takes damage—not because you did something wrong, but because you made a promise you couldn't keep.
This problem grows as you gain more customers. Your team gives inconsistent answers. Sometimes you say 'yes', sometimes 'no', even though it's the same question. You lose credibility too.
This is exactly the risk that the article "How to Avoid the Pitfalls of White-Label Solutions" warns about: lack of technical mastery leads to demos you can't give yourself and questions you can't answer.
Risk 2: You're trapped in something beyond your control
Your customer wants something the platform cannot (yet) do. You say: "Sure, I'll discuss that with 2LRN4." Weeks pass. Maybe it's possible, maybe not. Maybe it's on the roadmap for next winter.
In the meantime, you're stuck in the middle. You've made a promise, your customer is waiting, and you have no answer. Worse: you have to defend yourself to your customer about things you have no control over. "The platform can't do that yet" is not what you want to tell someone who pays you monthly.
You feel powerless. And that feeling grows every time something like this happens.
Risk 3: Your team burns out on questions that aren't your core business
Technical-level support is not part of what you do well. You're a salesperson, account manager, consultant—not someone who gives technical support. Yet you now spend hours each week on questions like "My password doesn't work" and "How do I end my session?"
These are precisely the questions everyone wants to avoid. They feel repetitive, they consume time, and they don't feel like the work you're actually good at. Your best team member, the one who enjoys helping customers, is getting frustrated resetting passwords instead of doing what she's good at.
In six months, you've lost that team member. And you've had much less time for real growth.
Practice: Who does what?
You build this division step by step as you grow. Ask yourself this question for every support inquiry: "Is this about how the platform works, or is it about how this fits into my customer's organization?"
You answer the second question. For example: "How do we use this for our phishing awareness program?" or "How do we fit this into our compliance routines?" or "What does this data mean for our organizational culture?"
2LRN4 answers the first question. For example: "How do I add a user?" "What is this field in the report?" "Why don't I see this option?" "How do I set this up?"
In practice, these lines blur quickly. An escalation protocol helps: you make a list of questions you answer yourself, and everything else goes to 2LRN4.
The 80/20 Rule
This is the division that lets you grow:
- You: 20% of support. These are the strategic, relationship-building questions.
- 2LRN4: 80% of support. These are the technical and operational questions about how the platform works.
This way you maintain personal contact with your customers and aren't trapped in technical questions where you don't have a satisfying answer anyway. Your customers get faster and better answers. And you and your team can invest energy in what actually drives growth.
Checklist: Are you ready to handle support yourself?
Use this checklist before deciding to set up support in-house:
- Do you have at least 5-10 customers and see clear question patterns?
- Do you know the platform well enough to answer 80% of questions yourself?
- Have you written a support handbook with answers to frequently asked questions?
- Is your team trained and enthusiastic about support, or does it feel like extra work?
- Do you have a clear escalation protocol to 2LRN4 for technical questions?
- Do you understand that support is a service, not part of your core business?
Didn't check everything? Then you're not ready yet. And that's fine—you're just not there yet.
Later: When you CAN take support in-house
Do you want to handle more support yourself later? Fine. But only do this once you can answer all the questions above with 'yes'.
Also read article 5 in this series: "How to Organize Your Support as a Partner". That article goes into detail about when you CAN take support in-house without burning out yourself and your team.
For how you master the platform yourself, consult all our guides at 2lrn4.com/en/support.
Start Small
Start by letting 2LRN4 do what it does best: give technical support. You onboard your customers, you ask the strategic questions, and you gradually learn the platform step by step—without sacrificing your team.
This feels less in control at first. And that feeling is correct: you don't control the technical side. But you don't need to. You do control what you do best: the relationship, the advisory value, and your business growth. That's where your margin is—not in answering technical questions.
See also: "Why White-Label Security Awareness Delivers More Than You Think". Margin comes from value, not from work.