{"id":5855,"date":"2026-11-22T06:50:00","date_gmt":"2026-11-22T06:50:00","guid":{"rendered":"https:\/\/www.devopssupport.in\/blog\/support-faq-tell-customers-what-you-gain\/"},"modified":"2026-11-22T06:50:00","modified_gmt":"2026-11-22T06:50:00","slug":"support-faq-tell-customers-what-you-gain","status":"publish","type":"post","link":"https:\/\/www.devopssupport.in\/blog\/support-faq-tell-customers-what-you-gain\/","title":{"rendered":"Support FAQ: Do You Tell Customers What You Gain From a Tip?"},"content":{"rendered":"<p>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.<\/p>\n<h2>What does &#8220;saying what&#8217;s in it for you&#8221; mean in a support setting?<\/h2>\n<p>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.<\/p>\n<h2>Why does it matter for managed support specifically?<\/h2>\n<p>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&#8217;s recommendation weightier than a stranger&#8217;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.<\/p>\n<h2>Does disclosing a tie mean the recommendation is bad?<\/h2>\n<p>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.<\/p>\n<h2>What should the sentence include?<\/h2>\n<ul>\n<li><strong>The other party&#8217;s name:<\/strong> which product or vendor you mean.<\/li>\n<li><strong>The kind of tie:<\/strong> reseller margin, partner arrangement, former employer, shared ownership, free tooling for the support team.<\/li>\n<li><strong>A neutral alternative, if one exists:<\/strong> &#8220;an option without any arrangement with us is also worth a look.&#8221;<\/li>\n<\/ul>\n<p>Keep it to a line or two. Long justifications invite more questions than they answer.<\/p>\n<h2>Where in a ticket reply should it go?<\/h2>\n<p>Immediately ahead of the suggestion, rather than tacked on afterward or hidden in a signature block. Example: &#8220;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.&#8221; The customer reads the tie, then the advice, and then judges both together.<\/p>\n<h2>What about tools the support team uses internally?<\/h2>\n<p>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.<\/p>\n<h2>Do we need to disclose every time, even to long-standing customers?<\/h2>\n<p>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.<\/p>\n<h2>How does this show up in a real ticket?<\/h2>\n<p>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: &#8220;Heads up that we earn a margin when customers buy this through us.&#8221; 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.<\/p>\n<p>For a broader view of how support teams approach daily work, you can read <a href=\"https:\/\/www.devopssupport.in\/blog\/devops-principles-for-effective-software-delivery\/\">the blog&#8217;s overview of principles behind steady software delivery<\/a>, which sets the context for why plain communication matters in operations.<\/p>\n<h2>Does this apply outside of IT?<\/h2>\n<p>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. <a href=\"https:\/\/collabgigs.com\/\">CollabGigs, a marketplace site for brand-backed sponsored content<\/a>, 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.<\/p>\n<h2>What if our contract with the vendor forbids saying so?<\/h2>\n<p>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.<\/p>\n<h2>How do we train a support team to do this?<\/h2>\n<ol>\n<li>Write a one-page list of the provider&#8217;s current vendor ties, kept in the team&#8217;s shared notes.<\/li>\n<li>Agree two or three sentence templates and keep them short.<\/li>\n<li>Review a handful of past tickets each month for missed opportunities.<\/li>\n<li>Treat misses as prompts to improve the template, not as blame.<\/li>\n<\/ol>\n<p>If you are weighing wider careers in this area, <a href=\"https:\/\/www.devopssupport.in\/blog\/a-guide-to-devops-role-titles-career-paths-job-roles\/\">a guide to the many job titles and routes within DevOps<\/a> shows where support fits among them.<\/p>\n<h2>What if the customer asks us to recommend something we have a tie with?<\/h2>\n<p>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.<\/p>\n<h2>What is the short version?<\/h2>\n<p>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.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Practical questions and answers on how DevOps support teams should state partner ties, margins and past employers before suggesting a product in a ticket.<\/p>\n","protected":false},"author":8,"featured_media":5856,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3948],"tags":[],"class_list":["post-5855","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops-support"],"_links":{"self":[{"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/posts\/5855","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/comments?post=5855"}],"version-history":[{"count":0,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/posts\/5855\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/media\/5856"}],"wp:attachment":[{"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/media?parent=5855"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/categories?post=5855"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopssupport.in\/blog\/wp-json\/wp\/v2\/tags?post=5855"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}