{"id":13856,"date":"2017-11-07T15:55:05","date_gmt":"2017-11-07T15:55:05","guid":{"rendered":"http:\/\/blog.intercom.com\/?p=13856"},"modified":"2024-07-25T11:58:07","modified_gmt":"2024-07-25T10:58:07","slug":"the-right-way-to-respond-to-feature-requests","status":"publish","type":"post","link":"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/","title":{"rendered":"The right way to respond to feature requests"},"content":{"rendered":"

If you work in customer support<\/a>, you\u2019ll likely encounter a familiar situation: a user will ask about a feature your product doesn\u2019t support.<\/p>\n

Even the best products with the most passionate users will have these \u201csuccess gaps<\/a>\u201d \u2013 a disparity between your product and the user\u2019s desired outcome.<\/p>\n

It\u2019s easy to respond to these feature requests with a generic \u201cKeep an eye on Twitter for updates\u201d response or a pre-canned \u201cWe\u2019ll pass your feedback onto the product team\u201d message, but we\u2019ve found that it\u2019s valuable to mine these feature requests for deeper information so that you fully understand what the customer is trying to achieve. That way, you\u2019ll be able to strike a balance between keeping customers happy and collecting valuable information that will improve your product\u2019s core value.<\/p>\n

\u201dIt\u2019s perfectly okay to acknowledge that a given feature is not supported.”<\/p>\n

Here\u2019s our best practice guide for handling feature requests in customer support.<\/p>\n

How to manage different types of feature requests<\/h2>\n

Firstly, it\u2019s worth highlighting that not all feature requests are the same. They can be broken out into three different types:<\/p>\n

    \n
  1. Unresolved problems with an existing feature<\/strong> e.g. the customer has experienced a technical issue and is unsure how to make progress.<\/li>\n
  2. Feature improvements<\/strong> e.g. the customer is not sure on how to achieve a certain result with your product.<\/li>\n
  3. A brand new feature request<\/strong> e.g. the customer is asking for something that\u2019s not yet supported in your product.<\/li>\n<\/ol>\n

    Let\u2019s explore these in some more detail.<\/p>\n

    1. Unresolved problems with an existing feature<\/h2>\n

    If you have a software product or web app, there are almost certainly parts of your product that aren\u2019t always working as well as they should be. You\u2019ll likely have customers writing in to say, \u201cHey, this feature I rely on (and pay for) isn\u2019t working. I need help ASAP.\u201d Sure, you could just log the issue in Github and move onto the next conversation but a good support team should be able to educate a customer on how to get to the right outcome, regardless of technical limitations.<\/p>\n

    In these cases, use the request as a jumping off point for a deeper conversation about what exactly they\u2019re trying to achieve. Ask for specific examples and details about the issues they\u2019re running into and act as a consultant on helping them achieve a given result in your product. (I\u2019ve shared some tips for asking these questions in another blog post<\/a>.)<\/p>\n


    \nAvoid committing to a specific time and dates when the issue will be resolved. It’s best to over-deliver rather than promise a specific date and fail to meet it. Instead, share any known workarounds for getting around the problem in the short-term. Quite often, customers don\u2019t care if specific features or functionality aren\u2019t working provided they can still get the job done.     Going the extra mile<\/a> and getting customers to their desired outcome will really help you build customer trust and loyalty towards your company.<\/p>\n

    2. Improvements to an existing feature<\/h2>\n

    Another common scenario is when customers ask for a new piece of functionality in your service. Your Customer Support Reps are your front line, so they will likely be the first people to hear about missing features that are leaving customers disappointed.<\/p>\n

    Resources at any startup are limited and it\u2019s simply not realistic for your product team to build every feature improvement request that comes in. Instead, you should take a step back and think about whether or not you can solve the customer\u2019s problem without any product being built at all. Quite often, what looks like a functionality gap might actually be something that has already been addressed by your product team, just in a different way than what your customer would like.<\/p>\n

    For example, one feature that is regularly requested by Intercom\u2019s customers is the ability to turn off the Intercom messenger outside of their working hours. This isn\u2019t a feature on the product roadmap right now but we can get customers to the same outcome by helping them set customers’ expectations through setting their office hours and expected response time.<\/p>\n

    These answers may not be exactly what the customer wants to hear, but an honest explanation and workaround is often enough to satisfy what they originally asked for. In many cases, customers are simply unaware that an existing feature can be used just as successfully in your product.<\/p>\n

    3. Brand new feature requests<\/h2>\n

    The trickiest conversations to handle are when something is really not supported in your product. Before you respond, ask yourself: Does this request fit into your roadmap and strategy for how you\u2019d like to develop your product?<\/p>\n

    Instead of making promises on something that will never come into life it\u2019s better to be honest and say no to it<\/a> (so long as you’re suggesting a viable workaround).<\/p>\n


    \nIt\u2019s always important to be honest with your customers, so long as you share the context on where this decision is coming from.<\/p>\n

    If the customer is asking for something very specific that\u2019s not on your roadmap, try suggesting a third-party solution or integration that fits that use case. For example, if a customer is looking to manage their calendar, YouCanBookMe already has a solution in place, while Zapier allows you to integrate with dozens of other types of software. Instead of making empty promises on something that doesn\u2019t align with your roadmap, think of possible solutions outside of your own product.<\/p>\n

    It also matters how you talk about gaps in your software. Instead of trying to look for excuses or bending the truth, share some context with your users. It\u2019s perfectly okay to acknowledge that a given feature is not supported yet (while explaining the cool features your engineering team are currently building) but that you\u2019re currently looking at ways to improve experience around the customer\u2019s specific pain point.<\/p>\n

    Sharing details about how you make these difficult decisions and explaining that you\u2019re dealing with limited engineering resources will show your human side and help the customer see your perspective. After all, there\u2019s never enough time to work on all the ideas you want while at the same time staying on top of bugs and issues and making sure you\u2019re aligned with your company mission and long term strategy.<\/p>\n

    How to prioritize feature requests<\/h2>\n

    Once you\u2019ve gathered feature request data from customers, along with their relative importance, you need to find a way to prioritize the suggestions.<\/p>\n

    Potential factors you\u2019ll want to include are:<\/p>\n

      \n
    1. Customer lifecycle<\/strong>. You might want to respond to customers who contact you in the first days after sign-up, as they are at the highest risk of churning.<\/li>\n
    2. High-value users<\/strong>. As they are the customers paying you the most money, you\u2019ll want to pay particular attention to their feedback. Especially if this group plays a crucial role in your long-term growth.<\/li>\n
    3. Difficulty of implementing the proposed improvement<\/strong>. Some feature improvements might be relatively straightforward to implement, and provide 10x value to customers. On the flip side, some improvements look simple, but require months of complex engineering.<\/li>\n
    4. Volume of feedback<\/strong>. Logging the number of times each individual product improvement<\/a> has been suggested can help you make a case for bringing a particular feature request to the product team.<\/li>\n<\/ol>\n

      Closing the loop<\/h2>\n

      Once you\u2019ve gathered and prioritized this feedback from your customers, you should think of ways to feed it back to your product teams. After all, if 50 customers can\u2019t find a given button every week, this is a sure sign something in the interface needs to be fixed.<\/p>\n

      The way we manage this internally is by tagging every single question<\/a> we get (in Intercom of course). It does require some effort, but once you\u2019ve embedded this into workflow of your team you\u2019ll get great data on types of conversations your team is having. On top of that our research team creates customer voice reports on a monthly basis showing the main pain points raised by our customers. This gets shared with the relevant Product Managers so they can prioritise working on specific features and decide what should make it to our roadmap. If you\u2019d like to have some more powerful ways of organising this feedback you could take a look at third- party integrations such as Productboard<\/a>, NomNom<\/a> or Trello PowerUp<\/a>.<\/p>\n

      But regardless of what tool you\u2019re using, the most important thing is not just to gather feature requests, but to act on them too. Whether that\u2019s with a polite, personal response, or an actionable idea handed on to product or engineering, when customers have made the effort to offer a feature request or suggestion, it is only right for us to make sure we respond in a manner that builds long-term customer success.<\/p>\n","protected":false},"excerpt":{"rendered":"

      All customers will have product improvements they would like to see, but responding to those requests requires a rigorous framework to be effective. Here\u2019s our best practice guide for handling feature requests in customer support.<\/p>\n","protected":false},"author":226,"featured_media":13857,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"category":[3],"tags":[19307,142,283],"coauthors":[501],"class_list":["post-13856","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-customer-support","tag-3-support","tag-customer-support","tag-feature-requests"],"yoast_head":"\nThe right way to respond to feature requests - The Intercom Blog<\/title>\n<meta name=\"description\" content=\"What do you do when a customer asks for a feature your product doesn't support? Here's our best practice guide on responding to feature requests in a human way\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The right way to respond to feature requests\" \/>\n<meta property=\"og:description\" content=\"What do you do when a customer asks for a feature your product doesn't support? Here's our best practice guide on responding to feature requests in a human way\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/\" \/>\n<meta property=\"og:site_name\" content=\"The Intercom Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/intercominc\" \/>\n<meta property=\"article:published_time\" content=\"2017-11-07T15:55:05+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-07-25T10:58:07+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2017\/11\/How_Will_You_Build_It-1-700x332.gif\" \/>\n\t<meta property=\"og:image:width\" content=\"700\" \/>\n\t<meta property=\"og:image:height\" content=\"332\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/gif\" \/>\n<meta name=\"author\" content=\"Paulina Welnic\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@pawwelnic\" \/>\n<meta name=\"twitter:site\" content=\"@intercom\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Paulina Welnic\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/the-right-way-to-respond-to-feature-requests\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/the-right-way-to-respond-to-feature-requests\\\/\"},\"author\":{\"name\":\"Paulina Welnic\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#\\\/schema\\\/person\\\/d4a73c4daaf1d87b4e55b502f504530f\"},\"headline\":\"The right way to respond to feature requests\",\"datePublished\":\"2017-11-07T15:55:05+00:00\",\"dateModified\":\"2024-07-25T10:58:07+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/the-right-way-to-respond-to-feature-requests\\\/\"},\"wordCount\":1500,\"publisher\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/the-right-way-to-respond-to-feature-requests\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2017\\\/11\\\/How_Will_You_Build_It-1.gif\",\"keywords\":[\"3 support\",\"customer support\",\"feature requests\"],\"articleSection\":[\"Customer Service\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/the-right-way-to-respond-to-feature-requests\\\/\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/the-right-way-to-respond-to-feature-requests\\\/\",\"name\":\"The right way to respond to feature requests - The Intercom Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/the-right-way-to-respond-to-feature-requests\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/the-right-way-to-respond-to-feature-requests\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2017\\\/11\\\/How_Will_You_Build_It-1.gif\",\"datePublished\":\"2017-11-07T15:55:05+00:00\",\"dateModified\":\"2024-07-25T10:58:07+00:00\",\"description\":\"What do you do when a customer asks for a feature your product doesn't support? Here's our best practice guide on responding to feature requests in a human way\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.intercom.com\\\/blog\\\/the-right-way-to-respond-to-feature-requests\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/the-right-way-to-respond-to-feature-requests\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2017\\\/11\\\/How_Will_You_Build_It-1.gif\",\"contentUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2017\\\/11\\\/How_Will_You_Build_It-1.gif\",\"width\":1968,\"height\":932},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/\",\"name\":\"The Intercom Blog\",\"description\":\"Articles and Podcasts on Customer Service, AI and Automation, Product, and more\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#organization\",\"name\":\"The Intercom Blog\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2019\\\/08\\\/Intercom-logo-sq-black-trans.png\",\"contentUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2019\\\/08\\\/Intercom-logo-sq-black-trans.png\",\"width\":1000,\"height\":1000,\"caption\":\"The Intercom Blog\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/intercominc\",\"https:\\\/\\\/x.com\\\/intercom\",\"https:\\\/\\\/www.instagram.com\\\/intercom\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/2491343\",\"https:\\\/\\\/www.pinterest.ie\\\/intercom\\\/\",\"https:\\\/\\\/www.youtube.com\\\/channel\\\/UCJG0MvLP03kyzzAkD-w98aQ\",\"https:\\\/\\\/en.wikipedia.org\\\/wiki\\\/Intercom_(company)\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#\\\/schema\\\/person\\\/d4a73c4daaf1d87b4e55b502f504530f\",\"name\":\"Paulina Welnic\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/289cff7a4e7ecbd913a0abeaf60acf9f688d6cee3cff46303b03d9a764c70957?s=96&d=mm&r=pg9f5f57a7c41a4965d520a386659c0543\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/289cff7a4e7ecbd913a0abeaf60acf9f688d6cee3cff46303b03d9a764c70957?s=96&d=mm&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/289cff7a4e7ecbd913a0abeaf60acf9f688d6cee3cff46303b03d9a764c70957?s=96&d=mm&r=pg\",\"caption\":\"Paulina Welnic\"},\"sameAs\":[\"https:\\\/\\\/x.com\\\/pawwelnic\"],\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/author\\\/pawwelnic\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"The right way to respond to feature requests - The Intercom Blog","description":"What do you do when a customer asks for a feature your product doesn't support? Here's our best practice guide on responding to feature requests in a human way","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/","og_locale":"en_US","og_type":"article","og_title":"The right way to respond to feature requests","og_description":"What do you do when a customer asks for a feature your product doesn't support? Here's our best practice guide on responding to feature requests in a human way","og_url":"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/","og_site_name":"The Intercom Blog","article_publisher":"https:\/\/www.facebook.com\/intercominc","article_published_time":"2017-11-07T15:55:05+00:00","article_modified_time":"2024-07-25T10:58:07+00:00","og_image":[{"width":700,"height":332,"url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2017\/11\/How_Will_You_Build_It-1-700x332.gif","type":"image\/gif"}],"author":"Paulina Welnic","twitter_card":"summary_large_image","twitter_creator":"@pawwelnic","twitter_site":"@intercom","twitter_misc":{"Written by":"Paulina Welnic","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/#article","isPartOf":{"@id":"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/"},"author":{"name":"Paulina Welnic","@id":"https:\/\/www.intercom.com\/blog\/#\/schema\/person\/d4a73c4daaf1d87b4e55b502f504530f"},"headline":"The right way to respond to feature requests","datePublished":"2017-11-07T15:55:05+00:00","dateModified":"2024-07-25T10:58:07+00:00","mainEntityOfPage":{"@id":"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/"},"wordCount":1500,"publisher":{"@id":"https:\/\/www.intercom.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/#primaryimage"},"thumbnailUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2017\/11\/How_Will_You_Build_It-1.gif","keywords":["3 support","customer support","feature requests"],"articleSection":["Customer Service"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/","url":"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/","name":"The right way to respond to feature requests - The Intercom Blog","isPartOf":{"@id":"https:\/\/www.intercom.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/#primaryimage"},"image":{"@id":"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/#primaryimage"},"thumbnailUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2017\/11\/How_Will_You_Build_It-1.gif","datePublished":"2017-11-07T15:55:05+00:00","dateModified":"2024-07-25T10:58:07+00:00","description":"What do you do when a customer asks for a feature your product doesn't support? Here's our best practice guide on responding to feature requests in a human way","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.intercom.com\/blog\/the-right-way-to-respond-to-feature-requests\/#primaryimage","url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2017\/11\/How_Will_You_Build_It-1.gif","contentUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2017\/11\/How_Will_You_Build_It-1.gif","width":1968,"height":932},{"@type":"WebSite","@id":"https:\/\/www.intercom.com\/blog\/#website","url":"https:\/\/www.intercom.com\/blog\/","name":"The Intercom Blog","description":"Articles and Podcasts on Customer Service, AI and Automation, Product, and more","publisher":{"@id":"https:\/\/www.intercom.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.intercom.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.intercom.com\/blog\/#organization","name":"The Intercom Blog","url":"https:\/\/www.intercom.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.intercom.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2019\/08\/Intercom-logo-sq-black-trans.png","contentUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2019\/08\/Intercom-logo-sq-black-trans.png","width":1000,"height":1000,"caption":"The Intercom Blog"},"image":{"@id":"https:\/\/www.intercom.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/intercominc","https:\/\/x.com\/intercom","https:\/\/www.instagram.com\/intercom\/","https:\/\/www.linkedin.com\/company\/2491343","https:\/\/www.pinterest.ie\/intercom\/","https:\/\/www.youtube.com\/channel\/UCJG0MvLP03kyzzAkD-w98aQ","https:\/\/en.wikipedia.org\/wiki\/Intercom_(company)"]},{"@type":"Person","@id":"https:\/\/www.intercom.com\/blog\/#\/schema\/person\/d4a73c4daaf1d87b4e55b502f504530f","name":"Paulina Welnic","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/289cff7a4e7ecbd913a0abeaf60acf9f688d6cee3cff46303b03d9a764c70957?s=96&d=mm&r=pg9f5f57a7c41a4965d520a386659c0543","url":"https:\/\/secure.gravatar.com\/avatar\/289cff7a4e7ecbd913a0abeaf60acf9f688d6cee3cff46303b03d9a764c70957?s=96&d=mm&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/289cff7a4e7ecbd913a0abeaf60acf9f688d6cee3cff46303b03d9a764c70957?s=96&d=mm&r=pg","caption":"Paulina Welnic"},"sameAs":["https:\/\/x.com\/pawwelnic"],"url":"https:\/\/www.intercom.com\/blog\/author\/pawwelnic\/"}]}},"jetpack_featured_media_url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2017\/11\/How_Will_You_Build_It-1.gif","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/posts\/13856","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/users\/226"}],"replies":[{"embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/comments?post=13856"}],"version-history":[{"count":0,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/posts\/13856\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/media\/13857"}],"wp:attachment":[{"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/media?parent=13856"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/category?post=13856"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/tags?post=13856"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/coauthors?post=13856"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}