Skip to content

Latest commit

 

History

History
51 lines (39 loc) · 3.91 KB

call_etiquette.md

File metadata and controls

51 lines (39 loc) · 3.91 KB
Raw
cover description
assets/img/covers/call_etiquette.png
You've just joined an incident call, and you've never been on one before. 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 on an incident call, and will provide a reference for future calls you may be a part of.

You've just joined an incident call and you've never been on one before. 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 on an incident call, and will provide a reference for future calls you may be a part of.

First Steps

  • If you intend on participating on the incident call you should join both the call, and Slack.
  • Make sure you are in a quiet environment in order to participate on the call. Background noise should be kept to a minimum.
  • Keep your microphone muted until you have something to say.
  • Identify yourself when you join the call; state your name and the system you are the expert for.
  • Speak up and speak clearly.
  • Be direct and factual.
  • Keep conversations/discussions short and to the point.
  • Bring any concerns to the Incident Commander (IC) on the call.
  • Respect time constraints given by the Incident Commander.

Lingo

Use clear terminology, and avoid using acronyms or abbreviations during a call. Clear and accurate communication is more important than quick communication.

Communication

Standard radio voice procedure 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,

  • Ack/Rog - "I have received and understood"
  • Say Again - "Repeat your last message"
  • Standby - "Please wait a moment for the next response"
  • Wilco - "Will comply"

Do not invent new abbreviations, and always favor being explicit rather than 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.

The Commander

The Incident Commander (IC) 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.

  • Follow all instructions from the Incident Commander - without exception.
  • Do not perform any actions unless the Incident Commander has told you to do so.
  • The Incident Commander will typically poll for any strong objections before performing a large action. This is your time to raise any objections if you have them.
  • Once the Incident Commander has made a decision, that decision is final and should be followed, even if you disagreed during the poll.
  • Answer any questions the Incident Commander asks you in a clear and concise way.
    • Answering that you "don't know" something is perfectly acceptable. Do not try to guess.
  • The Incident Commander 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.
    • Answering that you need more time is perfectly acceptable, but you need to give the Incident Commander an estimate of how much time.

Problems?

There's no incident commander on the call! I don't know what to do!

Ask on the call if an IC is present. If you have no response, type !ic page in Slack. This will page the primary and backup IC to the call.

I can join the call or Slack, but not both, what should I do?

You're welcome to join only one of the channels, however you should not actively participate in the incident response if so as it causes disjointed communication. Liaise with someone who is both in Slack and on the call to provide any input you may have so that they can raise it.