Sorry, I was on mute: Difference between revisions
Jump to navigation
Jump to search
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{anat|confcall|}} | {{anat|confcall|}} | ||
A partial defence to [[conference call ambush]], but one that will not excuse you from not having heard (for which, read, ''paid any attention to'') the dreary monologue that has gone on for the previous ten minutes, the conclusion to which is an open-ended question to you. “[[Sorry, I was on mute]]” buys time. | A partial defence to [[conference call ambush]], but one that will not excuse you from not having heard (for which, read, ''paid any attention to'') the dreary monologue that has gone on for the previous ten minutes, the conclusion to which is an open-ended question to you. | ||
“[[Sorry, I was on mute]]” buys only time. It is a shield, not a sword. | |||
But time won’t help you if you don’t have the foggiest idea what was being said in the first place. | But time won’t help you if you don’t have the foggiest idea what was being said in the first place. | ||
Revision as of 15:01, 24 November 2020
|
Conference Call Anatomy™
|
A partial defence to conference call ambush, but one that will not excuse you from not having heard (for which, read, paid any attention to) the dreary monologue that has gone on for the previous ten minutes, the conclusion to which is an open-ended question to you.
“Sorry, I was on mute” buys only time. It is a shield, not a sword.
But time won’t help you if you don’t have the foggiest idea what was being said in the first place.
A far better tactic is “sorry, I was having Skype trouble”, a modern-day equivalent to screwing up the newspaper in the receiver, announcing you have a bad connection, and hanging up on your mother-in-law.
The genuinely belligerent could try going crazy Ivan at the bottom of the hour.
See also
12/9/19