Bill W:
Chad G:
Story Idea #058 – TD EasyWeb’s Pre-Authorized Debit Form Scavenger Hunt: When the Help System Knows the Answer but the Navigation Doesn’t
The information existed. The document existed. TD’s own chatbot knew the working route. Yet a customer already logged into EasyWeb could search for a pre-authorized debit form, click the apparently relevant help link and get thrown back out to the public site for another login.
That makes this a useful little usability story rather than a banking catastrophe. We want to trace the full chain: authenticated customer, correct search topic, broken or circular route, chatbot workaround, and finally a document whose name and amount of explanatory material may not match the simple task the customer came to complete.
The broader question is how this happens inside a mature digital service. If one TD system knows that the document lives under the account’s Manage area, why doesn’t the search result take an authenticated customer there directly?
We will show the friction without exaggerating it. Small failures are worth examining precisely because companies and users often learn to tolerate them—and because dozens of little detours can become the actual experience of using an app or website.
Curious about the raw brainstorming behind this article?
