{"id":4772,"date":"2026-10-18T08:01:47","date_gmt":"2026-10-18T08:01:47","guid":{"rendered":"https:\/\/summitnext.com\/?p=4772"},"modified":"2026-10-18T08:01:53","modified_gmt":"2026-10-18T08:01:53","slug":"net-promoter-score","status":"publish","type":"post","link":"https:\/\/summitnext.com\/ru\/net-promoter-score\/","title":{"rendered":"Net Promoter Score: \u041a\u0430\u043a \u0438\u0437\u043c\u0435\u0440\u0438\u0442\u044c \u0438 \u0447\u0442\u043e \u0434\u0435\u043b\u0430\u0442\u044c \u0441 \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u0430\u043c\u0438"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>TL;DR<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Net promoter score is one question on a 0 to 10 scale. Promoters (9 to 10) minus detractors (0 to 6), as percentages, gives a score from minus 100 to plus 100.<\/li>\n\n\n\n<li>The number is a prompt, not a verdict. It earns its place when a named owner calls unhappy customers back and a fix list gets funded.<\/li>\n\n\n\n<li>Read it beside CSAT and CES. Segment it before you act on it. Keep it away from individual bonuses.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Net promoter score is the customer metric most boards have heard of and fewer teams know how to use. The calculation takes a minute. The harder part starts once the number lands on a slide: who calls the unhappy customers, which fixes get funded, what the front line hears when the score moves.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you run HR, finance or operations at a company of 50 to 500 people, there&#8217;s a good chance you inherit an NPS figure from a support or CX team and get asked to explain it, resource it or defend it. You may also be the person deciding whether a bonus plan should touch it. Those decisions go better when you know what the metric can and can&#8217;t tell you.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A score earns a place on the dashboard only when someone owns the follow-up. Most of the value sits there, and most of this article is about building it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What is net promoter score?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Net promoter score (NPS) is a customer loyalty metric built on one question: how likely are you to recommend us to a friend or colleague, scored from 0 to 10. Fred Reichheld of Bain introduced it in the December 2003 Harvard Business Review article &#8220;The One Number You Need to Grow&#8221;. Answers of 9 or 10 mark promoters. Answers of 7 or 8 mark passives, and 0 to 6 mark detractors. Subtract the percentage of detractors from the percentage of promoters and you get a whole number from minus 100 to plus 100. Passives stay in the response total but add nothing to either side of the subtraction. One figure stands in for a whole customer base, so NPS shows the direction of sentiment without the cause. It works best as a trigger for follow-up questions. This describes the standard published method; many companies adapt the wording and survey cadence, and that limits comparability. Source: <a href=\"https:\/\/en.wikipedia.org\/wiki\/Net_promoter_score\" target=\"_blank\" rel=\"noopener\">Wikipedia on net promoter score<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The bands look lopsided on purpose. Seven of the eleven points sit in the detractor range, because the method treats a 6 as a customer who isn&#8217;t going to speak well of you. A 7 or 8 is polite but unattached. Only a 9 or 10 counts as the kind of enthusiasm that sends a colleague your way.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Most surveys pair the 0 to 10 question with one open text box: &#8220;What is the main reason for your score?&#8221; That box is where the value sits. The number tells you how many people are unhappy. The comments tell you what to fix first.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How do you calculate NPS?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Work out the share of promoters and the share of detractors, then subtract the second from the first. Drop the percent sign and keep the whole number. Passives matter only because they enlarge the total behind the percentages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Here is a hypothetical worked example. The figures are invented to show the arithmetic and are not a benchmark for any business or industry.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Say a support team collects 200 responses in a quarter. Ninety people answer 9 or 10. Seventy answer 7 or 8. Forty answer 0 to 6. Promoters are 90 of 200, or 45 percent. Detractors are 40 of 200, or 20 percent. The score is 45 minus 20: 25.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Now take a second hypothetical team that also lands on 25 with a different mix: 30 percent promoters, 5 percent detractors and 65 percent passives. Same score, very different customer base. The first team has a loud, split audience. The second has a quiet, lukewarm one. One number hides that gap, so show the distribution every time you report the score.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Two habits keep the calculation honest. Report the number of responses beside the score. Keep the question wording and scale identical from one survey to the next, since a changed prompt breaks any comparison with last quarter.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you&#8217;d like help designing a feedback loop that fits your support operation, <a href=\"https:\/\/summitnext.com\/consultation-services\/\">talk to SummitNext about a free consultation<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Relational or transactional NPS: which should you run?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Run relational NPS to learn how customers feel about the company overall. Run transactional NPS to learn how a specific interaction landed. They answer different questions, so many teams run both and keep the results apart.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Relational surveys go out to your customers at regular intervals, regardless of recent contact. They pick up the cumulative effect of product quality, pricing, billing and support together. Transactional surveys fire after a defined event such as a closed ticket, a delivery or an onboarding call. They point you at a specific process and team.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Timing changes the answer. Send a survey minutes after a resolved ticket and you catch relief or irritation while it&#8217;s fresh. Send it a month later and you catch what stuck. Neither is wrong, but they measure different things, so pick the moment on purpose and keep it fixed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Watch the frequency. A customer who gets a survey after every interaction will tire of it, and survey fatigue is among the documented criticisms of the method. Cap how many times one customer can be asked, and apply the cap across channels so a phone caller and a chat user are treated alike.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If part of your support is outsourced, the surveys should still run under your brand and your rules. The customer relationship is yours, whoever picked up the call. <a href=\"https:\/\/summitnext.com\/how-to-choose-a-customer-support-outsourcing-partner\/\">How to choose a customer support outsourcing partner<\/a> covers how that split is usually set up, and <a href=\"https:\/\/summitnext.com\/what-is-bpo-a-complete-guide-to-business-process-outsourcing\/\">what BPO means for your operations<\/a> gives the wider context.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How many responses do you need, and what skews them?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There is no magic response count that makes NPS reliable. You want enough responses that a handful of answers can&#8217;t swing the score, and respondents who resemble the customers who stayed silent. Any single threshold would be false precision, so this article doesn&#8217;t offer one.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sample size first, in plain words. With few responses, one extra detractor moves your score by a lot. With many, it barely registers. If a segment has only a handful of answers, treat its score as a conversation starter, not a trend.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Response bias is the quieter problem. People who answer surveys are not a random slice of your customers. Customers with a strong opinion, good or bad, respond more often. Some groups respond far less than others. Declining response rates are among the documented criticisms of NPS, so the skew can grow over time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A few checks help. Compare the mix of respondents with your customer base by market, language and plan. Note which channels produce answers and which stay quiet. Record how many people received the survey as well as how many replied, so a falling response rate shows up instead of hiding inside a stable score.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How should you segment NPS results?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Segment the score before you act on it. A company-wide figure averages away the places where something is breaking. A flat overall score can sit on top of one improving segment and one deteriorating one.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Useful cuts are the ones tied to a decision you can make. Market or language, if you serve several. Channel, such as phone, chat or email. Customer tenure or account type. The team or queue that handled the contact. Each cut should point to an owner who could change something.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The comments matter more than the scores inside a segment. Read the open text for detractors in each cut and tag the reasons: a slow first reply, a repeated question, a billing error, a product fault. Rank the tagged reasons by frequency and you have the first draft of your fix list.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How do you close the loop with detractors?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">To close the loop, a named person contacts unhappy customers, hears the problem and says what will change. A survey becomes a service recovery step, and your team gets the unfiltered reasons behind low scores.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Decide who owns it before the first survey goes out. Pick someone with the authority to fix or escalate and the time to make the call. Set a response window you can keep, and track your record against it. A promised call that nobody makes does more damage than no promise.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Responsibility needs a clear split here. When a SummitNext-supported team works with your customers, SummitNext owns the HR side: payroll, compliance and benefits. You keep operational management. That covers the customer relationship, the scripts and the decision to credit or refund. The boundary tells you who calls the detractor and who can say yes to a remedy, and the loop breaks when nobody is sure which side owns the call. <a href=\"https:\/\/summitnext.com\/customer-experience-outsourcing-how-global-brands-scale-support-across-regions\/\">Customer experience outsourcing for global brands<\/a> shows how that division plays out across regions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Proximity helps too. SummitNext staff can work at your premises, so they sit near the product and billing teams who fix root causes. A detractor&#8217;s complaint can reach the right desk faster than a ticket note would. Remote-only models can close the loop as well, but they need a deliberate route for that information to travel.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How does NPS sit next to CSAT and CES?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">NPS gauges overall loyalty. CSAT gauges satisfaction with a specific interaction or product. Customer effort score (CES) gauges how hard it was to get something done. Each answers a different question, so they work better as a set than as rivals.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CSAT asks how satisfied a customer was with a particular interaction, on a short scale, and fits transactional moments such as a closed ticket. CES arrived in the 2010 Harvard Business Review article &#8220;Stop Trying to Delight Your Customers&#8221;. The original version was a single five-point item about the effort needed to handle a request, and later versions moved to a seven-point agreement format. An independent study found mixed predictive power for CES compared with satisfaction, so it isn&#8217;t a guaranteed forecaster either. (<a href=\"https:\/\/measuringu.com\/customer-effort-score\/\" target=\"_blank\" rel=\"noopener\">Source: MeasuringU on customer effort score<\/a>).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A workable pairing: use CES or CSAT right after a support interaction to find friction, and use NPS on a slower rhythm to see if the relationship is strengthening. If interaction scores look healthy while NPS falls, look outside support, at product, pricing or billing. If NPS holds while effort scores climb, a process is quietly getting harder and customers haven&#8217;t left yet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the operational data behind those readings, see <a href=\"https:\/\/summitnext.com\/ai-tools-analytics-for-malaysian-bpo-performance-measurement\/\">AI tools and analytics for BPO performance measurement<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What are the criticisms of NPS, and how do you avoid gaming it?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Critics point to thin evidence that the recommend question predicts growth better than other measures, no detail on causes, falling response rates, survey fatigue and the risk of tying the score to employee pay. All of it applies to any NPS programme, including a well-run one.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">NPS has several documented weaknesses. Critics note limited evidence that the recommend question predicts business growth better than other customer measures. A single score gives no detail on causes, so it needs open comments and follow-up to be useful. Response rates are declining, and repeated requests cause survey fatigue. The sharpest risk appears when the score is tied to employee pay, because staff then have reason to influence who is surveyed and how the question is framed. A careful programme treats NPS as one input beside CSAT, CES and operational data. It reports the response count with every score and keeps individual compensation separate from the figure. These criticisms are summarised from public references on the metric, and how much they matter depends on your customer base and how the survey is run. Source: <a href=\"https:\/\/en.wikipedia.org\/wiki\/Net_promoter_score\" target=\"_blank\" rel=\"noopener\">Wikipedia on net promoter score<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Gaming rarely looks like fraud, and you may never see it labelled as such. It looks like an agent asking happy customers to &#8220;rate us a 10&#8221;, a survey sent only after resolved cases, or angry customers routed away before the survey fires. Each action is small. Each inflates the score without improving anything.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Protect the metric with design, not suspicion. Send surveys on a rule that agents can&#8217;t influence. Report the response rate and the distribution with the score. Audit who was surveyed. Then settle as a leadership team that NPS informs coaching and process fixes rather than individual pay.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">HR carries part of this. If a bonus scheme or performance review will reference customer scores, test it against the gaming risk before it goes live. A team goal tied to completed fixes and call-backs is harder to distort than an individual target tied to a score. Where outsourced staff are involved, agree the principle in writing so both sides apply the same standard.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What should you do with the result? An operations plan<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Turn the score into a standing routine: a named owner, a fixed review rhythm, a ranked fix list and a record of what changed. A number nobody acts on is decoration. Linked to a short list of fixes that get done, it becomes a tool you can run the operation with.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ownership comes first. One person owns the programme, typically in CX or operations. That person reports to someone who can fund fixes. Detractor call-backs sit with people who have authority to resolve. Root-cause fixes sit with the teams that own the product, billing or process involved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Match the review rhythm to the survey. A weekly or fortnightly check suits call-back follow-up and new comments. A monthly or quarterly session suits trend review, segment cuts and funding decisions. Keep the agenda short: what customers said, what changed, what it did to the score and the comments.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Keep a fix list with an owner and a status against every item, ranked by how often the reason appears in detractor comments. When an item ships, note the date and watch for those comments to fade. That is the closest honest test that a fix worked, and it doesn&#8217;t depend on the headline score moving in one quarter.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A published SummitNext engagement shows the shape of a fix that comes out of a repeated pattern. For a leading enterprise, a multilingual call centre solution brought inbound inquiries down 30 percent through clearer self-service, with AI handling FAQs and escalating complex cases to people. The case study doesn&#8217;t present itself as an NPS project, so read it as an illustration of an operational change that follows a clear theme, not as proof of how that client chose its fix. You can read the details in the <a href=\"https:\/\/summitnext.com\/multilingual-call-centre-solution-for-a-leading-enterprise\/\">multilingual call centre case study<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Small is a fine start. SummitNext has no minimum headcount, so one dedicated hire to run call-backs and tag comments is a valid first step. The team can grow with the volume of feedback. The <a href=\"https:\/\/summitnext.com\/customer-experience-optimization\/\">customer experience optimization service<\/a> is the place to discuss that. Retention teams use the same feedback too: see <a href=\"https:\/\/summitnext.com\/how-malaysian-businesses-use-crm-to-boost-customer-retention-in-2025\/\">how Malaysian businesses use CRM to improve customer retention<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Brief the front line as well. Explain what the score is. Say what it won&#8217;t be used for. Show what changed because of customer comments. Agents who see their feedback turn into fixes engage with the programme. Agents who only see a score on a wall defend themselves against it. <a href=\"https:\/\/summitnext.com\/best-practices-for-managing-a-remote-customer-support-team\/\">Managing a remote customer support team<\/a> covers the day-to-day side.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently asked questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What is a good net promoter score?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">There&#8217;s no universal answer, because the figure depends on your customers, your market and how the survey is run. A score is more useful measured against your own history and your own segments than against an outside number. Watch the trend, the response count and the reasons in the comments rather than chasing a target.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do you calculate NPS from survey responses?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Count the share of respondents who answer 9 or 10 and the share who answer 0 to 6. Subtract the second percentage from the first. The result is a whole number between minus 100 and plus 100. Passives, who answer 7 or 8, count in the total but not in the subtraction.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How often should we send an NPS survey?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Send relational surveys at a steady interval that suits your customer cycle, and transactional surveys after defined events. The right frequency is the one that keeps response rates stable without tiring customers. Set a limit on how often any single customer can be asked, and apply it across every channel you use.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How many responses do we need for a reliable NPS?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No fixed number works for every business. The aim is enough responses that a few answers can&#8217;t swing the score, from people who resemble your wider customer base. Report the response count beside the score, and treat small segments as prompts for conversation rather than conclusions about performance.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should we replace CSAT with NPS?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No, they measure different things and work better together. CSAT or CES captures how a specific interaction went, while NPS tracks the wider relationship over time. Using them as a set lets you tell a support problem from a product or billing problem when scores move in different directions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should NPS be tied to employee bonuses?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It carries risk. Tying NPS to individual pay is among the documented criticisms, because staff gain a reason to influence who is surveyed and how. A safer approach uses NPS for coaching and process fixes, with any incentive linked to team-level actions such as completed call-backs and shipped fixes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Net promoter score is simple to calculate and easy to misuse. The question and the 0 to 10 scale give you a comparable number. The practice around it decides how much weight the number carries: a stable survey design, honest response reporting, segments tied to decisions and a named owner who calls detractors.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Treat the score as one input beside CSAT, CES and operational data. Keep it clear of individual pay. Judge success by fixes shipped and complaints that stop appearing. If you&#8217;d like a second pair of eyes on your feedback loop, or want to explore a small dedicated team to run it, <a href=\"https:\/\/summitnext.com\/contact-us\/\">book a free consultation with the SummitNext team<\/a>.<\/p>\n\n\n\n<script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is a good net promoter score?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"There's no universal answer, because the figure depends on your customers, your market and how the survey is run. A score is more useful measured against your own history and your own segments than against an outside number. Watch the trend, the response count and the reasons in the comments rather than chasing a target.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How do you calculate NPS from survey responses?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Count the share of respondents who answer 9 or 10 and the share who answer 0 to 6. Subtract the second percentage from the first. The result is a whole number between minus 100 and plus 100. Passives, who answer 7 or 8, count in the total but not in the subtraction.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How often should we send an NPS survey?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Send relational surveys at a steady interval that suits your customer cycle, and transactional surveys after defined events. The right frequency is the one that keeps response rates stable without tiring customers. Set a limit on how often any single customer can be asked, and apply it across every channel you use.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How many responses do we need for a reliable NPS?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"No fixed number works for every business. The aim is enough responses that a few answers can't swing the score, from people who resemble your wider customer base. Report the response count beside the score, and treat small segments as prompts for conversation rather than conclusions about performance.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Should we replace CSAT with NPS?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"No, they measure different things and work better together. CSAT or CES captures how a specific interaction went, while NPS tracks the wider relationship over time. Using them as a set lets you tell a support problem from a product or billing problem when scores move in different directions.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Should NPS be tied to employee bonuses?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"It carries risk. Tying NPS to individual pay is among the documented criticisms, because staff gain a reason to influence who is surveyed and how. A safer approach uses NPS for coaching and process fixes, with any incentive linked to team-level actions such as completed call-backs and shipped fixes.\"\n      }\n    }\n  ]\n}\n<\/script>\n<chat-widget key=\"Ylr00kdTsgQXZHKuRfRs\"><\/chat-widget>","protected":false},"excerpt":{"rendered":"<p>TL;DR Net promoter score is the customer metric most boards have heard of and fewer teams know how to use. The calculation takes a minute. The harder part starts once the number lands on a slide: who calls the unhappy customers, which fixes get funded, what the front line hears when the score moves. If [&hellip;]<\/p>\n","protected":false},"author":8,"featured_media":4773,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[18],"tags":[],"class_list":["post-4772","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-customer-experience"],"_links":{"self":[{"href":"https:\/\/summitnext.com\/ru\/wp-json\/wp\/v2\/posts\/4772","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/summitnext.com\/ru\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/summitnext.com\/ru\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/summitnext.com\/ru\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/summitnext.com\/ru\/wp-json\/wp\/v2\/comments?post=4772"}],"version-history":[{"count":1,"href":"https:\/\/summitnext.com\/ru\/wp-json\/wp\/v2\/posts\/4772\/revisions"}],"predecessor-version":[{"id":4774,"href":"https:\/\/summitnext.com\/ru\/wp-json\/wp\/v2\/posts\/4772\/revisions\/4774"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/summitnext.com\/ru\/wp-json\/wp\/v2\/media\/4773"}],"wp:attachment":[{"href":"https:\/\/summitnext.com\/ru\/wp-json\/wp\/v2\/media?parent=4772"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/summitnext.com\/ru\/wp-json\/wp\/v2\/categories?post=4772"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/summitnext.com\/ru\/wp-json\/wp\/v2\/tags?post=4772"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}