{"id":3234,"date":"2015-11-13t14:00:42","date_gmt":"2015-11-13t14:00:42","guid":{"rendered":"\/\/www.catharsisit.com\/?p=3234"},"modified":"2015-11-13t14:00:42","modified_gmt":"2015-11-13t14:00:42","slug":"pain-automate-iterate","status":"publish","type":"post","link":"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/","title":{"rendered":"pain, automate, iterate: improving communication with remote and internal teams"},"content":{"rendered":"

pain. the thing that makes our lizard brain flee, retreat, change course\u2014anything to stop the pain. it spurs us to act. scratch that. pain spurs us to react<\/em>. pain reminds us what not to do in the future, motivating us to think twice about repeating an action.<\/p>\n

work pain is a unique beast, though. usually, you can\u2019t run off, banishing the pain from your observable universe. we have to face it. this recently became clear to me.<\/p>\n

when magoosh was small, receiving around 500 questions per week, a few people were able to handle feedback from our students. students would find misspellings, misspeaks, errors, and mistakes in our lessons and questions. they\u2019d let us know, and myself and a couple other people at magoosh would manually add the issues to asana<\/a> where we track content errors and improvements.<\/p>\n

when we grew, what we could do manually was now painful, nearing impossible to do. a year on, we had 1000+ questions per week and a team of remote test prep experts answering student questions and receiving content error emails. what had not changed was that i was still manually entering all this information into asana.<\/p>\n

that was my pain. i needed to escape this pain. but how?<\/p>\n

automate! that\u2019s what you hear all the time. \u201coh, just automate that.\u201d easy to hear, but hard to do, especially for me. i’d been teaching and tutoring for the past decade\u2014not automating processes.<\/p>\n

what people forget to say, though, is that automating is really just a form of problem solving. so my goal became problem solving, and even though automation was a tool that i used (poorly at times), i was able to make more progress by attacking the problem instead focusing automating.<\/p>\n

what follows are the iterations of automating that i went through. i tried to include enough detail so that others could replicate what we did at magoosh.<\/p>\n

zendesk emails and asana<\/h1>\n

my first attempt to automate our content improvement process started in zendesk<\/a>, software we use to manage incoming student questions. i knew that i could forward a question in zendesk to an email address, and i knew that i could add a task in asana using an email address. so, i figured that\u2019d be a great solution! let\u2019s put the two together and see what happens.<\/p>\n

creating an email from a ticket and sending it out is a two-part process: first, we have to setup an email target, and second, we have to use this target in a trigger. let\u2019s start with adding the email target first:<\/p>\n

manage (gear icon) > extensions > add target > email target
\n\"email
\nfor the email address, go to the project in asana where the emails will be sent, and click on the down arrow next to the project name. there you will find \u201cadd tasks by email.\u201d
\n\"add
\ncopy the email address and drop it into the email address section and update the target. the first part is done.<\/p>\n

now for the trigger. the goal of the trigger is to send off an email when a tag is added to a ticket and updated. for this case, i used the self-explanatory tag\u2014content_improvement<\/em>.<\/p>\n

here are the conditions for my trigger:<\/p>\n

\"trigger\"<\/p>\n

i am using the content_improvement_sent<\/em> tag to ensure that my trigger doesn’t fire more than once. if i didn’t add this tag, i’d have no way of controlling how many times an email is sent to asana from the same zendesk question.<\/p>\n

now for the actual email. i want the body of the email to contain information from the zendesk questions, so i used the zendesk placeholder {{ticket.latest_comment_formatted}}<\/em> to grab the last comment from the zendesk question. the hope was that when the remote tutor responds to the student, it would make it easier for the content team to know what to fix. i also added the url of the ticket so it would be easy to get back to the original message, which has links to the question or lesson that needs fixing.<\/p>\n

(writing this now, i already know that this is not going to work. why would the last comment be useful for our content team? but i know more now than i knew then.)<\/p>\n

\"trigger<\/p>\n

with everything in place, i told our remote team to use the tag when they encountered a content error and waited for tasks to roll in.<\/p>\n

here\u2019s a sample of what i saw:<\/p>\n

\"nothing<\/p>\n

\"a<\/p>\n

some of the tasks had relevant information, but we started to see information buried below a lot of back and forth conversations. or the information that was there, wasn\u2019t enough for the content team to know what they needed to do. that lead to the content team digging through the zendesk to find the useful information.<\/p>\n

this attempt did not work for a few reasons:<\/p>\n

the information provided by the tutors was not always helpful or detailed enough to help our content team prioritize the issues or solve the problems.<\/p>\n

\n
    \n
  1. i didn\u2019t have enough control over how the the task was created in asana, which meant that there wasn\u2019t enough consistency.<\/li>\n
  2. sometimes the ticket would have multiple back-and-forths, requiring the content team to spend a lot of time to understand the error.<\/li>\n
  3. and for some reason, it was repeating information in the task, such as the url to the zendesk question!<\/li>\n<\/ol>\n<\/blockquote>\n

    back to the drawing board.<\/p>\n

    hello zapier<\/h1>\n

    even though the first attempt wasn\u2019t a success, i knew what i could do to make it better: more control over how the tasks are created and create a better process for our remote team to follow.<\/p>\n

    with a little googling i found zapier<\/a>\u2014a tool for connecting different apps, such as asana and zendesk, without any coding. zapier gave me more control over the tasks created in asana, and i could use a lot more zendesk attributes, giving me more control over structuring the email, and thus the task, created in asana. sweet!<\/p>\n

    creating a zap is fairly easy. you need to link accounts, test that they are connected, and then you can start sending tickets from zendesk to asana.<\/p>\n

    \"trigger<\/p>\n

    zapier, for all the great control it does provide, i discovered two little crooked parts during the set up. i couldn\u2019t just grab a ticket with a specific tag. zapier will only look at a specific view and grab tickets from that view, so i had to create a public view for tickets with the content_improvement<\/em> tag. easy enough. i made a new view:<\/p>\n

    \"content<\/p>\n

    now i could choose the appropriate view in zapier.<\/p>\n

    \"zap<\/p>\n

    and set up the message\/task for asana:<\/p>\n

    \"v1\"<\/p>\n

    the second crooked step was that i couldn\u2019t get zapier to grab a private comment from the assignee (i guess not all zendesk attributes were available).the only solution i could find was to have zapier use the last body comment made on the ticket. that’s what i was doing before with the zendesk email, and i knew that the last comment wasn\u2019t always helpful. to solve this problem, we needed a good process, an important part of making the automated content improvement process better.<\/p>\n

    creating a process<\/h1>\n

    first, we had to structure the information that the remote team was sending. this is easy to solve with a macro. the macro will ensure that all the information our content team needs is right there, and our remote team doesn\u2019t need to remember what to include. here is the text of the macro:<\/p>\n

    lesson\/question title: [add lesson or question title here]<\/p>\n

    prompt id: [if it is a question, add the prompt id. if it is a lesson, delete all of this line]<\/p>\n

    author of lesson or question: [add the name of the author of the lesson\/question. the lesson will have a picture of the instructor. the question author is listed under the admin section on the answer page<\/p>\n

    url: [url to question or lesson]<\/p>\n

    explanation of issue: [explain the error or issue]<\/p><\/blockquote>\n

    using a macro provides other benefits besides structuring information. we can default the response to private since it would only confuse the student, and the macro will automatically add the tag. the goal of any good process is to make it easy to follow, especially in the flow of work. if the team knows about the macro, it will be very easy for them to be successful.<\/p>\n

    with the automation in place, tested, and successfully working, it was time to train the remote team. for any changes or updates like this, repetition of information is key. i sent out an email to explain the process and changes, and i wrote a doc with more detail and linked to it in the email. at the end of every month, we send out a newsletter, and so, i repeated the change there too. the hope is that if someone doesn\u2019t see it the first time, they have an opportunity to see it again, and if they see it more than once then there\u2019s a good chance that they will remember what to do.<\/p>\n

    here are the steps that we originally outlined for the process:<\/p>\n

    \n
      \n
    1. reply to the student, thanking them for pointing out the error and explaining that our content team will look at the error and prioritize fixing it. you can use a macro for part of your response: \u201ccontent::thank you for your feedback\u201d<\/li>\n
    2. update the ticket as open<\/li>\n
    3. return to the ticket.<\/li>\n
    4. use the macro: \u201ccontent improvement \/ error in question or lesson\u201d and fill out all the lines in the macro. make sure your comment is private. you should also see the content_improvement tag too. \ud83d\ude00<\/li>\n
    5. update the ticket as solved<\/li>\n<\/ol>\n<\/blockquote>\n

      of course, nothing works perfectly. people forget. so i made sure to follow up with specific people to remind them about the new approach for the first week or so. i understand that it\u2019s easy to forget a change like this. following up with people is part of the automation process.<\/p>\n

      soon enough, we had some success! the formatting made it easy to see the vital information. having the author makes it easy to assign the task out. links to the lesson or question, and a link to the ticket, means that the content team doesn\u2019t need to search around for this information in the ticket. i can see who on the remote team filled out the information for easy follow up, and of course, a section that explains the error or issue.<\/p>\n

      \"small<\/p>\n

      iterate and make it better<\/h1>\n

      at this point, we didn\u2019t touch the process for a month or so. it worked well enough and was easy for our content team to prioritize tasks. but with time, we realized there was even more that we could do:<\/p>\n

      \"add<\/p>\n

      this extra little step was going to make the process even better. with it, we could leverage a feature in asana that identifies duplicates, thus making it much easier to see when something should become a high priority since it was affecting so many students.<\/p>\n

      for this change, we need to hop back to zapier and change a few things. we need to use \u201csubject\u201d to grab the title of the zendesk ticket, and we added \u201cexam\u201d as a custom ticket field recently, so we dropped that in the title too.<\/p>\n

      \"v2\"<\/p>\n

      again, once the zap is in place, we have to update the remote team about the change in the process. this is a significant change too. they will need to actually change the title of the zendesk ticket! (i ran a test to make sure that changing the title in the zendesk ticket won\u2019t do anything weird on the student\u2019s side.) another round of emails, newsletters, and follow-ups so that everyone was on the same page about the new process:<\/p>\n

      \n
        \n
      1. reply to the student, thanking them for point out the error and explaining that our content team will look at the error and prioritize fixing it. you can use a macro for part of your response: \u201ccontent::thank you for your feedback\u201d<\/li>\n
      2. update the ticket as open<\/li>\n
      3. return to the ticket.<\/li>\n
      4. write a private comment (\u201cinternal note\u201d) to the content team explaining the error. use the macro: \u201ccontent improvement \/ error in question or lesson\u201d and fill out all the lines in the macro. you should also see the content_improvement tag too. \ud83d\ude00<\/li>\n
      5. change the title of the ticket to the lesson or question title (click on the title and you\u2019ll be able to edit it).<\/li>\n
      6. update the ticket as solved<\/li>\n<\/ol>\n<\/blockquote>\n

        in closing<\/h1>\n

        as with any solution, rarely (probably never) is the first solution the best one. the key is to continually iterate on the process. to constantly look for ways to refine what you have.<\/p>\n

        the iterations we looked at are the most relevant ones. i spared the smaller iterations. we didn\u2019t originally default the macro to make the note private. we didn\u2019t always include the author of the lesson or question. zapier now allows us to grab the last private comment from the assignee instead of the last comment, so i\u2019ll be tweaking the process again soon. i also received feedback from someone on our remote team.<\/p>\n

        \"remote<\/p>\n

        so i\u2019ll be working on that soon.<\/p>\n

        our work is never done. it\u2019s never perfect. all we can do is take small steps towards improving what we have. that\u2019s what we do and that\u2019s what we\u2019ll continue to do at magoosh.<\/p>\n

         <\/p>\n","protected":false},"excerpt":{"rendered":"

        learn how we optimize our operations through a commitment to our core values.<\/p>\n","protected":false},"author":12,"featured_media":3249,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[248,249,250,251,252],"ppma_author":[497],"acf":[],"yoast_head":"\npain, automate, iterate: improving communication with remote and internal teams<\/title>\n<meta name=\"description\" content=\"as magoosh grows, keeping up with student emails is challenging. here's how our student help team set up email automation to deal with it and what they learned through the process.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/\" \/>\n<meta property=\"og:locale\" content=\"en_us\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"pain, automate, iterate: improving communication with remote and internal teams\" \/>\n<meta property=\"og:description\" content=\"as magoosh grows, keeping up with student emails is challenging. here's how our student help team set up email automation to deal with it and what they learned through the process.\" \/>\n<meta property=\"og:url\" content=\"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/\" \/>\n<meta property=\"og:site_name\" content=\"magoosh 2022年足球世界杯举办地\" \/>\n<meta property=\"article:published_time\" content=\"2015-11-13t14:00:42+00:00\" \/>\n<meta property=\"og:image\" content=\"\/\/www.catharsisit.com\/blog\/files\/2015\/11\/writing-notes-idea-conference-scaled.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"2560\" \/>\n\t<meta property=\"og:image:height\" content=\"1514\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"kevin rocci\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@kevinrocci\" \/>\n<meta name=\"twitter:label1\" content=\"written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"kevin rocci\" \/>\n\t<meta name=\"twitter:label2\" content=\"est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"webpage\",\"@id\":\"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/\",\"url\":\"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/\",\"name\":\"pain, automate, iterate: improving communication with remote and internal teams\",\"ispartof\":{\"@id\":\"\/\/www.catharsisit.com\/blog\/#website\"},\"datepublished\":\"2015-11-13t14:00:42+00:00\",\"datemodified\":\"2015-11-13t14:00:42+00:00\",\"author\":{\"@id\":\"\/\/www.catharsisit.com\/blog\/#\/schema\/person\/8f2a216208ae80e5bbba13893f7e1076\"},\"description\":\"as magoosh grows, keeping up with student emails is challenging. here's how our student help team set up email automation to deal with it and what they learned through the process.\",\"breadcrumb\":{\"@id\":\"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/#breadcrumb\"},\"inlanguage\":\"en-us\",\"potentialaction\":[{\"@type\":\"readaction\",\"target\":[\"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/\"]}]},{\"@type\":\"breadcrumblist\",\"@id\":\"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/#breadcrumb\",\"itemlistelement\":[{\"@type\":\"listitem\",\"position\":1,\"name\":\"home\",\"item\":\"\/\/www.catharsisit.com\/blog\/\"},{\"@type\":\"listitem\",\"position\":2,\"name\":\"pain, automate, iterate: improving communication with remote and internal teams\"}]},{\"@type\":\"website\",\"@id\":\"\/\/www.catharsisit.com\/blog\/#website\",\"url\":\"\/\/www.catharsisit.com\/blog\/\",\"name\":\"magoosh 2022年足球世界杯举办地\",\"description\":\"\",\"potentialaction\":[{\"@type\":\"searchaction\",\"target\":{\"@type\":\"entrypoint\",\"urltemplate\":\"\/\/www.catharsisit.com\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inlanguage\":\"en-us\"},{\"@type\":\"person\",\"@id\":\"\/\/www.catharsisit.com\/blog\/#\/schema\/person\/8f2a216208ae80e5bbba13893f7e1076\",\"name\":\"kevin rocci\",\"image\":{\"@type\":\"imageobject\",\"inlanguage\":\"en-us\",\"@id\":\"\/\/www.catharsisit.com\/blog\/#\/schema\/person\/image\/df76deb96ea0e0515eff3b8445244f8b\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/20ac858b1b699cfb1da4809df7a25b66?s=96&d=mm&r=g\",\"contenturl\":\"https:\/\/secure.gravatar.com\/avatar\/20ac858b1b699cfb1da4809df7a25b66?s=96&d=mm&r=g\",\"caption\":\"kevin rocci\"},\"description\":\"at uc santa cruz, kevin rocci began a decade of teaching and tutoring with the stevenson college junior fellow and writing assistance programs. he has worked with adults and kids, tutoring the gre, gmat, and sat at kaplan and teaching english as a second language in the jet programme and at the intercultural institute of california. at magoosh, he expanded beyond teaching, building and managing teams, like student help and content. when he's not magooshing, you can find him spinning his toddler in circles. connect with him on linkedin or twitter.\",\"sameas\":[\"https:\/\/www.linkedin.com\/in\/kevinrocci\/\",\"https:\/\/twitter.com\/kevinrocci\"],\"knowsabout\":[\"gre\",\"gmat\",\"sat\",\"toefl\",\"ielts\",\"esl\"],\"jobtitle\":\"general manager, toefl and ielts\",\"worksfor\":\"magoosh\",\"url\":\"\/\/www.catharsisit.com\/blog\/author\/kevin\/\"}]}<\/script>\n<!-- \/ yoast seo premium plugin. -->","yoast_head_json":{"title":"pain, automate, iterate: improving communication with remote and internal teams","description":"as magoosh grows, keeping up with student emails is challenging. here's how our student help team set up email automation to deal with it and what they learned through the process.","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":"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/","og_locale":"en_us","og_type":"article","og_title":"pain, automate, iterate: improving communication with remote and internal teams","og_description":"as magoosh grows, keeping up with student emails is challenging. here's how our student help team set up email automation to deal with it and what they learned through the process.","og_url":"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/","og_site_name":"magoosh 2022年足球世界杯举办地","article_published_time":"2015-11-13t14:00:42+00:00","og_image":[{"width":2560,"height":1514,"url":"\/\/www.catharsisit.com\/blog\/files\/2015\/11\/writing-notes-idea-conference-scaled.jpg","type":"image\/jpeg"}],"author":"kevin rocci","twitter_card":"summary_large_image","twitter_creator":"@kevinrocci","twitter_misc":{"written by":"kevin rocci","est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"webpage","@id":"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/","url":"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/","name":"pain, automate, iterate: improving communication with remote and internal teams","ispartof":{"@id":"\/\/www.catharsisit.com\/blog\/#website"},"datepublished":"2015-11-13t14:00:42+00:00","datemodified":"2015-11-13t14:00:42+00:00","author":{"@id":"\/\/www.catharsisit.com\/blog\/#\/schema\/person\/8f2a216208ae80e5bbba13893f7e1076"},"description":"as magoosh grows, keeping up with student emails is challenging. here's how our student help team set up email automation to deal with it and what they learned through the process.","breadcrumb":{"@id":"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/#breadcrumb"},"inlanguage":"en-us","potentialaction":[{"@type":"readaction","target":["\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/"]}]},{"@type":"breadcrumblist","@id":"\/\/www.catharsisit.com\/blog\/pain-automate-iterate\/#breadcrumb","itemlistelement":[{"@type":"listitem","position":1,"name":"home","item":"\/\/www.catharsisit.com\/blog\/"},{"@type":"listitem","position":2,"name":"pain, automate, iterate: improving communication with remote and internal teams"}]},{"@type":"website","@id":"\/\/www.catharsisit.com\/blog\/#website","url":"\/\/www.catharsisit.com\/blog\/","name":"magoosh 2022年足球世界杯举办地","description":"","potentialaction":[{"@type":"searchaction","target":{"@type":"entrypoint","urltemplate":"\/\/www.catharsisit.com\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inlanguage":"en-us"},{"@type":"person","@id":"\/\/www.catharsisit.com\/blog\/#\/schema\/person\/8f2a216208ae80e5bbba13893f7e1076","name":"kevin rocci","image":{"@type":"imageobject","inlanguage":"en-us","@id":"\/\/www.catharsisit.com\/blog\/#\/schema\/person\/image\/df76deb96ea0e0515eff3b8445244f8b","url":"https:\/\/secure.gravatar.com\/avatar\/20ac858b1b699cfb1da4809df7a25b66?s=96&d=mm&r=g","contenturl":"https:\/\/secure.gravatar.com\/avatar\/20ac858b1b699cfb1da4809df7a25b66?s=96&d=mm&r=g","caption":"kevin rocci"},"description":"at uc santa cruz, kevin rocci began a decade of teaching and tutoring with the stevenson college junior fellow and writing assistance programs. he has worked with adults and kids, tutoring the gre, gmat, and sat at kaplan and teaching english as a second language in the jet programme and at the intercultural institute of california. at magoosh, he expanded beyond teaching, building and managing teams, like student help and content. when he's not magooshing, you can find him spinning his toddler in circles. connect with him on linkedin or twitter.","sameas":["https:\/\/www.linkedin.com\/in\/kevinrocci\/","https:\/\/twitter.com\/kevinrocci"],"knowsabout":["gre","gmat","sat","toefl","ielts","esl"],"jobtitle":"general manager, toefl and ielts","worksfor":"magoosh","url":"\/\/www.catharsisit.com\/blog\/author\/kevin\/"}]}},"authors":[{"term_id":497,"user_id":12,"is_guest":0,"slug":"kevin","display_name":"kevin rocci","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/20ac858b1b699cfb1da4809df7a25b66?s=96&d=mm&r=g","user_url":"","last_name":"rocci","first_name":"kevin","description":"at uc santa cruz, kevin rocci began a decade of teaching and tutoring with the <a href=\"https:\/\/catalog.ucsc.edu\/en\/current\/general-catalog\/academic-units\/the-colleges\/stevenson-college\" rel=\"noopener\">stevenson college junior fellow and writing assistance programs<\/a>. he has worked with adults and kids, tutoring the gre, gmat, and sat at <a href=\"https:\/\/kaplan.com\/\" rel=\"noopener\">kaplan<\/a> and teaching english as a second language in the <a href=\"http:\/\/jetprogramme.org\/en\/\" rel=\"noopener\">jet programme<\/a> and at the <a href=\"https:\/\/iicesl.org\/\" rel=\"noopener\">intercultural institute of california<\/a>. at magoosh, he expanded beyond teaching, building and managing teams, like student help and content. when he's not magooshing, you can find him spinning his toddler in circles. connect with him on <a href=\"https:\/\/www.linkedin.com\/in\/kevinrocci\/\" rel=\"noopener\">linkedin<\/a> or <a href=\"https:\/\/twitter.com\/kevinrocci\" rel=\"noopener\">twitter<\/a>."}],"_links":{"self":[{"href":"\/\/www.catharsisit.com\/blog\/wp-json\/wp\/v2\/posts\/3234"}],"collection":[{"href":"\/\/www.catharsisit.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"\/\/www.catharsisit.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"\/\/www.catharsisit.com\/blog\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"\/\/www.catharsisit.com\/blog\/wp-json\/wp\/v2\/comments?post=3234"}],"version-history":[{"count":0,"href":"\/\/www.catharsisit.com\/blog\/wp-json\/wp\/v2\/posts\/3234\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"\/\/www.catharsisit.com\/blog\/wp-json\/wp\/v2\/media\/3249"}],"wp:attachment":[{"href":"\/\/www.catharsisit.com\/blog\/wp-json\/wp\/v2\/media?parent=3234"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"\/\/www.catharsisit.com\/blog\/wp-json\/wp\/v2\/categories?post=3234"},{"taxonomy":"post_tag","embeddable":true,"href":"\/\/www.catharsisit.com\/blog\/wp-json\/wp\/v2\/tags?post=3234"},{"taxonomy":"author","embeddable":true,"href":"\/\/www.catharsisit.com\/blog\/wp-json\/wp\/v2\/ppma_author?post=3234"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}