Why is this due diligence important?
Considering that Scotiabank and Quickbooks are different organizations, with different teams, managing different customer service offerings it is hard, at a cursory glance, to know exactly what the problem is. Being able to write a straightforward report, with visual examples, can help these outfits isolate where the problem is coming from.
Conversely, I could spend half a day on hold, get emotional with a customer support representative, fail to articulate the nuances of the problem to the teams themselves, and let an issue that could very well be experienced by many to fester and live on unresolved.
On the more technical side
Providing steps and visual examples can really help technical teams isolate the source of the problem. Is the 2FA a security service employed by the bank experiencing versioning issues with their API? Or could a model adjustment from the bank fail to run the callback script for dispatching the push notification...
It's not worth it for me, the reporter, to get into this much detail of course. It is important for the technical teams to know where the issue is happening, be able to ask the right questions, draft technical tickets with code snippets and technical resources attached, and ultimately assemble the team to produce the fix.
And perhaps this song has much more to do with isolating the code based correlates of software bugs in the absence of dutiful reproduction strategies...