Testers are said to be advocates for the customer, but when do most testers come face to
face with a real-life customer? I don’t mean internal stakeholders, but the people at the sharp end
of things, the ones actually using the software. Rarely, I find. Which is why it can be a SHOCK!
to be asked to participate in a customer support call. It’s an unusual situation, there’s pressure, the
customer is watching, something needs fixing, and there’s a deadline ... of yesterday. Gulp. But don’t
worry! You’re on the call because a colleague values your input. Perhaps you’re great at analysis, or
lateral thinking, or problem-solving. Maybe you have deep knowledge of your product, or the whole
ecosystem, or the historical angle. You could be there for questions, or answers, or honesty when you
don’t have either. These kinds of tools from your testing toolbox are valuable on support calls and in
this talk I’ll say how and why. I’ll also give an intro to customer support, talk about how to prepare for
calls, what to do during and after them, and - importantly - what you can take away personally, for
your product, and for your team.
From SoftTest 2018, http://softtest.ie/wp-content/uploads/2018/08/SoftTest_Programme_2018_20180829.pdf
2. @qahiccupps
James,
Will you be able to help with this one?
Sounds like a problem with installing and running.
The customer hasn't even started their project.
16. @qahiccupps
Who are Tech Support?
The face of your company to your
customer when things are not working.
Needs investigative, technical, domain,
social, and management skills.
And a great deal of strength.
23. @qahiccupps
James,
Will you be able to help with this one?
Sounds like a problem with installing and running.
The customer hasn't even started their project.
26. @qahiccupps
James,
Will you be able to help with this one?
Sounds like a problem with installing and running.
The customer hasn't even started their project.
28. @qahiccupps
CAN YOU AVOID THE CALL?
• Has this or any customer seen this issue before?
• Have we seen it ourselves?
• Have we missed anything so far?
29. @qahiccupps
I found a bug ticket with similar symptoms …
… but did you send a new license file?
Ah James, you're a genius ...
30. @qahiccupps
THOUGHT-PROVOKING QUESTIONS
• Can I describe the customer environment?
• Can I identify any questionable assumptions or inconsistencies?
• What might a solution look like?
35. @qahiccupps
Support Ticket
We did this …
We found …
Hypotheses are ...
Customer
conversation
Customer
conversation
Customer
conversation
Internal
conversation
Internal
conversation
Internal
conversation
38. @qahiccupps
Our interest is secondary to your need.
… but could you archive the VM?
We’d actually like to run this project on a
different architecture.
I understand that this is a rare bug that
you'd like to isolate [but I just want it]
working ASAP.
39. @qahiccupps
We’d actually like to run this project on a
different architecture.
I understand that this is a rare bug that
you'd like to isolate [but I just want it]
working ASAP.
You might want
to see this.
Yee-hah!
40. @qahiccupps
LOOK & SEE. HEAR & LISTEN.
• Signal vs noise
• Emotion vs fact
• Perception vs desire
45. @qahiccupps
… BUT IT’S DIFFERENT TOO
• Know there’s an issue
• Workaround vs diagnosis
• Limited visibility
46. @qahiccupps
I now have a working server … by
changing the license end date from 31st
October to 30th October.
I have no idea why.
Other things I tried included ...
47. @qahiccupps
ENDING A CALL
• What is a resolution?
• Be careful about language: resolution for who?
• Fix? Workaround? Questions for their side?