<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (raygrasso)</title>
    <link>https://pinboard.in/u:raygrasso/public/</link>
    <description>recent bookmarks from raygrasso</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://bthdonohue.com/2026/02/03/surfacing-account-information-filtering-spam-zendesk.html"/>
	<rdf:li rdf:resource="https://blog.developer.adobe.com/creating-a-thriving-on-call-engineering-workflow-by-embracing-healthy-team-habits-f05841e62ea1"/>
	<rdf:li rdf:resource="https://jacobbednarz.com/surviving-on-call"/>
	<rdf:li rdf:resource="https://www.adaptivecapacitylabs.com/blog/2018/03/23/moving-past-shallow-incident-data/"/>
	<rdf:li rdf:resource="https://helpy.io/"/>
	<rdf:li rdf:resource="https://blog.intercom.com/rapid-response-how-we-developed-an-on-call-team-at-intercom/"/>
	<rdf:li rdf:resource="https://medium.com/making-instapaper/instapaper-outage-cause-recovery-3c32a7e9cc5f#.7eyc5jumx"/>
	<rdf:li rdf:resource="https://response.pagerduty.com/"/>
	<rdf:li rdf:resource="https://support.pagerduty.com/hc/en-us/articles/202828690-PagerDuty-Quick-Start-Guide-Core-Concepts"/>
	<rdf:li rdf:resource="http://supportkit.io/"/>
	<rdf:li rdf:resource="http://supportdetails.com/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://bthdonohue.com/2026/02/03/surfacing-account-information-filtering-spam-zendesk.html">
    <title>Surfacing Account Information &amp; Filtering Spam in Zendesk</title>
    <dc:date>2026-02-04T02:15:59+00:00</dc:date>
    <link>https://bthdonohue.com/2026/02/03/surfacing-account-information-filtering-spam-zendesk.html</link>
    <dc:creator>raygrasso</dc:creator><dc:subject>support spam</dc:subject>
<dc:identifier>https://pinboard.in/u:raygrasso/b:478ac633ec64/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:support"/>
	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:spam"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.developer.adobe.com/creating-a-thriving-on-call-engineering-workflow-by-embracing-healthy-team-habits-f05841e62ea1">
    <title>Creating a Thriving On-Call Engineering Workflow by Embracing Healthy Team Habits</title>
    <dc:date>2022-11-06T12:34:49+00:00</dc:date>
    <link>https://blog.developer.adobe.com/creating-a-thriving-on-call-engineering-workflow-by-embracing-healthy-team-habits-f05841e62ea1</link>
    <dc:creator>raygrasso</dc:creator><dc:subject>support oncall</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:raygrasso/b:cc9073f1a8dc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:support"/>
	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:oncall"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://jacobbednarz.com/surviving-on-call">
    <title>Surviving on-call · Jacob Bednarz</title>
    <dc:date>2020-05-14T08:00:15+00:00</dc:date>
    <link>https://jacobbednarz.com/surviving-on-call</link>
    <dc:creator>raygrasso</dc:creator><dc:subject>support oncall</dc:subject>
<dc:identifier>https://pinboard.in/u:raygrasso/b:a03a3b8ffbcd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:support"/>
	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:oncall"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.adaptivecapacitylabs.com/blog/2018/03/23/moving-past-shallow-incident-data/">
    <title>Moving Past Shallow Incident Data » Adaptive Capacity Labs</title>
    <dc:date>2019-05-05T00:57:00+00:00</dc:date>
    <link>https://www.adaptivecapacitylabs.com/blog/2018/03/23/moving-past-shallow-incident-data/</link>
    <dc:creator>raygrasso</dc:creator><dc:subject>metrics support operations</dc:subject>
<dc:identifier>https://pinboard.in/u:raygrasso/b:647b84389646/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:support"/>
	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:operations"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://helpy.io/">
    <title>Helpy</title>
    <dc:date>2018-07-24T13:28:52+00:00</dc:date>
    <link>https://helpy.io/</link>
    <dc:creator>raygrasso</dc:creator><description><![CDATA[Hosted, on-premise and open source customer support helpdesk software]]></description>
