Composing

Sysadmins thrown into customer calls โ€“ how do you stay composed?

Iโ€™m composed by nature, but itโ€™s easy. When you donโ€™t know something (which is always, always gonna happen on customer calls), say: โ€œI donโ€™t know the answer to that, but will find out and get back to you.โ€

Easy. Super easy. And then research with the relevant team, FAQ or whatever and actually follow up.

A junior of mine was shadowing me on a customer call once and was flabbergasted that I said, โ€œI donโ€™t knowโ€ to half a dozen questions. However, when Iโ€™d tried letting her have a crack at answering on another customer call, she couldnโ€™t handle it and threw out tons of fabricated and incorrect responses that I later had to walk back. Or she otherwise flubbed them.

This is infinitely worse than just saying, โ€œI donโ€™t know.โ€

Because trust me, customers are always going to come up with some wild-ass crap ainโ€™t nobody ever thought of before.

Itโ€™s fine to research and answer later. I do it with nearly every customer call and I know a fucking lot about a lot.

Leave a Reply

Your email address will not be published. Required fields are marked *