{"id":37126,"date":"2019-10-31T22:15:53","date_gmt":"2019-10-31T19:15:53","guid":{"rendered":"https:\/\/prohoster.info\/blog\/razbor-kejsa-pro-obshhenie-s-tyazhelym-klientom\/"},"modified":"2019-10-31T22:15:53","modified_gmt":"2019-10-31T19:15:53","slug":"razbor-kejsa-pro-obshhenie-s-tyazhelym-klientom","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/razbor-kejsa-pro-obshhenie-s-tyazhelym-klientom","title":{"rendered":"Case study on communication with a 'difficult' client","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Case study on communication with a &#039;difficult&#039; client\" src=\"\/wp-content\/uploads\/2019\/08\/824fdbb6ccb9e743b0d425faec1d6fa0.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<i>Sometimes, a technical support engineer faces a tough choice: apply the dialogue model 'We prioritize high service culture!' or 'Click the button - get the result'?<\/i><\/p>\n<blockquote><p>\u2026Breaking a wing made of cotton,<br \/>\nLet\u2019s lie in the clouds like in crypts.<br \/>\nWe, poets, are seldom saints,<br \/>\nWe, poets, are often blind.<br \/>\n(Oleg Ladyzhensky)<\/p><\/blockquote>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nWorking in Tech Support is not just about funny stories of jumping time and GPS unicorns, and not only about detective puzzles in the style of Hercule Poirot. <\/p>\n<p>Technical Support is, first and foremost, communication, and communication implies people, and among our clients, there are very diverse characters:<\/p>\n<ul>\n<li> A German working from a cafe across from his office in Berlin, possessing truly Nordic endurance, perfect calmness, a meticulously calibrated network, and a vast array <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/en\/server\/\"   title=\"servers\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"1349\">servers<\/a> of cognitive abilities to set up and maintain everything at an A+. Requests from him usually evoke the same reaction as the last dumpling on a plate in a large company and poorly timed lighting.<\/li>\n<li>A Brit who has changed companies twice in the last 5 years but has not changed his support style. Either people run away from his cases like from the bubonic plague, or they take them on, anticipating the entire 'delight' of working with this person, as he may unexpectedly seize control during a remote session (to check his mail, sometimes personal), pressuring engineers and management over the smallest details, and, finally, just as suddenly close tickets with the comment 'DUPLICATE'. <\/li>\n<li>An Indian with a complex and unpronounceable surname, debunking all myths about Indian IT: polite, calm, competent, reading documentation, listening to engineers' advice, and always doing everything himself, sporting a fabulous turban (yes, we found him on Facebook) and perfect Oxford pronunciation. <\/li>\n<\/ul>\n<p>\nSuch 'named' clients, each engineer can remember about five without much thought. Some scare our newcomers ('if you misbehave in the lab \u2013 the boogeyman will come and!..'), while others we boast about ('I already have 5 tickets closed with N.!'). More often, we even remember and understand that positive and negative examples are merely our perception, which arises from communication, our interactions with clients and their interactions with us.<\/p>\n<p>Communication can take many forms.<\/p>\n<p>We've previously discussed <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/veeam\/blog\/252019\/\">the 'demons' that hinder engineers from working with clients<\/a><\/noindex>, and now I want to show how this can manifest with a live example.<\/p>\n<p>Here's a good example from two years ago: the client's reaction to the 'traditional' troubleshooting steps from the engineer and the engineer's response to the client's communication style.<\/p>\n<h3>A case about fragmentation<\/h3>\n<p>\nSo, the case: a very experienced and technically savvy client opens a support request and asks a direct question, providing numerous details to describe the situation.<\/p>\n<p>I took the liberty of rewriting the correspondence as a dialogue while preserving stylistic features.<\/p>\n<p><i>Client (C): \u2014 Good day, sir. My name is Marco Santino, we followed your best practices and installed the latest technology you recommended, but we see that the system's performance is becoming critically low due to high fragmentation. Is this normal?<\/p>\n<p>Engineer (E): \u2014 Hi, Marco! My name is Ignat, and I will help you. Is this happening all the time? Have you tried defragmenting?<\/p>\n<p>(C): \u2014 Dear Ignat! Yes, it occurs all the time. We tried defragmenting, but unfortunately, it takes too long during the complete downtime of the system, so it's not feasible.<\/p>\n<p>(E): \u2014 You know, I can't seem to find those best practices. Where did you find it? And maybe, let's consider doing the defragmentation?<\/p>\n<p>(C): \u2014 Dear Ignat! Understanding that you do not take our problem seriously and restraining myself from a direct, rather than politically correct response, we will still attempt to answer you. We lack your experience (we've only been in IT since 1960), and we are very grateful for your work and efforts in enlightening us. The best practices were shared with us by your Product Managers over dinner in Barcelona, and I sent you a link to them. We, however, would like to ask you directly, is this situation normal? If you are not interested in talking to us, please find someone who can help us.<\/p>\n<p>(E): \u2014 Marco, I can't seem to find those best practices. I need the logs, and I will pass the issue to another engineer. Let me say this: if you see fragmentation and do not defragment\u2014it\u2019s foolish and irresponsible. And seriously, how could you confuse the noble name 'Ignat' and call me Ivan? <\/p>\n<p>(K): \u2014 That's enough! I am not your brother or your relative, so please address me as Mr. Santino! If you cannot find the document and cannot handle such a simple task, either resign from the company or ask the author who submitted this document! As for the logs, we cannot provide them to you without special clearance, as we work with confidential documents. Your outrage regarding my mistake shows your ignorance and lack of upbringing. I truly pity you. And lastly: if we say we 'tried to defragment' and that it 'is impossible,' it means we tried and it is indeed impossible. Ignat, I ask you to stop with the nonsense and focus on your work \u2014 either give us an answer or find someone who will!<\/i><\/p>\n<p>After that, the request was escalated to a higher level, where it simply died\u2014 the client never provided the logs, full-scale testing yielded no results, and the problem could not be confirmed.<\/p>\n<p>Question: What could the engineer have done to avoid escalating tensions and conflict?<\/p>\n<p>(Try to answer this question yourself before reading on).<\/p>\n<p>A lyrical technical digression<br \/>\nFor those who love mysteries and the question 'who is the culprit?': the problem turned out to be much more serious: fragmentation of ReFS not only affected disk operations but, in some cases, increased CPU and RAM usage by up to ten times, and it was not just Veeam clients suffering\u2014 all ReFS users could be affected.<\/p>\n<p>Microsoft took more than a year, with the support of many vendors, to finally fix this bug (in which we see our own contribution\u2014 many copies were broken in the support of this giant at all levels).<\/p>\n<p>In response to the question 'what could have been done?', I want to pose another, eternal question: 'Who is to blame?'<\/p>\n<p>As a matter of professional solidarity, I really want to say: 'The client is to blame,' \u2014 and start defending the engineer. As a manager who constantly evaluates the work of my engineers, I see mistakes that Ignat made. Who is right?<\/p>\n<h3>Let's break this down step by step<\/h3>\n<p>\nThis case is very tough, there are more questions than answers.<\/p>\n<p>Formally, Ignat did everything quite well: <\/p>\n<ul>\n<li>he followed one of Veeam's core values: Conversation from the heart;<\/li>\n<li>addressed the client by name;<\/li>\n<li> clarified the situation before suggesting a solution.<\/li>\n<\/ul>\n<p>\nCould he have avoided such a passionate outburst?<\/p>\n<p>Yes: notice how Mr. Santino communicates (formally, using 'You' and his surname), refrain from 'basic questions', show genuine interest in the issue, and promise to investigate whether this behavior is acceptable.<\/p>\n<p>Minimal steps, without any technical details \u2013 would have helped 'extinguish' the situation. But even if that was missed, simply 'not reacting' could have been somewhat helpful.<\/p>\n<p>It sounds obvious: don't take a typo personally, don't be offended by a sarcastic client (even if everything suggests an inflated ego), don't make the conversation personal, don't give in to provocations\u2026 Look how many 'don'ts' there are, all important and all about communication.<\/p>\n<p>But what about the client? The letters are written in a 'high style', constant references to connections at the very top, veiled insults and hurt from perceived disrespect? Yes, we can read it that way. On the other hand, is Mr. Santino really wrong in his anger?<\/p>\n<p>And still, what could have been done from both sides? I see it this way:<\/p>\n<p>From the engineer's side:<\/p>\n<ul>\n<li>assess the client's level of formality;<\/li>\n<li>follow 'basic isolation' less strictly;<\/li>\n<li>(this will be subjective) read emails more carefully;<\/li>\n<li>respond to questions instead of evading them;<\/li>\n<li>and finally, don't give in to provocations and don\u2019t make it personal.<\/li>\n<\/ul>\n<p>\nFor the client:<\/p>\n<ul>\n<li>clearly state the issue in the very first email, without hiding it in technical details (this does not follow directly from the dialogue, but trust me, the level of detail was astounding);<\/li>\n<li>be a bit more tolerant of questions \u2014 not everyone thinks the same way, and sometimes you have to ask a lot to understand the essence of the problem;<\/li>\n<li>perhaps restrain the urge to showcase your significance and connections 'at the highest level';<\/li>\n<li>and, as for Ignat, avoid making it personal.<\/li>\n<\/ul>\n<p>\nI reiterate \u2014 this is just my view, my assessment, which in no way constitutes recommendations or a guide on 'how to live and work'. This is one way to look at the situation, and I would be happy if you could share your thoughts.<\/p>\n<p>I'm not defending the engineer \u2013 he's a malicious Pinocchio on his own. I'm not blaming the client \u2013 he has every right to communicate as he sees fit, even if that communication is more concealed in a delicate lace of almost subtly polite insult (a good image of a modern hidalgo, who doesn't engage in mercenary work or war, but in IT \u2013 although...)<\/p>\n<p>\"The scythe met the stone\" \u2014 this is how I can summarize this correspondence, or to express it in other words, in a truth I sincerely believe in: \"in any conflict, usually both parties are to blame.\"<\/p>\n<p>I could put it in the words of our business trainer: \"past experiences, communication habits, and different worldviews hinder successful communication.\" One can recall the golden rule of ethics: \"Treat others as you want them to treat you.\"<\/p>\n<p>Or I could simply say: in any communication, there are always two participants, and on the other end of the phone line or monitor from you is a living person, who also feels scared, happy, sad, or something else. Yes, it is believed that emotions and business are incompatible, but how can we escape emotions? They have been, are, and will be, and even if we are Technical Support dealing with specific tasks, our main job is defined by the second word: \"support.\"<\/p>\n<p>Support is about people.<\/p>\n<p>***<\/p>\n<p>Remember, I wrote twice that both parties are to blame? Well, in this case, there is even more \u2014 specifically in this situation, all three are to blame. Why? Simply because the engineer is not an isolated entity, but a part of the support team, and it is our job and responsibility to teach the employee how to navigate similar situations. We strive to learn from our mistakes \u2014 and to help our employees avoid them.<\/p>\n<p>Can such situations always be avoided? Not always. No matter how good a hypothetical engineer Ignat is, on the \"other side\" there may be a person who will do everything to escalate the situation.<\/p>\n<p>But the beauty of working in Veeam Technical Support, one of the values we take pride in \u2014 is teamwork. It is very important to remember: \"You are not alone,\" \u2014 and we do everything to make sure that it is so.<\/p>\n<p>Is it possible to teach someone to live and work in such situations? Yes, it is.<\/p>\n<p>We know, love, and practice this \u2014 that's why we've built our internal training and continue to refine and polish it. In the two and a half years since the situation described, we have seriously worked on our training program \u2014 and now actively use cases, model situations, accumulate, and continually revisit our mistakes to discuss the nuances of communication.<\/p>\n<p>We believe that our team is now much better prepared to face any situation when they go 'into the field', and if something comes up that they aren't ready for \u2014 we're here, ready to help, and afterwards we will enhance our courses with new examples.<\/p>\n<p>And this pays off. For instance, here\u2019s feedback from one of our clients about our work:<\/p>\n<p><i>\"We\u2019ve worked in the IT industry for more than 20 years, and we all agree no vendor offers the level of technical support that Veeam offers. It\u2019s a pleasure to speak to Veeam\u2019s technical staff because they\u2019re knowledgeable and resolve issues fast. Support should never be underrated. It\u2019s a measure of a company\u2019s commitment and success. Veeam is #1 for support.\" <\/i><\/p>\n<p><i>\"We\u2019ve worked in the IT industry for more than 20 years, and we all agree that no other vendor provides the level of technical support that Veeam does. It\u2019s a pleasure working with Veeam engineers because they know their stuff and can solve problems quickly. Technical support should never be underestimated. It is a measure of how responsible and successful a company is. Veeam has the best support.\"<\/i><\/p>\n<p>***<\/p>\n<p>Any communication is a field for experiments and mistakes, whether we like it or not. In my opinion, making mistakes is normal; moreover, my call is: make mistakes! It's not about tripping up, but about whether you learn to stand firm afterward.<\/p>\n<p>Sometimes it\u2019s hard to catch myself and remember all the instructions and recipes generously shared by 'gurus' of customer communication or experienced colleagues. It\u2019s much easier at times to remind myself: 'I am talking to a Human.'<\/p>\n<p>***<\/p>\n<p>I don\u2019t claim to have the highest knowledge or a special quality standard in customer communication. The list of just my mistakes would be enough for a comprehensive textbook.<\/p>\n<p>The goal I set for myself was to demonstrate how it can be in Technical Support and to spark a discussion on what can be considered acceptable in such cases, and what cannot.<\/p>\n<p>What do you think?<br \/>\n<br \/>Source: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/veeam\/blog\/463307\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u043e\u0440\u043e\u0439 \u043f\u0435\u0440\u0435\u0434 \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u043e\u043c \u0442\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u0438 \u0441\u0442\u043e\u0438\u0442 \u043d\u0435\u043b\u0435\u0433\u043a\u0438\u0439 \u0432\u044b\u0431\u043e\u0440: \u043f\u0440\u0438\u043c\u0435\u043d\u0438\u0442\u044c \u043c\u043e\u0434\u0435\u043b\u044c \u0434\u0438\u0430\u043b\u043e\u0433\u0430 \u201c\u041c\u044b \u2014 \u0437\u0430 \u0432\u044b\u0441\u043e\u043a\u0443\u044e \u043a\u0443\u043b\u044c\u0442\u0443\u0440\u0443 \u043e\u0431\u0441\u043b\u0443\u0436\u0438\u0432\u0430\u043d\u0438\u044f!\u201d \u0438\u043b\u0438 \u201c\u041d\u0430\u0436\u043c\u0438 \u043d\u0430 \u043a\u043d\u043e\u043f\u043a\u0443 \u2014 \u043f\u043e\u043b\u0443\u0447\u0438\u0448\u044c \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u201d? \u2026\u041d\u0430\u0434\u043b\u043e\u043c\u0438\u0432 \u043a\u0440\u044b\u043b\u043e \u0438\u0437 \u0432\u0430\u0442\u044b, \u041b\u044f\u0436\u0435\u043c \u0432 \u043e\u0431\u043b\u0430\u043a\u0430, \u043a\u0430\u043a \u0432 \u0441\u043a\u043b\u0435\u043f\u044b. \u041c\u044b, \u043f\u043e\u044d\u0442\u044b, \u0440\u0435\u0434\u043a\u043e \u0441\u0432\u044f\u0442\u044b, \u041c\u044b, \u043f\u043e\u044d\u0442\u044b, \u0447\u0430\u0441\u0442\u043e \u0441\u043b\u0435\u043f\u044b. (\u041e\u043b\u0435\u0433 \u041b\u0430\u0434\u044b\u0436\u0435\u043d\u0441\u043a\u0438\u0439) \u0420\u0430\u0431\u043e\u0442\u0430 \u0432 \u0422\u0435\u0445\u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u0435 \u2014 \u044d\u0442\u043e \u043d\u0435 \u0442\u043e\u043b\u044c\u043a\u043e \u0441\u043c\u0435\u0448\u043d\u044b\u0435 \u0431\u0430\u0439\u043a\u0438 \u043f\u0440\u043e \u0441\u0430\u043c\u043e\u043f\u0440\u044b\u0433\u0430\u044e\u0449\u0435\u0435 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27836,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37126","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.1.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u043e\u0440\u043e\u0439 \u043f\u0435\u0440\u0435\u0434 \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u043e\u043c \u0442\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u043e\u0439.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/razbor-kejsa-pro-obshhenie-s-tyazhelym-klientom\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0420\u0430\u0437\u0431\u043e\u0440 \u043a\u0435\u0439\u0441\u0430 \u043f\u0440\u043e \u043e\u0431\u0449\u0435\u043d\u0438\u0435 \u0441 \u201c\u0442\u044f\u0436\u0435\u043b\u044b\u043c\u201d \u043a\u043b\u0438\u0435\u043d\u0442\u043e\u043c | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u043e\u0440\u043e\u0439 \u043f\u0435\u0440\u0435\u0434 \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u043e\u043c \u0442\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u043e\u0439.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/razbor-kejsa-pro-obshhenie-s-tyazhelym-klientom\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:15:53+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:15:53+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Case Analysis on Communicating with a \"difficult\" Client | ProHoster","description":"Sometimes a technical engineer is faced with.","canonical_url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/razbor-kejsa-pro-obshhenie-s-tyazhelym-klientom","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0420\u0430\u0437\u0431\u043e\u0440 \u043a\u0435\u0439\u0441\u0430 \u043f\u0440\u043e \u043e\u0431\u0449\u0435\u043d\u0438\u0435 \u0441 \u201c\u0442\u044f\u0436\u0435\u043b\u044b\u043c\u201d \u043a\u043b\u0438\u0435\u043d\u0442\u043e\u043c | ProHoster","og:description":"\u041f\u043e\u0440\u043e\u0439 \u043f\u0435\u0440\u0435\u0434 \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u043e\u043c \u0442\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u043e\u0439.","og:url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/razbor-kejsa-pro-obshhenie-s-tyazhelym-klientom","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:15:53+00:00","article:modified_time":"2019-10-31T19:15:53+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37126","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-02-09 17:07:03","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:33:24","updated":"2026-02-09 17:07:03","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/37126","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=37126"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/37126\/revisions"}],"predecessor-version":[{"id":158593,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/37126\/revisions\/158593"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media\/27836"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=37126"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=37126"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=37126"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}