Anyone who runs or buys DevOps support knows the moment. A ticket comes in about slow deployments or noisy alerts, and the support engineer replies with a suggestion: switch the monitoring product, add a particular backup tool, move to a different managed database. The suggestion may be perfect. It may also come with a partner agreement the customer has never heard about. This FAQ answers the practical questions about telling customers what is in it for the support provider whenever such recommendations come up.
What does “saying what’s in it for you” mean in a support setting?
It means a support engineer, account manager or managed-services lead states in one plain sentence any interest the provider has in the product being suggested. A reseller margin, a partner programme, a shared roadmap or a past employer all count. The sentence comes before the recommendation, so the customer reads the advice with the right context.
Why does it matter for managed support specifically?
Support relationships are built on delegated trust. Customers hand over alerts, access and decisions to a provider because they lack the time to handle them. That delegation makes a provider’s recommendation weightier than a stranger’s online opinion. When customers later discover an undisclosed tie, they do not only doubt one recommendation; they wonder about every ticket the provider has ever closed with a suggestion attached.
Does disclosing a tie mean the recommendation is bad?
No. Many good recommendations come from providers who know a product well because they work with it. Familiarity is often the reason the advice is useful. Disclosure does not claim the advice is tainted; it lets the customer decide how much weight to give it. Picture an ingredient label on a jar rather than a warning sticker on the lid.
What should the sentence include?
- The other party’s name: which product or vendor you mean.
- The kind of tie: reseller margin, partner arrangement, former employer, shared ownership, free tooling for the support team.
- A neutral alternative, if one exists: “an option without any arrangement with us is also worth a look.”
Keep it to a line or two. Long justifications invite more questions than they answer.
Where in a ticket reply should it go?
Immediately ahead of the suggestion, rather than tacked on afterward or hidden in a signature block. Example: “We have a reseller arrangement with the vendor of this backup tool. With that said, based on what you described, here is how it would fit your setup.” The customer reads the tie, then the advice, and then judges both together.
What about tools the support team uses internally?
Internal tools matter when you suggest customers adopt the same ones. If your team receives a free licence for a ticketing or alerting product and then recommends it, say so. A tool used in-house is a legitimate reason to recommend it, and the licence status is simply part of the story.
Do we need to disclose every time, even to long-standing customers?
Yes, briefly. A customer who heard about a partnership two years ago may have forgotten, and new people join customer teams all the time. A short reminder costs a few words. If you have a standing arrangement, a footer note on your support portal can complement, but not replace, the sentence in the reply.
How does this show up in a real ticket?
Take a customer whose on-call engineers are drowning in duplicate alerts. The support engineer thinks a certain alert-routing product would help and that the provider earns a small margin on it. The reply opens: “Heads up that we earn a margin when customers buy this through us.” Then it explains how the routing works, offers a free open-source alternative with a short comparison and invites the customer to decide. The customer feels respected and often asks for a call to discuss the options.
For a broader view of how support teams approach daily work, you can read the blog’s overview of principles behind steady software delivery, which sets the context for why plain communication matters in operations.
Does this apply outside of IT?
Yes. Every field where people recommend things for a living has it. Content creators who feature products for brands are an obvious case, and sites that broker those deals have appeared around them. CollabGigs, a marketplace site for brand-backed sponsored content, is one such go-between; the posts themselves are made by independent publishers on their own platforms. Whatever the setting, the rule of thumb is identical: tell your audience what you gain before you tell them what to do.
What if our contract with the vendor forbids saying so?
Then raise it with the vendor before the next recommendation, or stop recommending that product to customers. A relationship you cannot mention is a relationship that should not be shaping advice. Most partner programmes do not forbid honest statements; if one does, that is a good reason to review the arrangement.
How do we train a support team to do this?
- Write a one-page list of the provider’s current vendor ties, kept in the team’s shared notes.
- Agree two or three sentence templates and keep them short.
- Review a handful of past tickets each month for missed opportunities.
- Treat misses as prompts to improve the template, not as blame.
If you are weighing wider careers in this area, a guide to the many job titles and routes within DevOps shows where support fits among them.
What if the customer asks us to recommend something we have a tie with?
Treat the request the same way. The customer asked for your view, which is a reason to be more open, not less. State the tie, give your honest answer and mention a comparable option where you have no arrangement. That small extra effort tends to be remembered at renewal time.
What is the short version?
Say what the provider gains, name the other party, point to a neutral alternative where there is one and put all of it before the suggestion. It takes under a minute per ticket and keeps the relationship on firmer ground. Customers do not expect a provider to have no interests. They expect to be told.