<metaproperty="og:title"content="Call Etiquette - Spearhead Systems Incident Response Documentation"/>
<metaproperty="og:site_name"content="Spearhead Systems Incident Response Documentation"/>
<metaproperty="og:description"content="A collection of information about the Spearhead Systems 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."/>
<metaname="twitter:title"content="Call Etiquette - Spearhead Systems Incident Response Documentation"/>
<metaname="twitter:description"content="A collection of information about the Spearhead Systems 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."/>
<p>You've just joined Spearhead Systems support staff and you've never worked in a service delivery function before. You have no idea what an incident or a service request is. You have no idea what's going on, or what you're supposed to be doing. This page will help you through your first time and will provide a reference for future issues you may be a part of.</p>
<em>Credit: <ahref="https://commons.wikimedia.org/wiki/File:Barack_Obama_on_phone_with_Benjamin_Netanyahu_2009-06-08.jpg">Official White House Photo</a> by Pete Souza</em></p>
<li>If you intend on participating on the incident call you should join both the call (if there is a call), review the associated cards in DoIT, and jump on the corresponding internal Chat channel.</li>
<p>Not all issues start with an incident call. Some issues may be completely automated and available only in DoIT while others may be in the incipient stages and the customer may still be on the phone/internal Chat detailing their issue.</p>
<p><strong>Use clear terminology, and avoid using acronyms or abbreviations during a call. Clear and accurate communication is more important than quick communication.</strong></p>
<p>Standard radio <ahref="https://en.wikipedia.org/wiki/Voice_procedure#Words_in_voice_procedure">voice procedure</a> does not need to be followed on calls. However, you should familiarize yourself with the terms, as you may hear them on a call (or need to use them yourself). The ones in more active use on major incident calls are,</p>
<ul>
<li><strong>Ack/Rog</strong> - "I have received and understood"</li>
<li><strong>Say Again</strong> - "Repeat your last message"</li>
<li><strong>Standby</strong> - "Please wait a moment for the next response"</li>
<li><strong>Wilco</strong> - "Will comply"</li>
</ul>
<p>Do not invent new abbreviations, and always favor being explicit of implicit. It is better to make things clearer than to try and save time by abbreviating, only to have a misunderstanding because others didn't know the abbreviation.</p>
<h2id="the-team-leader">The Team Leader<aclass="headerlink"href="#the-team-leader"title="Permanent link">#</a></h2>
<p>The Team Leader (TL) is the leader of the incident response process, and is responsible for bringing the incident to resolution. They will announce themselves at the start of the call, and will generally be doing most of the talking.</p>
<li>Follow all instructions from the team leader, without exception.</li>
<li>Do not perform any actions unless the team leader has told you to do so.</li>
<li>The team leader will typically poll for any strong objections before performing a large action. This is your time to raise any objections if you have them.</li>
<li>Once the team leader has made a decision, that decision is final and should be followed, even if you disagreed during the poll.</li>
<li>Answer any questions the team leader asks you in a clear and concise way.<ul>
<li>Answering that you "don't know" something is perfectly acceptable. Do not try to guess.</li>
</ul>
</li>
<li>The team leader may ask you to investigate something and get back to them in X minutes. Make sure you are ready with an answer within that time.<ul>
<li>Answering that you need more time is perfectly acceptable, but you need to give the team leader an estimate of how much time.</li>
<h4id="theres-no-team-leader-on-the-call-i-dont-know-what-to-do">There's no team leader on the call! I don't know what to do!<aclass="headerlink"href="#theres-no-team-leader-on-the-call-i-dont-know-what-to-do"title="Permanent link">#</a></h4>
<p>Ask on the call if an TL is present. If you have no response, try asking in our internal Chat. If there is no TL the sysadmin can take over this role temporarily.</p>
<h4id="there-is-not-enough-information">There is not enough information!<aclass="headerlink"href="#there-is-not-enough-information"title="Permanent link">#</a></h4>
<p>The definitive source of information for all issues is in DoIT. If it is lacking there then you need to make a note of it and make sure that whoever created the card understands the importance of complete information in a timely manner. If at any point there is a discrepancy ask the TL or Sysadmins to provide up to date information and update the card/tasks accordingly. </p>