<dc:subject>support</dc:subject>
<dc:identifier>https://pinboard.in/u:raygrasso/b:2b44cccb0d26/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:support"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.intercom.com/rapid-response-how-we-developed-an-on-call-team-at-intercom/">
    <title>Rapid response: how we fixed our on call process to avoid engineer burnout - Inside Intercom</title>
    <dc:date>2018-05-20T12:32:10+00:00</dc:date>
    <link>https://blog.intercom.com/rapid-response-how-we-developed-an-on-call-team-at-intercom/</link>
    <dc:creator>raygrasso</dc:creator><description><![CDATA[Ensuring that Intercom has great uptime requires a rapid response when things go wrong, and that means having engineers on call to solve problems when they occur. This is how we developed an effective, sustainable on call process for our teams.]]></description>
<dc:subject>oncall support</dc:subject>
<dc:identifier>https://pinboard.in/u:raygrasso/b:2caaf030d1f3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:oncall"/>
	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:support"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/making-instapaper/instapaper-outage-cause-recovery-3c32a7e9cc5f#.7eyc5jumx">
    <title>Instapaper Outage Cause &amp; Recovery</title>
    <dc:date>2017-02-15T02:19:38+00:00</dc:date>
    <link>https://medium.com/making-instapaper/instapaper-outage-cause-recovery-3c32a7e9cc5f#.7eyc5jumx</link>
    <dc:creator>raygrasso</dc:creator><description><![CDATA[Postmortem on the outage.]]></description>
<dc:subject>outage support databases</dc:subject>
<dc:identifier>https://pinboard.in/u:raygrasso/b:62ef644cd2cb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:outage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:support"/>
	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:databases"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://response.pagerduty.com/">
    <title>PagerDuty Incident Response Documentation</title>
    <dc:date>2017-01-08T07:29:36+00:00</dc:date>
    <link>https://response.pagerduty.com/</link>
    <dc:creator>raygrasso</dc:creator><description><![CDATA[A collection of information about the PagerDuty incident response process. Not only how to prepare new employees for on-call responsibilities, but also how to handle major incidents, both in preparation and after-work.]]></description>
<dc:subject>support</dc:subject>
<dc:identifier>https://pinboard.in/u:raygrasso/b:b6637f618604/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:support"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://support.pagerduty.com/hc/en-us/articles/202828690-PagerDuty-Quick-Start-Guide-Core-Concepts">
    <title>PagerDuty Quick Start Guide &amp; Core Concepts – PagerDuty Support and Help</title>
    <dc:date>2016-05-06T13:19:03+00:00</dc:date>
    <link>https://support.pagerduty.com/hc/en-us/articles/202828690-PagerDuty-Quick-Start-Guide-Core-Concepts</link>
    <dc:creator>raygrasso</dc:creator><description><![CDATA[This article will review how to navigate your PagerDuty account and understand the general layout of the application. We will also review...]]></description>
<dc:subject>support</dc:subject>
<dc:identifier>https://pinboard.in/u:raygrasso/b:344cc06b8690/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:support"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://supportkit.io/">
    <title>SupportKit - Beautifully simple in-app messaging</title>
    <dc:date>2015-03-24T01:39:28+00:00</dc:date>
    <link>http://supportkit.io/</link>
    <dc:creator>raygrasso</dc:creator><description><![CDATA[Build lasting relationships with your customers with beautifully simple in-app messaging.]]></description>
<dc:subject>support iosdev</dc:subject>
<dc:identifier>https://pinboard.in/u:raygrasso/b:d0838e3dc836/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:support"/>
	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:iosdev"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://supportdetails.com/">
    <title>Support Details | Tech Support Management</title>
    <dc:date>2012-01-30T03:57:45+00:00</dc:date>
    <link>http://supportdetails.com/</link>
    <dc:creator>raygrasso</dc:creator><dc:subject>support codetools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:raygrasso/b:a574e57e469e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:support"/>
	<rdf:li rdf:resource="https://pinboard.in/u:raygrasso/t:codetools"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>