{"id":28637,"date":"2023-02-21T14:53:15","date_gmt":"2023-02-21T14:53:15","guid":{"rendered":"https:\/\/www.intercom.com\/blog\/?p=28637"},"modified":"2025-01-03T14:00:05","modified_gmt":"2025-01-03T14:00:05","slug":"customer-support-product-launch","status":"publish","type":"post","link":"https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/","title":{"rendered":"Supporting product launches: How to set up your customer service team for new announcements"},"content":{"rendered":"

On the Intercom Support team, we\u2019re always experimenting with ways to offer our customers a better experience \u2013 whether that\u2019s a faster response, a more helpful answer to a question, or just a more delightful interaction with our reps.\u00a0<\/span><\/p>\n

One such experiment took place last year in the run-up to the launch of our <\/span>next-generation Inbox<\/span><\/a>, when we chose to dedicate a team of specialists to handling questions specific to the new product. We\u2019re going to dive into the idea, method, and results of our experiment; we hope it will help other customer service teams to think outside the box when it comes to product launches.\u00a0<\/span><\/p>\n

Starting with a cupcake<\/span><\/h2>\n

Here at Intercom, we call our little ideas and experiments <\/span>\u201ccupcakes\u201d<\/span><\/a> \u2013 small trials you carry out before taking on a larger project or adopting a major change (bake your cupcake so you learn how to bake your wedding cake). These cupcakes typically focus on how rethinking one part of a process can impact our team\u2019s performance and productivity.<\/span><\/p>\n

The next-gen Inbox represented a total <\/span>rebuild and redesign of our core Inbox product<\/span><\/a>. Given that support teammates spend most of their days in the Intercom Inbox, we anticipated that this particular launch would constitute a major change for our customers, and drive a lot of new conversations to our Support team. Our customers would want to learn more about the change, explore our new \u201ckeyboard-first\u201d approach and shortcuts, and find their favorite features, both new and old.<\/span><\/p>\n

\"intercom<\/p>\n

Intercom’s next-gen Inbox<\/em><\/p>\n

What did we do?<\/span><\/h2>\n

Intercom\u2019s support reps are generalists that carry an enormous amount of product knowledge across a wide range of areas. For this crucial launch, we decided to choose eight teammates from our global team and form a \u201ctiger team\u201d of customer support specialists to staff a dedicated inbox to which we would automatically route all queries related to our next-gen Inbox.\u00a0<\/span><\/p>\n

A tenured support specialist who had been \u201con tour\u201d with the Product team while they were developing the new Inbox \u2013 effectively acting as QA support \u2013 was able to invest several hours in putting together self-serve resources for our internal knowledge base, as well as delivering training directly to our \u201ctiger team.\u201d\u00a0<\/span><\/p>\n

\u201cChoosing specific team members to manage this task meant that they could focus their time on one particular topic instead of their usual broader menu of subjects\u201d<\/p><\/blockquote>\n

These eight teammates would take turns in daily shifts to monitor this inbox and respond to questions from our customers specifically related to our new Inbox. Each member of the tiger team would dedicate at least one full day of work towards staffing this inbox across the week of the launch.<\/span><\/p>\n

What was our goal?<\/span><\/h2>\n

There were two primary reasons that we adopted a specialist over a generalist approach for our product launch:<\/span><\/b><\/p>\n

We hoped that specialists could serve our customers better and faster during the launch<\/h3>\n

Our Support team had acted as beta testers for the next-generation Inbox before its wider release, becoming acclimated to a new way of providing support using Intercom \u2013 so they were well equipped to support our customers in their own journey. Choosing specific team members to manage this task meant that they could focus their time on one specific topic instead of their usual broader menu of subjects, and allowed them to become deeply familiar with this aspect of our product. <\/span><\/p>\n

Ultimately, we hoped that this level of increased familiarity would lead to quicker handling time and higher CSAT<\/a>, and allow our generalist support reps to maintain our high standards of service for customers with queries unrelated to the Inbox.\u00a0<\/span><\/p>\n

We wanted to identify trends in customer feedback<\/h3>\n

As well as analyzing the data behind our Inbox-related conversations, having a specialized group of support teammates focused on our new and improved Inbox allowed us to identify trends in customer feedback quickly and accurately. For example, the team was able to rapidly surface customer feedback requesting the return of pinned shortcuts in the Inbox composer, allowing the Product team to prioritize shipping this change.<\/span><\/p>\n

Routing Inbox-related conversations<\/span><\/h3>\n

We automated the routing of these conversations using two methods:<\/span><\/p>\n

    \n
  1. \u00a0An inbound Custom Bot<\/a> which we had set up to trigger for customers using our next-gen Inbox, where they could choose \u201cproduct confusion,\u201d \u201crequesting a feature,\u201d or \u201cleaving feedback\u201d as their reason for contacting.\u00a0<\/span><\/li>\n
  2. We used Inbox Rules<\/a> to capture conversations including terms relating to the new Inbox, which were then routed to the dedicated inbox.\u00a0<\/span><\/li>\n<\/ol>\n

    To ensure that nothing slipped through the cracks, we also asked teammates to manually reassign any Inbox-related conversations they pulled to this inbox.<\/span><\/p>\n

    \u201cWe saw our tiger team develop a high level of familiarity with the new Inbox, enabling them to deliver a greater standard of support to our customers\u201d<\/p><\/blockquote>\n

    The results<\/span><\/h2>\n

    We iterated as we went. Initially, as our conversation volume increased significantly, we found that we needed to alter the schedule. We moved from scheduling one teammate in each region to two teammates in each region to handle this volume spike. Once we felt we had resourced effectively, we began to see benefits like:<\/span><\/p>\n

    High rates of customer satisfaction<\/span><\/h3>\n

    We saw our tiger team develop a high level of familiarity with the new Inbox, enabling them to deliver a greater standard of support to our customers. We didn’t know what kind of score to expect for such a high volume of queries on a brand new product, and were pleased with the overall CSAT rating of 95.1% for conversations assigned to our dedicated inbox. We will continue to increase this score as the product knowledge is shared across the team. <\/span><\/p>\n

    Additionally, separating next-generation Inbox queries from our general conversation volume allowed the rest of our team to support our customers without getting bogged down in complex queries about a brand new product \u2013 and maintain our high standards of service.<\/span><\/p>\n

    \u201cA huge benefit of this approach was the collaborative relationship we built with our Product team throughout the experiment\u201d<\/p><\/blockquote>\n

    Cross-functional relationships<\/span><\/h3>\n

    A huge benefit of this approach was the collaborative relationship<\/a> we built with our Product team throughout the experiment, allowing us to surface bug reports which were then prioritized and share product feedback which led to significant changes within the next-gen Inbox. <\/span><\/p>\n

    Not only did this benefit our customers, our tiger team, and our Product team during the launch, it also allowed the Support team to nurture its relationship with our Product team, strengthening existing communication processes for future launches and positioning our Support team as a vital source of product feedback<\/a>.<\/span><\/p>\n

    We will continue to experiment<\/span><\/h2>\n

    Our approach to the launch of our next-gen Inbox has informed how our Support team prepares for Intercom product launches and has prompted our Support Operations team to explore how we might roll out wider topic specialization among our support teammates.\u00a0<\/span><\/p>\n\n","protected":false},"excerpt":{"rendered":"

    Last year, we took a different approach to customer support for the launch of our next-gen Inbox, dedicating a team of specialists to handling questions about the new product.<\/p>\n","protected":false},"author":279,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"category":[3],"tags":[3555,564,142],"coauthors":[620],"class_list":["post-28637","post","type-post","status-publish","format-standard","hentry","category-customer-support","tag-cupcake","tag-customer-service","tag-customer-support"],"yoast_head":"\nSet up your customer service team for product launch success<\/title>\n<meta name=\"description\" content=\"Last year, we tried a new approach to customer service during a major product launch. Here, we dive into the idea, method, and results.\" \/>\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\/customer-support-product-launch\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Supporting product launches: How to set up your customer service team for new announcements\" \/>\n<meta property=\"og:description\" content=\"Last year, we tried a new approach to customer service during a major product launch. Here, we dive into the idea, method, and results.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/\" \/>\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=\"2023-02-21T14:53:15+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-01-03T14:00:05+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2022\/12\/intercom-inbox-2.jpeg\" \/>\n<meta name=\"author\" content=\"Eric Fitzgerald\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@intercom\" \/>\n<meta name=\"twitter:site\" content=\"@intercom\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Eric Fitzgerald\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/customer-support-product-launch\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/customer-support-product-launch\\\/\"},\"author\":{\"name\":\"Eric Fitzgerald\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#\\\/schema\\\/person\\\/771a2e010608617e22d7535d06cfe0d7\"},\"headline\":\"Supporting product launches: How to set up your customer service team for new announcements\",\"datePublished\":\"2023-02-21T14:53:15+00:00\",\"dateModified\":\"2025-01-03T14:00:05+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/customer-support-product-launch\\\/\"},\"wordCount\":1150,\"publisher\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/customer-support-product-launch\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/12\\\/intercom-inbox-2.jpeg\",\"keywords\":[\"cupcake\",\"Customer Service\",\"customer support\"],\"articleSection\":[\"Customer Service\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/customer-support-product-launch\\\/\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/customer-support-product-launch\\\/\",\"name\":\"Set up your customer service team for product launch success\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/customer-support-product-launch\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/customer-support-product-launch\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/12\\\/intercom-inbox-2.jpeg\",\"datePublished\":\"2023-02-21T14:53:15+00:00\",\"dateModified\":\"2025-01-03T14:00:05+00:00\",\"description\":\"Last year, we tried a new approach to customer service during a major product launch. Here, we dive into the idea, method, and results.\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.intercom.com\\\/blog\\\/customer-support-product-launch\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/customer-support-product-launch\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/12\\\/intercom-inbox-2.jpeg\",\"contentUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/12\\\/intercom-inbox-2.jpeg\",\"width\":1200,\"height\":610,\"caption\":\"intercom inbox\"},{\"@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\\\/771a2e010608617e22d7535d06cfe0d7\",\"name\":\"Eric Fitzgerald\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/97a247b473e62539cd5ec667fdcce3b84ff78e1d490357ae7c886e147a56e995?s=96&d=mm&r=pg50d5e067ed65793dccde6edeecd0f187\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/97a247b473e62539cd5ec667fdcce3b84ff78e1d490357ae7c886e147a56e995?s=96&d=mm&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/97a247b473e62539cd5ec667fdcce3b84ff78e1d490357ae7c886e147a56e995?s=96&d=mm&r=pg\",\"caption\":\"Eric Fitzgerald\"},\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/author\\\/mrericfitz\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Set up your customer service team for product launch success","description":"Last year, we tried a new approach to customer service during a major product launch. Here, we dive into the idea, method, and results.","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\/customer-support-product-launch\/","og_locale":"en_US","og_type":"article","og_title":"Supporting product launches: How to set up your customer service team for new announcements","og_description":"Last year, we tried a new approach to customer service during a major product launch. Here, we dive into the idea, method, and results.","og_url":"https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/","og_site_name":"The Intercom Blog","article_publisher":"https:\/\/www.facebook.com\/intercominc","article_published_time":"2023-02-21T14:53:15+00:00","article_modified_time":"2025-01-03T14:00:05+00:00","og_image":[{"url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2022\/12\/intercom-inbox-2.jpeg","type":"","width":"","height":""}],"author":"Eric Fitzgerald","twitter_card":"summary_large_image","twitter_creator":"@intercom","twitter_site":"@intercom","twitter_misc":{"Written by":"Eric Fitzgerald","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/#article","isPartOf":{"@id":"https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/"},"author":{"name":"Eric Fitzgerald","@id":"https:\/\/www.intercom.com\/blog\/#\/schema\/person\/771a2e010608617e22d7535d06cfe0d7"},"headline":"Supporting product launches: How to set up your customer service team for new announcements","datePublished":"2023-02-21T14:53:15+00:00","dateModified":"2025-01-03T14:00:05+00:00","mainEntityOfPage":{"@id":"https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/"},"wordCount":1150,"publisher":{"@id":"https:\/\/www.intercom.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/#primaryimage"},"thumbnailUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2022\/12\/intercom-inbox-2.jpeg","keywords":["cupcake","Customer Service","customer support"],"articleSection":["Customer Service"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/","url":"https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/","name":"Set up your customer service team for product launch success","isPartOf":{"@id":"https:\/\/www.intercom.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/#primaryimage"},"image":{"@id":"https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/#primaryimage"},"thumbnailUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2022\/12\/intercom-inbox-2.jpeg","datePublished":"2023-02-21T14:53:15+00:00","dateModified":"2025-01-03T14:00:05+00:00","description":"Last year, we tried a new approach to customer service during a major product launch. Here, we dive into the idea, method, and results.","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.intercom.com\/blog\/customer-support-product-launch\/#primaryimage","url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2022\/12\/intercom-inbox-2.jpeg","contentUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2022\/12\/intercom-inbox-2.jpeg","width":1200,"height":610,"caption":"intercom inbox"},{"@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\/771a2e010608617e22d7535d06cfe0d7","name":"Eric Fitzgerald","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/97a247b473e62539cd5ec667fdcce3b84ff78e1d490357ae7c886e147a56e995?s=96&d=mm&r=pg50d5e067ed65793dccde6edeecd0f187","url":"https:\/\/secure.gravatar.com\/avatar\/97a247b473e62539cd5ec667fdcce3b84ff78e1d490357ae7c886e147a56e995?s=96&d=mm&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/97a247b473e62539cd5ec667fdcce3b84ff78e1d490357ae7c886e147a56e995?s=96&d=mm&r=pg","caption":"Eric Fitzgerald"},"url":"https:\/\/www.intercom.com\/blog\/author\/mrericfitz\/"}]}},"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/posts\/28637","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\/279"}],"replies":[{"embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/comments?post=28637"}],"version-history":[{"count":0,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/posts\/28637\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/media?parent=28637"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/category?post=28637"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/tags?post=28637"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/coauthors?post=28637"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}